Data Processing Agreement
Last updated: November 18, 2026
Admins can view a version of this agreement with their account details and download it as PDF in the app under Settings → Account → Data Processing Agreement.
Parties
This Data Processing Agreement ("DPA") is concluded between
- the customer (account holder of a Floxity account) as controller, hereinafter "Customer", and
- Sebastian Maronn Digital Experiences, Sebastian Maronn, Blankenburger Str. 22, 13156 Berlin, Germany as processor, hereinafter "Floxity".
This DPA forms part of the Floxity Terms of Service and applies as soon as Floxity processes personal data on behalf of the Customer. Version: November 18, 2026.
1. Subject matter, duration, nature and purpose
- Subject matter: provision of the Floxity survey platform (creation and publication of surveys, collection, storage, analysis and export of responses, notifications about new submissions by email, forwarding of submissions to the integrations and webhook addresses the Customer sets up, sending of verification codes and confirmation emails to respondents as instructed by the Customer, AI-assisted creation and translation of surveys, user management).
- Duration: the term of the contract under the Terms of Service.
- Nature of processing: collection, storage, organization, retrieval, analysis, display, export, transmission to sub-processors as listed in Annex 2, sending of submissions by email to the recipients the Customer chooses (users of its account and confirmed external addresses), transmission of submissions to the integrations (other services the Customer uses, e.g. a channel of a messaging service) and webhook addresses the Customer sets up, and erasure and anonymization, also automatically after the periods the Customer sets. Where an integration offers the choice, the Customer decides whether notification emails and messages to integrations contain the answers or only a notice. The Customer chooses these destinations and instructs Floxity to transmit to them; their operators (e.g. a messaging service, an automation service or the Customer's own systems) act for the Customer and are not sub-processors of Floxity.
- Purpose: provision of the Service to the Customer under the Terms of Service.
2. Types of personal data and categories of data subjects
- Respondents (persons answering the Customer's surveys): survey answers, including any personal data the Customer asks for in its surveys; time of opening and submitting a survey; where the Customer has the email address confirmed: a keyed hash of the address, the time of confirmation and, if the Customer allows one submission per address, a pseudonymous key per survey.
- Persons mentioned in survey content: any personal data the Customer includes in surveys.
- Users of the Customer's account (employees or other persons invited by the Customer): name, email address, role, preferences, usage times.
- External recipients of notifications (persons without an account whose email address the Customer adds to a workspace): email address, status and times of the confirmation, and the content of the notifications sent to them.
The Customer shall not collect special categories of personal data (Art. 9 GDPR) or data relating to criminal convictions (Art. 10 GDPR) with Floxity unless it has ensured that this is lawful and the measures in Annex 1 are appropriate for such data.
3. Instructions
- Floxity processes personal data only on documented instructions from the Customer, unless required to do so by Union or Member State law; in such a case, Floxity informs the Customer of that legal requirement before processing, unless the law prohibits this.
- The Terms of Service, this DPA and the Customer's use and configuration of the Service constitute the Customer's instructions. Further instructions can be given by email to support@floxity.com.
- Floxity informs the Customer immediately if it considers an instruction to infringe data protection law.
4. Confidentiality
Floxity ensures that all persons authorized to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. Currently, only the owner of Floxity has access to production data.
5. Security of processing
Floxity implements the technical and organizational measures described in Annex 1 (Art. 32 GDPR). Floxity may adapt these measures to technical progress, provided that the level of protection is not reduced.
6. Sub-processors
- The Customer grants general authorization to engage sub-processors. The sub-processors listed in Annex 2 are approved.
- Floxity informs the Customer of any intended addition or replacement of sub-processors at least 14 days in advance via its service notices to the Admins of the account. The Customer may object to the change within this period for important data protection reasons. If Floxity cannot accommodate the objection, the Customer may terminate the contract; Floxity refunds the price of unused purchased credits.
- Floxity imposes data protection obligations on sub-processors that are equivalent to those of this DPA. Transfers to third countries take place only in compliance with Chapter V GDPR (in particular an adequacy decision or Standard Contractual Clauses).
7. Assistance to the Customer
- Taking into account the nature of the processing, Floxity assists the Customer with appropriate measures in responding to requests from data subjects (Art. 12–22 GDPR). The Customer can view, export and delete responses itself in the Service. Floxity forwards requests from data subjects addressed to it to the Customer.
- Floxity assists the Customer in ensuring compliance with Art. 32–36 GDPR (security, notification of personal data breaches, data protection impact assessments, prior consultation), taking into account the information available to Floxity.
- Floxity notifies the Customer of a personal data breach without undue delay and at the latest within 48 hours after becoming aware of it. The notification contains the information available at that time in accordance with Art. 33(3) GDPR; further information is provided as soon as it becomes available.
8. Deletion and return of data
- The Customer can export its data at any time (Terms of Service, section 11). When the Customer deletes a survey, responses or the account, the data is deleted from the production database without undue delay.
- Submissions are deleted automatically once they are older than the storage period the Customer sets for its account, workspaces or surveys, at the latest after 365 days. The answers to questions the Customer marks are emptied (anonymized) once they are older than the anonymization period the Customer sets. Both are carried out every night and are final; deleted or emptied data cannot be restored. For a survey set to delete after forwarding, a submission (or its marked answers) is kept only until it has been transmitted to the Customer's integrations and deleted right afterwards, at the latest after 24 hours. The Customer decides on the periods, the storage of each survey and the marked questions; Floxity provides the means.
- Data that Floxity has transmitted on the Customer's instruction to integrations, webhook addresses or by email is not deleted or anonymized there by Floxity; the Customer and the operator of the destination are responsible for it.
- At the end of the contract, Floxity deletes all personal data processed on behalf of the Customer, unless Union or Member State law requires storage. Backups, and the data contained in them, are deleted after 7 days at the latest. Logs of the hosting providers are deleted after their short retention periods.
9. Information and audits
Floxity makes available to the Customer all information necessary to demonstrate compliance with Art. 28 GDPR and allows for and contributes to audits, including inspections, by the Customer or an auditor mandated by the Customer.
- Audits are primarily carried out by providing documentation: this DPA and its annexes, the certifications and audit reports of the subprocessors (e.g. ISO 27001 or SOC 2) and, on request, a written self-assessment by Floxity. Floxity provides this documentation free of charge.
- On-site inspections take place only if the documentation is demonstrably insufficient, after a personal data breach affecting the Customer's data, or if required by a supervisory authority. They must be announced in writing at least 30 days in advance, take place during normal business hours without disrupting operations, and are limited to once per calendar year unless there is a specific reason.
- The auditor must be bound to confidentiality and must not be a competitor of Floxity. Audits do not extend to data of other customers.
- The Customer bears the costs of on-site inspections, including reasonable compensation for the time spent by Floxity, unless the inspection reveals a material breach of this DPA by Floxity.
10. Liability and precedence
Liability is governed by Art. 82 GDPR and the Terms of Service. In the event of contradictions between this DPA and the Terms of Service regarding data protection, this DPA prevails.
Annex 1: Technical and organizational measures
Confidentiality
- Hosting with professional providers (Cloudflare, Supabase on Amazon Web Services in Frankfurt am Main) whose data centres have physical access controls.
- Two-factor authentication for all administrative accounts of Floxity where offered by the provider.
- Only the owner of Floxity has access to production systems and data.
- User authentication with hashed passwords; role-based access in the app (Admin, Editor, Viewer).
- Logical separation of customer data: every access is restricted server-side to the account of the logged-in user.
- Secrets and keys are stored in protected environment variables and not in source code.
Integrity
- Encryption of all connections with TLS (HTTPS).
- Validation of all input on the server.
- Changes to the application are versioned in a source code repository.
Availability and resilience
- Protection against attacks (DDoS protection and firewall by Cloudflare).
- Encryption at rest of the database and of stored files by the hosting providers.
- Backups at regular intervals, deleted after 7 days at the latest.
Procedures for regular review
- Documented procedure for handling personal data breaches.
- Review of sub-processors and measures when relevant changes occur.
- Data minimization: survey responses are stored without IP addresses.
- Storage limitation: automatic deletion and anonymization of submissions after the periods set by the Customer.
Annex 2: Approved sub-processors
- Supabase Pte. Ltd. (Singapore) – database, authentication; data location Frankfurt am Main, Germany; transfer basis: Standard Contractual Clauses.
- Cloudflare, Inc. (USA) – hosting, content delivery, security incl. bot protection, file storage (images uploaded by the Customer, stored in the EU), sending of emails to users of the Customer's account and of notifications about new submissions; transfer basis: EU-U.S. Data Privacy Framework and Standard Contractual Clauses.
- OpenAI Ireland Ltd. (Ireland), with processing in the USA and other third countries by OpenAI affiliates and their sub-processors (list: openai.com/policies/sub-processor-list) – only when the Customer uses AI-assisted generation or translation of surveys; survey content and prompts only, no responses; transfer basis: Standard Contractual Clauses or an adequacy decision (e.g. EU-U.S. Data Privacy Framework).
- Mailjet SAS (France) – service notices to admins of the Customer's account.