Version 1.0. Effective from 16 November 2026. Covers both vimpl and Ailean, and replaces all earlier versions of the vimpl Data Processing Agreement.
1. Parties, scope and definitions
1.1 Parties. This Data Processing Agreement ("DPA") is entered into between the customer ("Controller") and vimpl.com A/S, CVR no. 41663073, Asger Rygs Gade 19, 3. tv., DK-1727 Copenhagen V, Denmark ("Processor"). It takes effect when the Controller accepts the Processor's terms or signs an order form ("Effective Date").
1.2 Services. The Processor provides two cloud services. This DPA covers each one the Controller uses:
- vimpl — digital boards for planning, workshops and project follow-up.
- Ailean — AI-assisted process work: interviews (typed or by voice), process descriptions, BPMN diagrams, improvement suggestions, business cases, project plans and exports.
1.3 Purpose. This DPA sets out the Processor's obligations when it processes personal data on the Controller's behalf, as required by article 28(3) of Regulation (EU) 2016/679 ("GDPR").
1.4 Definitions. Personal data, processing, controller, processor, data subject and personal data breach have the meaning given in GDPR article 4. In addition:
- Customer Content — all data the Controller or its users enter into or generate with the services, including transcripts, voice input, process descriptions, diagrams, metrics, business cases and AI outputs based on them.
- AI Provider — a sub-processor that runs an AI model on Customer Content to produce an output for the Controller.
- Sub-processor — any third party the Processor engages to process personal data on the Controller's behalf.
1.5 Controller's responsibility. The Controller decides the purposes and means of the processing and is responsible for its legal basis. This includes informing the people it interviews or invites to contribute, for example participants in an Ailean round.
2. Processor obligations
2.1 Instructions. The Processor processes personal data only on the Controller's documented instructions: this DPA, Annex 1, the order form and the Controller's use of the services' features. If the Processor believes an instruction breaks the GDPR or other data-protection law, it informs the Controller without delay. Where EU or member-state law requires processing, the Processor informs the Controller first, unless that law forbids it.
2.2 Confidentiality. Only staff who need access to deliver or support the services can access personal data, and each is bound by a duty of confidentiality. Staff do not read Customer Content except to give support the Controller asks for, to investigate abuse or security incidents, or where law requires it.
2.3 Security. The Processor implements the technical and organisational measures in Annex 3 (GDPR article 32) and keeps them at least at that level for the term of this DPA.
2.4 Sub-processors. The Processor engages sub-processors only as set out in section 4.
2.5 Data-subject requests. The Processor helps the Controller answer requests to access, correct, delete, restrict or port personal data, mainly through the services' own features (edit, export, delete a flow or a board). A request received directly by the Processor is passed to the Controller without undue delay and is not answered by the Processor.
2.6 Personal data breaches. The Processor notifies the Controller without undue delay, and at the latest within 48 hours of becoming aware of a personal data breach affecting the Controller's data. The notice describes, as far as known, what happened, the data and data subjects affected, the likely consequences and the measures taken or proposed. The Processor updates the Controller as it learns more.
2.7 Assistance. The Processor gives the Controller the information it reasonably needs for data protection impact assessments and prior consultations (GDPR articles 35–36), taking into account the nature of the processing and the information available to the Processor.
2.8 Deletion and return. The Controller can export and delete its data at any time in the services. When the services end, the Processor deletes the Controller's personal data within 30 days, unless EU or member-state law requires it to be kept, and confirms the deletion in writing on request. Backups are overwritten within 7 days after that.
2.9 Audits. The Processor makes available the information needed to show compliance with this DPA. The Controller may audit once a year, or after a personal data breach, with 30 days' notice, at its own cost, during business hours and under confidentiality. A written questionnaire or an independent auditor's report may replace an on-site audit where it gives the same assurance.
2.10 Records. The Processor keeps a record of processing activities carried out on the Controller's behalf (GDPR article 30(2)).
3. AI processing
3.1 No training. Neither the Processor nor any AI Provider uses Customer Content to train or improve AI models. The Processor only uses AI Providers whose commercial terms forbid training on customer content.
3.2 What is sent. Only the content needed for the feature a user starts is sent to an AI Provider. For example: the transcript when a description is created, the process model when improvements are suggested, the step list when steps are classified. Login details, billing data and other customers' data are never sent.
3.3 Retention at AI Providers. AI Providers keep inputs and outputs only as long as their commercial terms allow for operating the service and detecting abuse, and at most 30 days, then delete them.
3.4 Voice. In a voice interview the user's speech is sent to the voice provider to be transcribed and answered in real time. Voices are used only for that. Neither the Processor nor the voice provider uses voices to identify people or to create voice profiles or voice clones. The voice provider does not keep audio recordings, and the transcript is stored in the services as part of the flow.
3.5 Outputs and human review. AI outputs are suggestions. Each output is shown to the user to accept, edit or reject before it is used: descriptions, diagrams, value classes, improvements, plans and business cases. The services make no decision by AI with legal or similarly significant effect on a person (GDPR article 22).
3.6 Ownership. Customer Content, including AI outputs based on it, belongs to the Controller.
3.7 Local option. For data that must not leave the Controller's environment, the Processor offers a local set-up of Ailean that runs an AI model on the Controller's own hardware. In that set-up no Customer Content is sent to the Processor or to any sub-processor, and this DPA does not apply to it.
4. Sub-processors and transfers
4.1 General authorisation. The Controller authorises the sub-processors listed in Annex 2. The Processor binds each sub-processor by written contract to data-protection obligations at least as strict as this DPA, and remains liable to the Controller for their performance.
4.2 Changes. The Processor gives at least 30 days' notice before adding or replacing a sub-processor, by e-mail to the Controller's account owner and by updating Annex 2 on this page. The Controller may object on reasonable data-protection grounds within that period. If the parties cannot agree, the Controller may end the affected service and receive a pro-rata refund of prepaid fees.
4.3 Where data is stored and processed. Customer Content is stored in the EU, and the services' servers process requests in the EU. Only the sub-processors marked in Annex 2 process data outside the EU/EEA.
4.4 Transfers outside the EU/EEA. Each transfer outside the EU/EEA relies on the sub-processor's certification under the EU–US Data Privacy Framework or on the European Commission's Standard Contractual Clauses (module 3, processor to processor), with supplementary measures where needed. On request, the Processor provides a copy of the relevant transfer terms; commercial details may be removed.
4.5 Government requests. If a public authority asks the Processor for the Controller's personal data, the Processor refers it to the Controller where the law allows, and challenges requests it considers unlawful.
5. Term, liability and precedence
5.1 Term. This DPA applies for as long as the Processor processes personal data on the Controller's behalf, including the deletion period in section 2.8.
5.2 Liability. Each party's liability under this DPA follows the limitations in the Processor's Terms of Service, except where the GDPR does not allow them to be limited.
5.3 Precedence. If this DPA conflicts with the Terms of Service or an order form on data protection, this DPA prevails.
5.4 Contact. Questions about this DPA and notices under it go to privacy@vimpl.com.
5.5 Law. This DPA is governed by Danish law. Disputes go to the courts of Copenhagen.
Annex 1 — Description of processing
| vimpl | Ailean | |
|---|---|---|
| Purpose | Provide digital boards for planning, workshops and project follow-up | Map, analyse and improve business processes with AI, and produce plans and exports |
| Nature of processing | Storage, display, sharing between invited users, export | Storage, AI processing (transcription, description, diagram, classification, suggestions), display, sharing in rounds, export |
| Data subjects | The Controller's users; people named on boards | The Controller's users; interviewees and round participants; people named in process descriptions, such as role holders |
| Personal data | Name, e-mail, login data, board content that names people, activity logs | Name, e-mail, login data; interview transcripts and, during a live voice interview, the user's voice; process content that names people or roles; usage logs |
| Special categories | Not intended; users are asked not to enter them | Not intended; voice is not used to identify anyone (section 3.4) |
| Duration | The term of the subscription, plus deletion under section 2.8 | The same |
| Location | EU (Annex 2) | EU storage and servers; AI processing as in Annex 2 |
The Controller's users can delete individual boards, flows and rounds at any time. Deletion takes effect at once in the service, and in backups when they are overwritten (section 2.8).
Annex 2 — Sub-processors
Authorised sub-processors as of the Effective Date. Changes follow section 4.2.
| Sub-processor | Service | Used for | Data | Location | Outside EU/EEA |
|---|---|---|---|---|---|
| Supabase Inc. | vimpl, Ailean | Database: accounts, boards, flows, rounds, preferences | All stored data | EU | No |
| Vercel Inc. | vimpl, Ailean | Hosting of the apps and their servers | Requests in transit, logs | Servers: EU (Frankfurt). Static files: worldwide network | Static files only |
| Anthropic PBC | Ailean | Text AI: descriptions, diagrams, classifications, improvements, plans | Content sent for the feature in use | US | Yes |
| ElevenLabs | Ailean | Voice interviewer (speech to text, spoken replies) and read-aloud; uses Anthropic (Claude) as its language model | Voice in real time, transcript | US | Yes |
| Stripe | vimpl, Ailean | Subscriptions and payments | Name, e-mail, billing details | EU and US | Yes |
| Resend | vimpl, Ailean | Account e-mails (sign-up, onboarding) | Name, e-mail | US | Yes |
| Google LLC | vimpl, Ailean | Sign in with Google | Name, e-mail | US | Yes |
Transfers outside the EU/EEA rely on the safeguards in section 4.4.
Annex 3 — Technical and organisational measures
| Area | Measures |
|---|---|
| Encryption in transit | HTTPS/TLS for all traffic to the apps, the servers and the sub-processors |
| Encryption at rest | Database encrypted at rest by the database provider |
| User access | Personal accounts; passwords stored only as bcrypt hashes; optional sign-in with Google; short-lived access tokens, with refresh tokens in httpOnly cookies |
| Separation between customers | Every request is checked against the signed-in user; boards, flows and rounds are served only to their owner or invited participants |
| Abuse protection | Rate limiting and security headers on the servers; AI calls only through the Processor's servers, never with keys in the browser |
| Staff access | Administrator rights limited to named accounts; access to Customer Content only as in section 2.2 |
| Availability and backups | Managed database and hosting; daily database backups kept for 7 days |
| Data minimisation | Only the content needed for a feature is sent to AI Providers; no audio recordings kept (section 3.4) |
| Incident handling | Breach procedure that meets the 48-hour notice in section 2.6 |
| Location | Database and servers in the EU |