GDPR Compliance Statement
Last updated . Effective . Version 2.4.
In short
This statement explains how Voice AI Portal applies UK GDPR, EU GDPR and the Data (Use and Access) Act 2025. We act as a processor for the client data agencies manage in the platform, and as a controller for agency account and billing data. It sets out our lawful bases, how we apply the data protection principles and how we handle rights requests.
1. Summary
This statement sets out how Voice AI Portal complies with the UK General Data Protection Regulation (UK GDPR), the EU General Data Protection Regulation (EU GDPR) and the Data (Use and Access) Act 2025. Voice AI Portal is a white-label client portal for voice AI agencies, operated by ALIM Ltd (Company Number 14528810). We process personal data on behalf of our agency customers and apply technical and organisational measures across all processing.
Key points:
- Inbound call recordings and transcripts stay in the voice AI provider account connected to each client workspace; the portal reads them live and does not keep copies. It stores call statistics, with no call content, for client billing, usage, results reports, client health checks and margin
- Voice AI provider API keys, Stripe keys and agency email keys are encrypted with AES-256-GCM
- Row level security keeps each agency’s data separate, and users see only the workspaces they are assigned to
- Agencies and their clients sign in with a one-time code by email; they have no passwords
- Data subject requests are handled within the legal time limits (one month as standard, 72 hours for urgent restriction and objection requests)
- Personal data breaches are reported to the ICO within 72 hours where required
- Standard Contractual Clauses or the UK IDTA are used for international transfers where needed
2. Our GDPR compliance framework
2.1 Scope
Geographic scope:
- Processing of personal data of individuals in the United Kingdom
- Processing of personal data of individuals in the European Economic Area (EEA)
- Customers and end users in the UK and EEA
- Transfers of data from the UK or EEA to other countries, with appropriate safeguards
Service scope:
- Client portals and reporting
- Multi-tenant workspace management
- Connections to voice AI providers (ElevenLabs, Retell AI and Vapi)
- Call data processing and reporting, including staff time handled estimates
- Results reports to clients, including any short note an agency adds
- Outbound campaigns and lead lists
- White-label branding and custom domains
- Webhook data received from voice AI providers
- Sign-in, roles and access control
Data subject categories:
- Agency owners and administrators (our direct customers)
- Client users who sign in to client workspaces (our customers’ clients)
- People whose calls appear in reporting, or who are contacted through outbound campaigns
- Website visitors and people who contact us
- Support contacts
2.2 Compliance objectives
Our GDPR programme aims to:
- Process lawfully: establish and document a lawful basis for all processing under Article 6 UK GDPR
- Build in privacy by design: build data protection into the product and our processes from the start
- Enable data subject rights: give people effective ways to use their rights under Articles 15 to 22
- Keep data secure: apply appropriate technical and organisational measures under Article 32
- Be accountable: keep records and demonstrate compliance under Article 5(2)
- Be transparent: give clear privacy information under Articles 13 and 14
- Reduce risk: carry out Data Protection Impact Assessments (DPIAs) for high-risk processing
- Manage international transfers: apply appropriate safeguards under Chapter V
2.3 Roles and responsibilities
Data protection contact: hello@voiceaiportal.com. Responsibilities include GDPR compliance oversight, liaison with supervisory authorities, data protection advice, DPIA review and breach notification.
Our roles:
- Data controller: ALIM Ltd, for agency account, billing and website data
- Data processor: Voice AI Portal, for client workspace data processed on behalf of agencies
- Joint controllers: only where defined in specific circumstances, with written arrangements
Who is responsible: our director is accountable for data protection, including privacy by design, security monitoring, incident response, data subject requests and consent. Everyone working on the platform keeps data confidential and reports incidents.
3. The seven GDPR principles
Our processing follows the seven principles in Article 5 UK GDPR.
Principle 1: Lawfulness, fairness and transparency (Article 5(1)(a))
- We process personal data only with a valid, documented lawful basis
- We are transparent through our Privacy Policy, Cookie Policy and Data Processing Agreement
- We do not use deceptive or manipulative data collection practices
- Privacy information is available wherever we collect data, and our privacy notices are reviewed at least once a year
Principle 2: Purpose limitation (Article 5(1)(b))
- Personal data is collected for specified, explicit and legitimate purposes, set out in our privacy notices
- Data is not processed for purposes that are incompatible with the original purpose
- Voice AI data is processed only to show it to the agency and its client, run campaigns the agency sets up and produce reporting
- Any new purpose is assessed for compatibility and communicated before it starts
Our purposes:
- Account management: sign-in, subscription management and billing
- Service delivery: client portals, reporting, workspace management, outbound campaigns and provider connections
- Security: fraud detection, access monitoring and threat prevention
- Support: technical help and communication
- Legal compliance: tax obligations, regulatory reporting and dispute resolution
- Marketing: promotional communications to business customers, with opt-out, and consent where required
Principle 3: Data minimisation (Article 5(1)(c))
- We collect only data that is adequate, relevant and necessary for our purposes
- Voice AI Portal does not keep copies of inbound call recordings or transcripts; it reads them from the voice AI provider when needed. Call times and durations are stored as call statistics, for client billing, usage, results reports, client health checks and margin
- Agencies choose which agents and phone numbers each client workspace reports on
- Client users are set up with only their name and email address
- Website analytics runs without cookies unless a visitor accepts Google Analytics
- We do not collect special category data (Article 9) for our own purposes
Principle 4: Accuracy (Article 5(1)(d))
- We take reasonable steps to keep personal data accurate and up to date
- Inaccurate data is corrected or erased without undue delay once we are told about it
- Rectification requests are handled within one month (Article 16)
- Call content is read from the voice AI provider each time, so the portal shows the provider’s current records. Stored call statistics are taken from those same records
- Data is validated where it is entered, for example email addresses and phone numbers in lead lists
Principle 5: Storage limitation (Article 5(1)(e))
Personal data is kept only as long as necessary, under a defined retention schedule that we review against legal requirements.
Retention schedule:
| Data category | Retention period | Legal basis |
|---|---|---|
| Active account data | Duration of subscription; deleted 30 days after cancellation | Contract performance |
| Sign-in data and roles | Duration of subscription; deleted with the account | Contract performance |
| Inbound call content from voice AI providers (recordings, transcripts, summaries, phone numbers, names) | Not stored; read live from the provider | Not applicable |
| Call statistics, for client billing, usage, results reports, client health checks and margin (call IDs, times, durations, channel, result category, provider status and end codes, provider-reported cost; no call content) | 13 months; per-call usage records for client billing up to 24 months, then kept only as monthly totals with billing records | Contract performance |
| Results report and margin totals (per-client figures worked out from call statistics; no call content) | For as long as the agency’s account exists; deleted with the agency’s data | Contract performance |
| Client health issues (what went wrong with a client’s AI agent and when; no call content) | 13 months after the issue is resolved | Contract performance |
| Results email recipients (email address, unsubscribe and bounce status) | For as long as the client workspace exists; deleted with the workspace | Contract performance |
| Outbound campaign records | For as long as the client workspace exists; deleted with the workspace, and cleared 60 days after an agency’s trial ends without a paid plan or after an agency has been paused for 90 days | Contract performance |
| Billing records | 7 years after the transaction | Legal obligation (UK tax law) |
| Usage and activity logs | 90 days | Legitimate interest (security) |
| Security and audit logs | 24 months | Legitimate interest (compliance) |
| Backup data | On the rolling backup schedule of our database provider, Supabase; overwritten as the schedule rolls on | Legitimate interest (business continuity) |
| Support communications | 24 months from case closure | Legitimate interest (quality and disputes) |
| Website form submissions | As long as needed to answer the enquiry and follow up; anyone can ask for theirs to be deleted at any time by emailing hello@voiceaiportal.com | Legitimate interest or consent |
| Marketing consent records | Until consent is withdrawn plus 3 years | Legal obligation (proof of consent) |
| Email delivery logs | 13 months | Contract performance |
| Data subject request records | 3 years from response | Legal obligation (compliance evidence) |
| Data breach records | Indefinitely, anonymised where possible | Legal obligation (regulatory) |
Grace period and suspension:
- Payment grace period (30 days): all data stays accessible and is kept as normal
- After suspension: customer data is kept for 90 days so payment can be resolved
- Deletion warning: sent 15 days before permanent deletion
- Read-only access: administrators keep read-only access during the 90-day retention period and can ask us for a data export
- Permanent deletion: at the end of the 90 days, customer data is permanently deleted and cannot be recovered
Legal holds: data may be kept longer where it is needed for litigation, regulatory enquiries, dispute resolution or security investigations. Each hold is documented with its reason and reviewed.
Principle 6: Integrity and confidentiality (Article 5(1)(f))
We apply appropriate technical and organisational measures under Article 32. In summary:
Technical measures:
- Encryption of keys: voice AI provider API keys, Stripe keys and agency email keys encrypted with AES-256-GCM
- Encryption in transit: TLS, with HSTS enabled
- Encryption at rest: provided by our hosting and database providers
- Passwordless sign-in: one-time codes sent by email, 8 digits, valid for 10 minutes, with rate limiting and lockout after repeated failed attempts
- Access control: roles (owner, admin and client) with least privilege; clients see only their assigned workspaces
- Data separation: row level security in the database, plus application checks on every client workspace request
- Audit logs: admin actions and call deletions are recorded
- Application security: input validation, a Content Security Policy and other security headers
- Network security: Cloudflare web application firewall and DDoS protection; automatic SSL certificates for verified white-label domains
Organisational measures:
- Confidentiality obligations for all staff and contractors before they get access
- Access limited to people who need it for their role, and removed promptly when roles change
- Data processing agreements with all sub-processors under Article 28
- An incident response process for detecting, containing, notifying and fixing breaches
Full details are in our Security Policy.
Principle 7: Accountability (Article 5(2))
We keep documentation that demonstrates compliance and update it as our processing changes:
- Records of processing activities (RoPA): Article 30 records covering our processing
- DPIAs: Article 35 assessments for high-risk processing
- Data processing agreements: in place with all processors under Article 28
- Privacy and Cookie Policies: public and reviewed at least once a year or when processing changes
- Data breach register: an Article 33(5) log of all breaches
- Data subject request logs: records of requests, responses and outcomes, kept for 3 years
- Consent records: proof of consent with time, method and scope
- Policy version control: earlier versions of our policies, with change logs
We can demonstrate compliance to supervisory authorities on request.
4. Lawful bases for processing
| Processing activity | Lawful basis | Article 6 reference | Description |
|---|---|---|---|
| Providing the client portal and reporting | Contract | 6(1)(b) | Needed to perform our contract with agency customers |
| Account set-up and management | Contract | 6(1)(b) | Needed to create accounts, manage subscriptions and provide access |
| Sign-in | Contract | 6(1)(b) | Needed to verify identity and give secure access |
| Roles and workspace access | Contract | 6(1)(b) | Needed to enforce permissions and workspace access |
| Payment processing | Contract | 6(1)(b) | Needed to bill subscriptions, take payments and issue invoices |
| Platform security and fraud detection | Legitimate interests | 6(1)(f) | Keeping the platform secure, preventing fraud and protecting users |
| Customer support | Contract | 6(1)(b) | Needed to give technical help and answer questions |
| Service improvement | Legitimate interests | 6(1)(f) | Improving the Services and developing features, using anonymised data where possible |
| Usage and performance monitoring | Legitimate interests | 6(1)(f) | Monitoring system performance and service quality, using technical logs |
| Responding to website enquiries | Legitimate interests | 6(1)(f) | Replying to people who contact us through our website |
| Tax and accounting | Legal obligation | 6(1)(c) | Complying with UK tax law (7-year retention) and accounting rules |
| Legal claims and regulatory compliance | Legal obligation | 6(1)(c) | Responding to legal requests, court orders and regulators |
| Marketing communications | Legitimate interests or consent | 6(1)(f) or 6(1)(a) | Marketing to business customers with an opt-out, or with consent where the law requires it |
| Website analytics cookies (Google Analytics 4) | Consent | 6(1)(a) | Set only after a visitor accepts analytics cookies |
| Launch update emails requested on our website | Consent | 6(1)(a) | Sent only to people who asked for them |
4.1 Legitimate interests assessments
Where we rely on legitimate interests (Article 6(1)(f)), we document a legitimate interests assessment covering:
- Purpose test: the legitimate interest we pursue (such as security, service improvement or fraud prevention) and why it is legitimate
- Necessity test: whether the processing is needed for that purpose and whether a less intrusive way exists
- Balancing test: whether our interests are overridden by the rights, freedoms and reasonable expectations of the people concerned
- Safeguards: the measures that reduce the impact, such as minimisation, encryption, access controls, transparency and opt-outs
Assessments are reviewed when processing changes materially and are available to the ICO on request.
4.2 Consent (Article 7)
Where we rely on consent, it is:
- Freely given: no detriment for refusing, not bundled with other terms
- Specific: separate for different purposes (for example marketing and analytics)
- Informed: with clear information about the purpose and the right to withdraw
- Unambiguous: given by a clear action, never by pre-ticked boxes or inactivity
- Recorded: with the time, method and scope
- Easy to withdraw: through unsubscribe links, the Cookie settings link on our website, or by emailing us
How we collect consent:
- The cookie banner on our website, with equal accept and reject options
- Separate opt-ins for marketing where consent is required
- Launch update forms that say what we will send
Withdrawing consent:
- Unsubscribe links in all marketing emails
- The Cookie settings link in our website footer, for analytics cookies
- Emailing hello@voiceaiportal.com
- Withdrawal does not affect processing that took place before it
5. Data subject rights
We support all data subject rights under Chapter III UK GDPR. Requests go to hello@voiceaiportal.com. Where we process data as a processor for an agency, we pass the request to the agency, which is the controller, and help it respond.
5.1 Right to be informed (Articles 13 and 14)
Our Privacy Policy is available from every page of our website and gives:
- The identity and contact details of the controller (ALIM Ltd, Company Number 14528810) and our data protection contact
- The purposes and lawful bases of processing
- The categories of personal data and recipients (including our sub-processors and voice AI providers)
- International transfer information and safeguards
- Retention periods
- The rights available, including the right to withdraw consent and to complain to the ICO
- Whether providing data is a legal or contractual requirement, and what happens if it is not provided
- Information about automated decision-making (we do not make decisions based solely on automated processing with legal or similarly significant effects)
Material changes to privacy information are emailed to users at least 30 days in advance.
5.2 Right of access (Article 15)
People can ask whether we process their personal data and get a copy of it.
How to ask: email hello@voiceaiportal.com with the subject “Data subject access request”.
Identity checks: a one-time code sent to the email address on the account, or government-issued ID for people without an account. Requests made on someone else’s behalf need proof of authority.
What we provide:
- Account and profile information, roles and permissions, and sign-in history
- Workspace settings and branding
- Usage records
- Outbound campaign records about the person, where we hold them
- Support correspondence
- Subscription and invoice records (full card details are held by Stripe, not by us)
- The purposes, recipients, retention periods and rights that apply
Timing: we acknowledge requests within 5 business days and respond within one month. For complex requests we may extend this by two further months, telling the person why.
Format: a structured, commonly used, machine-readable format (JSON), sent securely.
Fees: the first copy is free. We may charge a reasonable fee (£10) for further copies. For manifestly unfounded or excessive requests we may charge a reasonable fee (£25) or refuse, explaining why and telling the person about their right to complain to the ICO.
5.3 Right to rectification (Article 16)
People can ask us to correct inaccurate data or complete incomplete data. We make corrections within one month of a verified request, update the data in all our systems and tell the person when it is done. Where we have shared the data with others, we tell them about the correction unless that is impossible or involves disproportionate effort.
5.4 Right to erasure (Article 17)
People can ask us to delete their personal data where:
- It is no longer needed for the purpose it was collected for
- They withdraw consent and there is no other lawful basis
- They object and there are no overriding legitimate grounds
- It was processed unlawfully
- Deletion is required by law
How we delete: within 30 days of a verified request, we remove the data from our database, file storage and logs (security logs we must keep are anonymised), and from backups as they rotate. We suppress the email address in our email systems and tell our sub-processors to delete the data. We confirm when deletion is complete, including anything we had to keep and why.
Exceptions (Article 17(3)): we may keep data where it is needed to comply with a legal obligation (for example 7-year tax records) or for legal claims. We explain any exception and, where possible, restrict the data instead of keeping it in normal use.
Suspension compared with erasure: if an account is suspended after non-payment, the 30-day grace period and 90-day retention period apply before automatic deletion. An erasure request is handled within 30 days with no grace period, unless an exception applies.
Cancelled subscriptions: cancelling a paid subscription does not delete data by itself, so an agency can come back. An erasure request is what removes it, within 30 days.
5.5 Right to restriction of processing (Article 18)
People can ask us to restrict processing where:
- They contest the accuracy of the data (while we check it)
- Processing is unlawful but they prefer restriction to deletion
- We no longer need the data but they need it for legal claims
- They have objected and we are checking whether our legitimate grounds override theirs
We apply restriction within 72 hours of a verified request. Restricted data is stored but not otherwise processed without the person’s consent, except for legal claims or to protect the rights of others. We tell the person before lifting a restriction.
5.6 Right to data portability (Article 20)
People can receive the personal data they gave us, where processing is based on consent or contract and carried out by automated means, in a structured, machine-readable format (JSON by default, CSV on request), or ask us to send it directly to another controller where that is technically feasible. We respond within one month. Portability does not cover data processed under legal obligation or legitimate interests, derived data, or data about other people.
5.7 Right to object (Article 21)
Direct marketing: people can object at any time. We stop straight away, with no exceptions. Transactional emails (such as sign-in codes, security and billing emails) continue because they are needed to provide the service.
Legitimate interests: people can object on grounds relating to their situation. We assess the objection within one month and stop unless we can show compelling legitimate grounds that override their interests, or the processing is needed for legal claims. We explain our decision and the right to complain to the ICO.
5.8 Automated decision-making (Article 22)
Voice AI Portal does not make decisions based solely on automated processing that produce legal or similarly significant effects. Significant decisions about accounts involve human review.
6. Personal data breaches
- We notify the ICO within 72 hours of becoming aware of a reportable breach where we are the controller
- We notify affected agencies within 72 hours where we are their processor, so they can meet their own obligations
- We tell affected individuals without undue delay where a breach poses a high risk to them
- Every breach is recorded in our breach register with the actions taken
7. International transfers
Where personal data is transferred outside the UK or EEA, we use the UK IDTA or the UK Addendum, the EU Standard Contractual Clauses, or adequacy decisions, with supplementary measures where needed. Where data is processed is set out in our Privacy Policy and on our Third-Party Service Providers page.
8. Contact and complaints
Data protection contact: hello@voiceaiportal.com Controller: ALIM Ltd, trading as Voice AI Portal, Company Number 14528810, registered in England and Wales, registered office 17 Middleham Moor, Leeds, England, LS10 4TS
If you are not happy with how we handle your data, you can complain to the UK Information Commissioner’s Office (ICO), Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, telephone 0303 123 1113, ico.org.uk, or to your local supervisory authority.