Data Processing Agreement
Last updated: November 2026
1. Introduction and Parties
This Data Processing Agreement ("DPA") forms part of the Terms of Service between Allio ("Processor", "we", "us") and you ("Controller", "Customer") and governs the processing of personal data by Allio on behalf of the Customer.
This DPA is entered into pursuant to Article 28 of the General Data Protection Regulation (GDPR) and establishes the rights and obligations of both parties regarding the processing of personal data.
2. Definitions
- "Controller" means the natural or legal person who determines the purposes and means of processing personal data (the Customer).
- "Processor" means a natural or legal person who processes personal data on behalf of the Controller (Allio).
- "Personal Data" means any information relating to an identified or identifiable natural person.
- "Processing" means any operation performed on personal data, such as collection, storage, use, disclosure, or deletion.
- "Data Subject" means an identified or identifiable natural person whose personal data is processed.
- "Sub-processor" means any third party engaged by the Processor to process personal data on behalf of the Controller.
- "GDPR" means Regulation (EU) 2016/679 of the European Parliament and of the Council.
3. Subject Matter, Duration, Nature and Purpose
Subject Matter: The Processor will process personal data on behalf of the Controller in connection with the provision of the Allio platform services.
Duration: Processing will continue for the duration of the subscription term plus 30 days post-termination to allow for data export, after which data will be securely deleted.
Nature of Processing: The Processor will host, store, transmit, and process customer data submitted through the Allio platform, including but not limited to:
- Data storage, backup, and multi-tenant hosting
- Omnichannel communication facilitation (email via Gmail, Outlook, or the Controller's chosen IMAP host; SMS and voice via Twilio; Meta Messenger, Instagram, and WhatsApp; webchat)
- AI assistance (Adam): conversation history, customer and booking context, knowledge base content, attachments, spellcheck, and call transcription
- Booking (native Allio booking and optional Gecko sync) and calendar feeds (ICS)
- Review management (Google Business Profile sync and reply; Trustpilot review-link redirects)
- E-commerce sync (optional Shopify customer and order sync)
- Payment processing coordination (Stripe), bank data access (Enable Banking / PSD2), and accounting integrations (Billy/Shine, Dinero, e-conomic)
- Product analytics, error monitoring, job queues, and async workers
Purpose: Processing is performed to provide the services described in the Terms of Service and as instructed by the Controller, including the creation of anonymised industry benchmarks as authorised in Section 17.
4. Types of Personal Data and Data Subject Categories
Types of Personal Data processed:
- Contact information (names, email addresses, phone numbers, addresses)
- Business information (CVR numbers, company names, business addresses)
- Communication data (emails, SMS messages, chat messages including Messenger, Instagram DM, WhatsApp, and webchat, and support communications)
- Voice and call data (call recordings, CallSid and related telephony metadata, answering-machine detection metadata, and transcripts)
- Booking data (appointment times, services, assigned staff, notes, and calendar ICS content)
- Review data (reviewer name, review text, and location data from Google Business Profile; click and redirect metadata for Trustpilot review links)
- E-commerce data (Shopify customers and orders when the Controller connects Shopify)
- Payment and transaction data (order amounts, payment status, invoice details)
- Push notification tokens and notification payloads
- AI processing data (prompts, tool inputs/outputs, embeddings, and rerank chunks when Adam, automation, call intelligence, or spellcheck is used)
- Usage analytics and logs (feature usage, access logs, error reports)
- Product analytics data (e.g. PostHog): page views, feature usage events, and when the user is logged in a pseudonymised user ID plus email and profile traits such as company name, for product improvement and usage analysis
- User activity data (login timestamps and frequency, last-active heartbeat timestamps, action-level logs such as orders created, messages sent, and campaigns launched, and aggregated daily usage metrics linked to the user's organization)
- Error and performance monitoring data (including Session Replay: DOM structure and user interaction data for debugging; not video. Replay may include visible UI content such as inbox message previews or booking details.)
- Account credentials (encrypted passwords, authentication tokens)
Categories of Data Subjects:
- Controller's customers and end users
- Controller's employees and business contacts
- Controller's suppliers and partners
5. Processor Obligations
The Processor shall:
- Process personal data only on documented instructions from the Controller, unless required by EU or Member State law
- Not use the Controller's end-customer personal data for marketing, product development, or any purpose beyond service delivery without explicit instructions from the Controller. For clarity: (a) product analytics (PostHog) and error monitoring (Sentry) of platform-user activity, as described in Section 7, are performed as part of service delivery and platform reliability on the bases set out in Section 7; and (b) creation and use of anonymised and aggregated industry benchmarks from booking and related operational data is authorised under Section 17
- Implement and maintain role-based access controls limiting data access to personnel who need it
- Provide data processing configuration options through the platform's admin panel
- Assist the Controller in responding to data subject requests (access, rectification, erasure, portability)
- Assist the Controller in ensuring compliance with GDPR obligations (security, breach notification, impact assessments)
- Delete or return all personal data upon termination, unless retention is required by law
6. Confidentiality Requirements
The Processor ensures that all persons authorized to process personal data:
- Have committed to confidentiality through employment contracts with confidentiality clauses
- Are bound by contractor NDAs extending to personal data handling where applicable
- Have access limited to data necessary for their job functions (least privilege principle)
- Are subject to security and audit logging of relevant administrative and security events
- Receive appropriate training on data protection obligations
7. Sub-processor Management
The Controller grants the Processor general authorization to engage sub-processors subject to the following conditions:
- The current list of sub-processors is maintained and disclosed below
- The Processor will provide 30 days advance notice before adding new sub-processors
- The Controller may object to new sub-processors for legitimate data protection reasons
- If the Controller objects and the objection cannot be resolved, the Controller may terminate without penalty
- The Processor remains fully liable for the acts and omissions of its sub-processors
- Sub-processor agreements include equivalent data protection obligations
Current Sub-processors:
| Service | Purpose | Location |
|---|---|---|
| Supabase, Inc. | Database, authentication, storage, and Edge Functions | EU (Frankfurt / eu-central-1) |
| Vercel, Inc. | Frontend hosting and serverless API (Adam, call intelligence, MCP) | USA / global |
| Cloudflare, Inc. | CDN, Workers (short links, webchat, calendar feed, spellcheck), and rate limiting | USA / EU (global edge) |
| Upstash Inc. | Redis cache and QStash job queues | EU (QStash eu-central-1); Redis per configuration |
| Stripe, Inc. | Payment processing | USA / EU |
| Twilio, Inc. | SMS, voice, call recordings, and telephony metadata | USA |
| Google LLC (Gmail) | Email integration | USA / EU |
| Microsoft Corporation (Outlook) | Email integration | USA / EU |
| Meta Platforms, Inc. | Facebook Messenger, Instagram messaging, and WhatsApp | USA / EU |
| Apple Inc. (APNs) | iOS push notifications | USA / global |
| Shine Denmark ApS | Billy accounting integration (Shine Denmark ApS) | Denmark |
| Visma Dinero ApS | Accounting integration (optional) | Denmark |
| Visma e-conomic | Accounting integration (optional) | Denmark / EU |
| Erhvervsstyrelsen (Virk.dk) | CVR lookup and validation | Denmark |
| Enable Banking Oy | Bank account data access (PSD2) | Finland / EU |
| OpenAI, Inc. | Adam LLM, embeddings, spellcheck, call summaries/facts, and optional call transcription fallback (e.g. mono recordings) | USA |
| Soniox, Inc. | Primary speech-to-text for Allio Phones call recordings (dual-channel audio and temporary transcripts); EU region endpoint (api.eu.soniox.com) | EU |
| LangSmith (LangChain, Inc.) | AI tracing and evaluations (prompts and tool I/O) | USA |
| Cohere, Inc. | RAG reranking | International / USA |
| Google LLC (Cloud Vision) | PDF OCR for Adam when used | USA / global |
| Google LLC (Business Profile) | Review sync and reply (optional) | USA / EU |
| Gecko Booking | External booking sync (optional) | Per Gecko agreement |
| Shopify, Inc. | Customer and order sync (optional) | USA / global |
| Trustpilot A/S | Review-link redirect (click to Controller's Trustpilot page; Allio does not share CRM data beyond the redirect) | EU / international |
| Sentry, Inc. | Error monitoring and Session Replay (DOM and interaction data, not video; may include visible UI content) | EU (Germany ingest); Processor is US-based |
| PostHog, Inc. | Product analytics (page views, feature usage events, user ID and profile traits when logged in) | EU |
Optional integrations: Gecko, Shopify, e-conomic, Google Business Profile, Trustpilot, and accounting systems (Billy/Shine, Dinero) receive personal data only when the Controller connects the relevant integration. The Controller's own IMAP email host is chosen by the Controller and is not a fixed Allio sub-processor.
AI (OpenAI / Soniox / Cohere / LangSmith / Cloud Vision): Processing occurs when the Controller uses Adam, automation, call intelligence, spellcheck, or related AI features. Data may include conversation history, customer identity, booking context, knowledge content, attachments, and call audio or transcripts. For Allio Phones, dual-channel call recordings are transcribed by Soniox as a sub-processor in the EU (api.eu.soniox.com); temporary async audio files and transcripts are deleted after processing. OpenAI is used for call summaries/facts and as transcription fallback where Soniox cannot process the recording (e.g. mono). The Processor does not authorize AI providers to train foundation models on Controller data unless otherwise agreed in writing. Purpose and legal basis: Necessary for performance of the contract (Art. 6(1)(b)) where AI features are part of the service. Third-country transfers: Where processing occurs outside the EEA (e.g. OpenAI in the USA), transfers are governed by Standard Contractual Clauses or EU-U.S. Data Privacy Framework as applicable. Soniox call transcription for Allio Phones is configured for EU-region processing.
Product analytics (PostHog): The Processor uses PostHog for product analytics to understand platform usage and improve the service. Data processed includes page views, feature usage events (e.g. sign-in, sign-up), device and browser information, and when the user is logged in a user ID and profile traits (e.g. email, company name). Data is processed in the EU (via EU cloud / Allio proxy). Purpose and legal basis: Legitimate interest in product improvement and service optimization (Art. 6(1)(f) GDPR). Data minimization: Only usage and identification data necessary for analytics are sent; no payment or message content. Retention: In line with PostHog documentation; details available on request.
Error monitoring and Session Replay (Sentry): The Processor uses Sentry for error reporting and Session Replay (DOM and interaction data, not video) to diagnose faults and improve service stability. Replay may include visible UI content (e.g. inbox message previews or booking details). Sampling rates and redaction settings may change over time; Controllers should assume that Session Replay can capture on-screen personal data in the product UI. Purpose and legal basis: Necessary for performance of the contract and legitimate interest in service reliability and security. Data is sent to Sentry's EU ingest (Germany) where available. Retention: Limited in line with the vendor's documentation (typically 30–90 days for replay); details available on request. Third-country transfers: Where Sentry, Inc. (US) processes data outside the EEA, such transfers are governed by the same mechanisms as other sub-processors (e.g. Standard Contractual Clauses or EU-U.S. Data Privacy Framework as applicable).
8. Security Measures (Article 32)
The Processor implements appropriate technical and organizational measures to ensure a level of security appropriate to the risk, including:
- Encryption: Data encrypted at rest (AES-256) and in transit (TLS 1.2+)
- Access Controls: Multi-factor authentication available for accounts, role-based permissions, least privilege principle
- Network Security: Firewalls, intrusion detection, DDoS protection, regular security monitoring
- Data Isolation: Multi-tenant architecture with strict logical separation between customer data
- Business Continuity: Regular automated backups, disaster recovery procedures, redundant infrastructure
- Security Testing: Regular vulnerability assessments and security audits
- Vendor Management: Due diligence on sub-processors, contractual security requirements
- Incident Response: Documented procedures for detecting, responding to, and recovering from security incidents
9. Data Breach Notification
In the event of a personal data breach, the Processor shall:
- Notify the Controller without undue delay, and no later than 72 hours after becoming aware of the breach
- Send notification via email to the designated security contact on record
- Provide information including: nature of the breach, categories and approximate number of data subjects affected, likely consequences, and measures taken or proposed to address the breach
- Provide ongoing updates as more information becomes available
- Cooperate with the Controller in investigating and mitigating the breach
- Document all breaches including facts, effects, and remedial action taken
10. Audit Rights
The Controller has the right to verify the Processor's compliance with this DPA. The Processor shall:
- Make available security documentation upon reasonable request
- Permit one reasonable audit per year with 30 days advance notice and defined scope
- Permit regulator-mandated audits without restrictions
- Provide access to relevant records, systems, and personnel as reasonably required
- Controller shall bear its own costs for audits, unless the audit reveals material non-compliance
11. Data Return and Deletion
Upon termination of the service agreement:
- Controller has a 30-day window to export data in standard formats (JSON, CSV)
- After the export window, all personal data will be securely deleted within 60 days
- Deletion includes all copies, including backups, except where retention is required by law
- Processor will provide written certification of deletion upon request
- Financial data may be retained for 5 years in accordance with the Danish Bookkeeping Act
12. International Data Transfers
Some sub-processors are located outside the EU/EEA. The Processor ensures a legal basis for such transfers through:
- EU-U.S. Data Privacy Framework: For transfers to certified U.S. organizations
- Standard Contractual Clauses (SCCs): European Commission-approved clauses for transfers to other third countries
- Adequacy Decisions: Where the European Commission has determined adequate protection
The Processor will provide information about specific transfer mechanisms upon request.
13. Liability
The liability provisions of the Terms of Service apply to this DPA. Additionally:
- Each party is liable for damages caused by processing that violates GDPR or this DPA
- The Processor is liable for damages caused by processing that does not comply with Controller instructions or GDPR processor obligations
- The Processor is fully liable for the acts and omissions of its sub-processors
- Where both parties are responsible for damage, each party is liable for the entire damage to ensure effective compensation
14. Term and Termination
This DPA:
- Is effective from the date the Controller accepts the Terms of Service
- Remains in effect for the duration of the service agreement
- Survives termination for data retention periods required by law or this DPA
- May be terminated by either party upon material breach that remains uncured for 30 days after written notice
15. Amendments
The Processor may update this DPA to reflect changes in law, regulatory guidance, or processing activities. Material changes will be communicated with 30 days advance notice. Continued use of the services after the notice period constitutes acceptance of the updated DPA.
16. Conflict with Terms of Service
In the event of any conflict between this DPA and the Terms of Service, this DPA shall prevail with respect to the processing of personal data.
17. Anonymised Industry Benchmarks and Product Improvement
The Controller authorises the Processor, as a documented instruction under Article 28 GDPR, to process booking data and related operational metrics (including booking frequency, rebooking intervals, service categories, appointment outcomes, messaging timing relative to appointments, and similar non-content operational signals) solely for the purpose of creating anonymised and aggregated industry benchmarks and product recommendations that improve the Allio service for all customers over time.
Anonymisation standard: Before any data is used for cross-customer benchmarking, shared industry standards, or product recommendations derived from multiple Controllers, the Processor shall irreversibly anonymise and aggregate the data so that it is no longer personal data under GDPR. In particular:
- No natural person (end customer, patient, client, staff member, or other data subject) can be identified from the benchmark data, alone or in combination with other information reasonably available
- No Controller, clinic, salon, or other customer organisation can be identified from shared or published benchmarks (including by name, CVR, address, account identifier, or other unique organisational attributes)
- It is not possible to determine that a particular end customer booked with Clinic A, Clinic B, or both, or to link any end customer across Controllers
- Identifiers such as names, email addresses, phone numbers, postal addresses, free-text notes, message content, voice recordings, and direct organisational identifiers are removed or transformed before aggregation
- Aggregation uses cohort sizes and statistical methods designed to prevent singling-out, linkage, or inference of individuals or Controllers; small or unique cohorts are suppressed or further aggregated
What may be shared: Only anonymised, aggregated industry-level statistics and insights may be shared with Controllers (for example industry averages for rebooking rates, typical revisit intervals, or general messaging timing patterns). The Processor will not disclose another Controller's identifiable performance, customer lists, or raw booking records to any other Controller.
Permitted uses of anonymised benchmarks: The Processor may use such anonymised and aggregated data to:
- Benchmark a Controller's own performance (visible only to that Controller) against anonymised industry standards
- Generate product recommendations for Controllers, such as suggested pricing adjustments, revisit or follow-up messaging timing, or other operational practices correlated with higher return rates in anonymised industry data
- Improve Allio features, models, and default workflows for the benefit of all Controllers over time
Legal status after anonymisation: Fully and irreversibly anonymised data is not personal data and is not subject to GDPR. The act of anonymising personal data is itself processing and is performed only as instructed and authorised by this Section. Pseudonymised data (where individuals or Controllers could still be re-identified with additional information) is not treated as anonymised and remains subject to this DPA and GDPR until true anonymisation is achieved.
Controller role for own-purpose use: Where the Processor determines its own purposes for using anonymised industry benchmarks to improve the Allio product, such use of anonymised data falls outside GDPR. If any intermediate processing of personal data is required solely to produce those anonymised aggregates, it is limited to what is necessary for that anonymisation and aggregation under this instruction.
No marketing of end customers: Nothing in this Section authorises the Processor to use identifiable end-customer personal data to market to those end customers on the Processor's own behalf, or to sell or rent identifiable personal data to third parties.
18. Contact Information
For questions about this DPA or data protection matters, please contact:
Allio Data Protection
Email: privacy@allio.dk
See also our Privacy Policy and Terms of Service.