Legal

Privacy Policy

Last updated August 13, 2026

Working draft, not yet reviewed by a lawyer. Written to be accurate about what the Service actually does today, but not a substitute for a Thailand-based PDPA-literate lawyer’s review before this is relied on for real users.

1. Who this applies to

This Privacy Policy explains what FrameCatcher collects when you upload a video, create an account, or subscribe, and what we do with it. Thai business registration is in progress; this section will name the registered entity acting as data controller once it is.

2. What we collect

  • Video, for Shot Detection.Uploaded to our storage and processed to detect shots and extract frames. This routinely contains identifiable faces, which is personal data under Thailand’s Personal Data Protection Act the moment it’s processed — no facial-recognition feature is required to trigger that, and FrameCatcher doesn’t run facial recognition or identify who appears in your footage; it only extracts still frames at shot boundaries.
  • Video, for Interval Capture — we don’t collect it.This mode runs entirely in your browser. Your video file is read locally to capture frames and generate exports; it’s never uploaded to us, and none of the infrastructure providers in Section 5 ever see it.
  • Account info. Your email address, via Supabase Authentication (magic-link or Google sign-in). We never see or store a password.
  • Anonymous session identifier. A cookie set for visitors who process a video (either mode) without logging in, used only to enforce the free-tier daily processing limit and to catch abuse. Not used for advertising or tracking across other sites.
  • Payment information. Subscription payments are handled entirely by Stripe. We receive confirmation that a payment succeeded and store the resulting subscription status — we never see or store your card number.
  • Usage data. Records of jobs you run — video duration, shot count (Shot Detection) or frame count (Interval Capture), and credits spent (Shot Detection only, Interval Capture never spends credits) — kept to operate the credit ledger and provide support.
  • Feedback you send us. If you use the feedback widget, we store your message, the email address you provide (required, so we can read and reply), and which page you sent it from.

3. Why we process it

  • To perform the Service you asked for — detecting shots and extracting frames from a video you chose to upload.
  • To run the account, credit, and subscription system — signing you in, tracking your credit balance, billing a subscription.
  • Legitimate interest in preventing abuse — the anonymous rate limit and signup-bonus safeguards exist to stop the free tier from being farmed at everyone else’s expense.
  • Legal obligation — where content requires mandatory reporting (Section 5 of the Terms), or where tax/business records must be kept.
  • To read and respond to feedback you choose to send us.

We do not currently send marketing email or run advertising on FrameCatcher.

4. How long we keep it

  • Shot Detection source video: deleted automatically about 60 minutes after processing finishes, whether it succeeded or failed. Interval Capture has no source video to delete — it was never uploaded.
  • Shot Detection extracted frames and other exports: deleted automatically 30 days after creation. Interval Capture exports are generated and downloaded directly in your browser, so there’s nothing of yours stored on our servers to delete.
  • Feedback submissions: kept indefinitely for product-development purposes, deleted on request (Section 6).
  • Account, credit-ledger, and billing records: kept for as long as your account exists, and afterward only as long as needed for tax, accounting, or legal-dispute purposes.

5. Who we share it with

We don’t sell personal data, and we don’t share it with advertisers. Processing your data requires a small number of infrastructure providers (“subprocessors”), each of which only sees what it needs to do its job:

  • Cloudflare R2 — stores uploaded video and extracted frames.
  • Supabase — hosts the account database and handles sign-in.
  • Stripe — processes subscription payments.

Confirming a Data Processing Agreement is on file with each of these is still open — flagged for the pre-launch legal review, not yet resolved. Because these providers operate infrastructure outside Thailand, using the Service means your data may be processed on servers outside the country. This whole section doesn’t apply to Interval Capture’s video processing — as covered in Section 2, that video never leaves your browser, so none of these providers receive it.

6. Your rights

Under Thailand’s PDPA (and equivalent rights if you’re in the EU), you can ask us to:

  • Give you a copy of the personal data we hold about you.
  • Correct inaccurate data.
  • Delete your account and associated data (subject to what we’re legally required to keep, e.g. billing records).
  • Withdraw any consent you previously gave.

To exercise any of these, email privacy@framecatcher.app. You can also complain to Thailand’s Personal Data Protection Committee (PDPC) if you believe your rights have been violated.

7. Cookies

FrameCatcher uses one essential cookie (the anonymous session identifier described in Section 2) to enforce free-tier limits. No advertising or analytics cookies are set, and none are planned — if that ever changes, this policy will be updated first and consent collected before any such script loads.

8. Children

FrameCatcher isn’t directed at children and accounts require you to be at least 18, or the age of majority where you live.

9. Changes to this policy

We may update this policy as the Service changes. Material changes will be reflected by updating the “Last updated” date above.

10. Contact

Questions about this policy or your data: privacy@framecatcher.app.