Legal
Privacy policy
Effective October 9, 2026. This policy covers the SafeRepro Chrome extension (“SafeRepro”, “we”) published by EthanApp, and this website.
1. What SafeRepro handles, and why
| Data | What happens to it |
|---|---|
| Screenshots and tab recordings | Taken when you click Screenshot, Select an area or Record. A recording can include the tab's sound and, if you turn it on, your microphone. Stored in your browser on your computer. |
| Page logs: console messages, errors, network requests (addresses, status, timing, headers) and your actions on the page | Recorded in the page while you use it, and read by SafeRepro when you capture. Request and response bodies are kept only for failed requests (16 KB at most), and you can turn that off. What you type into form fields is never recorded, only which field you filled in. Stored with the report on your computer. |
| Page address and title, and technical details of your browser (version, operating system, window size, language, time zone) | Added to the report so the bug can be reproduced. Stored with the report. |
| What you write: title, description, steps, annotations | Stored with the report. |
| Issue-tracker details: Jira site, email and API token; GitHub token and repository; Linear API key and team | Only if you connect a tracker. Stored in Chrome's extension storage on your computer and sent only to that tracker, to create the issues you ask for. |
| Settings, including your redaction patterns and the sites with “always record logs” | Stored in Chrome's extension storage on your computer. |
On sites where you turn on “always record logs”, the page logger runs from the moment each page loads and keeps a limited log in that page's memory; it is read only when you capture a report, and is gone when you leave the page. On every other site, SafeRepro does nothing until you click it.
2. Redaction
Before a report can be downloaded, copied or sent, SafeRepro replaces likely secrets in everything it captured from the page: authorization headers and cookies, tokens in addresses, secret fields in bodies (passwords, tokens, card numbers and similar), JWTs, API and private keys, card numbers, email addresses (on by default) and IP addresses (off by default), plus any patterns you add. You review the result in the report before sharing. This happens on your computer. Redaction is automatic pattern matching and can miss something or hide too much; please check the review before you share. Text you type yourself is not changed, and the screenshot shows what was on screen: use the Blur tool for anything visible.
3. When data leaves your computer
- When you download or copy a report (zip, HTML, HAR, Markdown, screenshot): the redacted report is saved where you choose or put on your clipboard.
- When you send a report to Jira, GitHub or Linear: the redacted report is sent from your browser directly to the service you connected, with your token, and is then governed by that service's terms and privacy policy.
- “Suggest title” uses Chrome's built-in AI, which runs on your computer; nothing is sent to an AI service.
Nothing is ever sent to us. We have no server that receives your data.
4. What we don't do
- No SafeRepro account, and no server that receives your reports, logs or tokens.
- No analytics, advertising, tracking or crash-reporting code in the extension.
- We never sell, rent, share or transfer your data, and never use it for advertising, credit decisions or anything other than the features described here.
- No person, including us, can read your data unless you send it to them.
5. Chrome Web Store Limited Use
The use of information received by SafeRepro complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Page content, logs and browsing data are used only to provide SafeRepro's single purpose: creating bug reports with sensitive data redacted, and sharing them where you choose. They are not transferred to anyone except as you direct (to the issue tracker you connected), not used for advertising, not used to determine creditworthiness, and not read by any person at SafeRepro.
6. Permissions
| Permission | Why |
|---|---|
activeTab | Capture the tab you clicked SafeRepro on (toolbar button, shortcut or right-click menu), only at that moment. |
scripting | Run the page logger and the area selector in that tab, and read the log. |
storage, unlimitedStorage | Keep reports, screenshots, recordings and settings on your computer. |
offscreen | Record the tab in a hidden page while you keep working. |
alarms, contextMenus | Delete old reports daily; add “Report a bug” to the right-click menu. |
tabCapture (asked on first recording) | Record the tab as video. |
| Access to a site (asked per site) | “Always record logs on this site”. Remove a site in Settings to give the access back. |
| Access to your tracker's address (asked when you connect it) | Create issues in Jira, GitHub or Linear. |
7. Keeping and deleting your data
Reports are deleted automatically after 30 days by default (7, 30, 90 days or never, in Settings → Storage). Delete a report yourself at any time, or all of them with Settings → Delete all reports. Disconnecting a tracker deletes its token from your computer. Uninstalling the extension removes all of its data from Chrome. Issues you created in a tracker stay there; delete them in that service.
8. This website
This website is a static site. It sets no cookies and runs no analytics. Our hosting provider (Cloudflare) may process standard request data, such as IP addresses, to deliver and protect the site.
9. Children
SafeRepro is not directed at children under 13 and collects no personal information from anyone.
10. Changes
If a future version handles data differently (for example optional uploads to your company's storage), this policy will be updated before that version is released, with a new effective date, and the new feature will ask for your consent before anything new leaves your computer.
11. Contact
Questions about privacy: ethanhdt@gmail.com.