Privacy Policy (Apantio)
Version: 2026-10-03
Last updated: 3 October 2026
This Privacy Policy explains how the person or business named in section 1, which offers the Apantio service ("we", "us"), uses personal data about:
- our business customers and the people who use their Apantio accounts (owners, staff, team members);
- people from businesses we are in contact with about our service (prospects, suppliers, partners); and
- visitors to our website.
It is written to meet GDPR Articles 13 and 14 (Regulation (EU) 2016/679) and Cyprus Law 125(I)/2018.
If you called, chatted with or received a text from a business that uses Apantio, that business is responsible for your data, not us. Please read section 11 below.
1. Who is responsible for your data (the controller)
- Controller: Operator details to be published, offering the Apantio service
- Address: Address to be published
- Email (also for privacy requests): Contact details to be published
We have not appointed a Data Protection Officer because we do not believe the law requires one for our current activities.
2. What personal data we collect
2.1 Customer account data
When your business signs up or is set up by us: your name, business email address, phone number, job role, business name and address, VAT number, log-in details (your password is stored only as a scrambled "hash"), team members you invite and their roles, and your account settings. We check your phone number during sign-up by sending you a one-time code.
2.2 Billing data
Your plan, billing contact, billing address, VAT number, invoices, payment history and usage (for example minutes and messages used). When you pay by card, the payment is handled by Stripe. We do not see or store your full card number.
2.3 Service usage and technical data
Log-in times, IP address, browser and device type, actions in the dashboard, error reports and performance data, and security logs. We use this to run, secure and fix the service.
Product telemetry is switched off today. Dashboard analytics and all server-side telemetry (product events, AI traces and error reports) are switched off for the whole platform, whatever a customer's account setting says. So today no data from our customers' accounts, and no call content, is sent to PostHog. Each customer account also has its own telemetry setting. It is off by default for new accounts; accounts created earlier keep their setting. While the platform switches are off, it sends nothing, whatever the setting. We will switch telemetry back on only after all of these: the data sent is limited to a small set of fields with caller content removed, and this has been checked; PostHog runs on its EU host; the chat widget on our customers' websites never loads PostHog for their website visitors; and we have updated this policy (and, for our customers, the Data Processing Agreement and its sub-processor list, with notice to them first).
Dashboard analytics. PostHog is switched off in the Apantio dashboard. No analytics, click tracking or session recording (a replay of what happened on screen) runs there. If we switch analytics back on, we will first update this policy and ask each dashboard user. It will run only on PostHog's EU host, and any recording will mask all on-screen text and form fields.
2.4 Calendar connection data
If you connect Google Calendar, see section 6.
2.5 Communications with us
Emails, support requests, feedback, meeting notes and anything else you send us.
2.6 Prospects and business contacts
If we contact your business about our service, or you contact us, we may hold your name, business contact details, your business's public website and the content of our conversations. If we prepare a demo for your business, we may import text from your public website to set up a demo assistant. We collect this from you, from your business's public website, or from public business directories.
Demo assistants for prospective clients. If we prepare a demo for your business, we store the name and email address of the person we send it to and an internal campaign reference, and we make the demo available for up to 30 days. The demo assistant answers questions using text imported from your business's public website; it may contain staff names or contact details that appear there. The demo assistant and the imported text are kept until we delete them; you can ask us to delete them at any time (see section 8). If you talk to a demo assistant by voice, see section 2.8.
2.7 Website visitors
Pages visited, links clicked, approximate location from IP address, referring page, browser and device, and, only if you accept analytics cookies, analytics identifiers and session recordings (form fields masked). See section 10.
2.8 Voice calls in the browser, website demos and chat demos
Besides phone calls, people can talk to an Apantio AI assistant through their web browser using their microphone. This happens in four places:
| Where | Who uses it | Who is responsible for the data |
|---|---|---|
| The voice demo (and chat demo) on our own website | Visitors to our website | Us (controller) |
| Demo assistants we prepare for a prospective client (section 2.6) | People at that business who open the demo link | Us (controller) |
| The "Test call" button in the Apantio dashboard | Our customers' staff, testing their own assistant | The call is stored in the customer's account like its other calls |
| The voice button in the chat widget on a customer's own website | That customer's website visitors | The customer (controller); we are its processor. See section 11 |
What is processed: your voice, which is streamed live to our AI provider (OpenAI) so the assistant can understand you and reply, even if nothing is stored; what you and the assistant say; a random visitor or session ID; and technical data (IP address, browser and device, time and length of the call). Voice calls in the browser may be recorded (audio of both sides) and transcribed.
Chat demos: what you type is sent to our AI provider (OpenAI, or Google's Gemini service for website chat) so the demo assistant can reply, and the conversation is stored.
How long: recordings of voice calls in the browser are deleted automatically after 90 days at the latest. Transcripts and demo chat conversations are kept until we delete them; you can ask us to delete them at any time (see section 8). Prospect demo assistants: see section 2.6.
Contact form in demos: we keep the contact form switched off in the demos we show to prospects. Its note is written for a real business's own website and names the business shown in the demo, which is not right for a demo we run. If anything is submitted by mistake, we (as the operator of the demo) delete it by hand.
Please don't give real personal, health or other sensitive information in a demo.
3. Why we use your data and our legal basis
| Purpose | Data | Legal basis (GDPR Art. 6(1)) |
|---|---|---|
| Create and run your account and provide the service you ordered | Account, usage, calendar connection | (b) performance of a contract with your business. For individual staff users: (f) our legitimate interest in providing the service your employer has ordered |
| Verify sign-ups and prevent fraud and abuse (phone code, bot check) | Account, technical | (f) legitimate interest in keeping the service secure |
| Billing, invoicing, VAT and accounting | Billing | (b) contract, and (c) legal obligation (tax and accounting law) |
| Support and service messages (security alerts, changes to terms, breach notices) | Account, communications | (b) contract; (f) legitimate interest; (c) legal obligation for some notices |
| Security, logging, error monitoring and service improvement | Usage and technical | (f) legitimate interest in a secure, working and improving service |
| Website analytics (after you accept analytics cookies) | Website visitor data | (a) consent, which you can withdraw at any time in "Cookie preferences" |
| Voice calls in the browser and chat demos that we control (section 2.8: our website demo, prospect demos) | Demo data | Live processing so the demo you started works: (f) legitimate interest in showing our service to people who ask to try it |
| Dashboard analytics (section 2.3; switched off today) | Usage and technical | (a) consent of each dashboard user, if we switch it back on. Session recording: none (switched off; see section 2.3) |
| Product telemetry from customer accounts (section 2.3; switched off today) | Usage and technical | (f) legitimate interest in running and improving a secure service |
| Contacting prospects and business contacts about our service, and preparing demos | Prospect data | (f) legitimate interest in promoting our business to other businesses, or (a) consent where the law requires it |
| Marketing emails to customers about similar services | Account | (f) legitimate interest, or consent where required; you can opt out at any time |
| Handling legal claims and complying with the law or requests from authorities | Any relevant data | (c) legal obligation; (f) legitimate interest in defending legal claims |
Where we rely on legitimate interests, we have weighed them against your rights. You can ask us for details and you can object (see section 8).
We do not use your data for decisions based solely on automated processing that have legal or similarly significant effects on you (GDPR Art. 22).
Giving us account and billing data is needed to sign a contract with us; without it we cannot provide the service.
4. Who we share data with
We share personal data only with service providers who help us run our business, under contracts that require them to protect it, and only as far as needed:
| Provider | What they do for us | Where and transfer safeguard |
|---|---|---|
| Hosting provider: Railway Corporation (San Francisco, USA) | Hosts the application, database and files, including uploaded files and call recordings | We are moving our hosting to Railway's EU West region (the Netherlands); until the move is finished, data may be stored in the United States. EU-US Data Privacy Framework (Railway is certified), plus the EU Standard Contractual Clauses in Railway's data processing addendum, which we are putting in place |
| Payment provider: Stripe | Card payments, subscriptions and invoices, when you pay by card | Where Stripe processes data outside the EEA, one of the safeguards in section 5 applies |
| Email delivery provider | Sends account, verification and alert emails | Where the provider processes data outside the EEA, one of the safeguards in section 5 applies |
| Twilio (Twilio Inc.) | Sends one-time sign-up verification codes and checks phone numbers | United States (Twilio Verify is US-hosted) and other countries. EU-US Data Privacy Framework (Twilio Inc. is certified, including the UK Extension and Swiss-US DPF); Twilio's data processing addendum applies the DPF, then Twilio's Binding Corporate Rules, then Standard Contractual Clauses |
| PostHog | Website analytics (only after you accept). Product analytics and error reports: switched off today (section 2.3) | Website analytics data goes to PostHog's US host today; one of the safeguards in section 5 applies |
| Cloudflare (Cloudflare, Inc., USA) | DNS for our domain and hosting of our public marketing website (Cloudflare Pages), protecting it against attacks; may run a bot check on sign-up (Turnstile). Not used to host the app or store app data | US company with a global network; where data leaves the EEA, one of the safeguards in section 5 applies |
| Cloudflare Web Analytics, where enabled on our website | Anonymous website statistics | As for Cloudflare above |
| Cal.com, if you book a call with us through it | Booking a call with us from the website | Where Cal.com processes data outside the EEA, one of the safeguards in section 5 applies |
| Firecrawl | Imports text from public websites when we set up an assistant or a demo | US company; where data leaves the EEA, one of the safeguards in section 5 applies |
| OpenAI (OpenAI Ireland Ltd; onward processing by OpenAI OpCo, LLC) | Powers the AI assistant, including demo assistants we prepare for prospects | OpenAI Ireland Ltd (EU); OpenAI OpCo, LLC (United States) for processing outside that scope, including AI processing generally until EU data residency is switched on for our account. Standard Contractual Clauses (Decision (EU) 2021/914) in OpenAI's data processing addendum |
| Google (Google LLC, USA) | Website chat replies may be generated by Google's Gemini AI service; and, only if you connect Google Calendar, calendar access (see section 6) | Google LLC is certified under the EU-US Data Privacy Framework; otherwise one of the safeguards in section 5 applies |
We may also share data with our professional advisers (accountant, lawyer, insurer), with authorities where the law requires it, and with a buyer or successor if the business is transferred or incorporated as a company.
We do not sell personal data.
The providers that process your callers' data for your business are listed in our Data Processing Agreement, Annex 3.
5. International transfers
Some of our providers are based in, or process data in, countries outside the European Economic Area, in particular the United States. Not all data stays in the EU. In particular:
- OpenAI (AI assistant): our contract is with OpenAI Ireland Ltd in the EU. Until EU data residency is switched on for our account, OpenAI may process data in the United States (OpenAI OpCo, LLC) under Standard Contractual Clauses. Some limited account and usage metadata may be processed in the United States even after that.
- Twilio (sign-up verification codes and phone-number checks): processed in the United States under the EU-US Data Privacy Framework.
- Twilio (calls and texts): processed in the United States today under the EU-US Data Privacy Framework; we plan to move this to Twilio's Dublin (IE1) region.
- Railway (hosting of the app and its database): Railway Corporation (San Francisco, USA). We are moving our hosting to Railway's EU West region (the Netherlands); until the move is finished, data may be stored in the United States. Railway is a US company, so transfers are covered by the EU-US Data Privacy Framework, plus the EU Standard Contractual Clauses in Railway's data processing addendum, which we are putting in place.
- PostHog (website analytics, only after you accept): this data currently goes to PostHog's US host. We plan to move to PostHog's EU host. Product telemetry from our customers' accounts is switched off today (section 2.3).
- Stripe (payments, when you pay by card), Firecrawl (a US company that imports public website text, including text from prospects' websites, section 2.6), Cloudflare (Cloudflare, Inc., USA: DNS and our marketing website on Cloudflare Pages, with its security and the sign-up bot check; not the app or its data), Cal.com (if you book a call with us through it), our email delivery provider and Google (if you connect Google Calendar): where any of them processes data outside the EEA, one of the safeguards below applies.
When data leaves the EEA, we rely on one of these safeguards:
- the European Commission's adequacy decision for the EU-US Data Privacy Framework (Decision (EU) 2023/1795), where the recipient is certified; or
- the European Commission's Standard Contractual Clauses (Decision (EU) 2021/914), usually built into the provider's data processing terms, with a transfer risk assessment.
You can ask us for a copy of the relevant safeguards at Contact details to be published.
6. Google Calendar integration
This section explains how Apantio accesses, uses, stores, shares and deletes Google user data. It applies only if a business user chooses to connect a Google account in the Apantio dashboard.
What Google data we access. With your permission (Google OAuth), we access only:
- your Google account ID and email address, to identify which Google account is connected (scopes:
openid,email); - the list of your calendars (names and IDs), so you can choose which calendar Apantio uses (
calendar.calendarlist.readonly); - free/busy information for the calendar you chose: only the start and end times of busy periods, not event titles, descriptions, attendees or locations (
calendar.freebusy); - the appointment events that Apantio itself creates on that calendar, which we create, update and delete when a booking is made, changed or cancelled (
calendar.events).
We do not read the content of your other Google Calendar events, and we do not access Gmail, Google Drive, Contacts or any other Google service.
How we use it. We use this data only to provide the booking feature you switched on: to show your busy times in the Apantio calendar, to stop the AI assistant and the dashboard from offering times when you are busy, and to put the appointments booked through Apantio into your Google Calendar and keep them up to date. An appointment event contains the booking time and, depending on your settings, the service and the customer's name.
How we store it. We store the OAuth access and refresh tokens encrypted. We keep your Google account ID and email, the ID of the chosen calendar, the busy periods (start and end times only) for the next 90 days, and the IDs of the events Apantio created, so we can update or delete them. This data is stored in our database, separated per customer account.
How we share it. We do not sell Google user data and we do not share it with anyone, except: with the users of your own Apantio business account (who see your busy times in the dashboard); with our hosting and infrastructure providers that store it on our behalf (section 4); when the law requires it; or as part of a merger or sale of our business, with the same protections. People at Apantio do not read your Google data, unless you ask us to for support, it is needed for security (for example to investigate abuse), or the law requires it.
How you can delete it. You can disconnect Google Calendar at any time in the Apantio dashboard (Calendar, Google Calendar, Disconnect). When you disconnect, we delete the stored tokens and the cached busy periods for that calendar straight away, and we ask Google to revoke Apantio's access. You can also remove Apantio's access at any time from your Google Account at https://myaccount.google.com/permissions. Appointment events already created in your Google Calendar stay there unless you delete them. To have all remaining Google-related data (such as the connected account email) deleted, email Contact details to be published; we will delete it, and we also delete it when your Apantio account is deleted.
Limited Use. Apantio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we do not use Google user data for advertising, we do not sell it, we do not use it to train or improve general AI or machine-learning models, and we do not use it to determine creditworthiness or for lending.
7. How long we keep data
Where the table says "kept until we delete it", we have not yet set an automatic deletion period. You can ask us to delete your data at any time (see section 8), and we will do so unless the law requires us to keep it.
| Data | How long |
|---|---|
| Account data | While your account is active; after it closes, kept until we delete it. Account deletion is handled by us on request |
| Billing records and invoices | As long as Cyprus tax and accounting law requires |
| Support and business correspondence | Kept until we delete it, unless needed for a legal claim |
| Security and server logs | Kept until we delete them |
| Website analytics (with consent) | Kept until we delete them |
| Prospect data (no contract signed) | Kept until we delete it; we delete it if you object (section 8) |
| Prospect demo assistants, including the text imported from the prospect's website (section 2.6) | The demo is available for 30 days after it is created; the demo assistant and the imported text are kept until we delete them |
| Recordings of browser voice calls (section 2.8) | Deleted automatically after 90 days at the latest |
| Transcripts of browser voice calls and chat demo conversations (section 2.8) | Kept until we delete them |
| Dashboard analytics | None collected today (switched off, section 2.3) |
| Data needed for a legal claim | Until the claim is resolved |
8. Your rights
Under the GDPR you have the right to:
- access your personal data and get a copy;
- have inaccurate data corrected;
- have your data erased in certain cases;
- restrict our use of your data in certain cases;
- data portability (receive data you gave us in a machine-readable format, or have it sent to another provider) where we rely on consent or contract;
- object at any time to processing based on our legitimate interests, and always to direct marketing;
- withdraw consent at any time where we rely on consent (this does not affect processing that already happened).
To use these rights, email Contact details to be published. We will reply within one month. In complex cases we may extend this by up to two more months, and we will tell you why. We may ask you to prove your identity. Using your rights is free unless a request is clearly unfounded or excessive.
9. Complaints
We would like the chance to fix any concern first, so please contact us at Contact details to be published. You also have the right to complain to the data protection authority in Cyprus:
Commissioner for Personal Data Protection
Kypranoros 15, 1061 Nicosia, Cyprus (postal: PO Box 23378, 1682 Nicosia)
Tel: +357 22818456 · Fax: +357 22304565
Email: commissioner@dataprotection.gov.cy
Website: https://www.dataprotection.gov.cy
You may also complain to the authority in the EU country where you live or work.
10. Cookies and similar technologies (summary)
Under Cyprus Law 112(I)/2004, s.99(5), we ask for your consent before storing or reading information on your device, except where it is strictly necessary for a service you asked for. In short:
- Strictly necessary (always on): remembering your cookie choice (in your browser's storage); security and bot-protection cookies set by Cloudflare; log-in session cookies in the dashboard; a random visitor ID if you start a browser voice demo.
- Analytics (only with your consent): PostHog cookies and browser storage for page views, clicks, errors and session recordings (form fields masked). This data goes to PostHog's US host today (see section 5). If you choose "Reject non-essential", we do not load PostHog on the website.
- Dashboard analytics: switched off completely. If we switch them back on, each dashboard user will be asked first. Dashboard session recording: switched off; if it ever comes back, only with all text and form fields masked and on PostHog's EU host.
- You can change your choice at any time through "Cookie preferences" in the website footer.
Chat widget on our customers' websites: when a business adds the Apantio chat widget to its own website, the widget stores a random visitor ID in the visitor's browser storage so the conversation can continue. The widget creates this ID and contacts our servers (sending the site's widget key, the visitor ID and, as with any web request, the IP address) when the page loads, before the visitor opens the chat. The business that runs that website is responsible for telling its visitors about this in its own cookie notice.
11. If you contacted a business that uses Apantio (callers, chat users and text recipients)
Businesses such as clinics use Apantio to answer their phone calls and website chats with an AI assistant, book appointments and send text messages.
- The business is the controller of your data. It decides why and how your data is used. We are its processor: we process your data only on its instructions and under a data processing agreement, as GDPR Article 28 requires.
- What is processed: your phone number, what you say during the call, a summary, the details of any booking or message, call details (time, duration, outcome, your answer to the recording question), and chat messages or text messages. Your voice is processed live by the AI service (OpenAI) so it can understand and reply, even if the call is not recorded. If you agree, a recording and a written transcript are also kept; transcripts and summaries are generated automatically by AI and may contain mistakes. If you mention health information when calling a clinic, that is processed too, on behalf of the clinic.
- AI assistant and recording choice: phone calls and chats are handled by an AI assistant, not a person. On phone calls, the assistant asks for your permission before recording the call or keeping a transcript. If you say no, or don't answer clearly, it won't record the call or keep a transcript, but it still keeps what is needed to handle your request (for example your number, name, booking or message). If you change your mind during the call, say so: it stops recording and deletes what was recorded on that call.
- Voice button on the business's website: if you talk to the assistant through the voice button in the business's website chat, the call may be recorded (audio of both sides) and transcribed (see section 2.8).
- Messages you leave: if you ask to leave a message, the assistant writes it down as text for the business (no audio of the message is recorded). Before taking your message, the assistant tells you, in English or Greek, that your message will be recorded in writing and passed to the team.
- How long: if you agree to recording, the audio is deleted automatically after 90 days; the business can delete recordings sooner. Messages you leave for the business are kept for 90 days; after that the message text is blanked, and the record that a message was left stays (messages taken before this 90-day period was introduced may be kept for up to 365 days). Transcripts, chat messages, contact details and bookings are kept until the business deletes them or stops using Apantio. The business's own privacy notice may say more.
- Contact form in the chat: if you fill in the contact form in a business's chat, your name, contact details and message go to that business so it can reply; we process them on its behalf. The form shows a short privacy note in English or Greek and a link to the business's privacy policy (or, if the business has not added one, to this policy). With your details we keep a record of which version and language of that note you were shown, and when you sent the form. (This is a record that the note was shown, not a consent.)
- Where data goes: your data is stored by us on the business's behalf, and processed by our providers, including Google (website chat replies may be generated by its Gemini AI service, in the United States, under the EU-US Data Privacy Framework), OpenAI (AI; our contract is with OpenAI Ireland Ltd in the EU, but data may be processed in the United States until EU data residency is live) and Twilio (calls and texts: processed in the United States today under the EU-US Data Privacy Framework; we plan to move this to Twilio's Dublin (IE1) region). The full list is in our Data Processing Agreement with the business, Annex 3. See section 5 for the safeguards.
- To object or ask questions: contact the business directly. You can also ask the assistant during the call not to record.
- Your rights: please contact the business directly to use your rights or ask how it uses your data, and read its own privacy notice. If you contact us instead, we will pass your request to the business within 5 business days and help it respond.
12. Security
We use technical and organisational measures to protect personal data. These include separating each customer's data in the database, role-based access, hashed passwords, encryption of stored access tokens, and automatic deletion of call recordings after a set period. No system is completely secure. If a personal data breach is likely to put your rights at risk, we will notify the Commissioner and, where required, you, as the GDPR requires.
13. Children
Our service is for businesses and is not aimed at children. We do not knowingly collect children's data for our own purposes. (Callers to a client's business may include children; the client, as controller, is responsible for that data.)
14. Changes to this policy
We may update this policy. We will change the date at the top and, for important changes, tell customers by email or in the dashboard.
15. Contact
The controller named in section 1: Operator details to be published, Address to be published, Contact details to be published.