Privacy

How we protect your data

One page, no legal language. Everything here is something the platform actually does. Where we do not do something, it says so — a page like this is only worth reading if the gaps are in it too.

Last checked against the platform on 16 October 2026. The full agreement a client signs is the Data Processing Agreement; ask us for it.

Whose data this is

If you are our client, the people being called are your customers and prospects. You decide who is called and why; we run the machinery that calls them, on your instructions. In the language of the law, you are the controller and we are the processor.

One consequence worth knowing up front
Whether you may call a particular person is your decision. Before a campaign launches, the platform shows you what the law of each lead's country says — the rule, the penalty with real figures, the statute it comes from, and which rows of your list it applies to. You tick "I understand, launch anyway", and that acknowledgement is recorded with your name, the time, and a copy of exactly what was on the screen.
We warn. You decide. Both are recorded.

What we hold

Contact detailsname, phone number, email, company
Call recordswhen, how long, which number, which direction, the outcome
Recordingsthe audio of the call
Transcripts and summariesevery word, and a short summary
Whatever you uploadedyour list is yours. We do not add to it or inspect it
Consent recordswhere permission to call came from

We never sell it, share it with another client, use it to train a model of our own, or use it for anything except running the service you asked for.

How long we keep it

WhatKept for
Call recordings90 days
Transcripts and summaries365 days
Call records (time, length, cost)while you are a client, then as long as accounting rules require
Your leads and listsuntil you delete them. They are yours
Do-not-call entriesfor ever — forgetting that somebody asked not to be called is not a feature

A job runs every night and deletes whatever is past its time, including deleting the recordings held at our telephone provider, and keeps a record of what it deleted. If your contract sets different periods, yours are used instead of these.

Where it is, and who else touches it

The platform runs on Amazon Web Services in Frankfurt, Germany. Four other companies are involved, because the service cannot work without them.

WhoWhat forWhere
Twiliothe telephone network, and they hold the recordingsUS / EU
OpenAIthe agent's side of the conversationUnited States
ElevenLabsthe agent's voiceUnited States
Deepgramturning speech into textUnited States
Data leaves the EU
The conversation goes to three companies in the United States. There is no version of this service that does not, and we would rather say so than leave it out. We will tell you before we add another one.

What we actually do to keep it safe

Encrypted, at rest and in transit

The database is encrypted, and so is every backup Amazon takes of it. Your browser reaches us over modern encryption only — the old, broken versions are refused outright — and so does every connection between us and the companies above.

Our staff see only what their job needs

Our support people see no costs, no margins and no billing. Our billing people see no calls, no recordings and no transcripts. These are not hidden buttons: the server refuses the request before the data is sent.

Two-factor login, compulsory for us

Every Maiss Automation staff account must use an authenticator app, and it cannot be switched off. You can require the same of your own users, and we would recommend it.

Every recording played is recorded

Each time anybody plays a recording, opens a transcript or exports a list, we log who, which call, when, and from where. Ask us who in our company has heard a particular call and we can tell you.

The do-not-call list is absolute

Checked before every single call, with no setting that skips it. An entry is never deleted — taking a number off needs a written reason and is recorded against the person who did it.

Password guessing is slowed, then stopped

Repeated wrong passwords are deliberately delayed and then the account is locked, and its owner is emailed about it — so if it was not them, they find out the same day.

Said plainly

What we do not do

A page like this is usually a list of reassurances. These are the things we would want to know if we were you.

The server's own disk is not encrypted The database is, and so are its backups. The machine that runs the application is not. Fixing it needs the machine stopped, and it is planned work rather than done work.
There are no off-site backups The copies that exist are Amazon's own, in the same region, plus one on a company laptop. We do not yet have a plan for losing the whole region.
It is one server There is no automatic failover. If it stops, calls stop until somebody starts it again.
The telephone network is not encrypted The leg between the carrier and the handset is the public phone network. No voice platform can promise otherwise.
A transcript can hold what nobody meant to collect A caller can say anything, including something about their health. We have no field for it and never ask — but a transcript records what was said. Our answer is the retention period: deleted a year after the call, and sooner if you ask.

If somebody asks what we hold about them

Tell us and we will do it. It works across every one of our clients at once, because somebody who rings up does not know which of our clients called them.

"What do you have about me?"

We produce a file with every call, recording, transcript, summary, lead record, campaign entry and email we hold about them, with the client each one belongs to named against it. Normally within 5 working days.

"Delete it."

We erase them. It takes a typed confirmation and a written reason, and it is specific about what goes and what stays.

Deleted

The recordings — here and at our telephone provider, where they cannot be recovered. The transcripts. The summaries. The personalised greeting audio, which is a recording of their own name being spoken. Their lead record. Their campaign entries. Our record of the emails we sent them.

Kept, and why

Their do-not-call entry. It is the only thing stopping us ringing them again. Deleting it to honour "delete everything about me" would mean the next campaign dials the person who asked us not to.

The call record, with the name and number replaced by [erased]. It is what an invoice was built from: how long, for which client, on what day. Keeping accounting records is a legal requirement; keeping the caller's name in them is not.

The money records, unchanged — because there is nothing of the person in them. A ledger row reads "Outbound call — 2 minutes at $0.15 a minute".

The record that the deletion happened — who asked, when, why, how much. The phone number and email are cleared from that record the moment the deletion finishes, and what is left cannot be turned back into a number.

And the backups

Deletion is immediate on the live platform. Copies take longer to expire, and these are the real figures rather than a round number.

CopyGone within
Amazon's automatic database backups7 days (in practice 8 to 9)
The manual copy on a company laptop35 days
The application's own log14 days
So: gone from the platform today, and gone from every copy we hold within 35 days
We will clear the laptop copy immediately on request, which leaves Amazon's 7-to-9-day window as the only wait.

If something goes wrong

We will tell you without undue delay, and in any event within 72 hours of finding out. Not "if we think it is serious" — if your data is involved, you hear from us.

You will get the facts: what happened, when, whose data, what about them, what we have already done, and what we are changing. If we do not yet know the extent, you will get that email too, with what we do know and a time by which we will write again.

We have a written plan for the first 72 hours — who does what, in what order, with the wording of the notifications already drafted. You are welcome to read it before you need it; ask us.

Asking us something

Say what you need and we will answer. If it is a question about one person's data, we can usually answer it the same day.