Cookie Policy

Effective: May 28, 2026 · Last updated: May 28, 2026

This Cookie Policy explains what cookies and similar technologies Pilot Protocol ("we", "us") uses on pilotprotocol.network, why we use them, and how you can control them. It supplements our Privacy Policy.

What Are Cookies?

Cookies are small text files placed on your device by websites you visit. They are widely used to make websites work, improve efficiency, and provide information to the site owners. "Similar technologies" includes localStorage, session storage, and browser-level storage APIs that serve a similar purpose.

Cookie Inventory

Here is every cookie and browser-storage entry used on pilotprotocol.network, what it does, how long it lasts, and who sets it:

Name Provider Purpose Duration Category
__cf_bm Cloudflare Bot management. Cloudflare may set this to distinguish human visitors from automated bots when bot protection is active on the zone. Does not track users across sites. 30 minutes Strictly necessary
pilot_consent Pilot Protocol (localStorage) Stores your cookie consent preference (accepted or rejected). No personal data, no tracking. Persistent (until cleared) Strictly necessary
pilot-theme Pilot Protocol (localStorage) Remembers your light/dark theme choice. No personal data, no tracking. Persistent (until cleared) Functional
pilot.publish.draft.v1 Pilot Protocol (localStorage) Saves your in-progress app-submission draft on the Publish page so you don't lose it on reload. Set only if you use that form. Persistent (until cleared) Functional
pilot.publish.ui.v1 Pilot Protocol (localStorage) Remembers UI state on the Publish page (e.g. which step you're on). Set only if you use that form. Persistent (until cleared) Functional
_ga Google Analytics Distinguishes unique users for analytics. Set only after you accept cookies. Contains a randomly generated client identifier. 2 years Analytics
_ga_EEWEKT0GW5 Google Analytics Session-level analytics for our GA4 property. Set only after cookie consent. Tracks page views and session state. 2 years Analytics

Cookieless Analytics

In addition to the cookies above, we use Cloudflare Web Analytics, which is entirely cookieless. It sets no cookies or localStorage and does no client-side fingerprinting or persistent tracking; it reports only aggregated page-view and performance metrics. (As with any web request, the analytics beacon transmits your IP and user-agent to Cloudflare; see Cloudflare's privacy documentation for how they handle it.)

Consent Model

When you first visit pilotprotocol.network, a consent banner appears offering two options:

The banner does not use a "nag wall" — you can browse the site without interacting with it. If you do not make a choice, no analytics cookies are set (implied rejection).

How to Change Your Preference

You can change your consent at any time:

  1. Cookie preferences link — In the site footer (on the main marketing pages), click "Cookie Preferences" to reopen the consent banner. You can also clear the pilot_consent entry (below) to make the banner reappear.
  2. Clear localStorage — Removing pilot_consent from your browser's localStorage will reset your preference, and the banner will reappear on your next visit.
  3. Browser settings — Most browsers allow you to block or delete cookies globally. See your browser's help documentation for instructions.

Third-Party Tools We've Disabled

For transparency: our site includes a PostHog integration in the codebase, but it is currently disabled. No PostHog cookies, events, or analytics are active. If we enable PostHog in the future, we will update this policy, add it to the cookie inventory, and require fresh consent.

Changes to This Policy

We will post changes to this page and update the "Last updated" date. If we add new cookies or substantially change how we use existing ones, we will re-prompt for consent where required by law.

Contact

Questions about cookies or our use of analytics?

Email: founders@pilotprotocol.network

This policy was drafted for transparency. If you are a legal professional reviewing this document, please direct feedback to founders@pilotprotocol.network.