Security and privacy
Data security, explained clearly.
The app, database and sending server are hosted in France. This page explains what we store, how we protect it and what information may reach other providers, including AI providers.
- 01Gravelines, France
The sending server, at OVHcloud
- 02No contact lists
sent to AI providers for text or image generation
- 03Transfers explained
free text used by AI may reach the United States
045° Where data is stored
Our core infrastructure is in France.
The app, database, files and sending server are hosted by OVHcloud in France. Contact lists, contact records and shop orders are not sent to AI providers. AI features receive the text and aggregate data needed for the request, not your contact database.
AI and contact data
Your contact database stays on our servers. AI works with the content you submit.
We do not send contact lists, contact records, email addresses or order histories to AI providers as a dataset. Writing and translation features send editor text with personalisation placeholders unfilled; segments and reports use field definitions and aggregate figures. If you connect an external AI assistant through MCP, it can read the campaigns and templates you authorize; their content is sent to that assistant’s provider. MCP does not expose contact records or recipient lists. A user can still enter personal data in free text. Ordinary support requests may be assisted by AI and may contain personal data written in the message; requests in the privacy queue are not sent to AI.
090° How we send
We protect every customer’s reputation, including yours.
Our sending server handles email for many shops. Spam from one account can damage deliverability for everyone. That is why the same sending rules apply to every account.
- A dedicated sending server
We send from our own server, hosted by OVHcloud in France, rather than outsourcing delivery to a US email provider.
- Your domain, authenticated
We prepare SPF, DKIM and DMARC for your shop’s domain and regularly check that the records are still in place.
- DKIM keys in a vault
The private signing keys are kept in a separate secrets vault, never in the database.
- One-click unsubscribe
Every marketing email has one-click unsubscribe, following the RFC 8058 standard required by Gmail and Yahoo.
- Suppressed addresses
We stop sending to addresses with permanent delivery failures or spam complaints. Suppression remains in place even if you delete the contact.
- Daily limits based on sending performance
Every account starts with a low daily limit. It doubles while delivery and complaint rates remain healthy; paying more does not raise it.
When we stop sending
We assess an account’s rates after at least 200 emails, so a handful of early delivery failures does not distort the result.
| Signal | Limit stops growing above | Sending stops above |
|---|---|---|
| Spam complaints | 0.1% | 0.3%, the threshold Gmail and Yahoo publicly require |
| Hard-bounced addresses | 2% | 5%: the list needs cleaning |
- 01Encrypted connections
- 02Your shop’s keys, encrypted
- 03Audit log with limited retention
- 04Roles and two-factor sign-in
- 05API keys with separate permissions
- 06Limited support access
- 07Payments through Stripe
135° How we protect data
Safeguards for accounts, data and activity.
- Encrypted connections
The app and API use TLS for traffic between your device and the service.
- Your shop’s keys, encrypted
Your shop’s API keys and other access details are stored encrypted. Once you save them, we never show them again, not in the interface and not in logs.
- Audit log with limited retention
We record relevant actions, the actor, time and IP address. Entries cannot be changed in the app; personal identifiers can be redacted when a person is erased, and the log expires under its retention policy.
- Roles and two-factor sign-in
Permissions are checked for each action. Users can enable two-factor sign-in, and Azimea operators must use it.
- API keys with separate permissions
Each key gets only the permission it needs, has its own rate limit and can be revoked at any time.
- Limited support access
When our team needs to view an account for support, it uses a read-only session limited to one hour and recorded in the audit log.
- Payments through Stripe
You enter your card details directly with Stripe. They never reach Azimea’s servers.
180° Your customers’ rights
When a customer asks about their data, the tools are ready.
You are the data controller; we are the processor. Azimea gives you the tools to answer a GDPR request in minutes, not days.
-
Erasure on request (Art. 17). The person’s name, address and phone number disappear from every module. Orders remain as figures, with no person attached, and the next import does not bring them back.
-
Export (Arts. 15 and 20). Download everything we know about a contact, in one file.
-
The legal basis, for every contact. You know why you may email them: consent or existing customer, since when and from where.
-
Limited retention. After 400 days, sent emails lose the recipient’s address and their content. Only the numbers remain, for reports.
225° Service providers
The providers behind our service.
This table shows the hosting, payment and AI providers, the data involved and relevant locations. Stripe processes subscription payments, not your contact database. Providers used for the public site and support are described in the Privacy policy. We announce changes to providers that process your contacts on our behalf as set out in the DPA.
Read the Privacy policy| Provider | What for | What data it receives | Where |
|---|---|---|---|
| Cloudflare Turnstile | Security checks on account forms | IP address, browser/device signals and verification tokens; no account passwords or contact lists. | See Cloudflare’s Turnstile privacy terms. |
| OVHcloud | Hosting the app and the database, file storage (images, imports), the sending servers, and the keys that protect secrets | Your account data, your shop’s customer data and the content of the emails you send | France (EU) |
| Stripe Payments Europe | Subscription payments | Your company’s billing details. You enter your card directly with Stripe. | Ireland (billing entity; processing may occur elsewhere) |
| OpenAI | AI features and support assistance | Feature input, your shop’s public website text and aggregate figures; not contact lists or records. Free text and AI-assisted support requests may contain personal data entered by people. | United States; other regions may apply |
| Anthropic | AI features and support assistance | Feature input, your shop’s public website text and aggregate figures; not contact lists or records. Free text and AI-assisted support requests may contain personal data entered by people. | United States; other regions may apply |
Last updated: 31 October 2026.
Data processing agreement (DPA)
Read the public DPA, including technical measures, retention periods and transfer terms. Contact us for a copy completed with your company details.
Acceptable use policy
No bought, rented or scraped lists. No emails to people who have not given you consent or bought from you. No misleading subject lines and no hidden unsubscribe. Above 0.3% complaints, sending stops automatically.
Read the full policy315° Questions
Common questions about your data.
Have another question, or does your accountant or lawyer need something specific? Write to us at support@azimea.com.
Where is my customers’ data stored?
The app, database and sending server are at OVHcloud in France. Contact lists and records are not sent to AI providers. Text used by AI features and AI-assisted support may reach providers in the United States, and may contain personal data if someone enters it in free text.
Do I need to sign a DPA with you?
If the GDPR applies to the data you entrust to us, a DPA is required. Our DPA forms part of the accepted Terms without a separate signature. Read the full agreement from this page.
Can I email customers who did not tick the newsletter box?
The existing-customer exception may allow messages about your own similar products if the person could object when you collected the address and can easily opt out in every email (ePrivacy Directive, Art. 13(2)). Check the law in the countries where you send. Azimea records the basis you declare for each contact; you remain responsible for using the correct one.
Why might sending from my account be stopped?
If more than 0.3% of recipients mark your emails as spam, or more than 5% of addresses bounce them. The account then goes into quarantine and a person on our team restarts it, once we have talked to you. You will see the reason in the app.
Can I use Azimea if my company is outside the EU?
Yes. The core infrastructure remains in France regardless of where your company is based. Rules for collecting contacts and sending marketing email also depend on your country and your recipients’ countries. You decide the basis for sending; this page and the public documents show what we process and where.
Are you ISO 27001 or SOC 2 certified?
No. The measures we use are described here and in the technical annex of the public DPA. We do not claim certifications we do not hold.
000° Start today
Emails that bring orders, from a server in Europe.
14 days free, counted from the day you create your account. No card needed.