Email Policy & Intended SES Use

Domain: chongtian.me • Maintainer: Chongtian (Student, developer & hardware enthusiast)

Who I am

Hi! I'm Chongtian, a student who builds software, embedded electronics, and cloud projects for learning and personal use. I run small web apps and hobby services under the chongtian.me domain. I am currently based in Japan and operate my infrastructure across reputable providers (e.g., AWS, Google Cloud, Cloudflare) with security and responsible use as top priorities.

What I email about

  • Transactional notifications from my apps (sign‑in links, password resets, alerts, and receipts for donations or small purchases).
  • Account & security messages (new login alerts, 2FA, unusual activity notifications).
  • Opt‑in updates about open‑source projects, development logs, or new features. No advertising for third parties.

Who receives my emails

  • Only people who initiate a transaction with my apps/services (e.g., sign‑up, password reset, donation checkout).
  • Subscribers who have explicitly opted in via my site or app settings.
  • No purchased, scraped, or third‑party lists.

Planned sending domains & addresses

I will send from @chongtian.me. Initial mailboxes include:

These may expand as projects grow; each additional mailbox will follow the same policy.

Compliance & best practices

  • ✔ Opt‑in for all non‑transactional messages; no cold outreach.
  • ✔ One‑click unsubscribe and a visible List‑Unsubscribe header.
  • ✔ Accurate sender identity and valid reply‑to.
  • ✔ Bounce/complaint handling via SES feedback loops; automatic suppression.
  • ✔ Rate limits and content checks to protect reputation.
  • ✔ Logs & audits for consent, sends, and unsubscribes.

Authentication (DNS)

  • SPF: v=spf1 include:amazonses.com -all

  • DKIM: 2048‑bit keys generated by SES for chongtian.me

  • DMARC: v=DMARC1; p=quarantine; rua=mailto:[email protected]; pct=100 (tightened as reputation grows)

  • Custom MAIL FROM: e.g., mail.chongtian.me with aligned SPF.

DNS is managed with Cloudflare; records will be kept current and monitored.

Data & privacy

  • Minimal data collection (email, necessary metadata). No sale or sharing with third parties.
  • Purpose limitation: data is used only to deliver the selected service or update.
  • Retention: remove inactive subscribers; honor deletion requests promptly.
  • Security: TLS in transit; restricted access; secret rotation and least privilege on AWS.

Frequency & content

  • Transactional: only when you take an action.
  • Project updates: typically monthly or less unless you opt into a higher‑frequency channel.
  • No gambling, adult content, political fundraising, or misleading subjects.

Unsubscribe & contact

Every bulk or non‑transactional email contains an unsubscribe link and a working reply‑to address. For questions or removal requests, email [email protected].

A valid physical mailing address will appear in email footers to comply with applicable laws.

Sample email footer

© [[year]] Chongtian · chongtian.me
You received this because you signed up for updates or interacted with our app.
Unsubscribe: [[unsubscribe_link]]  |  Preferences: [[prefs_link]]
Questions? Reply to this email or write to us at: [[postal_address]]

Why Amazon SES?

SES offers reliable deliverability, authentication, and feedback loops for a small developer like me to send low‑volume, high‑quality mail responsibly. My goal is to use SES for transactional mail and a strictly opt‑in update list tied to my own projects and learning journey.

Change log

  • 2025‑11‑07: Initial policy published for SES review and public transparency.