Data processing agreement
PaperPlane Data Processing Agreement (Art. 28 GDPR)
Version: 1.0 · Effective: 27 October 2026
Between the Customer (controller) and META Frame Technologies Softwaredesign & Consulting GmbH (processor). This agreement forms part of the Terms of Service.
1. Subject matter and duration
The processor provides the PaperPlane Service. This agreement applies to personal data the processor processes on the Customer's behalf in the Customer's projects. It lasts as long as the processor processes such data.
2. Nature, purpose, data and data subjects
- Purpose: running submission, review and decision workflows for the Customer's events; hosting, backup, support and security.
- Data subjects: authors and co-authors, reviewers, committee members, organizers and other project participants.
- Categories of data: names, email addresses, affiliations, account identifiers; submission metadata and files; reviews, scores, bids, conflicts of interest, assignments, messages, decisions; custom form fields defined by the Customer; usage and log data related to projects.
- Special categories: not intended. The Customer must not collect them unless strictly necessary and must inform the processor in advance.
3. Instructions
The processor processes the data only on documented instructions from the Customer. The Terms of Service, this agreement and the Customer’s configuration of the Service are its instructions. The processor informs the Customer if it considers an instruction to infringe data protection law. The processor may also process the data where Union or Member State law to which it is subject requires this; in that case it informs the Customer of that legal requirement before the processing, unless that law prohibits such information on important grounds of public interest.
The AI features of the Service: canvas generate, transcription, and title generation can be used by any signed-in PaperPlane user; programme generate can be used by a project organizer or an admin; authors and reviewers on a personal link cannot use them. They cannot be switched off. Their use on project content is an instruction of the Customer.
4. Confidentiality
Persons authorized to process the data are bound to confidentiality.
5. Security
The processor implements the technical and organisational measures in Annex 1 and may update them provided the level of protection is not reduced.
6. Sub-processors
6.1 The Customer grants general authorization for the sub-processors in Annex 2.
6.2 The processor informs the Customer at least 30 days in advance of any intended addition or replacement. The Customer may object for important data protection reasons; if no solution is found, the Customer may terminate the affected service.
6.3 The processor imposes equivalent data protection obligations on each sub-processor and remains liable for them.
7. International transfers
Transfers outside the EU/EEA only take place where Chapter V GDPR is complied with (adequacy decision, including the EU–U.S. Data Privacy Framework, or Standard Contractual Clauses).
8. Assistance
The processor assists the Customer, taking into account the nature of processing, with:
- responding to data subject requests (the Service provides export, correction and deletion functions; the processor forwards requests it receives);
- security, breach notification, data protection impact assessments and prior consultation (Arts. 32–36 GDPR).
9. Personal data breaches
The processor notifies the Customer without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Customer data, with the information available at that time.
10. Deletion and return
At the end of the service, the processor, at the Customer's choice, deletes or returns all personal data processed on the Customer's behalf and deletes existing copies, unless Union or Member State law requires storage of the data. For that obligation to delete existing copies: live data is deleted or returned; copies in shared database backups and blob soft-delete age out on the Annex 1 retention; there is no targeted per-customer backup delete. The Customer makes this choice in the Switching Notice or by email to support@paperplane.services within the periods set out in section 10 of the Terms of Service (including the retrieval period). If the Customer makes no choice, the processor deletes the data in accordance with section 10 of the Terms of Service after giving the Customer the opportunity to export it.
11. Audits
The processor makes available the information necessary to demonstrate compliance, primarily through documentation and, where available, certifications of its hosting providers. On-site audits are possible with reasonable notice, during business hours, at most once per year unless there is a specific reason, and at the Customer's cost.
12. Liability
12.1 This agreement does not limit the rights of data subjects under Art. 82 GDPR or any liability that cannot be limited by law. The right of recourse between the parties under Art. 82(5) GDPR remains unaffected.
12.2 Between the parties, the limitations of liability in section 12 of the Terms of Service apply to claims under this agreement, to the extent permitted by law.
13. Precedence
In case of conflict between this agreement and the Terms of Service regarding the processing of personal data, this agreement prevails. This does not apply to liability between the parties, which is governed exclusively by section 12.
Annex 1 — Technical and organisational measures
- Encryption: TLS for all connections; encryption at rest for database and blob storage (Azure platform encryption).
- Access control: sign-in via Entra External ID; role-based project permissions (organizer, reviewer, author); least-privilege administrative access; administrative access logged.
- Separation: logical separation of Customer projects in the application.
- Availability: Postgres backup retention of 7 days and blob delete retention of 43 days, shared across customers, ageing out only when that retention expires, with no per-customer backup delete; infrastructure in Azure Germany West Central (Frankfurt).
- Secrets: application secrets stored as Container App secrets or encrypted infrastructure configuration, never in source code.
- Integrity: input validation; dependency and vulnerability scanning in CI; code review for all changes.
- Incident response: documented procedure for security incidents and breach notification.
- Staff: confidentiality obligations; data protection training.
Annex 2 — Sub-processors
| Sub-processor | Service | Location | Transfer mechanism |
|---|---|---|---|
| Microsoft Ireland Operations Ltd. | Azure Container Apps, Azure Database for PostgreSQL, Azure Blob Storage | Germany West Central (Frankfurt) | EU; DPF + SCC for exceptional support access |
| Microsoft Ireland Operations Ltd. | Entra External ID (sign-in) | EU | EU; DPF + SCC for exceptional support access |
| Microsoft Ireland Operations Ltd. | Azure Communication Services and Email (email delivery) | Germany | EU; DPF + SCC for exceptional support access |
| Microsoft Ireland Operations Ltd. | Azure AI Foundry (Azure OpenAI Service) | EU (Standard or Data Zone EU) | EU; DPF + SCC for exceptional support access |
| OpenAI Ireland Ltd. | AI features (OpenAI API) | United States | EU–U.S. Data Privacy Framework + SCC |
Paddle.com Market Ltd. (merchant of record for the purchase of the Service) processes only Customer billing data, as an independent controller. It is not a sub-processor for conference content.
See also Terms of Service and Privacy.