Reliability and support
What letr.dev commits to, how the status page measures it and where your data lives.
Commitments
| Promise | Value |
|---|---|
| Going live | On payment; review within 1 Swiss business day. Declined: full refund at once, with the reason. |
| Support | First answer by email within 1 Swiss business day. |
| Sending stopped or paused | Answered the same business day, within 4 business hours (Monday to Friday, 08:00 to 18:00 Swiss time). |
| Incidents | Status page updated within 30 minutes between 07:00 and 22:00 Swiss time; a note afterwards for anything over 30 minutes. |
| Availability | Objective 99.9 % a month, measured publicly by Starwatch on status.letr.dev. No service credits. |
| Cancel | Monthly, effective at the end of the period; data deleted 30 days after. |
| Over the plan | Mail keeps going: CHF 0.50 per started 1'000 over 10'000, up to a ceiling you set (10'000 or 25'000; 25'000 by default). Emails at 80 % and 100 % of the plan and 90 % of the ceiling. |
Write to [email protected]; the people who build letr.dev answer. Report spam or other abuse sent through letr.dev to [email protected]; mail operators reach us at [email protected].
Status page
status.letr.dev runs on Starwatch and watches two public endpoints:
GET /meta/health: the API answers and reaches its database.GET /meta/health/pipeline: the oldest email waiting for handoff is younger than 5 minutes, the mail server accepts connections, and a test email letr.dev sends every 5 minutes to its own mailbox at an external provider arrived within the last 15 minutes.
Where your data lives
Email content and message logs are stored and processed on letr.dev's servers in Germany (Hetzner), with encrypted database backups at Contabo in the EU. Datadog (USA) receives the servers' health metrics, the web server's error log with client IP addresses and requested URLs, which can contain email addresses, and the mail server's operational log with email addresses masked. The content is kept encrypted with the email for as long as the email is in your history (30 days, 365 with the add-on) and deleted with it; a recipient erasure deletes the content of every email addressed to the erased recipient or naming it in its subject or tags at once. A scheduled email that only names the address in its subject or tags is still sent at its time, and letr.dev's queue keeps it until then. letr.dev's queue keeps it at most 3 days after the send time, and a scheduled email (up to 7 days ahead) keeps its content from the request until its send time. If the receiving mail server defers the email, the mail server's queue keeps it at most 3 more days after the hand-off. Sender, recipients, subject, tags and delivery events are shown for 30 days and deleted after 32; with the 365-day history add-on they are shown for 365 days and deleted after 367. Backups keep all of this for up to 52 weeks after it is deleted. Cloudflare (USA) carries the website and API traffic in transit, including the emails sent through the API, Stripe handles payment and WorkOS handles the dashboard sign-in. Google Workspace holds letr.dev's mailboxes, so support requests and abuse reports, which can contain email addresses or content, are processed by Google (USA and worldwide). The privacy policy names the controllers, and the list of sub-processors names each provider with its location and transfer basis.