GDPR by design
EU-only processing, data minimisation and purpose limitation are defaults, not options. A data processing agreement under Art. 28 is part of onboarding, with standard contractual clauses where a transfer cannot be avoided.
Email infrastructure for regulated finance
fmail is the sending platform for banks, brokers and payment institutions. EU-hosted, GDPR-first by design, and traceable from composition to delivery.
Platform
Regulated teams do not buy email volume — they buy defensibility. fmail is built around that: minimal data, explicit retention, and a record for everything that leaves the building.
EU-only processing, data minimisation and purpose limitation are defaults, not options. A data processing agreement under Art. 28 is part of onboarding, with standard contractual clauses where a transfer cannot be avoided.
Accepted, delivered, deferred, bounced — each event carries a timestamp, a message ID and the sending identity. Logs are exportable for internal audit, supervisors and incident reviews.
SPF, DKIM and DMARC enforcement, MTA-STS and TLS reporting are configured per domain before the first send. Reputation is monitored per sending identity, not averaged across customers.
SSO, role-based access, IP allowlists and scoped API keys. Configuration changes are logged, so access reviews and internal audits start from evidence rather than memory.
Use cases
Customer communication in financial services is mostly obligations. fmail is designed for messages that must arrive, must be attributable, and must be explainable to a supervisor.
Compliance model
The obligations below shape how the platform is operated. Each one comes with a document or a setting you can point your auditor at.
DPA with documented instructions, sub-processor list and change notification.
Processing activities are documented and available for your own Art. 30 register.
Encryption in transit and at rest, least-privilege access, enforced TLS.
Defined escalation path so you can meet the 72-hour notification window.
Export and erasure tooling for message metadata, plus a contact for DSARs.
EU processing by default; SCCs only where a transfer is unavoidable.
Security
Email is where customer trust is most visible. Access is scoped, transport is encrypted, and nothing is retained longer than the agreed window.
DKIM keys, SPF and a DMARC policy are published and checked before activation.
REST API or SMTP relay, with keys scoped to the environment that needs them.
Each message returns an ID; delivery events stay queryable for the retention window.
FAQ
Storage of message bodies is a configuration decision, not a default. Delivery metadata — recipient domain, timestamps, status events — is retained so a delivery can be evidenced later. The retention window is agreed in the DPA.
Yes. fmail acts as a processor for the personal data contained in the messages you send, and as a controller only for the account data needed to run the service. A DPA is part of onboarding.
Within the EU by default. If a sub-processor or support path involves a third country, it is disclosed in advance and covered by standard contractual clauses.
Yes. You keep the domain and its reputation; fmail publishes and enforces the authentication records. Moving away later does not cost you the domain.
Both. Transactional systems usually take the REST API, while legacy core banking applications tend to prefer the SMTP relay. Access controls apply equally to both paths.
The current list is part of the DPA. Changes are notified before they take effect, with a documented objection path.
One domain, one use case, reviewed by your compliance team before go-live.