Privacy Policy
Last updated: 21 September 2026
1. Who we are
Repros ("Repros," "we," "us") is a Chrome extension and web dashboard for structured QA testing, operated by Otis Saint. This policy explains what information we collect when you use Repros, why we collect it, how long we keep it, and who can see it. It covers the Repros dashboard and the Repros Chrome extension when used by a member of an organization with a Repros account. It does not yet fully cover the separate "send a session link to an external customer" flow — that flow is still being finalized and will be governed by its own terms once complete.
2. Information we collect
Account and organization data. Your email, any name you provide, your organization's name, who invited you, and your permissions within your organization. Required to operate your account.
Test session data (from the Chrome extension). When a member of your organization runs a test session, we automatically capture: console output (warnings, errors, uncaught exceptions, unhandled rejections); page navigation events within the tab under test; failed network requests only (4xx/5xx or connection errors — we never capture successful requests, and we never capture request or response headers or bodies at all, for any request); screenshots, manual or automatic on error; any notes, annotations, checklist responses, and severity ratings a tester enters; and click events during the session, which record only the element type and a selector — never the value typed into a field, so a click near a password or payment input can't leak what was entered. This is tied to a deliberate, signed-in test session — not continuous background monitoring, and not data from your end customers' production use of your product.
Billing data. Stripe is our payment processor and handles your card details directly — we never store raw payment credentials. We store your plan, status, and the Stripe identifiers needed to reconcile your account.
We do not run third-party advertising or analytics trackers, and we do not sell any data we collect.
3. Where data is stored
Supabase, our database and file-storage provider. Screenshots live in a private storage bucket, separate from the database records referencing them.
4. Who can access your data
Your own organization's members, per the permissions your organization grants them. We can access organization data only for support, billing, or platform-operations purposes, through separately access-controlled internal tooling — not the same login your team uses. Shareable report links: a member of your organization can generate a read-only link viewable by anyone who has it, without a Repros account — treat these as you would any document you choose to share outside your organization; we don't control further forwarding. We do not sell, rent, or share your data with third parties for their own marketing.
5. Data retention
Retained for as long as your organization has an active subscription or trial. If cancelled or lapsed, retained for 30 days in case you reactivate; after that, your organization's account and session data (including screenshots) is deleted unless reactivated or otherwise arranged.
6. Cookies
Authentication session cookies only. No third-party advertising or tracking cookies.
7. Your choices and rights
Request a copy of, correction to, or deletion of your personal data at privacy@repros.dev. If removed as a member, we retain a record of your prior membership per Section 5's retention window, but you lose login access.
8. Customer testing sessions (separate, still being finalized)
Repros is developing a feature letting a member of your organization send a one-off testing-session link to your own end customer (not a Repros account holder), with additional data deliberately scrubbed or minimized for that flow. Because the legal basis for that customer's consent, retention period, and visibility are still being finalized, this policy doesn't yet make firm commitments about that flow — it will be governed by its own separately published terms before general availability, and this policy will be updated accordingly.
9. Changes to this policy
Updated as the product changes; the "Last updated" date above reflects this. Material changes are communicated to organization administrators directly.