Security

SceneRecap handles screen recordings, which can contain anything. Here is how we protect them.

Capture

Recording is explicit and per-session; the extension requests tab/screen access only when you press record and holds no background capture permission.
Password and payment fields are visually masked during capture. Keystrokes are never logged as text.
You can trim, cut segments, blur regions and mute ranges before upload; redactions are applied at transcode and the unredacted original is deleted afterwards.
Recording is blocked in incognito windows and on domains you blocklist.

TLS 1.2+ everywhere. Uploads go directly to private object storage via short-lived signed URLs.
Media is served through short-TTL signed URLs or a token-gated media proxy — object storage is never public.
Integration tokens are encrypted at rest with AES-256-GCM using a rotatable key; API keys and refresh tokens are stored as SHA-256 hashes.
Hosting in Google Cloud europe-west3 (Frankfurt) with encryption at rest.

Passwordless sign-in (single-use magic links), rotating refresh tokens with reuse detection, and per-device session revocation.
Row-level tenancy: every workspace-scoped query goes through a repository layer that enforces membership and role.
Staff access to customer data is limited to a small admin console with audit logging.

Only sampled frames, the interaction log and transcript are sent to the model by default — not the full video. Model outputs are schema-validated before use.
Google's paid Gemini API terms apply: prompts and outputs are not used to train Google's models.

Dependency scanning and secret scanning in CI; infrastructure defined in code.
Backups of the primary database; media stored redundantly by the cloud provider.
Coordinated disclosure: report vulnerabilities to hello@scenerecap.com. We acknowledge within 2 business days.

SOC 2 is on the roadmap; this page describes our current posture honestly rather than a certification.