---
title: "AI voice agent data security in the Web-based AI Callcenter"
description: "AI voice agent data security built in: role-based access, audit logs, encryption, client separation, recording consent, retention and GDPR. See how it works."
url: https://aifortis.com/en/web-ai-callcenter/security/
language: en
last_updated: 2026-11-08
publisher: AI Fortis Ltd. (Sofia, Bulgaria)
---

# AI voice agent data security and privacy

Phone calls carry personal data. Security is designed into the platform from the first line, and it is run by the same team that built it — around the clock.

- GDPR by design
- 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 →](https://aifortis.com/en/how-we-prove-it/)

## What is built in

### Role-based access

People see and do only what their role allows: who may listen to recordings, who may change an agent, who may start a campaign.

### Audit logs

Actions in the platform are logged, so you can see who changed what and when.

### Encryption

Data is encrypted in transit and at rest; credentials to your systems are stored encrypted.

### Strict separation between clients

Each client's data, agents and calls are kept separate from every other client's.

### Recording consent and retention

Recording consent and retention are part of the platform's compliance controls, so recordings are kept only as long as your policy says.

### Do-not-call enforcement

Outbound campaigns respect your do-not-call list automatically.

### GDPR

Personal data is handled under the GDPR. AI Fortis is a company in Sofia, Bulgaria, in the EU.

### 24/7 operation

We monitor the platform and support it around the clock.

## Transparency towards callers

Callers have a right to know they are talking to a machine. Our agents say that they are an AI at the start of the call, in line with the transparency duty of the EU AI Act. Tell callers, too, if and why calls are recorded.

## Your part: decisions only you can make

- Which personal data the agent may ask for, and which it must never ask for.
- How long recordings and transcripts are kept.
- Who in your company may listen to recordings and export data.
- Which systems the agent may read from or write to, and with which permissions.
- Which calls must always go to a person.

## What to ask any cloud voice AI vendor

General guidance — use these questions with every provider, including us:

- Where is call data processed and stored, and under which law?
- Is the data used to train models for other customers? Get the answer in the contract.
- Which sub-processors are involved, and how are you informed of changes?
- How are credentials to your CRM or calendar stored, and can you revoke them at any time?
- What happens to your data when the contract ends — export format and deletion?
- How are security incidents reported to you, and how fast?

## When data must not leave your building

Some organisations cannot send call audio to any cloud. For them we offer the Enterprise AI Callcenter, which runs on your own servers so the data stays inside. You can also start in the cloud and move on-premises later.

## How we run the platform

- Encryption in transit and at rest, separation between clients and least-privilege access are defaults, not afterthoughts.
- Secrets and credentials are kept in encrypted storage, never in plain text, and access is limited to the people who need it.
- Administrative access to production is restricted, logged and auditable.
- Production systems are monitored, patched and load-tested.
- Recording consent, retention and deletion, and do-not-call enforcement are part of the platform, not separate tools.
- Specific security measures and responsibilities for your project are written into the contract and the data processing agreement.

## Reporting a security issue

If you believe you have found a vulnerability in our website or our products, write to us with the details. We ask for a reasonable opportunity to investigate and fix the issue before any public disclosure, and we acknowledge legitimate reports.

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.

## Frequently asked questions

### Are recordings and transcripts encrypted?

Yes. Data is encrypted in transit and at rest, and credentials to your systems are stored encrypted.

### Can other clients of the platform see our data?

No. The platform keeps strict separation between clients.

### Who in our company can listen to recordings?

You decide. Access is role-based, so only the roles you allow can open recordings or transcripts.

### Is the service GDPR-compliant?

Personal data is handled under the GDPR. We agree the data processing terms with you before go-live; ask us for the documents.

### Can we keep call data on our own servers instead?

Yes, with the on-premises Enterprise AI Callcenter, where the data never leaves your building.

### Do you sign NDAs and data processing agreements?

Yes. AI Fortis is a registered EU company; NDAs and data processing agreements are standard in our client work.

Who you are dealing with

## A registered EU company and the people who wrote the code

- **Company**: AI Fortis Ltd. „ЕЙ АЙ Фортис“ ООД
- **EIK**: 208238799
- **Seat**: Sofia, Bulgaria, EU
- **Team**: Kristian Kamenov, Bojidar Komarov, Martin Paskalev, Vladi Avramov, Mariela

- [Privacy policy](https://aifortis.com/en/privacy/)
- [Terms of use](https://aifortis.com/en/terms/)
- [Imprint](https://aifortis.com/en/imprint/)
- [Responsible disclosure](https://aifortis.com/en/responsible-disclosure/)

- **Named people**You talk to the engineers who built the product, not to a call script.
- **Proper paperwork**Contracts, NDAs and data-processing agreements as standard.
- **Clear pricing logic**We explain what drives the price before you sign, and confirm it in writing.
- **Your data, your rules**GDPR processes in every product. On-premises where data must stay inside.

### What happens after you book

1. **You send the request**Name and work e-mail are enough.
2. **We reply personally**Within one business day, with times for a call.
3. **Short call**We look at your case and answer your questions.
4. **Written proposal**What is included, what it costs, when it starts.

## Ask about Web-based AI Callcenter

Ask us your security questions — we answer them in writing.

- GDPR by design
- 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 →](https://aifortis.com/en/how-we-prove-it/)

---
Source: https://aifortis.com/en/web-ai-callcenter/security/
