Privacy Notice

Congratulations on opening this page.

No, really. Most people blindly click "Accept All Cookies" without reading what they're agreeing to. Privacy notices exist because companies collect, share, analyse, and profit from data. If you cannot be in control of your data completely, then at the very least you should make an informed decision about how it is used. Reading documents like this is one of the few practical ways to protect yourself online.

What this document is: A privacy notice that is intentionally more transparent and detailed than most. It is written in plain English so you can understand the trade-offs and make informed choices.

The TL;DR

  • No tracking: No Google Analytics, no pixels, no heatmaps, no session replay.
  • No analytics or advertising cookies: This site does not set cookies for analytics or advertising.
  • Open source: You can inspect the full site code on GitHub.
  • Infrastructure processes limited technical data: GitHub Pages (hosting) and Cloudflare (DNS, CDN, and security proxy) process technical request data as part of delivering and protecting the site.
  • No behavioural profiling: I do not receive analytics, visitor reports, or behavioural insights from this infrastructure.

The Good News: I'm Not Tracking You

There is no cookie banner on this site because you are not being tracked. There are no analytics platforms, advertising pixels, or behavioural monitoring tools. I do not know who you are, where you came from, or what pages you read. That is intentional.

Complete transparency: you can verify this yourself.

The entire source code for this site is publicly available on GitHub. Every line of HTML, CSS, and JavaScript is there for you to inspect. If you find tracking code, call me out.

"If you don't pay for the product, you are the product."

You've heard this before, and it's often true. Free services monetise you through ads, data collection, or both. (Learn more).

So let's talk about what "free" means for this site.

My costs:

Total annual cost: US$10.46 + my time (invaluable).

Who Processes Data and Why

Although I do not collect personal data myself, running a website requires infrastructure providers. These providers process limited technical data as part of normal internet operations such as routing, caching, and security.

Controller and processors: I am the data controller for this website. GitHub and Cloudflare act as infrastructure providers. I do not receive raw access logs from either service and I do not analyse visitor behaviour.

The Infrastructure Layer

While I do not track you, the "pipes" that deliver this website (GitHub and Cloudflare) have their own technical requirements. I've chosen them because they have strong privacy reputations, and below is exactly what they can and cannot see in this setup.

GitHub Pages (Hosting)

What they handle:
GitHub hosts the static site files. When you request a page, those files are ultimately served from GitHub’s infrastructure, either directly or via Cloudflare’s cache.

What they may process:
GitHub may process standard web server access log data, which can include:

  • Your IP address
  • Which pages or files you request
  • Timestamps of requests
  • Your browser type and version (user-agent)
  • The referring website (where you came from)

What they do with it:
According to GitHub's privacy documentation, this data is used for:

  • Basic infrastructure operation and security monitoring
  • DDoS protection and abuse detection
  • Aggregate service statistics

Important: I do not have access to GitHub's raw access logs for this site.

Data retention:
GitHub states retention varies by data type and purpose. Publicly specified exact retention periods for access logs are limited. In practice, operational logs are often retained for a limited period and aggregated data may be kept longer.

International transfers:
GitHub is a U.S. company owned by Microsoft. Your data may be stored and processed in the United States or other countries where GitHub operates, using recognised international transfer mechanisms.

Their full privacy policy: GitHub Privacy Policy

Cloudflare (Domain Registrar, Authoritative DNS, and Proxy for A record)

What they handle:
Cloudflare manages three things for this site:

  1. Domain registration for dontfeedthemonkeys.com
  2. Authoritative DNS hosting (they host the DNS records that tell the internet where this site is located)
  3. Reverse proxy/CDN for the A record that serves the website

What is DNS and why does it matter?
When you type "dontfeedthemonkeys.com" into your browser, your device needs to translate that human-readable name into an IP address (the location of the server). Your device asks a DNS resolver (often your ISP's, or one you've chosen) to look this up. That resolver queries Cloudflare's authoritative DNS servers (because Cloudflare hosts this domain's DNS records), and Cloudflare responds with the appropriate DNS record.

What Cloudflare may process at the DNS layer:
When DNS resolvers query Cloudflare's authoritative DNS for this domain, Cloudflare may log:

  • That someone requested DNS records for dontfeedthemonkeys.com
  • When the request was made
  • Which resolver made the request (typically the resolver IP, not your personal IP)

Edge cases: Some DNS configurations and standards (for example EDNS Client Subnet in certain contexts) can leak partial client network information. This site is not configured to intentionally collect that, but the DNS ecosystem has nuances.

What authoritative DNS alone does not reveal:
DNS is about resolving a domain name to a destination. By itself, it does not show which pages you visit, what you read, or how long you stay.

CDN/Proxy configuration

Cloudflare also offers CDN and reverse proxy services. When enabled (often shown as an "orange cloud" in Cloudflare's dashboard), Cloudflare sits between you and the hosting provider for the proxied record.

In this configuration, Cloudflare can technically process additional request data for that record, including IP address, requested URLs, and request headers, in order to provide security, caching, and abuse prevention.

Current configuration: Cloudflare proxy/CDN is enabled (orange cloud) for the A record for dontfeedthemonkeys.com only. All other DNS records for this domain are DNS-only (grey cloud).

Why it is enabled:
The proxy is enabled for protection and safety, including basic DDoS mitigation, abuse prevention, and shielding the origin hosting from common automated attacks.

Data use and retention:
According to Cloudflare's privacy policy, data is used for infrastructure security, abuse prevention, and service improvement. Retention periods vary by data type and service.

International transfers:
Cloudflare is a U.S. company and may process data in the United States. Cloudflare describes its international transfer mechanisms in its privacy policy.

Their full privacy policy: Cloudflare Privacy Policy

The Bottom Line

What I control: I have chosen not to implement tracking, analytics, advertising, or behavioural profiling on this site.

What I do not control: Infrastructure providers (Cloudflare and GitHub) process limited technical data as part of operating the internet and securing their services.

What neither service does (based on their published policies):

What both services may do:

The Infrastructure Transparency Table

Data Type What I see GitHub Pages Cloudflare (proxy enabled)
Your IP address Nothing May appear in logs Processed for security and delivery
Pages requested Nothing May appear in logs Processed and cached
Tracking cookies None None None for analytics or ads

Your Privacy Rights

Depending on your location, you may have rights to access, correct, or request deletion of personal data processed by infrastructure providers.

Because I do not collect or store personal data myself, most requests should be directed to the relevant provider:

Future Considerations

If anything changes on this page, I will update the "Last updated" date below and note what changed.

Questions or Concerns?

If you have questions about this privacy notice or concerns about your data, you can:

Update History

6 February 2026: Updated this privacy notice to accurately reflect that Cloudflare proxy/CDN is enabled for the A record of this site. The previous version incorrectly described the configuration as entirely DNS-only. No tracking or analytics were added as part of this change.

Last updated: 6 February 2026

Not legal advice. This privacy notice is provided for informational purposes only.

Back to top Home