Skip to main content
Privacy policynot lawyer-reviewedLast updated: 2026-09-29

What CodeParty does and does not collect.

This page describes how the app handles data today. Repository work is local-first, while account sign-in and optional Friends features use CodeParty's Supabase project.

For support and privacy questions, email codepartysupport@gmail.com.

§ 01

This site

CodeParty's site code does not ask for an account or intentionally collect personal information. It does not run analytics, ads, session replay, fingerprinting, heatmaps, or third-party embeds. The hosting service may still process ordinary request data such as an IP address, user agent, requested page, and time to deliver and protect the site.

The only storage the site itself uses is transient in-memory routing state. No cookies are set by the site's code. See cookies & storage.

§ 02

The desktop app

CodeParty stores repository worktrees, party state, prompts, responses, activity, drafts, terminal output, and preferences locally on the Macs where they are created. People who join a party can receive the collaboration state and project files made available through the authenticated party connection. Local party data is not uploaded to Supabase by the account or Friends features.

Provider sign-in for Codex, Claude, Gemini and GitHub Copilot uses each participant's installed CLI. CodeParty does not ask for provider keys as account settings or intentionally store or broadcast them. Prompts and CLI output may be shared with party members; avoid including secrets in either. If a provider CLI is not authenticated, its features require sign-in through that CLI.

LAN parties send party state between machines you explicitly connect. Sessions are token-authenticated and rate-limited by address. Do not expose the coordinator port to the open internet.

If you turn on internet sharing, the app sends party traffic through the Cloudflare relay over HTTPS/WSS. The relay terminates TLS and transiently handles collaboration payloads; they are not end-to-end encrypted from the relay operator. The relay stores room ownership, party code and expiry, but does not persist source code or provider credentials in its application logs or room storage. Your local worktrees and AI execution remain on the participants' machines.

§ 03

Accounts and Friends

Signing in sends the information required by your chosen sign-in method to the configured Supabase Auth service. This can include your email address, account identifier, provider metadata, and session information. CodeParty keeps the active session and any accounts you choose to remember in encrypted native storage on your Mac; session credentials are not exposed to the React interface.

If you use Friends, Supabase stores your username, friend code, friend and block relationships, visibility and recent presence, current advertised party name and connection descriptor, plus party invitations and join requests. Invitations expire after one hour. Direct table access is revoked and the feature uses an authenticated database function, but this is still hosted personal data.

CodeParty does not sell subscriptions, run a marketing waitlist, or use account data for advertising. Supabase acts as the hosted authentication and social-data service. Its privacy policy also applies to its own processing.

§ 04

Signing in with Google

When you choose Continue with Google, CodeParty opens Google's own sign-in page in your browser and completes the sign-in through the configured Supabase Auth service. CodeParty does not see or store your Google password, and it does not ask Google for extra permissions such as access to your contacts, files, mail or calendar.

From that sign-in, the app itself uses only your account identifier and your verified email address, to identify your CodeParty account; it refuses to continue if the email address is not verified. It also uses the optional CodeParty username you choose later. Supabase may keep basic profile details that Google shares at sign-in, such as your name and profile picture, as provider metadata on the account; the app does not display or use them.

§ 05

Services the app uses

  • Supabase: account sign-in, sessions and the optional Friends features, as described above.
  • Resend: delivers sign-in confirmation and password-recovery emails for the Supabase Auth service. It receives your email address and the content of those emails. See Resend's privacy policy.
  • Cloudflare: hosts this site, the downloads and the app's update checks, and runs the relay used when you turn on internet sharing. Update checks and relay connections carry ordinary request data such as your IP address.
  • Your AI provider: Codex, Claude, Gemini or GitHub Copilot CLIs run on your Mac and talk to their own companies under your own account and those companies' terms.
§ 06

Retention and deletion

The app keeps the newest 10,000 local timeline events per party. Live views use smaller windows. Friend invitations expire after one hour, while account, friendship, and block records remain until removed or the account is deleted. Exact hosted log and backup retention periods are not documented here.

Signing out ends the active local session. Removing a remembered account deletes that encrypted saved copy. The app can download the signed-in profile, Friends records and saved-account labels as JSON without passwords, session tokens, CLI credentials or project files. Save the export in a private folder. Neither signing out nor exporting deletes the Supabase account or its hosted social records.

Saved chats: after each finished AI turn, the app saves your own prompts and your AI's replies from that party on your Mac only, encrypted with the macOS keychain and kept separately for each account. Tool steps are not saved, nothing is uploaded, and the newest 100 chats are kept. Delete one, or all of them, from the lobby at any time. Deleting your CodeParty account also deletes that account's saved chats on the Mac you delete it from; signing out or removing a remembered account does not.

The app also includes a separately confirmed self-service deletion flow backed by an authenticated Supabase Edge Function; the function derives the target from the signed-in identity and deletes the hosted account and its cascading Friends records. For privacy questions, email the support address above.

Note

This page is written to match what the app does today. It is not legal advice and has not been reviewed by a lawyer.