GDPR-compliant AI call centre: data stays on your premises

AI Fortis is installed on your servers. Voice, recordings, transcripts and contacts are processed and stored there — not in a voice-AI vendor's cloud.

Illustration: Illustration: on-premises AI call centre — the data stays inside your premises YOUR PREMISES — DATA NEVER LEAVES AI Fortis GPU server speech recognition · voice · hub Language model local (optional) SIP trunk / PBX Your CRM / ERP Caller your provider (API) Illustration
With your LLM provider via API only the text of the turns leaves; with a local LLM, nothing does.

Where the data goes

DataProcessed whereStored where
Call audioYour server (speech recognition and voice)Your server (recordings)
Transcripts and extracted fieldsYour serverYour server, with retention
Contacts and campaignsYour serverYour own database
Text of the turns sent to the language modelYour provider via API — or your server with a local LLMPer your provider contract — or nowhere outside your premises
Phone trafficYour SIP provider / PBX—

Security architecture

Network

Runs inside your network. Outbound connections only to your SIP provider and, if chosen, your LLM provider.

Identity

Strong password hashing, server-side sessions, CSRF protection, two-factor sign-in, login throttling.

Data

Local database with client isolation; recordings with retention per client; encrypted secrets for your systems.

Installation

Signed licence bound to your hardware; voice models encrypted for the specific machine; signed integrity manifest of shipped files.

Built-in controls

  • AI disclosure at the start of the call (EU AI Act, Art. 50) and recording notice — on by default.
  • Recording retention per client (default 90 days) with automatic deletion.
  • Do-not-call list, per-contact consent and allowed calling hours — checked at every dial.
  • Roles and users per client; client portals that only see their own data.
  • Audit log of platform actions.
  • Access to and export of your data at any time — even if the licence lapses.

Legal framework we design for

GDPR

Processing on your own servers simplifies your processor map. Health data is a special category (Art. 9) — one more reason for recordings to stay inside.

EU AI Act, Art. 50

People must know they are talking to an AI. The agent says so at the start of every call.

ePrivacy / national rules

Marketing calls usually need prior consent (in Bulgaria: Electronic Communications Act, Art. 261(1)). Service calls (reminders, requested call-backs) are a different case — confirm with your counsel.

Certifications

We do not claim certifications we do not hold. If your process requires a specific assessment (e.g. vendor ISO 27001), let us discuss it in discovery.

Free, no commitment

Request the security pack

Send us your security questions or your questionnaire. An engineer answers in writing for your deployment: architecture, data flows, access control, logging and GDPR processing.

  • Written answers from an engineer
  • Data flows and where the data is stored
  • Access control, audit logs and GDPR details

Your details are used only to answer this request.

Questions from security teams

Is internet access required?

For telephony, only to your SIP provider. With a fully local language model the platform runs without internet access; the licence has a grace period for offline operation.

Who can access the recordings?

Only the users you give a role in the platform. We have no access to your server unless you grant it for support.

Can we delete a specific person's data?

Retention deletes recordings automatically; the data is exported and managed entirely on your side.

See it working on your own scenario

Book a 20-minute call, listen to the agent, or let us build a free sample agent for one of your call types. No commitment.

  • GDPR by design
  • Runs on your own servers
  • 24/7 operation and support
  • A team of 5 in Sofia, EU

Already running in production at organisations in Bulgaria — names under NDA.

How we prove it →