Legal

Security

Screenshots and recordings are stored in private storage buckets and are served only after a workspace access check, or through a signed link that opens one file.

Last updated:

Where screenshots and recordings are stored

  • Screenshots live in a private storage bucket per workspace. Recordings live in a separate private bucket per workspace.
  • No bucket is publicly readable. Direct access to these buckets through the storage API is blocked for signed-in users and for anonymous visitors alike; only our server reads them.
  • When a workspace member opens a screenshot or a recording in the admin area, our server checks that member’s access to the workspace on every request and then streams the file.
  • Captures are deleted after 90 days.

Links that open one file

Some places cannot hold a sign-in session: the confirmation email a reporter receives, and the image preview inside a GitHub issue. For those we create a signed link that opens exactly one screenshot or recording, expires, and cannot be used to list or reach anything else. Treat such a link like an unlisted link: anyone who holds it can open that one file until it expires, so do not forward it, and mark regions that must never appear in a screenshot with the data-cc-mask attribute.

How the app is protected

  • Sign-in runs on Supabase Auth, and workspace data is protected by row level security in the database.
  • Connection tokens for GitHub and other destinations stay on the server and are never sent to the widget.
  • The widget runs inside a shadow root on your page and does not open a cross-origin frame, so your site needs no extra frame permission.
  • Secrets and tokens are removed from report text and recording metadata on our servers before delivery.
  • Before upload the widget masks password and credential-autofill fields, card fields and regions you mark with data-cc-mask in screenshots, and sensitive typed values in recorded steps. The full list is in the privacy policy.

Report a vulnerability

Write to [email protected] and describe what you found and how to reproduce it. Please do not open a public issue for a vulnerability we have not fixed yet.

More

Who processes data for us is listed on the data processing agreement page, and what we collect is described in the privacy policy.

Questions and related pages