Privacy Policy

Last updated: July 9, 2026.

Privacy on janitor-ai.io is short because there isn't much to have a policy about. This is a read-only editorial site — nothing here asks you for an email, a name, a payment method, or account credentials of any kind. What follows describes the modest data footprint that touches this site when a page loads, and what becomes of it afterwards.

Data that actually moves through this site

When your browser fetches a page from janitor-ai.io, the hosting provider keeps a request record for a rolling thirty-day window. The record captures the IP address the request came from, the URL that was asked for, whichever page pointed the browser here, the user agent string, and a timestamp. Those logs exist for operational monitoring and to make abuse investigations possible. They aren't linked to any identity we hold, and they don't leave the hosting environment.

Alongside the server logs, aggregated visit statistics arrive through a privacy-respecting analytics provider. What appears in that data: total page views, rough geographic distribution, referral sources. What doesn't: browser fingerprints, cross-site identifiers, or anything that would let us tie an individual reader across separate visits.

Data we intentionally never collect

There are no accounts on this site. No comment sections, no contact forms, no newsletter signups, no upload endpoints. If a future version of the site ever adds anything interactive, the collection practices for that new mechanism will land on this page first, before the feature ships. Data isn't sold. Data isn't purchased. Visitor information isn't handed to advertisers, aggregators, or brokers.

Third-party services in the stack

Three third parties are involved in delivering this site to you:

The hosting infrastructure. Serves the static HTML and CSS pages and holds the server logs described above.
Google Fonts. Delivers the display typography (Bricolage Grotesque, Instrument Sans, Space Mono). Google's own privacy notice covers what their font-serving endpoint sees when your browser fetches a font.
Privacy-respecting analytics. Handles the aggregated visitor statistics referenced above, with no fingerprinting or persistent identifiers on their end.

None of these providers receive information that would let them identify you as an individual visitor from what janitor-ai.io sends them.

Cookies and browser storage

The only browser-side storage this site actually needs is the small flag that remembers you confirmed 18+ at the age gate — so you don't see the prompt on every visit. That flag lives in localStorage (not a cookie) and stays only in the browser that set it. No advertising cookies are set by janitor-ai.io. No cross-site tracking cookies either. Third-party embeds — fonts and analytics — may set their own minimal cookies subject to their own separate policies.

Affiliate CTAs and outbound tracking

Several outbound buttons on this site — most visibly the "Open Janitor AI" calls-to-action — are affiliate links. When you follow one and go on to complete a qualifying action at the destination platform, a small commission gets sent to janitor-ai.io by that platform. The mechanical effect on your end is that the destination sees a referral signal from janitor-ai.io in the URL that opens their page. What the destination does with that signal, and what data they collect after you arrive, is governed by their privacy policy — not this one. Informational links (documentation, Reddit threads, Discord, status pages) aren't affiliate. Those are ordinary editorial references.

Your rights over your data

GDPR for visitors in the EU or UK, CCPA in California, and comparable frameworks elsewhere give you rights over data an operator holds about you: access, correction, deletion, portability, and objection. Because janitor-ai.io doesn't retain identifiable data about individual visitors, most of these rights resolve to "there is nothing on our side to access, correct, or delete." If you'd like clarification about whether any specific visit produced identifiable log data on our side, the contact channel below gets you a definitive answer.

How to reach us about privacy

Privacy correspondence goes straight to the editor via LinkedIn: linkedin.com/in/melissablake1. Typical turnaround is two or three business days; the outer limit we commit to is seven.

How this policy changes

Substantive updates to how data is handled here — a new provider, a new collection mechanism, anything material — appear on this page with a refreshed "Last updated" date at the top. Minor edits (typography fixes, small clarifications, phrasing adjustments) happen without a date refresh.

Last reviewed: July 9, 2026 · by Melissa Blake

18+ only