Privacy

Nothing leaves your browser.

This is a static website. There is no backend, no database, no login, no analytics, no tracking. Your profile, your registration statuses, your notes — all of it lives in your browser's local storage and never gets sent anywhere. The author of this site cannot see your data because there is no place for it to land.

The whole privacy posture in 5 bullets

  • Your profile and event statuses live in this browser's localStorage. Nowhere else.
  • No analytics. No tracking pixels. No third-party cookies. No fingerprinting.
  • The Chrome extension only reads from cannes.airpost.ai. It cannot read from any other site.
  • The extension never submits forms for you. You always click submit yourself.
  • The code is open source under MIT. Audit it: github.com/ReadySetCo/cannes-2026-dashboard.

What gets stored in your browser

All under versioned ccc:v1:*keys in your browser's localStorage. Open DevTools → Application → Local Storage and you can see and clear it yourself any time.

ccc:v1:profile
Your name, email, company, title, LinkedIn URL, and phone. Used to pre-fill RSVP forms.
ccc:v1:statuses
Which events you marked Registered, Pending, Action-needed, Attended, or Skipped.
ccc:v1:customEvents
Events you added yourself (dinners, meetings, anything not in the public seed).
ccc:v1:onboarding-completed
Whether you finished the first-visit walkthrough. So we don't show it again.
ccc:v1:privacy-banner-dismissed
Whether you've dismissed the privacy banner. So we don't keep showing it.
ccc:v1:extension-banner-dismissed
Whether you've dismissed the install-the-extension banner.

Clear localStorage in DevTools and your data is gone — there's no backup, no server copy, no way to recover it. That's the price of the privacy story.

What gets shipped in the public dataset

Two JSON files in the open-source repo, visible to everyone:

  • data/events.json — the curated Cannes Lions 2026 event directory. Sourced from publicly-listed registration pages. Update via pull request.
  • data/people.json — the "Who's going" feed. Each card is sourced from a public LinkedIn post, X post, or official Cannes Lions announcement, with a link back to the original. Every entry is on a person who publicly posted about their attendance — never private profiles, never private data.

The Chrome extension

Optional companion. Reads your saved profile from this dashboard and fills it into Cannes event RSVP forms automatically.

  • What it reads: only ccc:v1:profile from cannes.airpost.ai. Nothing else, no other origin.
  • What it writes: form fields on the specific Cannes event domains listed in its manifest. The full domain list is public in extension/manifest.json.
  • What it stores: a local copy of your profile in the extension's own Chrome storage, so it can fill forms even when the dashboard tab isn't open. This copy is also browser-local — it never leaves your machine.
  • What it never does: submit forms for you, contact a server, run analytics, send telemetry, or read from any domain not in its manifest. You always click submit yourself.

What we don't do

  • No accounts. No sign-ups. No passwords stored anywhere.
  • No analytics (no Google Analytics, no Plausible, no Posthog, no Mixpanel).
  • No cookies, with one exception: a single dismiss-the-privacy-banner flag.
  • No newsletter sign-up. No retargeting pixels. No ad networks.
  • No server logs of your personal data — because nothing personal is sent to a server.
  • No share-with-partners. No data brokering. There is no "data" to share or broker.

Takedowns & questions

If you're on the Who's going feed and want to be removed, email john@airpost.ai — or open an issue using the takedown request template. We'll remove the entry from data/people.json and add your URL to the blocklist so future scrape refreshes skip you.

Other privacy questions? Same address.

Audit the code

Don't take our word for it. The entire site + extension is MIT-licensed and lives at github.com/ReadySetCo/cannes-2026-dashboard. Open DevTools and watch the Network tab while you click around — you'll see no calls except the initial page load.

Last updated: 18 May 2026