Run the runtime, database, object storage, analytics, and SIP edge in your chosen region or VPS.
← Back to overview
Data residency and GDPR posture
Your calls stay in your infrastructure.
The call path, audio, transcripts, recordings, provider credentials, and webhook payloads are processed by the runtime you deploy. The Aywa Control Plane only needs licensing, release, health, and migration metadata — it never sits in the media path.
aywa runtime helps teams operate with data minimization, private deployment, retention controls, and redacted support workflows. It does not automatically certify a customer deployment as GDPR compliant.
The control plane does not sit in the media path for phone calls, recordings, or transcripts.
LLM, STT, TTS, SIP, storage, analytics, and webhook secrets belong to the customer deployment.
Use your own database, analytics sink, and S3-compatible storage policies for logs and artifacts.
Run production where your data already lives.
Install the runtime on your own infrastructure, then pair it with the control plane for licensing and updates only.