EU Hosting & Data Residency

1. EU-hosted by default

Loryvoice rendering, processing, and storage run in European Union regions by default. That covers the data that matters most in this product: source recordings, finished renders, voice models, and the consent receipts attached to them. EU hosting is our standard configuration, not a premium add-on.

2. Where processing happens

Application infrastructure, the rendering pipeline, and primary data storage operate in EU data-centre regions. Backups remain within the EU. Content delivery uses an edge network, so static site assets are cached at edge locations close to visitors; customer content is served from EU origins.

3. What leaves the EU

Customer content, voice models, and consent receipts are processed and stored in the EU and do not leave it by default.

Website analytics data — the analytics events, session recordings, heatmap data, survey answers, and error reports described in section 2 of our Privacy Policy — is also stored in the European Union: the analytics project runs on PostHog's EU Cloud in Frankfurt, Germany. It is collected only from website visitors who have accepted analytics, it contains no customer content and no voice data, and it does not travel from a visitor's browser to PostHog at all — it goes to loryvoice.com and our own server forwards it.

The cases we publicly name today where personal data can be touched outside the EU, described precisely:

• Cloudflare operates a global edge network for content delivery, security filtering, and Turnstile anti-bot verification. Connection metadata (such as IP addresses and security signals) may transit edge locations worldwide; customer content is served from EU origins.
• Resend delivers our transactional email. The data in those emails — names, email addresses, and the content of form submissions and service notices — is processed by Resend, a US-based provider.
• PostHog processes our website analytics. The data comes to rest in the EU, so this is not a residency exception, but PostHog Inc. is a US-incorporated company: remote administrative and support access to the EU-region project from outside the EU is possible. That access, rather than the storage location, is what the transfer basis covers.

All three operate under data processing agreements incorporating the European Commission's Standard Contractual Clauses for any transfer outside the EU. Any other subprocessor that processes personal data outside the EU operates under the same standard — SCCs, with supplementary measures where required; the full subprocessor list is available on request from privacy@loryvoice.com.

4. Subprocessors

The subprocessors we publicly name today are listed below. The full current list, including the countries each operates from, is available on request from privacy@loryvoice.com.

PostHog is engaged only for website visitors who accept analytics: if a visitor declines, no data about their visit reaches it, and no customer content, voice model, or consent receipt is sent to it in any case. We intend to run that workload on infrastructure we host ourselves rather than on a third-party cloud; we are not putting a date on that, and this page will say so when it changes.

5. Data-residency commitments

For customers whose procurement requires it, we commit contractually to EU data residency for stored customer content, voice models, and consent receipts, with the exact scope defined in the data processing agreement. We will inform contracted customers before adding or replacing a subprocessor that touches their data, and before any change that would move their content processing outside the EU — which would require their agreement.

6. Security measures

Data is encrypted in transit (TLS) and at rest. Access to customer content is restricted to personnel who need it to operate the service, gated by role-based access controls, and logged. Public forms sit behind layered anti-abuse controls (Turnstile verification and rate limiting). Full technical and organisational measures are documented in the data processing agreement.

7. Certifications

We claim no third-party certifications at this time. What this page states is what we operate — we would rather be precise about that than decorate the page with badges. When an independent audit or certification is completed, it will be listed here.

8. GDPR posture

Loryvoice processes personal data under the GDPR: as controller for the data described in our Privacy Policy, and as processor for the personal data inside customer content — including speakers' voices — under a data processing agreement available to every contracted customer. Voice cloning runs only on the speaker's signed, explicit consent, and the consent receipt travels with every render, on every plan.

9. Contact

Security and residency questions from procurement teams: privacy@loryvoice.com. We answer vendor-assessment questionnaires for prospective Enterprise customers on request.