Skip to content
DMSurvey Codingby Decision Models Beta
Your workspaceDeutsch

Annex S (Survey Coding) to the Data Processing Agreement

Version 1.0 · Last updated: 16 November 2026

This Annex S supplements the Data Processing Agreement (version 1.3.1 or a later version, "DPA") between the Customer ("Controller") and productivity-boost.com Betriebs UG (haftungsbeschränkt) & Co. KG ("Processor" or "we") for "Survey Coding by Decision Models" ("Survey Coding"). The Controller accepts this Annex S together with the DPA and the Survey Coding Additional Terms by clicking in Survey Coding before its first upload (section SC2.2 of the Additional Terms). We record the date and time, the accepted versions and the accepting account. Acceptance in electronic form satisfies Art. 28(9) GDPR. A German version exists; if the two versions differ, the German version prevails. A plain-language summary is on the Data handling page.

S1. Scope and relation to the DPA

S1.1 This Annex S applies to personal data that we process on behalf of the Controller in connection with Survey Coding. For this purpose, Survey Coding is part of the Service within the meaning of section 1.1 of the DPA, and the Main Contract includes the Survey Coding Additional Terms.

S1.2 All provisions of the DPA apply to Survey Coding unless this Annex S provides otherwise. For Survey Coding only, this Annex S takes precedence over the DPA as follows:

  • (a) Sections S2 to S6 replace sections 1 to 5 and 8 of Annex 1 of the DPA and supplement its section 6 (place of processing). In particular, the statements in Annex 1, section 5 that request and response bodies are not stored do not apply to Survey Coding: the Survey Coding application stores Customer Content for the retention period set out in section S5. For the inference step through the Decision Models API, Annex 1, section 5 continues to apply (section S4.2).
  • (b) Section S5 replaces section 11.1 of the DPA.
  • (c) Section S7 supplements Annex 2 of the DPA and takes precedence where it differs, in particular because the Survey Coding database and its backups contain Customer Content.
  • (d) Section S8 supplements Annex 3 of the DPA.

For all other services, the DPA and its Annexes remain unchanged.

S1.3 Account, billing and usage data of Survey Coding, which we process as a controller for our own purposes, are not covered by this Annex S (section 1.2 of the DPA); see section 2.11 of our Privacy Policy.

S1.4 The Controller's use and configuration of Survey Coding are part of its documented instructions (section 2.2 of the DPA), in particular: the upload, the choice of columns, the survey question text, the codebook, the masking option, the thresholds and calibration, review decisions, exports, the retention period of each Project and deletion.

S1.5 If the Controller is itself a processor for its own client (for example a market research agency), the Controller ensures that its client's instructions permit this processing; we then act as its sub-processor.

S2. Subject matter, nature and purpose

S2.1 Subject matter: coding of open-ended survey answers that the Controller uploads.

S2.2 Nature of the processing: receipt and storage of the uploaded file; reading it and taking over the chosen columns; optional masking of email addresses, phone numbers and IBANs; sending the text of each unique answer, together with the survey question text and the code definitions, to the Decision Models API on the EU tier, which computes the probability that each code applies; storage of the probabilities and suggested codes; display for review; recording of review decisions and codebook versions in an audit trail; creation of exports on request; deletion.

S2.3 Purpose: solely to provide the coding results, the review functions and the exports to the Controller. We do not use Customer Content for training, fine-tuning or evaluating models, for tuning prompts, templates or default settings, or for published quality figures (section SC8 of the Additional Terms).

S3. Types of personal data and categories of data subjects

S3.1 Types of personal data: determined by the Controller. Typically: the text of open-ended answers, which may contain names, contact details, descriptions of experiences, opinions and behaviour, and information about third parties; respondent IDs or other values of the ID column; the survey question text; codebook texts; and the account identifier of the user who made a review decision (audit trail). Answers may contain special categories of personal data (Art. 9 GDPR) even where the question did not ask for them; section 3.2 of the DPA applies.

S3.2 The uploaded file is kept only until the Controller confirms the column mapping. After that, we keep only the ID column, the chosen open-text column and the survey question text. If masking is chosen, only the masked text is stored and sent for coding.

S3.3 Categories of data subjects: determined by the Controller. Typically: survey respondents, such as customers, users, prospects and event participants of the Controller or of its clients; employees of the Controller or of its clients as respondents in employee surveys; people mentioned in the answers; and users of the Controller's account.

S4. Location of processing and storage

S4.1 Survey Coding application and live database (including the uploaded file until mapping, answers, results and audit trail): Hetzner Online GmbH, Helsinki (Tuusula), Finland, Hetzner data centre HEL1-DC6 (EU). The streaming replica on our second server at Hetzner HEL1-DC7, Finland (EU), receives deletions continuously, in step with the primary database. Local database dumps remain unencrypted on the database server at HEL1-DC6 for approximately two days.

S4.2 Coding (inference): the Decision Models API on the EU tier only. Survey Coding never uses the Peer-to-Peer tier, worldwide processing or network processing under the Peer-to-Peer Network Processing Addendum. The API gateway runs at Hetzner in Helsinki (EU) as set out in Annex 1, section 6 of the DPA; the GPU inference may be carried out by UpCloud Oy (EU data centres listed on the sub-processor page) and GPU Server Hub (4DataCenter Katowice, Poland). For the inference step, the statements and limits of Annex 1, section 5 of the DPA apply: the API gateway and usage database do not store the content of the requests.

S4.3 Customer Content is not transferred to third countries. Sign-in emails sent through Resend and payment data processed by Stripe contain no Customer Content (section S7.3).

S5. Retention and deletion

S5.1 Retention period: each Project is deleted automatically 30 days after it was created, unless the Controller sets a different period of up to 90 days after creation in the Project settings. From the end of the retention period, the Project is no longer accessible; it is deleted from the live database within 24 hours, normally within one hour. Deletion covers the uploaded file, the answers, the codebook and its versions, the probabilities, the results, the review decisions and the audit trail.

S5.2 Deletion now: the Controller can delete a Project or its whole account at any time in the app. Deletion from the live database takes effect immediately. We cannot restore deleted data on request.

S5.3 Backups: Backups of the Survey Coding database consist only of local database dumps, kept unencrypted on the same database server at HEL1-DC6, Finland, for approximately two days. Deleted Customer Content remains in backups until they are replaced in rotation, and is removed from all backups at the latest 7 days after deletion from the live database (local dumps are kept for about two days). We use backups only to restore the service after a fault or data loss. If we restore a backup, we delete again, before the data become accessible, all Projects whose retention period has ended and all Projects and accounts deleted after the backup was created; for this purpose we keep a record of deleted Project and account IDs without content.

S5.4 Copies for availability: the streaming replica on our second server at Hetzner HEL1-DC7, Finland (EU), receives deletions continuously, in step with the primary database.

S5.5 End of the contract: the Controller exercises its choice between deletion and return (Art. 28(3)(g) GDPR) by exporting its results before the retention period ends or before deletion. When the contract ends, all Customer Content is deleted under sections S5.1 to S5.3. We confirm deletion in text form on request (section 11.2 of the DPA). We are not required by law to keep Customer Content.

S5.6 Demo: the demo uses only a sample dataset provided by us and contains no data of the Controller. Demo projects are deleted 24 hours after creation.

S6. Duration

For the duration of the Main Contract for Survey Coding, until deletion under section S5 (section 1.4 of the DPA).

S7. Technical and organisational measures for Survey Coding

The measures in Annex 2 of the DPA apply, with the following additions and deviations:

S7.1 Access control per account: every Project belongs to one account. Survey Coding checks on every request that the Project belongs to the signed-in account; requests for other accounts' Projects are answered as "not found". Sharing Projects between accounts is not offered. Sign-in is by single-use email links valid for 20 minutes; requests for sign-in links are rate-limited. Session cookies are HttpOnly, Secure and SameSite=Lax and expire after 30 days at the latest. All state-changing requests are protected by a CSRF token.

S7.2 Encryption in transit: connections between the browser and decisionmodels.io use TLS (HTTPS). Survey Coding calls the Decision Models API over TLS; the path from the API gateway to the inference hosts is described in Annex 2, section 2.1 of the DPA.

S7.3 No content in logs and messages: Survey Coding is configured to write only identifiers, counts and status information to its application logs, and no answer texts, codebook texts or file contents. Sign-in emails contain only the sign-in link. Stripe receives only the plan, the Project ID and the account ID as payment metadata, and no Customer Content. These statements concern the Survey Coding application logs, the sign-in emails and the data sent to Stripe. Temporary files created while reading an upload are deleted after reading. Operating-system swap and crash-dump mechanisms on the server have not been excluded.

S7.4 Storage and separation: Customer Content is stored in a database of its own for Survey Coding, logically separated by account and Project. File names of uploads are never used as file paths. The live database is at Hetzner HEL1-DC6, Helsinki (Tuusula), Finland (EU). The streaming replica on our second server at Hetzner HEL1-DC7, Finland (EU), receives deletions continuously, in step with the primary database. Local database dumps remain unencrypted on the database server at HEL1-DC6 for approximately two days. The deviation from Annex 2, section 2.4 of the DPA ("no content") applies: the backups of the Survey Coding database contain Customer Content and are deleted as described in section S5.3.

S7.5 Access by our staff: the internal administration page shows only aggregate counts. Our staff access Customer Content only where this is necessary to remedy a fault reported by the Controller, to ensure security, or where the law requires it; Annex 2, section 2.2 of the DPA applies. Only named persons may access Customer Content; no automated agents or third-party AI tools read Customer Content.

S7.6 Testing and evaluation: development, testing and quality measurement use only our own test data and sample data, never Customer Content.

S8. Sub-processors for Survey Coding

S8.1 The following sub-processors process Customer Content of Survey Coding:

Sub-processor Service for Survey Coding Location
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany Hosting of the Survey Coding application, its live database, streaming replica and local database dumps; hosting of the Decision Models API gateway App and live database: HEL1-DC6, Helsinki (Tuusula), Finland (EU); unencrypted local dumps: same server, approximately two days; streaming replica: HEL1-DC7, Finland (EU), deletions in step with the primary; API gateway: Helsinki, Finland (EU)
UpCloud Oy (EU data centres listed on the sub-processor page) and GPU Server Hub (4DataCenter Katowice, Poland) GPU inference for the EU tier of the Decision Models API may be carried out by these providers EU, as stated in the sub-processor list

S8.2 Lium, independent GPU providers and the providers of the Peer-to-Peer network are not used for Survey Coding. Stripe and Resend receive no Customer Content; they are described in our Privacy Policy.

S8.3 The current list is the Survey Coding section of the sub-processor list. Sections 6.2 and 6.3 of the DPA apply to additions and replacements.

S9. Data subject requests

Section 8 of the DPA applies. Survey Coding does not currently offer deleting individual answers within a Project. To erase or correct the answer of an individual respondent, the Controller can delete the Project and upload a corrected file, or ask us for support at info@productivity-boost.com.

GuidesDecision Models Survey Coding · Beta
Data handlingImprintPrivacyTermsSurvey Coding Additional TermsDPA Annex S