SiteReel

Privacy Policy

This is a structural starting point, not legal advice — have an actual lawyer review it before relying on it, particularly because recording video and personal data can trigger regional requirements (GDPR, CCPA, and similar) that this outline doesn't substitute for.

What's collected

Account information (via Clerk — email, name), the video content you record, your edit/timeline data (zoom, spotlight, arrow, callout, and cut keyframes), and your plan (Free or Pro). When something goes wrong, we also collect basic error-diagnostic data (via Sentry) — browser/OS details, IP address, and stack traces — to help us find and fix bugs. We don't run behavioral or marketing analytics, and we don't sell or share data with advertisers.

Where it's processed and stored

The following sub-processors handle data on our behalf:

  • Neon — database (projects, recordings, timelines)
  • Backblaze B2 — raw and exported video files
  • Clerk — authentication and account data
  • Render / Vercel — application hosting
  • Sentry — error monitoring and diagnostic logging

Recording-specific disclosure

Since you're recording a live session of a website, that recording could incidentally capture personal data visible on screen — form fields, other people's information, account details, and similar. Responsibility for what ends up in a recording sits with the person doing the recording. Don't record sessions containing someone else's personal data without the appropriate rights or consent to do so.

Your rights

You can access, export, or delete your account and recordings at any time from Settings.

Cookies

We use a cookie required for authentication (your signed-in session), and one purely functional cookie that remembers whether the sidebar is expanded or collapsed. Neither is used for tracking or advertising. If you're in the EU, a cookie consent banner will apply once one is added.

Other

This service isn't directed at children under 13. Recordings and account data are retained until you delete them. Questions about this policy can be directed to the account owner via the contact details on our GitHub repository.