Public sample for processing under EU GDPR Article 28, with annexes covering processing, safeguards, providers and deletion.
Last updated: 16 October 2026
1. Parties
The commissioning practice is the controller. Its legal entity, address, country, authorized representative and privacy and instruction contacts are recorded in the acceptance receipt when the agreement is concluded.
The processor is Volker Brauer, trading as Asklivio, c/o MDC Management#4722, Welserstraße 3, 87463 Dietmannsried, Germany. Contract, instruction and privacy contact: contact@asklivio.de.
2. Subject matter, roles and duration
Asklivio processes the data described in Annex 1 on behalf of the practice to provide, operate and support its website assistant. The practice determines the purposes, permitted content, form fields and recipients. This DPA supplements the service agreement and applies for the duration of the commissioned processing, including its orderly termination. Protection duties continue until all data has been deleted.
Asklivio acts as an independent controller for its own contract administration, billing and business communications where it determines their purposes and means. Patient inquiries are not used for these purposes. This DPA addresses the EU GDPR; it does not replace a HIPAA Business Associate Agreement or any required UK addendum.
3. Instructions and the practice’s responsibilities
Asklivio processes data only on documented instructions, including for international transfers. The agreement, annexes and traceable saved settings form the initial instructions. Additional instructions are given in writing and checked for authorization. Legally required processing is communicated in advance unless the law prohibits this.
If Asklivio considers an instruction to infringe data protection law, it promptly informs the practice and suspends the affected processing until resolved. The practice is responsible for its legal bases, including GDPR Article 9 where relevant, patient notices, authorized recipients and content, and staff permissions. This does not relieve Asklivio of its own obligations.
4. Confidentiality and professional secrecy
Access is limited to people who need it for their duties and are bound by confidentiality obligations or an appropriate statutory duty of secrecy. These obligations continue after their work ends. Where Asklivio participates in a professional activity within German Criminal Code section 203, it protects the professional secrets disclosed to it and ensures corresponding commitments from other participating persons.
Support access is limited to what is necessary for a documented reason. General support inquiries must not contain patient data; any necessary sensitive information is exchanged only through a separately agreed, suitable protected channel.
5. Security of processing
Asklivio implements appropriate technical and organizational measures under GDPR Article 32, taking account of health-related data, the state of the art and the risks. Annex 2 describes the measures. Their effectiveness is reviewed regularly and following material changes or security incidents. Changes must not reduce the agreed protection level; material changes are documented and communicated.
Email delivery uses a process suitable for the intended data. Ordinary email is not automatically end-to-end encrypted. A notice to patients does not replace these obligations.
6. Subprocessors and international processing
The practice authorizes the subprocessors identified in the Annex 3 provided when the agreement is concluded, for the stated activities. Asklivio gives written notice of additions or replacements at least 14 calendar days before their intended use, including their activities, processing locations and any transfer basis. The practice may object within that period on reasonable data protection grounds.
While an objection is being resolved, the affected practice’s data is not sent to the disputed provider. If no lawful alternative is possible, the affected service may be terminated. Updating the public list does not replace contractually required advance notice.
Asklivio binds subprocessors to the same relevant data protection obligations, checks their sufficient guarantees and remains responsible for their performance. Processing outside the EEA, including remote access, takes place only within documented instructions and subject to GDPR Chapter V. This DPA is not itself an international transfer mechanism.
7. Assistance and individual rights
Taking account of the nature of processing and available information, Asklivio assists the practice with individual rights and its obligations under GDPR Articles 32–36, including security assessments, data protection impact assessments and necessary consultations. Requests received directly concerning data processed on behalf of the practice are forwarded promptly; Asklivio does not decide them independently unless required by law.
8. Personal data breaches
Asklivio notifies the practice without undue delay after becoming aware of a breach affecting personal data processed on its behalf, using the designated privacy contact. Initial notification is not withheld until the investigation is complete. It includes, as available, the nature and scope, affected data and people, likely consequences, response measures and a contact. Missing information follows without undue delay.
Asklivio limits harm, preserves necessary evidence and assists with assessment and notification. Each party’s own notification obligations remain unaffected.
9. Evidence and audits
Asklivio provides the information necessary to demonstrate compliance with this agreement and GDPR Article 28 and allows and contributes to audits, including inspections by the practice or an auditor bound by confidentiality. Routine audits are reasonably announced; incidents or justified urgency may require short-notice audits.
Other customers and unrelated business secrets are protected without obstructing the audit. Suitable evidence does not replace further necessary inspection. Statutory audit and assistance rights must not depend on advance payment; any separate charge for additional services requires a lawful agreement.
10. Return, deletion and termination
At the end of the processing services, Asklivio returns existing data in an agreed commonly used format or deletes it, at the practice’s choice. Remaining copies are also deleted after return unless Union or Member State law requires retention. Exceptions are communicated with their scope, legal basis and duration; retained data remains protected and is not used for other purposes.
Annex 4 describes periods and procedures. Subprocessors are included in deletion, and completion is confirmed on request. Restores must not permanently undo completed deletions. Messages already received in the practice’s inbox are the practice’s responsibility; this does not remove deletion duties for copies held by Asklivio or its providers.
11. Unlawful processing and precedence
If material obligations are breached, the practice may suspend the affected processing until remedied. If lawful continuation is impossible or a serious breach is not remedied within a reasonable period, the affected service may be terminated. Asklivio promptly reports obstacles. This agreement takes precedence over general service terms concerning protection of data processed on behalf of the practice. Mandatory law, individual rights and statutory liability, including GDPR Article 82, remain unaffected.
12. Conclusion and annexes
The agreement is concluded in writing or in a demonstrable electronic form. The complete practice-specific version and annexes are provided and bindingly agreed before processing begins. The signatory’s identity and authority, acceptance time, version and checksum are recorded. Both parties receive the agreed version in a form they can retain.
Annexes 1 (processing), 2 (safeguards), 3 (subprocessors) and 4 (retention and deletion) form part of the agreement. Viewing this public sample does not constitute acceptance or amend an existing agreement.
Annex 1 · Processing
Purposes and operations: providing and operating the practice assistant, managing approved practice content and visitor sessions, receiving and forwarding administrative inquiries to the designated practice inbox, and necessary support, abuse prevention and troubleshooting. Operations include collection, organization, storage, retrieval, disclosure, restriction and deletion within the agreed scope.
People concerned: patients, prospective patients, inquiring relatives or representatives, website visitors, practice staff and business contacts.
Data categories: names, callback numbers, email addresses where applicable, preferred contact times and administrative appointment requests; IP addresses in connections and technical logs, session identifiers, timestamps, language, website origin and selections; business contact details and permission assignments.
The scope is limited to callback details and appointment organization. Symptoms, diagnoses, findings, medication, prescription requests and treatment records are not intentionally requested. The association of an inquiry with a practice may itself constitute health data under GDPR Article 9; accidentally supplied medical information also requires appropriate protection.
The service does not replace patient records, medical advice, diagnosis or emergency care. Patient inquiries are not used for advertising or training Asklivio’s own models and are not passed to optional AI translation.
Annex 2 · Technical and organizational measures
Access and tenant separation
Password hashing, server-side sessions, Secure/HttpOnly cookies, CSRF checks, and server-side role and tenant checks. Password confirmation for agreement acceptance and billing administration.
Administration
MFA for AWS administrative access, limited operational roles and no publicly accessible database. Documented maintenance access and regular permission reviews.
Forms and data minimization
Checks of approved forms, fields, origins, sessions and volumes; recipients taken from practice settings. No form answers in the receipt table. Technical identifiers instead of message text in the delivery journal; open and click tracking disabled.
Encryption and backups
HTTPS for the portal/API and Paubox; certificate-verified TLS to the database. Encrypted AWS volumes, database and file backups. Protected key management and separated access roles.
Operations and recovery
Protected audit trails with minimized content, alert monitoring, security updates and regular restore checks. Completed deletions are reapplied before resuming service after a restore. Incidents are handled under clause 8.
These measures do not promise end-to-end encryption of all messages, exclusively European processing throughout the entire provider chain, independent certification or uninterrupted availability.
Annex 3 · Subprocessors and data flows
Amazon Web Services EMEA SARL
38 Avenue John F. Kennedy, L-1855 Luxembourg, Luxembourg
Activity
Hosting of the API, customer portal and widget; database, files and backups; key management, minimized monitoring, audit trails and maintenance.
Data categories
Practice configurations, accounts, sessions, technical receipts and inquiry data required for the respective processing step.
Processing locations
Regional application resources in Frankfurt, Germany (eu-central-1). Other AWS entities and data flows depend on the service used and AWS contractual documentation. Selecting a region does not promise exclusively European processing across the entire provider chain.
Paubox, Inc.
5 Third Street, 324, San Francisco, CA 94103, USA
Activity
Email API for delivery of administrative practice inquiries and service messages, and processing delivery status.
Data categories
Recipient and sender details, message text, necessary attachments, technical delivery and log data, and protected message copies where applicable.
Processing locations
United States. Paubox uses AWS infrastructure. The email processing path is not restricted to the EU.
This overview covers Asklivio’s direct subprocessors for the described practice-assistant service, not every company in their downstream provider chains. International processing must meet the applicable contractual and legal requirements; this list is not itself a transfer mechanism or a certification.
The practice selects its recipient inbox and email provider. Stripe is not a recipient of patient forms. IONOS hosting of the public website, sales-demo booking and general business communications are separate from the AWS/Paubox practice-inquiry path. Patient form answers are not passed to optional AI import or translation.
The applicable transfer basis and any supplementary safeguards must be specified in the practice-specific contractual documentation before the relevant transfer. This public sample does not supply or replace Standard Contractual Clauses.
Annex 4 · Retention, return and deletion
Form answers
Processed in the browser and API memory and sent through Paubox. The form delivery path does not store answers in the application database. Provider and inbox copies are handled separately.
Technical form receipts
Eligible for deletion after 72 hours; bounded hourly cleanup with backlog monitoring, not a promise of deletion at an exact second.
Sessions and tokens
Widget sessions: valid for 30 minutes, with sessions and events eligible for cleanup 72 hours after expiry. Portal sessions: 30 days after expiry, idle expiry or revocation. Confirmation, reset and address-change tokens: seven days after expiry, use or cancellation.
Practice configuration and backups
Configuration is held for the commissioned term; JSON export and authorized deletion within 30 days after assessing necessary retention. Automated database/server backups: seven days; no ordinary use of deleted data from backups.
Working and rollback copies
Working/export files are removed within seven days after their purpose ends; migration/rollback copies seven days after successful acceptance. Necessary exceptions are reviewed at least every 30 days.
Delivery and security evidence
No message text in the Paubox journal. Tracking IDs and polling diagnostics for completed deliveries are minimized in the next successful bounded run after 30 days without a relevant change. Technical suppression records, deletion registers and necessary security/contract evidence are handled separately according to their evidentiary and protection purposes and regularly reviewed for necessity.
Paubox and the practice inbox
Paubox is included in return and deletion requests and completion is followed up. No single blanket deletion period is promised for all provider content, logs and backups. The practice deletes messages already delivered to its inbox under its own retention policy.
Periods apply by data category. A retention duty for billing or security evidence does not justify keeping all patient inquiries. Mandatory retention is limited to its lawful purpose; data already deleted is not recreated solely for a later return request.