Data processing agreement
Version 2026-11-17
1. Parties and roles
This agreement is between you, the professional who uses Askwell (the "controller"), and Askwell (the "processor"). It applies to all personal data of your clients that Askwell processes for you, and it forms part of the terms of service. It meets the requirements of Article 28 of the General Data Protection Regulation (GDPR).
2. Subject, duration, nature and purpose
- Subject: providing Askwell, a service for sending assessments to clients, scoring them and keeping the results, notes and related records.
- Duration: from your acceptance until your practice is closed and its data erased (section 11).
- Nature: collection through client links, storage, encryption, scoring, display, export and erasure.
- Purpose: only to provide Askwell to you.
3. Types of data and data subjects
- Data subjects: your clients, and any other person whose details you enter.
- Personal data: identification details you choose to record (name, email, phone), client codes and tags, answers to assessments, scores and risk flags, your notes, and link and consent records.
- Special categories: data concerning health (Article 9 GDPR).
4. Your instructions
We process the data only on your documented instructions, which are your use of Askwell and this agreement, including transfers (section 8). If we believe an instruction breaks the GDPR or other law, we tell you. If the law requires us to process data in another way, we tell you first unless the law forbids it.
5. Confidentiality
Everyone authorised to process the data on our side is bound by a duty of confidentiality. We never access the content of your practice's data except when you ask us to, for example to investigate a problem you report, or when the law requires it.
6. Security
We take the technical and organisational measures listed in Annex 1, and we keep them up to date with the state of the art. Askwell gives us no way, in the application, to view your clients' data. Whoever administers the server holds the encryption keys and could technically decrypt data; we commit never to do so except as allowed in section 5, keep the keys apart from the database and backups, and log administrative access to the server.
7. Sub-processors
You give general authorisation for the sub-processors listed on the sub-processor page. We tell you at least 30 days before adding or replacing one, so you can object; if we cannot address an objection, you may close your practice before the change. We bind every sub-processor to the same data protection obligations as this agreement, and we remain responsible for them.
8. Location and transfers
The data is stored and processed on a server in the United Kingdom, under the European Commission's adequacy decision for the United Kingdom (Article 45 GDPR). We do not transfer it anywhere else. If that decision ends or is suspended, we move the data to the European Economic Area or put appropriate safeguards in place, and tell you first.
9. Helping you
- Requests from your clients: Askwell lets you export and erase a client's data; we help further where needed.
- Security, impact assessments and consultations: we give you the information you need about Askwell (Articles 32 to 36 GDPR), including our DPIA for the platform.
10. Personal data breaches
We notify you without undue delay, and we aim to do so within 48 hours of becoming aware of a breach affecting your data, so that you can notify the Hellenic Data Protection Authority within 72 hours where required. The notice describes what happened, the data and people likely affected, the likely consequences, and the measures taken or proposed. We add information as it becomes available.
11. End of the service
When your practice is closed, you can export your data for 30 days. After that we erase it from Askwell. Encrypted backups are overwritten within a further 30 days. We do not keep copies unless the law requires it, and in that case we tell you.
12. Demonstrating compliance and audits
We make available the information needed to demonstrate compliance with this agreement and allow audits by you or an auditor you appoint, with reasonable notice and confidentiality. Audits take place at most once a year, unless a breach or a supervisory authority makes another one necessary, and each party bears its own costs. We may first offer written answers or the results of an independent review, if they answer your questions.
13. Liability and precedence
Liability is governed by the terms of service. If this agreement and the terms conflict on data protection, this agreement prevails.
Annex 1: technical and organisational measures
- Encryption: client identity details, tags, answers, results, notes and two-step sign-in secrets are encrypted with AES-256-GCM before storage; keys can be rotated. Connections use HTTPS (TLS 1.2 or newer).
- Access control: every account uses a strong password and two-step sign-in (TOTP); accounts lock after repeated failures; sessions expire after inactivity. Each practice is separated from all others on every query. Clients reach only their own assessments, through a link and a separate PIN that are stored only as hashes; links expire, lock after wrong PINs and can be revoked.
- Logging: a tamper-evident audit log records access to and changes of client data, sign-ins and administrative actions; it contains identifiers, not names or answers.
- Application security: no third-party scripts, fonts or trackers; a strict content security policy; protection against cross-site request forgery; no personal data in addresses or server logs; rate limiting.
- Data minimisation and retention: you choose which identity details to record; results are deleted automatically after your retention period; closed practices are erased after 30 days.
- Availability: daily encrypted backups kept in the United Kingdom or the EEA, with restores tested at least every three months.
- Organisation: confidentiality commitments, least-privilege server access, and a written breach procedure.