Data Processing Agreement (DPA)

This translation is provided for information only. The German version is legally binding; German law applies.

Version 2026-11-13

This agreement supplements the Terms and Conditions of tiaki, in particular § 14. It applies to the personal data you process in your workspace (content and contact data of third parties). For your account, contract and billing data we are ourselves responsible; the Privacy Policy applies to that, not this agreement.

The DPA is concluded in tiaki under Settings › Contracts and applies with the click for the workspace for which you conclude it.

Contracting parties

Controller (customer): the tiaki customer who concludes this agreement for their workspace (“you”).

Processor: INREMA Unternehmensberatung GmbH, Rentmeister-Wilthelm-Weg 16, 33181 Bad Wünnenberg, Germany, represented by the managing director Tanja Rüdiger, Local Court (Amtsgericht) Paderborn HRB 14352, email hallo@tiaki.de (“INREMA”, “we”).

We are not obliged to appoint a data protection officer. The contact for data protection is hallo@tiaki.de.

§ 1 Subject matter and duration

(1) We process personal data on your behalf insofar as you process it with tiaki: posts and media, inbox and messages, comments and reviews, contacts and customers, submissions from forms and landing pages, short link and bio page statistics, and WhatsApp messages.

(2) This agreement applies for the duration of the usage contract under the Terms and Conditions. It ends when that contract ends, but, after fulfillment of the obligations to delete and return under § 5 (6), at the earliest with deletion.

§ 2 Nature and purpose of the processing

(1) Nature: collecting, recording, storing, organizing, retrieving, modifying, transmitting to the networks you have connected, displaying, deleting. This includes processing by tiaki’s AI features insofar as you use them.

(2) Purpose: providing the functions of tiaki according to the service description in the main contract: creating, planning, approving and publishing posts, handling messages, comments and reviews in the inbox, running workflows, maintaining contacts, providing customer pages.

§ 3 Type of personal data

Depending on what you process in your workspace, the following data may be affected:

  • names, identifiers and profile pictures of people who interact with your connected profiles (e.g. commenters, senders of messages, reviewers);
  • phone numbers, email addresses and other contact data of your contacts and customers, including WhatsApp identifiers;
  • content of comments, messages and reviews, including images, documents and voice messages;
  • consents of your contacts with time, wording and proof;
  • entries in forms and landing pages that you provide with tiaki;
  • files, images and videos that you upload and that may show people;
  • click counts of your short links and bio pages (without storing the IP address);
  • name, role and actions of your team members in your workspace log.

You may not process special categories of personal data (Art. 9 GDPR) and data subject to professional secrecy without your own examination. tiaki is not designed for this (Terms and Conditions § 9).

§ 4 Categories of data subjects

Affected are your team members, followers, commenters, senders of messages and reviewers on your connected profiles, your contacts and customers including WhatsApp contacts, as well as visitors and submitters on your customer pages (bio page, landing pages, short links, shared files).

§ 5 Obligations of the processor

(1) Instructions. We process the data only on your documented instructions. This agreement and your settings and entries in tiaki are the instruction. Further instructions require text form. If we consider an instruction to be unlawful, we tell you immediately.

(2) Confidentiality. Persons who process data are bound to confidentiality or subject to a statutory duty of secrecy.

(3) Security. We take the technical and organizational measures under Art. 32 GDPR that are set out in Annex 3 and continue to develop them. The level of protection does not decrease in the process.

(4) Sub-processors. You authorize the use of the sub-processors in Annex 2. We announce new or replaced sub-processors by email at least four weeks in advance. You may object for good cause relating to data protection; if we do not agree, you can terminate the contract as of the time of the change. A contract exists with every sub-processor that imposes on it the same data protection obligations as we have towards you.

(5) Support. We support you, within what is possible and reasonable, with requests from data subjects (access, rectification, erasure, restriction, portability) and with your obligations under Art. 32 to 36 GDPR. We forward requests from data subjects that reach us directly to you.

(6) Deletion and return. After the contract ends we delete your data within the periods in Annex 3 section 5, unless a statutory retention obligation prevents this. Until then you can export your content insofar as the application provides for it.

(7) Evidence and audits. We provide you with the information you need to demonstrate compliance with the obligations under Art. 28 GDPR and enable audits by you or an auditor you appoint. You announce audits at least 14 days in advance; they must not disrupt operations unreasonably and take place only to the extent the purpose requires.

§ 6 Obligations of the controller

(1) You are the controller for the data in your workspace and for the lawfulness of the processing. This concerns in particular legal bases, necessary consents (e.g. for advertising by WhatsApp or email) and informing your contacts, for example in your own privacy policy.

(2) You give instructions in text form; settings in tiaki count as instructions.

(3) You tell us immediately if you notice errors or irregularities in the processing.

(4) You do not process special categories of personal data or data subject to professional secrecy without having first examined the legal basis and protective measures yourself.

§ 7 Sub-processors and third countries

(1) The sub-processors used when the contract is concluded are listed in full in Annex 2.

(2) Data reaches a country outside the EEA only if a safeguard under Art. 44 et seq. GDPR exists, stated per sub-processor in Annex 2: an adequacy decision (EU-US Data Privacy Framework) or standard contractual clauses.

(3) AI assistants that you connect (e.g. ChatGPT or Claude via mcp.tiaki.de) are not our sub-processors. You choose and connect them yourself and decide which rights and workspaces they receive. We have no influence on their processing and conclude no contract with their providers. You clarify the data protection basis for this yourself with the provider.

(4) Networks and recipients on your instruction. Meta (Facebook, Instagram, Threads), LinkedIn and Google (Business Profile) are not sub-processors. They receive data because you connect your profile and trigger publishing or replying yourself, and they stand in a contractual relationship of their own with you. The same applies to your WordPress website, your own mail servers that you store, and webhooks and API callers that you set up. Annex 2 no. 7 applies to the WhatsApp Business Cloud API.

(5) tiaki’s AI features. We use the AI features in tiaki ourselves; the providers (OpenAI and, if it is unavailable, Anthropic) are therefore our sub-processors (Annex 2). Under our contracts with these providers, the transmitted content is not used to train the models.

§ 8 Personal data breaches

We inform you immediately, and at the latest 24 hours after becoming aware, if the security of data in your workspace has been breached. The notification contains, as far as known: the nature of the breach, the categories of data and persons affected, the likely consequences and the measures taken or proposed. The notification to the supervisory authority (Art. 33 GDPR) and the notification of data subjects (Art. 34 GDPR) lie with you as controller; we support you in this.

§ 9 Liability

Art. 82 GDPR applies to liability; between us, § 16 of the Terms and Conditions applies in addition.

§ 10 Final provisions

(1) German law applies; § 19 of the Terms and Conditions applies accordingly to the place of jurisdiction. Only the German version of this agreement is binding.

(2) If a provision is invalid, the rest of the agreement remains valid. In the event of conflicts between this agreement and the Terms and Conditions, this agreement prevails insofar as the processing of personal data is concerned.

(3) All annexes are on this page and are part of the agreement.

Annex 1 – Subject matter of the processing

Subject matter

Provision of the tiaki software: planning and publishing posts, inbox, workflows, contacts, customer pages and AI features.

Categories of data subjects

Team members; followers, commenters, senders of messages and reviewers on the connected profiles; contacts and customers including WhatsApp contacts; visitors and submitters on the customer pages.

Types of data

Names, identifiers, profile pictures, phone numbers, email addresses, content of comments, messages and reviews including media, consents with proof, entries in forms and landing pages, click counts without IP address, the customer’s files.

Special categories

Not intended (see § 3 and § 6 (4)).

Duration

Term of the usage contract plus the deletion periods in Annex 3 section 5.

Annex 2 – Sub-processors

All sub-processors on this list are authorized upon conclusion of the contract. We announce changes four weeks in advance by email under § 5 (4).

1. IONOS SE

  • Address: Elgendorfer Str. 57, 56410 Montabaur, Germany
  • Service: hosting of the application, the database and background processing on dedicated servers, and storage of backup copies of the files
  • Location: data centers in Germany, ISO 27001 certified
  • Third-country safeguard: not required (no third country)

2. Cloudflare, Inc.

  • Address: 101 Townsend St., San Francisco, CA 94107, USA
  • Service: delivery, protection against attacks and automated access (web application firewall, bot protection, rate limits, Turnstile), encrypted tunnel to the servers; Cloudflare R2 as file storage for uploaded files and as storage for an encrypted backup copy
  • Location: global network; storage location of R2: EU
  • Third-country safeguard: USA: EU-US Data Privacy Framework, additionally EU standard contractual clauses

3. DomainFactory GmbH

  • Address: Oskar-Messter-Straße 33, 85737 Ismaning, Germany
  • Service: hosting and email services
  • Location: Germany
  • Third-country safeguard: not required (no third country)

4. OpenAI Ireland Ltd.

  • Address: 1st Floor, The Liffey Trust Centre, 117–126 Sheriff Street Upper, Dublin 1, Ireland
  • Service: tiaki’s AI features (texts, reply suggestions, classification of messages, images) via the programming interface; no training with your inputs
  • Location: Ireland, with processing also in the USA
  • Third-country safeguard: USA: EU standard contractual clauses

5. Anthropic Ireland, Limited

  • Address: Dublin, Ireland (parent company Anthropic, PBC, USA)
  • Service: AI features of tiaki, only if OpenAI is unavailable; no training with your inputs
  • Location: Ireland, with processing also in the USA
  • Third-country safeguard: USA: EU standard contractual clauses

6. Twilio Ireland Limited

  • Address: 25–28 North Wall Quay, Dublin 1, Ireland (parent company Twilio Inc., USA)
  • Service: sending the SMS confirmation codes to the user’s mobile number; your contacts’ data is not transmitted in the process
  • Location: Ireland, with processing also in the USA
  • Third-country safeguard: USA: EU-US Data Privacy Framework and EU standard contractual clauses

7. Meta Platforms Ireland Limited (only if WhatsApp is connected)

  • Address: Merrion Road, Dublin 4, D04 X2K5, Ireland
  • Service: WhatsApp Business Cloud API: delivery and receipt of your company’s WhatsApp messages. Meta is a sub-processor only if you connect WhatsApp. § 7 (4) applies to the other Meta networks.
  • Location: Ireland, with processing also in the USA
  • Third-country safeguard: USA: EU-US Data Privacy Framework, additionally standard contractual clauses

8. INREMA’s own infrastructure (Germany)

  • INREMA mail server: sending of system emails and of the emails from your workflows
  • Backup on INREMA-owned hardware: encrypted backups of database and files
  • Administration and monitoring: receiving server logs, monitoring, release of keys at startup (two separate key servers)
  • Location: Germany; no third-country safeguard required. These are not third parties but our own technology.

Recipients on your instruction (not sub-processors)

Meta (Facebook, Instagram, Threads, Messenger), LinkedIn (LinkedIn Ireland Unlimited Company, Wilton Plaza, Wilton Place, Dublin 2, Ireland) and Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland), your WordPress website and its host, your own mail servers that you store, AI assistants that you connect, and webhooks and API callers that you set up. See § 7 (3) and (4).

Further service providers without contract data

Stripe Payments Europe, Ltd. (payment) and Haufe Service Center GmbH with Lexware Office (invoices) process only contract and billing data for which we are ourselves responsible. They receive no content from your workspace.

Annex 3 – Technical and organizational measures (Art. 32 GDPR)

1. Confidentiality

Physical access control

  • The servers are located in the hosts’ data centers under Annex 2; physical access control lies with the host. IONOS’s data centers are certified to ISO 27001.

System access control

  • User login with password (at least 12 characters, stored as an Argon2id hash) and mandatory two-factor authentication (app code). Unknown devices are additionally confirmed by email.
  • Login runs in a dedicated login service on a dedicated virtual machine. The application has no access to password hashes and two-factor secrets.
  • Throttling and blocking after failed attempts (per account and IP address, increasing waiting time, IP block of up to 24 hours, also at the edge at Cloudflare) as well as rate limits for login, registration and the programming interface; Cloudflare Turnstile for login and registration.
  • Server administration only with an SSH key, without root login, only via a private network with individually approved paths.
  • No publicly reachable ports on the application servers. Access from outside runs only through the Cloudflare tunnel; access bypassing the tunnel is rejected.

Data access control

  • Database: a separate role per service with minimal rights, row-level security on every table with tenant data, tenant context only via checking database functions. The database is reachable only via TLS with certificate verification and only from approved servers.
  • Roles in the workspace (owner, manager, employee). Sensitive actions (connecting or disconnecting a profile, granting API or AI access, switching on direct publishing, changing rights) require renewed confirmation with the second factor.
  • API and AI access (OAuth 2.1 with PKCE) is bound to exactly one user, one workspace and one scope of rights, expires and can be revoked. Every call re-checks workspace, user and right.
  • Access keys to networks, two-factor secrets and mail server passwords are never displayed, output or logged.

Separation control

  • Every workspace is a tenant. Separation takes place on several levels: service layer, row-level security in the database, a separate data key per tenant, access bound to the tenant, and logging. An automated mandatory test checks that one tenant cannot access any resource of another tenant.
  • The functions run on separate virtual machines (edge with tunnel, login, application, database, background processing, virus scan).

Pseudonymization and encryption

  • Click counts for short links and referral links are stored without the IP address, only as an irreversible check value. Codes, links and session identifiers exist only as hashes.
  • In logs, phone numbers are shortened; message contents are not in logs.
  • Transport: TLS (at least 1.2, HSTS) between browser and Cloudflare and between Cloudflare and the servers (“Full (strict)”); TLS with certificate verification to the database; internal paths additionally over an encrypted private network.
  • Secrets at rest: envelope encryption with AES-256-GCM and a separate data key per tenant. The master key is never on disk in plain text; it is released at startup via two separate key servers (Tang, one of two is enough).
  • The application’s secrets are stored on the servers only in sealed form and are unlocked into memory only at startup.
  • Files are stored encrypted in storage (R2) and are delivered only via tiaki’s own addresses, not via storage addresses. Backups are encrypted.

2. Integrity

Transfer control

  • Outgoing connections to the networks run only via fixed target lists and only over HTTPS.
  • Calls to customer sites (WordPress, webhooks) run only through a checked egress point: HTTPS on port 443 only, public addresses only, protection against DNS rebinding, no redirects, size and time limits, signature with HMAC-SHA256.
  • Incoming callbacks from the networks are accepted only with a valid signature; those that cannot be matched are discarded and logged.

Input control

  • Immutable log of every write action (who, workspace, what, when, from where; insert-only).
  • System logs of all servers and audit logs go in real time to a separate log server, where an attacker on the source server cannot delete them. If delivery fails, this triggers an alert.
  • All inputs are strictly checked (type, length, pattern, allowlist). Protection against forged requests (CSRF), open redirects and SQL injection (parameterized queries only), output only with automatic escaping, strict Content Security Policy.
  • Uploads: file type checked by content, images re-encoded (metadata removed), virus scan of all files; findings are blocked and deleted.

3. Availability and resilience

  • The database is backed up every three hours, encrypted, and copied to separate storage. The files are additionally backed up as complete snapshots; deleted files therefore do not disappear from older snapshots.
  • Every day the latest backup is automatically restored into a disposable database and compared with live operation (“restore test”). A backup counts as good only once it can be restored.
  • Deleted content stays in the workspace trash for 30 days and can be restored there.
  • Protection against overload and attacks by Cloudflare (firewall, bot protection, rate limits).
  • Automatic security updates; failed services restart automatically. The services are monitored; a backup that is too old or a failed restore test triggers an alarm.

4. Procedure for regular review

  • The target state of every server configuration is kept in version control; every day a program checks all servers for deviations and reports them.
  • A nightly check tests links and performance values and reports deviations.
  • Before every release, automated checks run (tests, type checking, checking dependencies for known vulnerabilities).
  • The internal security reviews are documented.

5. Deletion and retention

  • If you disconnect a profile, we delete the access key immediately and the content of this profile within 30 days.
  • If the trial period ends without a booking or a contract ends, the workspace is paused. If the pause is not ended by a booking, we delete the content 30 days after the start of the pause if no payment was ever made, and 90 days after the start of the pause if the customer was a paying customer (Terms and Conditions § 15).
  • Backups: we keep the file snapshots in storage at IONOS for 14 days. We keep database backups in a staggered way for at most 12 weeks (the snapshots of the last 24 hours, then one per day for 7 days, then one per week). Deleted data has thus also disappeared from the backups after about 12 weeks at the latest.
  • We retain invoices and accounting records for ten years (§ 147 of the German Fiscal Code (AO), § 257 of the German Commercial Code (HGB)); they are not part of this agreement.

6. Organization

  • In the event of a personal data breach, we inform you under § 8 within 24 hours of becoming aware.
  • We handle requests from data subjects that concern you with you under § 5 (5).
Sign upLog in