Email on infrastructure you already qualify

Why regulated organisations self-host

A hosted marketing platform adds a sub-processor to your register: contact data, reading habits and campaign content sit on servers your organisation did not qualify, under contracts you cannot inspect at code level.

Self-hosted, the software runs where your other qualified systems already run. The database is yours, each workspace is isolated, and the code can be read by your own teams before it is deployed.

Health data: what certification does and does not cover

In France, hosting personal health data requires an HDS-certified host. That certification attaches to the hosting provider and its perimeter — not to a piece of software.

Notifuse claims no HDS certification, and no certification is promised for the software itself. If your sending involves health data, deploy Notifuse on your own certified infrastructure, or with a host that holds the required certification for the data you process. Qualifying the deployment remains your organisation's responsibility, as it does for the rest of your stack.

The same logic applies in other regimes: we make no HIPAA, ISO 27001 or other attestation claim for Notifuse. What we provide is software your organisation can qualify inside its own compliance perimeter — and keep email content free of medical information wherever a simple notification is enough.

What your reviewers can verify

• Access control. Single sign-on through your identity provider, granular permissions per workspace, and scoped API keys.
• Audit logs. Admin actions are recorded, so who changed what — templates, settings, permissions — can be reviewed after the fact.
• The code. The source is public, and each release becomes AGPL-3.0 after four years. Your teams can read what they deploy.
• The security process. Private vulnerability reports, a reply within three business days, first assessment within ten, fixes in the latest release with a public advisory. Details on our security page.
• No phone-home. Licence keys are checked locally. Nothing about your installation is sent to us.
• The licence. What needs a key, what never will, and what happens without one — written, dated and versioned on our licence page.

An example

Illustrative scenario — not a customer case.

A group of clinics deploys Notifuse on the group's certified hosting. Each clinic has its own workspace, contacts and domain; appointment reminders carry no medical content, only a time and a link to the patient portal. Staff sign in through the group's identity provider, and admin actions stay in the audit logs for the compliance team to review.

When the group adds entities, it moves to a Custom licence rather than changing tools.

How purchasing works

Standard licences are bought online. Larger deployments — several entities, more than fifteen workspaces, specific requirements — use a Custom licence: quoted per deployment, with purchase-order purchasing. Paid licences include private email support in English and French, Monday to Friday.