Email infrastructure for regulated finance

Email that survives
an audit.

fmail is the sending platform for banks, brokers and payment institutions. EU-hosted, GDPR-first by design, and traceable from composition to delivery.

  • EU data residency
  • Art. 28 DPA
  • SPF · DKIM · DMARC
Built for teams under supervision
  • Banking
  • Brokerage
  • Payments
  • Fund management
  • Insurance

Platform

Compliance is the architecture, not a policy PDF.

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.

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.

Every message leaves a trail

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.

Deliverability as a baseline

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.

Fits your change process

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

The mail regulated teams actually send.

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.

  • KYC, AML and re-verification notices
  • Account statements and annual reports
  • Payment, settlement and custody confirmations
  • Regulatory disclosures and client consent changes
  • Transactional authentication codes
  • Onboarding and contract correspondence

Compliance model

Written down, not assumed.

The obligations below shape how the platform is operated. Each one comes with a document or a setting you can point your auditor at.

Art. 28

Processor agreement

DPA with documented instructions, sub-processor list and change notification.

Art. 30

Records of processing

Processing activities are documented and available for your own Art. 30 register.

Art. 32

Technical measures

Encryption in transit and at rest, least-privilege access, enforced TLS.

Art. 33

Breach notification

Defined escalation path so you can meet the 72-hour notification window.

Art. 15–20

Data subject rights

Export and erasure tooling for message metadata, plus a contact for DSARs.

Art. 44

Transfers

EU processing by default; SCCs only where a transfer is unavoidable.

Security

Narrow surface, explicit controls.

Email is where customer trust is most visible. Access is scoped, transport is encrypted, and nothing is retained longer than the agreed window.

  • TLS 1.2+ enforced on every connection
  • Encryption at rest for stored metadata
  • Scoped API keys, rotation and revocation
  • SSO and role-based access control
  • Per-domain reputation isolation
01

Verify the domain

DKIM keys, SPF and a DMARC policy are published and checked before activation.

02

Connect your system

REST API or SMTP relay, with keys scoped to the environment that needs them.

03

Send with evidence

Each message returns an ID; delivery events stay queryable for the retention window.

FAQ

The questions procurement asks first.

Do you store the content of our emails?

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.

Are you a processor under Art. 28 GDPR?

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.

Where is data processed?

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.

Can we keep our own sending domains?

Yes. You keep the domain and its reputation; fmail publishes and enforces the authentication records. Moving away later does not cost you the domain.

Is there an SMTP option, or only an API?

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.

How do sub-processor changes reach us?

The current list is part of the DPA. Changes are notified before they take effect, with a documented objection path.

Start with a scoped pilot.

One domain, one use case, reviewed by your compliance team before go-live.

Talk to us