Content Tripwire processes
Tripwire reads content only after you click a scan action. You can inspect selected text, visible content from the current page, or the main-frame DOM using Deep DOM mode.
Deep DOM can include hidden text, HTML comments, structured data and text-bearing attributes such as ARIA labels, alternative text, titles and placeholders. Tripwire does not read form-field values, passwords, cross-origin frames, images or PDFs.
Local session storage
The latest result for each scanned tab is stored in Chrome's temporary session storage. This lets the popup show the result and re-highlight exact evidence when you reopen it. Stored state includes the verdict and matched snippets, not the full page content. Copied reports redact URLs, email addresses and credential-like strings by default.
- Navigation
- The result is invalidated when the tab starts navigating.
- Browser close
- Session data is cleared when the browser session ends.
- Manual control
- You can remove the result from the extension popup at any time.
No external transmission
The extension makes no network requests. Scanned content and scan results are not sent to Tripwire, Google or another third party. There are no analytics identifiers, advertising services or user profiles.
Tripwire's use of Chrome APIs is limited to the user-requested local inspection feature and follows the Chrome Web Store Limited Use requirements.
Minimal Chrome permissions
- activeTab
- Temporary access to the current tab after you invoke Tripwire.
- scripting
- Runs the local content collector on that tab after your action.
- storage
- Keeps the latest per-tab result in temporary session storage.
- contextMenus
- Adds the option to scan selected text.
Tripwire does not request permanent access to every website.
Retention and deletion
There are no server-side scan records because there is no server connection. Choose Clear result, close Chrome or uninstall the extension to remove local scan state.
Website forms are separate from scans
The release-list form collects the email address you submit. The review fit-check form collects the work email, public product URL, input-to-action description, and any campaign tags included in the page link. This information is used only to respond to the request, assess fit, and measure which published route produced the enquiry.
Website forms are processed by Netlify, the hosting provider, and stored in the site owner's Netlify form account. Netlify may also process standard request metadata as described in its privacy statement. Do not submit credentials, private customer data, production prompts, or sensitive logs.
Enquiry data is kept only as long as needed to handle the request, maintain the related business record, and meet applicable legal obligations. You can request access, correction, or deletion by emailing kuba.opoczka@gmail.com. Deletion may be limited where a record must be retained by law.
Changes and contact
This policy will be updated before any material data-practice change ships. Questions can be sent to kuba.opoczka@gmail.com.