Privacy Policy
1. Controller
Controller within the meaning of the GDPR:
The Boring Cat
Owner: Harllens George de la Cruz
Eiffestrasse 600
20537 Hamburg
Germany
Email: [email protected]
General inquiries: [email protected]
This privacy policy applies to all websites, applications, digital products, and online services operated by The Boring Cat, regardless of the specific project or product name.
2. General information on data processing
Protecting your personal data is important to us. We process personal data only in accordance with applicable laws, in particular the GDPR and the German Federal Data Protection Act (BDSG). Personal data is processed only to the extent necessary for providing our websites, communicating with you, fulfilling contracts, or complying with legal obligations.
Domains
This privacy policy applies to services running on the following domains:
- https://theboringcat.com (main website, including the Library at https://theboringcat.com/library/ and the talk pages)
- https://documents.theboringcat.com (former address of the Library, which redirects to https://theboringcat.com/library/)
- https://api.theboringcat.com (our own API, which receives the forms, comments and talk requests described below)
This site itself sets no cookies. The only value it stores in your browser is your choice of light or dark theme (section 9). The spam check (section 11) and the embedded videos and posts (section 9) come from other providers. They may store data on your device only after your own action: sending a form, or pressing the button for an embedded item. Hosting and security are provided by Cloudflare (section 6).
3. Legal bases for processing
The legal basis for each processing is stated in the section that describes it. The GDPR provisions used are:
- Article 6(1)(a) GDPR: consent
- Article 6(1)(b) GDPR: performance of a contract or pre-contractual steps
- Article 6(1)(c) GDPR: legal obligation
- Article 6(1)(f) GDPR: legitimate interest
4. Rights of data subjects
You have the following rights under the GDPR:
- Right of access to your personal data (Art. 15 GDPR)
- Right to rectification of inaccurate data (Art. 16 GDPR)
- Right to erasure (Art. 17 GDPR)
- Right to restriction of processing (Art. 18 GDPR)
- Right to data portability (Art. 20 GDPR)
- Right to object (Art. 21 GDPR): you may object at any time to processing that is based on Article 6(1)(f) GDPR, for reasons relating to your particular situation. We then stop the processing unless we can show compelling legitimate grounds that override your interests, rights and freedoms. You may also ask us to remove a comment or a talk request you have sent (sections 12 and 13).
If processing is based on consent, you may withdraw your consent at any time with effect for the future (Art. 7(3) GDPR). Withdrawal does not affect the processing carried out before it.
You also have the right to lodge a complaint with a data protection supervisory authority. The authority competent for our business in Hamburg is Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit. You may also complain to any other supervisory authority in the European Union.
To use any of these rights, write to [email protected]. Our websites do not have a separate request form.
5. Access data, server logs and rate limits
When you visit our websites, information sent by your browser is collected automatically. This includes IP address, date and time of the request, browser type and version, operating system, and referrer URL. This data is processed to ensure technical operation, analyze errors, ensure security, and prevent abuse.
Legal basis: Article 6(1)(f) GDPR.
Recipient: Cloudflare, Inc. (section 6).
Retention period: up to 14 days.
Rate limits and hashed values. To prevent abuse, our API limits how often the contact form, the talk request form and the comment form can be sent from one visitor. For this it stores a hash of your IP address and browser type, together with the number of requests in the current minute. Records older than about four hours are deleted by a cleanup that runs on a share of requests. Talk requests and comments are also stored with a visitor value (section 12).
Purpose: protection against abuse and spam.
Legal basis: Article 6(1)(f) GDPR.
Recipient: Cloudflare, Inc. (section 6).
Retention period: rate-limit records up to about four hours, as described above.
Where the API limits the number of emails sent to one recipient, it stores an hourly hash of that email address. These records are deleted after seven days. The forms on this site do not use this limit.
Our home page shows public activity figures from GitHub. Your browser asks our own API for these figures (api.theboringcat.com), not GitHub. Our API fetches the figures from GitHub itself. Your IP address reaches our API as with any request to it (section 6). Your browser contacts GitHub only if you follow a link to GitHub.
6. Hosting, content delivery, security and database (Cloudflare)
We host our websites, run our API and store the data described in this policy with Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA, as our processor. Cloudflare delivers and protects our websites (content delivery network and protection against attacks such as DDoS), runs our API and database, and delivers the emails sent from our forms (sections 7, 8, 12 and 13). Cloudflare processes technical access data, such as IP addresses and header information, the rate-limit records described in section 5, and the form data described in the sections named above.
Legal basis: Article 6(1)(f) GDPR (security, stability and performance of the websites). For form data, the legal basis is stated in the section concerned.
Transfers to third countries: Cloudflare is a company based in the United States, so data may be processed in the United States and in other countries. Cloudflare's privacy policy (section 7) states that it relies on its certification under the EU-U.S. Data Privacy Framework for such transfers and that, should that certification lapse, it relies on standard contractual clauses.
More information: https://www.cloudflare.com/privacypolicy/
7. Contact form
When you send a message through the contact form on our website, we process the email address and the message you enter, the language of the page, and the result of the spam check (section 11). We do not store your message in our database. We send it by email to our inbox, and we send you an automatic email confirming that we have received it. The rate-limit records described in section 5 also apply to this form.
Purpose: to answer your inquiry and to confirm that it has arrived.
Legal basis: Article 6(1)(b) GDPR (pre-contractual communication) and Article 6(1)(f) GDPR (answering general inquiries).
Recipients: Cloudflare, Inc. (delivery, section 6) and our email hosting provider (section 8).
Retention period: until your inquiry is dealt with, and at the latest 12 months after our last message. If the message becomes business correspondence, such as an offer, an order or a contract, the statutory periods in section 19 apply.
8. Email communication
We use the following service providers to send and receive emails:
- Cloudflare, Inc. (delivery of the emails sent from our forms, section 6)
- Our email hosting provider, which holds our mailbox, where messages arrive
The following data is processed: email addresses, sender and recipient details, the content of the messages, and the data entered in the forms described in sections 7, 12 and 13.
Legal basis: Article 6(1)(b) GDPR (pre-contractual communication) and Article 6(1)(f) GDPR (legitimate interest in answering messages).
9. Cookies, local storage and embedded content
This site itself sets no cookies. If your browser still holds an older theme cookie, the site deletes it.
Theme choice: when you use the theme button, we store your choice (light or dark) in the local storage of your browser, under the name tbc-theme. This value stays on your device. We do not send it to our servers and we do not read it from our servers.
Legal basis: the storage is needed to show the theme you chose, which you requested. It is strictly necessary for that function, so no consent is required for it under section 25(2) no. 2 of the German Telecommunications Digital Services Data Protection Act (TDDDG). The processing of personal data is based on Article 6(1)(f) GDPR.
Retention period: until you change the theme again or clear the site data in your browser.
Embedded videos and posts: our pages can show a YouTube video or a LinkedIn post. Nothing is loaded from these providers until you press the button for that item. After you press it, the item loads for that view only:
- YouTube videos load from youtube-nocookie.com, a service of Google LLC.
- LinkedIn posts load from LinkedIn, a service of Microsoft.
The provider then receives your IP address and the other data its own service needs. Legal basis: Article 6(1)(a) GDPR (consent, given by pressing the button). The provider's own privacy policy applies to its processing.
10. Web analytics (Cloudflare Web Analytics)
We use Cloudflare Web Analytics on the live website. It counts page views in aggregate. Cloudflare counts page views without cookies and without storing anything on your device.
Recipient: Cloudflare, Inc. (section 6).
Legal basis: Article 6(1)(f) GDPR (measuring the use of our websites in aggregate).
Retention period: Cloudflare keeps its aggregated statistics under its own retention rules. We keep no personal data from this measurement.
11. Spam protection (Cloudflare Turnstile)
Our forms use Cloudflare Turnstile to check that a person, and not an automated program, sends the form. The check loads from Cloudflare only when you send one of our forms (contact form, talk request, or comment). It sends your IP address and a check token to Cloudflare. Cloudflare may set technically necessary storage on your device at that point. This site sets no cookie itself for this check. Our API checks the token with Cloudflare and does not store it.
Legal basis: Article 6(1)(f) GDPR (protection of our forms against abuse and spam).
Recipient: Cloudflare, Inc. (section 6).
Retention period: as set by Cloudflare under its privacy policy.
12. Comments on Library pages
On Library entries and talk pages you can write a comment with a name and a message. Comments are shown publicly on the page, with the name you gave. We store the name, the message, the page and the language, the time of the comment, and a visitor value. The comment form does not ask for an email address.
The visitor value is pseudonymous. If your browser sends a visitor identifier (an `X-Visitor-Id` header or a `tbc_vid` cookie, which our sites do not set), our API uses that identifier, hashed. Otherwise it uses a hash of your IP address and browser type. We store this value with the comment and use it only for abuse protection. The rate limit for comments is described in section 5.
Purpose: to publish the comments visitors choose to post, and to prevent abuse.
Legal basis: Article 6(1)(f) GDPR (publishing what the visitor chooses to post, and abuse protection).
Recipient: Cloudflare, Inc. (hosting and database, section 6). Comments are visible to every visitor of the page.
Retention period: as long as the comment is published. You can ask us to delete your comment at any time by email to [email protected]. We then delete the comment together with the technical value stored with it.
13. Talk requests
On talk pages you can send a question or request the resources of a talk. We store your email address, your message, the type of request (question or resources), the page, the language, and the visitor value described in section 12. The rate limit for talk requests is described in section 5. We use your email address to answer you.
Purpose: to answer your question or send the requested resources.
Legal basis: Article 6(1)(b) GDPR (pre-contractual steps) and Article 6(1)(f) GDPR (answering requests).
Recipients: Cloudflare, Inc. (storage and delivery, section 6) and our email hosting provider (section 8).
Retention period: 12 months after we receive your request.
14. View counts
When an entry in the Library is opened, the page can send a view to our API. For each view we store the entry, a time window of ten seconds, and the visitor value described in section 12. Each visitor is counted once per entry in each ten-second window. The views are added up per entry. We show the resulting counts on our site: the number of views of each entry and a list of the most read entries.
Purpose: to see which entries are read, and to report on it.
Legal basis: Article 6(1)(f) GDPR (understanding which content is read).
Recipient: Cloudflare, Inc. (storage, section 6). The counts are visible to every visitor.
Retention period: the counts are kept for as long as the entry exists. Individual view records are kept for 12 months and then deleted.
15. AI providers
We use the following AI tools in our own work: OpenAI, Anthropic (Claude), Microsoft, and AI models that run on our own equipment.
At present, messages sent through our forms, comments and the data of visitors are not passed to an AI provider.
If this changes, for example if we add an assistant that answers questions on this site or use AI for reporting, we will update this privacy policy and the page "How we use AI" before the change starts. We will then state which data each provider receives, where it is processed, and the legal basis.
16. Business and contract communication
In the course of our business activities, we process personal data of customers, prospects, and business partners as required for contract performance, communication, or compliance with legal obligations.
Legal basis: Article 6(1)(b) and (c) GDPR.
17. SaaS and application users
If we provide SaaS or digital applications, we process personal data only to provide, maintain, secure, and improve these services. If we process personal data on behalf of customers, this is done on the basis of a data processing agreement pursuant to Article 28 GDPR.
18. Recipients and processors
Personal data is shared with third parties only when necessary. The recipients are:
- Cloudflare, Inc., USA: hosting, content delivery, security, database, email delivery, spam protection and web analytics (sections 5, 6, 8, 10 and 11)
- Our email hosting provider: our mailbox (section 8)
- Google (YouTube, through youtube-nocookie.com) and Microsoft (LinkedIn): only after you press the button to load a video or post (section 9)
Our websites link to other websites, such as the Chrome Web Store. Those sites have their own privacy policies. When you visit our pages we do not send them your data; this happens only when you choose to follow a link.
We do not sell personal data. We choose providers with care and use their data processing terms.
Payments: our websites in this release take no payments. If we take payments in future, we will update this policy first.
19. Retention and deletion
Personal data is deleted once the purpose for processing no longer applies, unless statutory retention obligations require longer storage. The retention periods are:
- Server logs: up to 14 days (section 5)
- Rate-limit records: up to about four hours (section 5)
- Hashed recipient records for email limits: seven days (section 5)
- Contact messages: until the inquiry is dealt with, and at the latest 12 months after our last message (section 7)
- Comments: as long as they are published, or until deletion is requested (section 12)
- Talk requests: 12 months after we receive the request (section 13)
- View records: 12 months (section 14)
- Theme choice: until changed or cleared (section 9)
Statutory retention obligations: business letters, such as offers, orders and contracts, are kept for six years, counted from the end of the calendar year in which the letter was received or sent (section 147, paragraphs 3 and 4, of the German Fiscal Code, AO; section 257, paragraphs 1, 4 and 5, of the German Commercial Code, HGB). Accounting records and vouchers are kept for the statutory periods of tax and commercial law.
20. Data security
We implement appropriate technical and organizational measures to protect personal data against loss, manipulation, unauthorized access, and misuse. The rate limits and hashed values used for abuse protection are described in section 5.
21. Changes to this privacy policy
We may update this privacy policy to reflect legal, technical, or organizational changes.