Repro — Privacy Policy

Last updated: August 11, 2026

Repro is a browser extension that records a web page you choose — screen video, console logs, network requests, user actions, and storage — into a single capture that you can replay to reproduce and debug frontend issues. This policy explains what data Repro handles and how.

In short: Repro is local-first. Everything it captures stays on your own computer unless you explicitly turn on Google Drive upload, in which case captures go only to your own Google Drive. Repro shows no ads, uses no third-party tracking or advertising SDKs, and never sends recorded content anywhere. The only data that can leave your device automatically is an optional, off-by-default anonymous count of which features you use — described in full below.

What Repro captures

Repro only captures data while you actively start a recording or take a screenshot on a tab you have chosen. During a recording it may record:

Website content — screen video of the tab, page text and images, the page's HTML/CSS, and the bodies and headers of network requests made by the page.
User activity — clicks, keystrokes, scrolling, navigation, and network activity that occur on the page during the recording.
Page environment — the recorded page's URL and title, browser user-agent, language, timezone, viewport, and storage values (localStorage, sessionStorage, cookies, IndexedDB) for the recorded page.
Microphone audio — only if you explicitly enable narration and grant Chrome's microphone permission. Audio is mixed into the recording on your device and is never streamed anywhere.

All of this stays on your device. Repro does not track your browsing history, and it does not run or collect anything on pages where you have not started a recording or capture.

How your data is stored and used

Captures and settings are stored locally on your device (in the browser's IndexedDB and local storage) and, when you save or export, in your Downloads/Repro folder or a folder you choose.
Data is used only to display, replay, and export your own captures — the extension's single purpose. It is never used for advertising, profiling, creditworthiness, or lending.
Repro does not sell or transfer your data to third parties.

What leaves your device

Only three things can ever leave your device, and you control all three:

What	When	Where it goes
A capture (video, logs, network, screenshots)	Only when you choose to export, download, or upload it	Your own disk, or your own Google Drive if you enable it
Anonymous feature-usage events	Only if you turn on usage analytics (off by default)	A Cloudflare Worker operated by Repro's developer
Google sign-in	Only if you enable Google Drive upload and sign in	Google, under Google's own privacy policy

Optional usage analytics

Usage analytics is off by default. It is only active if you turn it on — either on Repro's welcome screen or in Settings — and you can turn it off again at any time in Settings, which stops all sending immediately.

What is sent

When enabled, Repro sends a small JSON message each time you use a tracked feature. The message contains only:

An event name from a fixed list, for example recording_started, screenshot_taken, gif_exported, or capture_deleted.
An anonymous ID — a random identifier generated on your device the first time analytics runs. It is not derived from your account, email, hardware, or IP address, and it is not linked to any identity. It exists only so repeated events can be counted as one user rather than many.
The extension version and a timestamp.
A build flag indicating whether the extension was installed from the Chrome Web Store or loaded unpacked, so developer testing can be excluded from the totals.
A few non-identifying feature flags — for example whether console capture was switched on or off, or a coarse recording-length bucket such as "30–60s". These values are stripped to simple on/off, numeric, or short alphanumeric values before storage.

What is never sent

Analytics never includes anything from a capture. Specifically, Repro does not send page content, HTML/CSS, screenshots, video, audio, console logs, network requests or headers, storage values, page URLs or titles, your browsing history, your name, your email address, or any other personal identifier.

Where it goes and how long it is kept

Events are sent to a Cloudflare Worker operated by Repro's developer at repro-analytics.aditya-tiwari1998-apps.workers.dev and stored in a Cloudflare D1 database. There is no Google Analytics, no advertising SDK, and no third-party analytics provider involved. Cloudflare acts only as the hosting provider and processes the request under Cloudflare's privacy policy. IP addresses are not recorded in the analytics database. Stored events are automatically deleted after 180 days.

Your control

Turn analytics off in Settings to stop all sending. Because the anonymous ID is stored only on your device, removing the extension or clearing its data permanently disconnects you from any past events, which remain only as anonymous aggregate counts until they are deleted on the schedule above.

Optional Google Drive upload

Google Drive upload is off by default. If you enable it and sign in, Repro uses Google OAuth solely to upload your finished capture to your own Google Drive and to create a shareable link that you control. Repro requests only the drive.file scope, which limits access to files the app creates. Repro does not read your other Drive files and does not send your data anywhere else. Data handled through Google Drive is subject to Google's Privacy Policy.

Sensitive content in recordings

Because Repro records whatever is on the page you choose, a recording could incidentally contain sensitive information (for example, personal details, authentication tokens, cookies, or payment fields shown on or sent by that page). Repro does not seek out or extract such data, it stays on your device, and Repro offers redaction and blur tools for screenshots and exports. You control what you record and where you share it — please review captures before sharing them.

Your control and data deletion

You can delete any capture from the Captures library at any time, which removes its data from local storage.
You can turn usage analytics off at any time in Settings.
Removing the extension deletes its locally stored data, including the anonymous analytics ID. Files you exported to disk, and anything you uploaded to your own Google Drive, remain until you delete them yourself.

Children

Repro is a developer tool and is not directed to children under 13, and Repro does not knowingly collect personal information from them.

Permissions

Repro requests only the permissions needed for the above: recording the active tab (tabCapture, activeTab, offscreen), running its capture scripts on the pages you record (tabs and host access), saving files (downloads, storage, unlimitedStorage), and optional Drive sign-in (identity). Microphone access is requested separately by Chrome and only when you enable narration. Repro does not execute remote code; all code ships inside the extension.

Changes

If this policy changes, the "Last updated" date above will be revised. Material changes to what leaves your device will not be applied retroactively — analytics, in particular, will always require a fresh opt-in.

Contact

Questions about this policy: aditya.tiwari1998.s@gmail.com