Privacy Policy
Last updated: July 29, 2026
Repliqa is a browser extension that captures bug context from a webpage — screenshot, console output, network activity, and reproduction steps — and turns it into a structured report. This policy explains what data Repliqa accesses, how it's used, and where it goes.
Summary
Repliqa runs entirely on your device. It does not have a server, does not send your data anywhere on its own, and does not include any analytics, advertising, or tracking code. Everything Repliqa captures is stored locally in your browser and only ever leaves your device when you explicitly export or share a report.
What Repliqa accesses
When you click the Repliqa icon (or use "Start Recording") on a page, it can capture:
- A screenshot of the visible page, and any additional screenshots you choose to add via the snip tool.
- A DOM snapshot of the page at the moment of capture.
- Console output (log, info, debug, warn, error, and uncaught exceptions) from the page and its frames.
- Network activity: request/response metadata (URL, method, status code, timing, headers, and — for JSON/text responses — bodies) for requests made by the page while Repliqa is active.
- Reproduction steps, if you start recording: clicks and form field changes on the page, logged as short descriptions (e.g. "Clicked Checkout button").
- What you type into Repliqa itself: the title, description, and notes fields of the bug report you're composing.
- Basic environment info: the page URL, browser/OS, and screen/viewport size, used to fill in the report's metadata.
When capture happens
Repliqa only captures this on pages where you actively invoke it. It does not run in the background collecting data from every page you visit.
Sensitive data handling
Repliqa is designed to avoid capturing credentials and payment details as part of reproduction steps and network logs:
- Password fields, and any field whose name, id, placeholder, or autocomplete attribute matches patterns for card numbers, CVV/CVC, SSNs, PINs, tokens, or similar, are recorded as "changed" without ever recording the value typed into them.
- Sensitive HTTP headers (Authorization, Cookie, Set-Cookie, X-Api-Key, Proxy-Authorization) are redacted from the network activity log before they're ever shown in a report.
Screenshots and DOM snapshots
These protections apply to the step recorder and network log specifically. A screenshot or DOM snapshot is a capture of whatever is visibly on the page, so avoid capturing a page that is itself displaying sensitive information you don't want included in a report.
Where your data is stored
All of the above is stored locally in your browser using Chrome's storage APIs:
- Local storage: your theme preference and your local report history (past reports you've exported or sent, kept so you can re-download or delete them later).
- Session storage: an in-progress draft of the report you're currently composing (so closing and reopening the sidebar doesn't lose what you've typed) and the state of an active recording session (so it survives a page reload while you're reproducing a bug). Session storage is cleared automatically when the browser closes.
No remote access
None of this is synced to a remote server, an account, or any third party by Repliqa. We do not operate a backend, and we do not have access to any of this data ourselves.
When data leaves your device
Data only leaves your device when you take an explicit action to make that happen:
- Copy to Clipboard — copies the plain-text or Markdown report to your system clipboard.
- Download HTML Report / Download ZIP Archive — saves a file to your Downloads folder using Chrome's downloads API. What you do with that file afterward (email it, upload it, paste it into a chat) is entirely up to you.
No automatic uploads
Repliqa itself never uploads, transmits, or sends captured data to any server, API, or third party.
No remote code
Every script Repliqa runs is bundled with the extension at build time. Repliqa does not download, fetch, or evaluate any remote or dynamically-loaded code.
No third parties, no ads, no tracking
Repliqa does not sell, rent, or transfer your data to third parties. It contains no analytics SDKs, no advertising code, and no tracking pixels. We don't know how many people use Repliqa, what pages they use it on, or what's in their reports, because none of that is ever sent to us.
Your control over your data
- Report history: viewable and individually deletable from the Repliqa settings page, with a "Clear All" option to remove every saved report at once.
- Uninstalling the extension removes all locally stored Repliqa data (settings, drafts, and history) along with it, per standard browser behavior.
Children's privacy
Repliqa is a developer/QA tool not directed at children, and we do not knowingly collect data from children.
Changes to this policy
If this policy changes, we'll update the "Last updated" date above and, for material changes, note them here.
Contact
Questions about this policy or Repliqa's data practices can be sent to: hi@douglasmasho.com