What procurement asks, answered in one place
Who processes your data, where it's stored, how long it's kept, and where to check whether the service is up. Each answer links to the page or document it comes from.
GDPR and data residency
Data flow, DPA and sub-processor policy
Security practices
Keys, webhooks, access and infrastructure
System status
Live API health, also as JSON
Privacy policy
What Envello collects about its own customers
Terms of service
The agreement the DPA sits under
Acceptable use
What can't be sent through Envello
Who processes your data
The sub-processors named in Envello's public pages and DPA. The complete current list is available on request, and active customers hear about changes by email 30 days ahead.
| Company | Purpose | Data | Location |
|---|---|---|---|
| Hetzner Online GmbH | Hosting for the API, dashboard, database and job queue | Account data, hashed API keys, send and event logs, suppression list | Germany |
| Amazon Web Services (Amazon SES) | Delivering email to recipients' mail servers and reporting delivery events | The message and its recipients, for as long as delivery takes | eu-central-1 (Frankfurt) |
| Stripe | Payments, invoices and EU VAT (Stripe Tax) | Billing contact and payment details. No message data | EU-based processor, per the privacy policy |
Request the full list from [email protected].
Every add, removal and change, dated
The public record of changes to the list above, with the reason for each. Subscribe to the feed to get them without checking this page. Active customers still get the 30-day email notice.
No changes recorded in this log yet. It starts with the list as published above, and every change from here on is added with its date and reason.
RSS feed: /trust/subprocessors/feed.xml
Where each kind of data lives
What each store holds and how long it's kept. The same map is published as JSON for your own tooling.
| Store | Holds | Retention |
|---|---|---|
| Postgres (EU) | Account data, API keys (SHA-256 hashed), send and event logs, suppression list | Logs: 7 days on Free, 90 days on Pro, 7 to 365 days on Scale, then deleted by a scheduled job. Account data: life of the account plus statutory periods |
| Object storage (EU) | Raw MIME content for messages older than 30 days | Not published separately yet |
| Amazon SES (eu-central-1) | Nothing at rest on our side beyond what delivery and reporting need | Not kept by Envello there |
| Application logs | Request metadata only. Recipient addresses are not written to application logs | Not published separately yet |
Machine-readable: /trust/data-map.json
Check it live
The status page reads the API's health check on every request, and the same data is available as status.json for monitors. Past incidents are listed below. Changes to the product are in the changelog.
Past incidents
Incidents that affected the API, sending or customer data, with their impact and a link to the post-mortem once it's written.
Nothing has been published in this log yet. When an incident is written up, it's listed here with its dates, impact and post-mortem.
Questions security and legal teams ask first
Do you sign a DPA, and on which plans?+
Yes, on every plan including Free. It's generated from your account details in the dashboard, with no sales call, and covers subject matter, duration, location, sub-processors, security, data subject rights and deletion.
Where is personal data processed?+
In the EU. The API, database and logs run on Hetzner infrastructure in Germany, and email is delivered through Amazon SES in eu-central-1 (Frankfurt). Data leaves the EU only if you configure something that sends it there, such as a webhook endpoint outside the EU.
How do you handle sub-processor changes?+
Active customers are told by email 30 days before a sub-processor is added or replaced. A sub-processor outside the EEA is bound by the EU Standard Contractual Clauses. The full current list is available on request.
How long do you keep data, and is deletion real?+
Message logs are kept for your plan's window (7 days on Free, 90 on Pro, 7 to 365 on Scale) and then deleted by a scheduled job, not soft-deleted.
How is data protected in transit and at rest?+
TLS on every connection to the API and dashboard. API keys are stored as SHA-256 hashes, so a key can't be read back. Webhooks are signed with HMAC-SHA256 so you can verify they came from Envello.
How do you answer data subject requests?+
Write to [email protected]. Requests about your own account are answered within 30 days, and the DPA commits Envello to help you answer requests from your recipients.
Will you fill in our security questionnaire?+
Yes, before you sign up. Send it to [email protected].
Do you sign a DPA, and on which plans? DPA details
Where is personal data processed? Data flow
How long do you keep data, and is deletion real? Retention in the privacy policy
How is data protected in transit and at rest? Security practices