How your data is protected

Last updated October 16, 2026

On your Mac, before anything is sent

• Secrets are masked. API keys, tokens and passwords that show up in screen text or transcripts are masked on the Mac before anything is uploaded.
• Password fields and password managers are never read. Neither are Keychain Access, private or incognito browser windows, or any app you mark as private.
• Audio is never stored or sent. Calls are transcribed on the Mac by Apple's speech engine; only the text is kept.

In transit

• Everything to and from cachejay.com is encrypted with TLS, served through Amazon CloudFront.
• The server only accepts requests that come through CloudFront, so it can't be reached around it.
• The server talks to its Postgres database over TLS and checks the database's certificate.

Stored data

• One namespace per account. Each account's notes and captures are kept in their own namespace, keyed by a random ID. Every request is checked against the signed-in account, so one account can't read another's.
• Screenshots are kept in a private storage bucket with all public access blocked, and deleted after 14 days. Only the server reads and writes it.
• Tokens and sessions are stored only as hashes. That covers the Mac's sign-in token, web sessions, sign-in codes and the tokens given to connected AI apps. License keys too: we keep only a hash of each, so a copy of the database wouldn't let anyone sign in.
• Your own AI keys, if you add an Anthropic, OpenAI or Gemini key, are kept encrypted on the server, used only there, and never sent to a Mac.

Signing in

• There are no Cachejay passwords to steal or reuse. You sign in with a link or 6-digit code we email you, or with Google or Apple, whose sign-in tokens we check against their published signing keys.
• The web session cookie is HttpOnly, Secure and SameSite=Lax, so page scripts can't read it and it's only sent over HTTPS.
• AI apps you connect (ChatGPT, Claude and others) sign in with OAuth 2.1 and PKCE, read-only unless you also let them change your projects. You can disconnect them all at any time from the Mac's menu bar, and a team's owner can keep every member's AI apps read-only.
• Single sign-on for teams. A team with a verified domain can connect Okta, Entra ID, Google Workspace or any SAML or OIDC provider (through WorkOS), require it for everyone at the domain, and have people its IT deactivates removed from the team and signed out everywhere.
• An audit log records sign-ins, Macs and AI apps added, exports, deletions and team changes (never content), for a year. You see yours on your Account page; a team's owner sees the team's.

Who can access your data

You, and AI apps you connect. If you share a project with a team, your teammates can read that project's notes and call notes (what a team sees).

At Cachejay, only the founder has production access today. It's used only to operate the service, fix problems, or help when you ask for support, and every look at a customer's data outside the app is written down in our access log. We don't browse your data.

The companies we rely on, and what each handles, are listed on Subprocessors.

Deleting data

• Export everything in your account as JSON, and delete your account (which also ends any subscription), from Account › Your data at cachejay.com/app.
• Choose how long the cloud keeps what Cachejay captures: forever, a year, 90 or 30 days. Older captures are deleted each day; your written-up notes stay.
• Settings › Delete Cloud Notes… on the Mac deletes everything in the cloud, screenshots included, and disconnects every app.
• When a trial or plan ends, everything in the cloud is deleted after 60 days.

What we don't have yet

• SOC 2. We're not SOC 2 audited yet. If you need a security questionnaire answered, email us and we will.
• HIPAA. We don't sign business associate agreements, so Cachejay isn't for protected health information.

Reporting a vulnerability

If you find a security problem, email security@cachejay.com with what you found and how to reproduce it. We'll reply, keep you updated while we fix it, and won't take action against good-faith research that avoids other people's data and doesn't disrupt the service. Our security.txt has the same contact.