Pilot programme open: be one of the first publishers to launch on NewsroomCloud 🚀Apply
Shape 1
Shape 2
Legal

Data processing agreement

1. Parties

Controller: the customer who subscribes to NewsroomCloud (“Customer”).

Processor: Cloudorax UG (haftungsbeschränkt), Prenzlauer Allee 7, 10405 Berlin, Amtsgericht Charlottenburg, HRB 286107 B, USt-IdNr. DE465264832 (“Provider”).

This agreement forms part of the subscription contract (terms of service) between the parties.

2. Subject-matter, nature and purpose

Hosting, storing and processing data to operate the Customer’s news site and newsroom on the NewsroomCloud platform, for the term of the contract.

Types of data: account, contributor, subscriber, comment, usage, advertising and billing data. Data subjects: readers, subscribers, contributors, advertisers and the Customer’s staff.

3. Provider obligations

The Provider processes personal data only on documented instructions of the Customer (including the contract and the Customer’s configuration of the service), binds authorised persons to confidentiality, implements the measures in the annex (Art. 32 GDPR), assists with data subject requests and Art. 32–36 obligations, and informs the Customer if an instruction infringes data protection law.

4. Sub-processors

The Customer gives general authorisation for the sub-processors listed below. The Provider announces any addition or replacement at least 30 days in advance; the Customer may object on reasonable data protection grounds. The Provider imposes equivalent obligations on each sub-processor and remains liable for them.

5. Personal data breaches

The Provider notifies the Customer without undue delay after becoming aware of a personal data breach, with the information available to meet Art. 33/34 GDPR.

6. Audits

The Provider provides the information necessary to demonstrate compliance and allows audits by the Customer or a mandated auditor bound to confidentiality, on reasonable notice [confirm].

7. International transfers

Transfers outside the EU/EEA take place only on the basis listed for each sub-processor (adequacy decision, EU-US Data Privacy Framework or EU Standard Contractual Clauses).

8. Return and deletion

At the end of the contract the Provider returns or deletes all personal data at the Customer’s choice within [confirm] days, unless retention is required by law. Customers can export their content (WordPress WXR, media, subscribers, URL redirects) from the panel at any time.

9. Governing law

German law; place of jurisdiction Berlin [confirm].

Annex 1 — Sub-processors

2026-11-04 · /subprocessors

Components we run ourselves

We operate the following software ourselves on the hosting provider’s servers listed above; no further third party receives data for them.

  • PostgreSQL — Database
  • Redis / BullMQ — Queue and cache
  • MinIO (S3) — Media and backup storage
  • Meilisearch — Site search
  • Keycloak — Authentication and sessions
  • Sentry — Error monitoring
  • PostHog — Signup-funnel measurement; on customer sites, product analytics only after analytics-cookie consent

Annex 2 — Technical and organisational measures (Art. 32 GDPR)

1. Access control

  • Role-based access in the product (author, editor, moderator, admin and further roles) with capability checks on the server; least privilege for staff.
  • Single sign-on via a self-operated Keycloak identity server; sessions are issued and revoked there.
  • Two-factor sign-in (TOTP) is available to every account but is not enforced yet, including for our own staff. Repeated failed sign-ins trigger brute-force protection.

2. Tenant separation

  • Every customer (tenant) is logically separated in one database: tenant-scoped records carry a tenant id that the data-access layer injects and enforces; a query without tenant context fails instead of returning all tenants.
  • An automated cross-tenant regression suite (reads, writes and stamping across articles, users, media, comments, billing, webhooks, API keys, ads, audit) runs against a real PostgreSQL database.

3. Encryption

  • In transit: TLS between visitors and the edge (Cloudflare); edge to origin [confirm].
  • Credentials saved through the settings panel (for example SMTP passwords, payment-provider and API secrets) and two-factor secrets are encrypted at the application layer with AES-256-GCM. The master key is kept outside the database and its backups.
  • Not encrypted yet: credentials stored in a tenant’s integration settings, and settings saved before August 2026 until they are saved again or migrated. These values are masked in every API response; moving them to the same encryption is in progress.
  • We do not currently claim disk or volume encryption on the servers, and database backups are not separately encrypted.

4. Availability, backups and restore

  • A nightly PostgreSQL backup (pg_dump) is written to self-hosted S3-compatible object storage and kept for 30 days.
  • Not covered yet: an offsite copy (backups sit on the same host as the database), media files and the identity database.
  • Last documented restore drill: 2026-10-17 (run manually). The newest backup restored into an isolated database with 0 errors in about 2 minutes. Full service recovery has not been timed end to end, and scheduled weekly drills are prepared but not active yet.
  • Recovery objectives: RPO up to 24 hours (since the last nightly backup). RTO is not stated until full service recovery has been timed.

5. Logging and monitoring

  • Per-tenant audit log of administrative actions (actor, action, time) with archival to object storage.
  • Self-hosted error monitoring (Sentry) and health endpoints for the API and its dependencies; an external status monitor probes them from outside our hosting [confirm].

6. Data subject rights and deletion

  • Export of a user’s data in machine-readable form and admin-approved erasure that anonymises the user and disables the identity account.
  • Return or deletion of customer data at the end of the contract within [confirm] days, unless retention is required by law.

7. Incident handling

  • Runbooks for alerts, rollback and recovery; personal data breaches are reported to the controller without undue delay.