Privacy.
Courtesy translation. The German version is legally binding.
In one sentence: This website sets no cookies, loads nothing from third parties and uses no fingerprinting. Audience measurement runs cookieless through our own server (§ 5a). We process personal data only insofar as this is technically necessary to deliver the website, or when you write to us or use the contact form, request trial access or apply as a design partner.
§ 1 Controller
Christian Schappeit — protagx
Nußbaumallee 27
14050 Berlin
Germany
Email: hello@protagx.com
§ 1a Data Protection Officer and CMP42 as GDPR expertise
For the processing described on this website — server logs, applications and email contact — the formal appointment thresholds under § 38(1) BDSG are not met: fewer than twenty people are permanently engaged in automated processing (sentence 1), no Data Protection Impact Assessment is required (sentence 2 in conjunction with Art. 35 GDPR), and no commercial transmission or market/opinion research takes place (sentence 3). The triggers under Art. 37(1) GDPR — public authority, large-scale regular and systematic monitoring, large-scale processing of special categories — do not apply to the operation of this website either.
We therefore do not appoint a data protection officer for website operations. Where customers use CMP42 as a processing solution (see § 13), the data protection responsibilities are regulated concretely in the data processing agreement — including impact assessment, notification procedures and sub-processors. As soon as protagx — with any single customer or across customers — reaches processing volumes that trigger a DPO under the above criteria, a data protection officer will be appointed and named here.
For data protection enquiries, the contact in § 10 is responsible in any case.
§ 2 Overview: purposes, data, legal bases
| Purpose | Data | Legal basis | Retention period |
|---|---|---|---|
| Delivery and security of the website | Truncated IP address, date/time, requested URL, status code, user agent, referrer | Art. 6(1)(f) GDPR (legitimate interest in operation and security) | 7 days |
| Design partner application | Form data (see § 6) | Art. 6(1)(b) GDPR (pre-contractual measures at your request) | see § 6 |
| Enquiry through the contact form | Name, email, company (optional), topic, preferred time window, message | Art. 6(1)(b) GDPR (pre-contractual measures at your request), otherwise (f) (answering enquiries); for the optional tick (a) (consent) | see § 6a |
| Voting on planned capabilities | Capability chosen, language, form version | Art. 6(1)(f) GDPR (legitimate interest in prioritising) | see § 6c |
| Requesting trial access | Form data (see § 6b) | Art. 6(1)(b) GDPR (pre-contractual measures at your request) | see § 6b |
| Newsletter after voluntary consent | Email address, wording and version of the consent, time, confirmation or withdrawal | Art. 6(1)(a) GDPR (consent) | until withdrawal; the evidence thereafter under Art. 7(1) GDPR |
| Replying to your email | Name, email address, content of the message | Art. 6(1)(b) or (f) GDPR (communication at your request) | until the matter is resolved, thereafter statutory retention periods |
| Performance of contracts and accounting | Master, contract and billing data | Art. 6(1)(b) and (c) GDPR | statutory periods (§ 257 HGB, § 147 AO: up to 10 years) |
§ 3 No cookies, no access to your device
This website sets no cookies and uses neither local storage, session storage nor IndexedDB. It loads no fonts, maps, videos or scripts from third parties; all files are served from our own server. A Content Security Policy technically prevents external resources from being loaded. This applies to audience measurement too: its script comes from our server, not from a third party (§ 5a).
As no information is stored in or read from your terminal equipment, consent pursuant to § 25 TDDDG is not required — which is also why there is no cookie banner.
§ 4 Server logs
When you access the website, our web server processes technically necessary access data:
- IP address, truncated before storage (IPv4: last octet, IPv6: to /48)
- date and time of the request
- requested URL and HTTP status code
- user agent (browser identifier)
- referrer (referring page)
The untruncated IP address is passed on at one single point, and not into the logs: when measurement events are forwarded to Plausible (§ 5a).
The logs serve exclusively for secure operation (e.g. error analysis, defence against attacks) and are automatically deleted after 7 days. They are not combined with other data sources or analysed to create usage profiles. IP truncation and 7-day rotation are implemented in nginx. The upstream Traefik reverse proxy logs requests only for operational purposes and does not itself store client IP addresses beyond the active connection.
§ 5 Hosting
This website and the application endpoint are operated on a server provided by:
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany.
The server is located in Germany (Falkenstein or Nuremberg data centres). A data processing agreement pursuant to Art. 28 GDPR is in place with Hetzner, dated 24 April 2025, covering both data centre locations.
§ 5a Audience measurement with Plausible Analytics
For the anonymous analysis of website usage we use Plausible Analytics, operated by Plausible Insights OÜ, Västriku tn 2, 50403 Tartu, Estonia. Processing takes place entirely within the European Union; there is no transfer to third countries. A data processing agreement pursuant to Art. 28 GDPR is in place with Plausible Insights OÜ.
Technically. Plausible sets no cookies whatsoever, writes nothing to browser storage (local storage, session storage, IndexedDB) and creates no device fingerprints. IP address and user agent are processed into an irreversible hash using a server salt that rotates daily; after 24 hours re-identification is technically impossible. There is no recognition beyond that period or across several devices (information provided by Plausible, retrieved on 24 October 2026: plausible.io/data-policy).
Events recorded. Pageviews with page path, referrer, entry page, device type, browser, operating system and country; the campaign parameters ref, source, utm_source, utm_medium, utm_campaign, utm_content and utm_term, where present in the address requested; requests for pages that do not exist (404); clicks on links to other websites; file downloads; and the submission of a form as an event without the content entered. All other parameters of the address requested are discarded by Plausible. No personal identifiers are transmitted; the events cannot be attributed to any person.
First-party transmission. The Plausible scripts are served via cmp42.com/js/, events go to cmp42.com/api/event and are forwarded by our server to Plausible. Your browser establishes no connection to any third-party domain in the process. For the unique-visitor counting provided for in Plausible, our server transmits your IP address to Plausible as part of this forwarding, where it is used solely to compute the hash described above and is not stored. In our own server logs your IP address continues to be truncated (§ 4).
Why this needs no consent banner. The consent requirement in § 25(1) TDDDG attaches to access to your device — storing or reading information on it. Neither happens here: no cookie, no browser storage, no probing of device characteristics. The provision is therefore not triggered at all, regardless of how one assesses the processing that follows.
What remains is a count with no link to a person. We do not track individuals, and with this setup we could not: there is no identifier connecting a second visit to a first once the daily salt has rotated, and none across two devices at any time. No profile, no recognition, no combination with other sources. A page count is not the observation of a person.
Legal basis. As Plausible neither stores information in nor reads information from your terminal equipment, consent pursuant to § 25(1) TDDDG is not required. Insofar as a legal basis is nevertheless required for the aggregated analysis, we rely on our legitimate interest in statistical audience measurement (Art. 6(1)(f) GDPR). You may object to this processing pursuant to Art. 21 GDPR (§ 10). Further information directly from Plausible: plausible.io/data-policy.
§ 6 Design partner application
If you apply using the form on the design partner page, we process the data you provide there: name, company, role, email address, company website, team size, CRM and AI tool in use, and your free-text entries. Mandatory fields are name, company, email address and the description of your workflow; all other information is voluntary.
The purpose is to review your application, arrange the 15-minute call and, where applicable, admit you to the design partner programme. The legal basis is Art. 6(1)(b) GDPR (pre-contractual measures at your request).
How the submission travels: The form is sent over HTTPS to our own intake service, where your details become a prospect record in our own CRM (CMP42), with the source of the application on it. No third-party form service and no third-party mail provider is involved; the notification to our mailbox hello@protagx.com goes out through our own mail gateway. The server logs contain no form content.
The optional tick: You only receive our newsletter if you set the additional checkbox. We then store your consent as an event of its own — with the exact wording you saw, its version and the time — and confirm the address through a link in an email (double opt-in). The consent takes effect only when you click that link. Without the tick no consent event is created at all, and your application does not depend on it. You can withdraw at any time through the link in every email, with effect for the future (Art. 7(3) GDPR); the withdrawal is kept as an event, as evidence.
Retention period: If no collaboration results, we delete your application no later than twelve months after completion of the application process. This period covers the six-month programme term and a subsequent replacement phase during which vacated places may be filled from the original applicant pool. If a contract is concluded, the periods set out in § 2 apply.
§ 6a The contact form
When you write to us through the contact form, we process your name, your email address, your company if you give one, and what your enquiry is about: the topic, the time window you prefer and your message. The purpose is to answer your enquiry and, if you want one, to arrange a meeting with you. The legal basis is Art. 6(1)(b) GDPR where your enquiry is directed at a contract, otherwise Art. 6(1)(f) GDPR — our legitimate interest in answering enquiries. No consent is required for this.
Transmission and storage are as described above: encrypted to CMP42 on our server at Hetzner in Germany, with a notification to us through our own mail gateway. The server logs contain no form content.
The optional tick for news: § 6 applies to it. Your enquiry does not depend on it.
Retention period: 24 months after the last contact, unless a contract results from the enquiry; the statutory retention periods then apply.
§ 6b Requesting trial access
When you request access through the form on the trial page, we process: first name, last name, work email address, company, country and — optionally — your role. You also confirm the trial terms; we store that confirmation together with the request.
The purpose is to review and set up your trial access. The legal basis is Art. 6(1)(b) GDPR (pre-contractual measures at your request).
What happens: the form is sent over HTTPS to our own intake service; your details become a prospect record in our own CRM (CMP42), with the source of the request on it. No third-party form service, no mail-delivery provider. To confirm your address we send you an email through our own mail gateway containing a link valid for 24 hours; only the click releases the request. The server logs contain no form content.
The optional tick: the newsletter checkbox is separate from this and optional; § 6 applies to it. Your trial access does not depend on it, and without the tick no consent event is created.
Retention period: if no collaboration follows, we delete the request no later than twelve months after the trial access ends. If a contract is concluded, the periods set out in § 2 apply.
§ 6c Voting on planned capabilities
When you press “Vote” next to a planned capability, your browser sends only which capability you voted for, the language of the page and the version of the form. We store that vote in CMP42 on our server at Hetzner in Germany — no name, no email address, no cookie. The page shows nothing but the number of votes per capability. To prevent abuse the number of requests is limited for a short period; the server logs contain no form content. The legal basis is Art. 6(1)(f) GDPR: our legitimate interest in learning which capabilities are wanted. Votes are kept until the poll is closed and evaluated, at most twelve months.
§ 7 Contact by email
If you send us an email, we process your information in order to deal with your enquiry (Art. 6(1)(b) GDPR for contract-related enquiries, otherwise point (f)). We delete the correspondence once the matter has been resolved, unless statutory retention obligations prevent this.
§ 8 Recipients
We disclose personal data only insofar as this is necessary for the purposes stated:
- Hosting provider: Hetzner Online GmbH (Germany), see § 5.
- Audience measurement: Plausible Insights OÜ (Estonia), see § 5a. Processing exclusively within the EU.
- Email mailbox hello@protagx.com: Google Workspace, operated by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. A data processing agreement pursuant to Art. 28 GDPR is in place. Google Ireland engages sub-processors of its parent company Google LLC (USA); the transfer is safeguarded by EU Commission Standard Contractual Clauses and supplementary technical measures. Google LLC is additionally certified under the EU-U.S. Data Privacy Framework.
- Tax advisory services and accounting software within the scope of statutory retention obligations (§ 257 HGB, § 147 AO). The specific recipients will be named on request under the right of access (§ 10).
§ 9 Transfers to third countries
The processing by the email mailbox (Google Workspace) takes place primarily in the European Union. Google Ireland engages sub-processors of its US parent company. Transfers to the USA are safeguarded by EU Commission Standard Contractual Clauses pursuant to Art. 46(2)(c) GDPR together with supplementary technical and organisational measures; Google LLC is additionally certified under the EU-U.S. Data Privacy Framework (adequacy decision of the EU Commission dated 10 July 2023, Art. 45 GDPR). We use no third party to send mail: notifications and confirmations go through our own mail gateway. For the operation of the website itself (hosting, server logs) and for audience measurement (§ 5a), no transfer outside the EEA takes place.
§ 10 Your rights
You have the following rights at any time:
- Access to the data stored about you (Art. 15 GDPR)
- Rectification of inaccurate data (Art. 16 GDPR)
- Erasure (Art. 17 GDPR), unless a retention obligation prevents this
- Restriction of processing (Art. 18 GDPR)
- Data portability (Art. 20 GDPR)
- Objection to processing based on Art. 6(1)(f) GDPR (Art. 21 GDPR)
- Withdrawal of consent given, with effect for the future (Art. 7(3) GDPR)
An informal message is sufficient: hello@protagx.com — Art. 15 GDPR request. We will respond within the statutory period of one month.
§ 11 Right to lodge a complaint with a supervisory authority
Without prejudice to any other remedy, you may lodge a complaint with a data protection supervisory authority pursuant to Art. 77 GDPR, in particular in the Member State of your habitual residence, place of work or place of the alleged infringement. The authority competent for us is:
Berliner Beauftragte für Datenschutz und Informationsfreiheit (Berlin Commissioner for Data Protection and Freedom of Information)
Alt-Moabit 59–61, 10555 Berlin
datenschutz-berlin.de
§ 12 Security
All connections to this website are encrypted via TLS; HTTP Strict Transport Security (HSTS) enforces HTTPS. A restrictive Content Security Policy prevents external scripts and resources from being loaded.
§ 13 CMP42 as a product
This policy relates to the website cmp42.com. Where companies use CMP42 as a design partner or customer, we process the data entered there as a processor on behalf of the respective company. For this purpose we conclude a data processing agreement pursuant to Art. 28 GDPR; the customer company is the controller.
§ 14 Automated decision-making
No automated decision-making, including profiling, within the meaning of Art. 22 GDPR takes place.
§ 15 Changes
We will amend this policy if the legal situation or the functions of the website change. The version published here at any given time applies.
Last updated: 2 November 2026