Data practices

CodeSense is a desktop app that runs on your Mac. This page says plainly what it stores, what it talks to, and what we collect to run the private beta. The privacy page is the short version.

What's stored where

~/.codesense
The app's local folder: your local copy of each team's context repository, caches, and the tools CodeSense manages.
Your context repository
Instructions, skills, agents, stories and dashboards, as plain files in a git repository on your own git host. It changes only when you or your team push to it.
Your worktrees
Git worktrees of your code repositories, next to each repository by default (../<repo>-wt/). CodeSense writes your team's context into them as real files and lists those files in the worktree's local git exclude, so they stay out of your commits.
macOS Keychain
The credentials you connect, such as your GitHub sign-in and any service tokens.
~/Library/Logs/ai.codesense
The app's log file. It stays on your Mac.

What the app talks to, and why

  • GitHub, with the account you connect: to list and clone your repositories, sync your team's context repository, and show pull requests and reviews.
  • The daily update check. CodeSense checks for updates about once a day. It sends your beta key, the app version and a random install ID. When an update is available, it downloads it in the background. Like any web request, our server sees your IP address; we keep only the country for checks, and for downloads we store a salted hash of the IP address, not the address itself. Nothing else. It's how the app learns about new builds and whether your beta key is still active. When a new build exists, the app downloads it in the background from the same server. That download carries no beta key. If the check can't reach us, the app keeps working for 14 days.
  • The agents you run. CodeSense starts agent CLIs such as Claude Code or Codex in your worktrees. They talk to their own model providers under their own settings and terms. CodeSense doesn't change what they send, and it doesn't call a model provider itself.

Accounts and credentials

There is no CodeSense account. In the private beta the first launch asks for the beta key from your invite email, then asks you to connect GitHub, and the app doesn't open your workspace until you do; that connection is how the app knows who you are. Your beta key and the credentials you connect are stored in the macOS Keychain on your Mac.

Telemetry

The app has no usage analytics, tracking or crash-reporting service built in, so it sends no telemetry. If we ever add product telemetry, it will be opt-in: off until you turn it on, with a plain description of what it sends. The daily update check and the background update download aren't telemetry: they carry no usage data.

Feedback

Feedback is separate from everything above: it reaches us only when you choose to send it from the app. It includes:

  • Your message, and what kind of feedback it is
  • A screenshot or the app's logs, only if you attach them
  • The app version and macOS version, and which beta key and Mac it came from, so we can reply

To fix what's wrong and to reply to you. Kept for the beta period, then 30 days after it ends.

What we collect for the beta

To run the private beta, our server keeps the records below. Applications aren't open yet; until they are, the first record we hold for you is your invite.

You, as a beta user

When we invite you, or when you apply once applications open.

  • Your email address, and your name and company if you give them
  • Your email's domain, and whether you confirmed the address
  • Your status in the beta (invited, waiting, approved, ended) and which wave you joined in
  • If you apply: your answers, your platform, the version of the terms you agreed to and the country you applied from
  • A referral code, and who referred you, if anyone did

Why: To decide who gets in, send your invite and beta key, and contact you about the beta.

How long: Kept for the beta period, then 30 days after it ends. An application you never confirm is deleted after 7 days.

Your beta key and Macs

When you activate CodeSense on a Mac.

  • Your beta key, its plan and whether it's active
  • Each Mac you activate (up to 3): a random install ID made by the app, when it was activated, and the version and country of its last update check

Why: So the app works on your Macs and stops working on a Mac you remove or a key that's ended.

How long: Kept for the beta period, then 30 days after it ends.

The daily update check

About once a day, from each activated Mac.

  • The install ID, the app version and the time of the check
  • The country your IP address is in. We don't store the address itself
  • Your Mac's clock reading, used only to notice a clock set backwards

Why: To offer you new builds, keep your key working, and spot a build that needs pulling.

How long: Each check is kept for 180 days.

Downloads

When you use a download link from your email.

  • The version and file, the time and the country
  • A one-way hash of your IP address, made with a key we change every day, so we can tell when one link is used from many places

Why: To keep download links personal and notice a link that's been shared.

How long: Kept for the beta period, then 30 days after it ends.

Emails we send you

Each time we write to you.

  • A copy of each email: its subject, its body, when it was sent and whether it was delivered

Why: So we know what you've been sent and can answer questions about it.

How long: Kept for the beta period, then 30 days after it ends.

Who handles it for us

  • Cloudflare hosts this site and the beta service, stores the beta's database and builds, and forwards mail sent to beta@codesense.ai to us. Server logs are kept for 7 days and never contain your beta key.
  • Resend sends the emails we write to you, from beta@codesense.ai.

They process your data only to provide those services to us. We don't sell it or share it with anyone else.

How long we keep it, and how to delete it

  • An application you never confirm: 7 days.
  • Each update check: 180 days.
  • Everything else: for the beta period, then 30 days after it ends.

To see or delete your data, write to beta@codesense.ai from the address we have for you. We delete your record and everything linked to it, and tell you when it's done. Deleting your data ends your beta access. Our database backups may still hold a copy until they roll off; we never restore a deleted person from them.

This website

This site has no analytics or tracking scripts and sets no cookies. Fonts are served from this site. Your browser's local storage remembers your light or dark theme choice, and that never leaves your browser.

The site has no forms while the beta is invite-only. If you write to beta@codesense.ai, we keep your message and address only to reply and, if you ask, to invite you.

Sources

Each statement about the app was checked against its source code at commit 1b3d5a69d73473db077dfb44f4390b42cded6bd4. Paths are relative to the app repository. The beta key and the daily update check belong to beta builds, which add them to the app; they follow the private beta's design rather than this commit.

The first launch waits for GitHub
  • src-tauri/src/commands/auth.rs (build_auth_status)
  • src/app/App.tsx
No analytics or crash-report service
  • package.json
  • src-tauri/Cargo.toml
Local folders
  • src-tauri/src/commands/paths.rs (codesense_home_dir)
  • src-tauri/src/context_repo/path.rs
  • src-tauri/src/commands/worktree.rs (DEFAULT_WORKTREE_DIR)
  • src-tauri/src/lib.rs (log file)
Context kept out of your commits
  • src-tauri/src/commands/content_engine.rs (.git/info/exclude)
Credentials in the macOS Keychain
  • src-tauri/src/commands/credential_store.rs
  • src-tauri/Cargo.toml (keyring)

Questions about this page? Write to beta@codesense.ai; a person reads every message.