Voice AI That Keeps Your Data Inside the EU

Inside the EU. Contact data and call records are processed and stored on EU-hosted infrastructure that Ainora runs, with no US-default routing. That means a European buyer does not have to explain a transatlantic data transfer to their data protection officer, and there is no reliance on adequacy decisions or Schrems-II transfer mechanisms for the default flow.

US-only voice-AI rivals default to US regions - for example us-east-1 - which pulls EU personal data across the Atlantic and invites Schrems-II and transfer-mechanism scrutiny. Ainora keeps the data in the EU by default instead. On top of that, the EU-native locality - per-country voice-call compliance and local language - is configured per market rather than one-size-fits-all, which is the differentiator that is hard to replicate from outside Europe.

Yes. Ainora signs a Data Processing Agreement and acts as your GDPR processor for your callers’ data. The managed-numbers and reseller model already does this on a per-client basis, so the DPA your DPO needs is a standard part of onboarding rather than a bespoke negotiation.

GDPR is the baseline of how the service is built, not a bolt-on. We process on a lawful basis - legitimate interest for B2B outbound with a documented balancing test and an honoured right to object, or consent where the situation requires it - honour data-subject rights, and keep records that prove the basis, the opt-out handling and the AI disclosures. This is general information, not legal advice - verify current rules for your use case.

Every call opens by disclosing that the caller is an AI. Article 50 of the EU AI Act requires that a person be informed they are interacting with an AI system, and it binds across the EU from 2 August 2026. In Ainora that disclosure is designed in from the start - it is not a setting a client can accidentally leave off.

The moment a prospect says stop, it is honoured on the spot, logged, and the contact is suppressed across both voice and text - with a record of who opted out and when. There is no re-dial, and the suppression follows the contact rather than living in a single channel. Where a national opt-out registry applies, lists are also scrubbed against it before dialling.

Where a market requires it, yes. Lists are checked against the relevant national opt-out registries before dialling - including the Portuguese DGC legal-person list, the Irish National Directory Database, and France’s consumer Bloctel - so a campaign starts clean in the markets that maintain such a register.

We keep contact data and call records in the EU on infrastructure we run, and we do not route to the US by default. What we will not do is make an absolute, situation-independent guarantee - lawful data handling depends on your configuration, your integrations and your jurisdiction. This is general information, not legal advice - confirm the specifics for your use case, and we are glad to walk your DPO through the exact setup on a call.