Privacy policy

qrpage.co is built for minimum data collection. This page explains what we store, why, and for how long.

Last updated: 29 May 2026

1. Data controller

Caspar von Wrede
Goethestr. 32
14163 Berlin, Germany
Email: hi@qrpage.co

A Data Protection Officer is not legally required for us: we do not regularly employ more than 20 people on automated personal-data processing, nor do we carry out processing that would require a data protection impact assessment.

2. What we process

3. Legal bases

4. Cookies

qrpage.co does not set any tracking cookies of its own, and does not load any consent-requiring third-party cookies. No cookie banner is therefore required under § 25 TTDSG (Germany's implementation of the ePrivacy Directive).

Cloudflare may set a strictly necessary cookie (__cf_bm) for bot detection. That cookie serves only security and service functionality and is exempt from consent under § 25(2)(2) TTDSG.

5. Recipients / processors

We use the following processors, with Data Processing Agreements (DPAs) and EU Standard Contractual Clauses (SCCs) in place where applicable:

6. International data transfers

Some processors listed above (Cloudflare, AWS, SendGrid, Fathom, Ahrefs) may process data in the United States. We rely on the EU Standard Contractual Clauses and, where applicable, the European Commission's adequacy decision under the EU–U.S. Data Privacy Framework.

7. Retention

8. Your rights

Under the GDPR you have, in particular, the following rights:

To exercise these rights, email us at hi@qrpage.co.

9. Right to lodge a complaint

You have the right to lodge a complaint with a supervisory authority. Our lead authority is:

Berlin Commissioner for Data Protection and Freedom of Information
Friedrichstr. 219, 10969 Berlin, Germany
www.datenschutz-berlin.de

10. Security

Traffic is encrypted with TLS. We apply security updates promptly, run regular backups, and restrict internal access to personal data.

11. Changes to this policy

If we make material changes, we will update the date above and, where relevant, notify users in the app.