DPA Annex M (Moderation API)

Changes in 1.1 (2026-11-16): paid review removed, current acceptance required, backup details corrected and deletion log added.

Version 1.1 · Updated: 16 November 2026. If the language versions differ, the German version prevails.

This Annex M supplements the Decision Models DPA, version 1.3.1 or later between the Customer (Controller) and productivity-boost.com Betriebs UG (haftungsbeschränkt) & Co. KG (Processor) for the Moderation API. The Additional Terms form part of the Main Contract. Click acceptance before signup, checkout and each upload includes the DPA and this Annex; we record versions and UTC time. This electronic form satisfies Article 28(9) GDPR.

M1. Scope and instructions

The Moderation API is part of the Service for this purpose. All DPA provisions apply unless this Annex differs. For this service only, M2–M6 replace Annex 1 sections 1–5 and 8 and supplement its section 6; M5 replaces DPA section 11.1; M7 supplements Annex 2 and M8 supplements Annex 3. In-memory API inference remains governed by DPA Annex 1 §5. Storage statements there do not apply to stored migration content and custom policies described here. Other services remain unchanged. Account, billing, acceptance and security metadata processed for our own purposes follow the privacy addendum. Uploads, attribute and threshold choices, custom rules/examples, exports and deletion requests are documented instructions. If the Customer is a processor, it ensures its own client's authorisation.

M2. Subject matter, nature and purpose

We receive comment text, compute AI-generated attribute probabilities and return scores or threshold comparisons. Migration processing includes receiving and parsing CSV/JSONL, scoring, storing per-row results, computing aggregate correlations, flag rates and label metrics and providing exports. Custom-policy rules and examples are stored until deletion. A paid migration review is not offered at this time. The sole purpose is providing the requested service. Customer content is never used for training, fine-tuning, model evaluation, prompt tuning or published quality measurements.

M3. Personal data and data subjects

Determined by the Controller: comments, opinions, experiences and identifiers in uploaded columns, optional labels and Perspective scores, custom-policy rules and examples and generated scores. Text may mention third parties or special-category data under Article 9 GDPR; DPA section 3.2 applies. Data subjects may include users, commenters, people mentioned in comments and the Controller's personnel. The Controller ensures a lawful basis, minimises data and fulfils information duties; pseudonymous IDs are recommended.

M4. EU locations and inference path

The live database and local unencrypted dumps are at Hetzner HEL1-DC6, Finland (dumps retained for about two days), with a streaming replica at Hetzner HEL1-DC7, Finland. The replica mirrors deletions immediately. There is no offsite copy. Deleted content can remain in local dumps until rotation after about two days.

API texts are held in application memory only. They are not stored or logged by the Moderation API; our gateway does not store request content (DPA Annex 1 §5). The gateway path follows that section, EU tier only, never Peer-to-Peer or worldwide/network processing. EU GPU inference may be carried out by UpCloud Oy (EU data centres on the sub-processor page) and GPU Server Hub (4DataCenter Katowice, Poland). Content processing and storage stay in the EU. Stripe and Resend receive no customer content; account/payment data and transfer safeguards are described in the main privacy policy.

M5. Retention, return and deletion

API text is released from memory after the response. Migration files are deleted after scoring. Per-row migration results, including comment texts, expire after seven days and are removed from the live database by the hourly cleanup. Custom-policy content remains until policy or account deletion. Deleting an account removes its migration jobs and policies immediately. Export before expiry or deletion; at contract end content is deleted under these periods. On request we confirm deletion in text form under DPA section 11.2. No statutory duty requires keeping customer content.

The live database and local unencrypted dumps are at Hetzner HEL1-DC6, Finland (dumps retained for about two days), with a streaming replica at Hetzner HEL1-DC7, Finland. The replica mirrors deletions immediately. There is no offsite copy. Deleted content can remain in local dumps until rotation after about two days. A content-free deletion log records object type, SHA-256 of the object identifier, UTC deletion time and reason for uploads, migration results, policies and accounts, including retention cleanup. It is used to re-delete content after a restore. Before restoring a snapshot, operators must preserve the current deletion log independently of that snapshot and replay it, then run retention cleanup before allowing traffic. Deletion records are retained for recovery and contain no customer content.

M6. Duration

For the Main Contract's duration until deletion under M5. Export implements return under Article 28(3)(g) GDPR; alternatively the Controller instructs deletion.

M7. Technical and organisational measures

Annex 2 applies with these additions: account-scoped access checks; unguessable 256-bit anonymous job capabilities; single-use 15-minute email links; 30-day Secure, HttpOnly, SameSite=Lax sessions; CSRF on state-changing browser requests; upload limits and filenames never used as paths; TLS browser and gateway connections. The gateway-to-inference path follows Annex 2 section 2.1. Application logs contain identifiers, counts, status and timing, not comment or policy content. Sign-in mail contains only the sign-in information and link. Stripe metadata contains account/plan identifiers, no customer content. Stored migration content and policies in this separate database and its backups are exceptions to Annex 2's no-content storage statements. OS swap and crash dumps are not excluded. Only named persons may access content where necessary for a customer-reported fault, security or law; no automated agents or third-party AI tools read customer content. Development and evaluation use our own test data only.

M8. Sub-processors

  • Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany: app/live database/local dumps at HEL1-DC6 Finland, replica HEL1-DC7 Finland; no offsite copy; EU gateway hosting.
  • UpCloud Oy (EU data centres listed on the sub-processor page) and GPU Server Hub (4DataCenter Katowice, Poland): EU inference may be carried out by these providers.

The current sub-processor list applies; DPA sections 6.2 and 6.3 govern changes. No P2P providers are used. Cloudflare R2 is not used for this database. Stripe and Resend receive no customer content. A review queue is not currently offered; introducing one requires a future Annex M version and notice before launch.

M9. Data subject requests

DPA section 8 applies. For a correction or erasure request, delete the affected account or contact info@decisionmodels.io; export and re-upload corrected data if needed. German controlling version.