Privacy Policy

1. Information we collect

Account information. Your name, email address, and — if you sign in with Google or another OAuth provider — the identity information that provider returns to us (provider user ID, email, and display name). We do not receive your password from OAuth providers.

Recording content. The screenshots, video, and audio files you capture, along with titles and other metadata you add. This is the most sensitive category of data we hold: a screen recording can contain anything that was on your screen or said out loud, including other people's information. We treat it accordingly and it is never public unless you make it so.

Usage data. When a recording page or share link is viewed, we record a hashed or truncated IP address (never the raw IP), coarse device and browser information, a timestamp, and, for video, how much was watched. These rows live in our views table and power the view counts you see on your links.

Cookies. See our Cookie Policy for what we set and why.

2. Where your data is stored

ctrlcapture runs on Supabase, which provides our database, authentication, file storage, and hosting. Your recordings are stored as files in Supabase Storage and their metadata in a Supabase Postgres database, in the [STORAGE REGION — CONFIRM ONCE CHOSEN] region. When the region is finalized it will be named here explicitly rather than described in general terms.

3. Sub-processors

Today we use exactly one sub-processor: Supabase (database, authentication, file storage, hosting).

When we add automatic transcription and AI summaries, the speech-recognition vendor and the AI-summary vendor will be named individually on this page on the day each is put into service, along with what data is sent to them. We will not fall back on a vague "we may share data with third parties" statement.

4. How long we keep it

Recordings are kept until you delete them or delete your account. Deleting a recording removes the file and its metadata; deleting your account removes all of your recordings, share links, and view records.

Accounts that have been inactive for [RETENTION PERIOD, e.g. 24 months] may be cleaned up along with their content. We will email you before that happens.

5. Your rights

You can access, correct, export, and delete your information. Most of this is available directly in the product; for anything else, email privacy@ctrlcapture.com and we will respond within the period required by applicable law.

California residents. If you live in California, you have the right to know what personal information we collect, use, and disclose about you; the right to request deletion of that information; and the right not to be discriminated against for exercising these rights. You may make up to two such requests in any 12-month period. We do not sell or share personal information for cross-context behavioral advertising. Submit requests to privacy@ctrlcapture.com.

6. Children's privacy

The Service is not directed to children under 13, and ctrlcapture does not knowingly collect personal information from anyone under 13. If we learn that we have, we will delete it. We do not operate an age-verification process.

7. Security

Every table that holds your data enforces row-level security in the database itself, not just in the application. Recording rows, share links, and view records are readable and writable only by the account that owns them, checked against the signed-in user's identity on every query. Share links work by token: a token grants read-only access to exactly one recording and nothing else, and does not expose your library, your account, or any other recording. Recording files live in a private storage bucket and are served through short-lived signed URLs rather than public paths. Passwords on share links are stored hashed, and viewer IP addresses are hashed or truncated before they are written.

No system is perfectly secure. If we become aware of a breach affecting your data, we will notify you as required by law.

8. Contact

Privacy questions and requests: privacy@ctrlcapture.com.