Amazon SES use case

Summary for the SES request form

Mail type: Transactional.

Website URL: Use the final production URL of this site.

Sending domain: timeplanpush.com.

Additional contacts: support@timeplanpush.com, abuse@timeplanpush.com, privacy@timeplanpush.com, security@timeplanpush.com.

Use case: Time Plan sends account verification, password reset, workspace invitation, user-configured task reminder, billing, and service notification emails for a planning and workspace productivity application.

Recipient source: Recipients are registered users, users who request account actions, workspace invitees entered by authenticated workspace administrators, or users who have enabled reminder email in product settings.

List policy: Time Plan does not buy, rent, scrape, share, or import third-party email lists. It does not send cold outreach.

Privacy policy: Time Plan does not collect data for advertising, profiling, resale, lead generation, or third-party marketing. It processes only the minimum information needed for account, security, reminder, billing, support, and email-delivery workflows.

Bounce and complaint process: SES event publishing, CloudWatch alarms, and suppression lists will be used. Hard bounces, complaints, and unsubscribe events stop future non-essential sending to the address.

Acknowledgement: Time Plan sends only to recipients who requested the workflow, have an account relationship, were invited by an authenticated workspace administrator, or enabled reminders. Bounce and complaint notifications are processed as stop-sending signals.

Message inventory

Transactional messages only

Email	Trigger	Recipient relationship	Sender and reply-to	Suppression rule
Email verification	User registers or requests a verification resend.	The user typed the address into Time Plan and requested account creation.	From security@timeplanpush.com; Reply-To support@timeplanpush.com.	Rate-limited. Stop if hard bounce, complaint, or account deletion.
Password reset	User requests a reset from the login or recovery screen.	The address belongs to an existing account and the user requested recovery.	From security@timeplanpush.com; Reply-To security@timeplanpush.com.	Rate-limited. Token expires. Stop if hard bounce or complaint.
Workspace invite	Workspace owner/admin invites a member.	Recipient is invited into a specific workspace by an authenticated user with invite permission.	From support@timeplanpush.com; Reply-To support@timeplanpush.com.	Invite can be revoked or ignored. Complaints suppress future invites.
Task reminder	User enables email reminder rules for a task, workspace, or notification setting.	Reminder email is controlled by product notification preferences.	From support@timeplanpush.com; Reply-To support@timeplanpush.com.	User can disable email globally, by workspace, by task, or by topic. Optional topics include unsubscribe controls.
Billing notice	Subscription, invoice, plan, payment, coupon, or billing event.	Registered account owner or billing contact.	From billing@timeplanpush.com; Reply-To billing@timeplanpush.com.	Service-critical notices remain minimal; non-critical billing notices honor preferences and suppression.
Service and support notice	Support response, account notice, security notice, or service-impacting operational update.	Registered account owner, affected workspace member, or user who contacted support.	From support@timeplanpush.com; Reply-To support@timeplanpush.com.	Only sent when needed for account support or service operation. Complaints suppress non-essential mail.

Reviewer evidence

How Time Plan addresses SES review concerns

Review concern	Time Plan control	Public evidence
Is this transactional?	All email is tied to account actions, security, invitations, billing, service notices, support, or user-configured reminders.	This SES use case page and the message inventory above.
How are recipients obtained?	Recipients enter their own address, request recovery, receive an invite from an authenticated workspace admin, enable reminders, or contact support.	Product page recipient-source section and Anti-spam Policy.
Are purchased or scraped lists used?	No purchased, rented, scraped, harvested, shared, imported, or third-party lists. No cold outreach.	Privacy Policy, Anti-spam Policy, and Terms of Service.
How are complaints handled?	Complaints are immediate stop-sending signals, added to suppression controls, and investigated through abuse@timeplanpush.com.	Contact page and Anti-spam Policy.
How are bounces handled?	Hard bounces suppress future non-essential sending. Soft bounces are retried conservatively and stopped after repeated failure.	This SES use case page and deployment checklist.
Can recipients opt out?	Optional reminders and digest-style messages include unsubscribe or preference controls. Account/security emails are only user-triggered or service-critical.	Privacy Policy and Anti-spam Policy.

Required controls

SES production checklist

Verify the timeplanpush.com domain identity in the selected AWS Region before submitting the request.
Enable Easy DKIM with 2048-bit signing where supported and wait for DKIM status to become successful.
Publish SPF and custom MAIL FROM DNS records if a custom MAIL FROM subdomain is used.
Publish a DMARC record for timeplanpush.com and monitor aggregate reports.
Serve the public website, Privacy Policy, Terms, Anti-spam Policy, and Contact page over HTTPS.

Create an SES configuration set named timeplan-transactional for all application mail.
Publish delivery, bounce, complaint, reject, and unsubscribe events to monitoring destinations.
Enable account-level suppression for BOUNCE and COMPLAINT.
Add CloudWatch alarms for bounce, complaint, reject, and delivery anomalies.
Keep abuse@timeplanpush.com, security@timeplanpush.com, privacy@timeplanpush.com, and support@timeplanpush.com visible on the public website.

Operational limits

Sending controls before production scale

Conservative launch

Start with account verification, password reset, workspace invitations, billing, and support notices. Add optional reminder email gradually after reputation metrics remain clean.

Authentication rate limits

Limit verification and password reset resends per user, email address, IP-derived signal, and time window. Tokens expire and cannot be reused.

Invitation safeguards

Workspace invitations require authenticated users with invite permission. Repeated invites to the same address are limited and can be revoked.

No bulk import

Time Plan does not support CSV list uploads, purchased list imports, scraped list imports, lead-generation campaigns, or one-to-many promotional campaigns through SES.

Copy for AWS support

Production access request text

The following text can be pasted into the AWS SES production access request.

We are requesting Amazon SES production access for Time Plan, a workspace-based task planning and reminder application.

Mail type: TRANSACTIONAL.

Website URL: https://timeplanpush.com/

Sending domain: timeplanpush.com

Additional contacts: support@timeplanpush.com, abuse@timeplanpush.com, privacy@timeplanpush.com, security@timeplanpush.com

We will send account verification, password reset, workspace invitation, user-configured task reminder, billing, service notification, security, and support emails. Recipients are obtained only through first-party product actions: users registering their own accounts, users requesting password resets, authenticated workspace administrators inviting members, registered users enabling email reminders in notification settings, account owners receiving billing or service notices, and users contacting support.

We do not collect data for advertising, behavioral profiling, resale, lead generation, cold outreach, or third-party marketing. We do not buy, rent, scrape, share, or import third-party email lists. Email reminders are controlled by user preferences and can be disabled globally, per workspace, and per task. Optional reminder or digest topics will include unsubscribe controls and List-Unsubscribe support where applicable.

User content is treated as private. Data is encrypted in transit and at rest, passwords are stored only as secure hashes, and operational access is restricted, logged, and limited to the minimum needed for security, reliability, legal compliance, or user-authorized support.

Before production sending, we will verify the timeplanpush.com domain identity in the selected SES Region, enable Easy DKIM, publish SPF/custom MAIL FROM records where applicable, publish DMARC, use a dedicated SES configuration set, publish delivery/bounce/complaint/reject/unsubscribe events, monitor CloudWatch reputation metrics, enable account-level suppression for BOUNCE and COMPLAINT, and suppress hard-bounced or complained addresses immediately.

Optional AWS CLI request

Use the selected Region and only the four allowed additional contact addresses.

aws sesv2 put-account-details \
  --production-access-enabled \
  --mail-type TRANSACTIONAL \
  --website-url https://timeplanpush.com/ \
  --additional-contact-email-addresses support@timeplanpush.com abuse@timeplanpush.com privacy@timeplanpush.com security@timeplanpush.com \
  --contact-language EN

Operational references

This site follows public Amazon SES production access and sending reputation guidance. Keep the implementation aligned with the latest AWS documentation before submitting the request.