Privacy Policy
The short version
- The developer does not collect, receive, sell or share any data about you or the pages you capture. There is no server, account, analytics, advertising or tracking.
- Captures are built on your computer and saved to your Downloads folder. Nothing is uploaded.
- To save a page, the extension makes web requests from your browser to the sites that page already uses, the same way the page loads itself.
- A few settings and your last capture result are stored in your browser. You can clear them from the popup, and uninstalling removes them.
- Captured files can contain private information that was on the page. They are yours; protect them accordingly.
1. Who is responsible
Page Source Capture (“the extension”) is developed and maintained by Win Htut Hein, an independent developer (“the developer”, “I”). For privacy questions or requests, write to apex.decoy.scarface.web@gmail.com.
2. What the extension does with data, and when
The extension does nothing on a page until you start a capture (toolbar button or keyboard shortcut). It does not run in the background on pages you browse, and it does not read tabs you did not choose to capture. When you start a capture it:
- Reads the page in the tab you chose: the rendered document, frames, open and closed shadow roots, stylesheets, scripts, images, fonts, the page’s Content Security Policy, and, if you enable “Site intel”, the names and counts (never the values) of the page’s
localStorage,sessionStorage, IndexedDB databases, service workers and JavaScript-readable cookies. - Requests the page’s own resources (CSS, JS, fonts, images, source maps and, optionally, the original server HTML) directly from your browser. Those requests go to whichever hosts the page uses, and they include your browser’s normal cookies for those hosts, just as when the page loaded. The operators of those sites can see these requests in their logs, as they would see any visit.
- In Deep mode only, attaches Chrome’s debugger interface to that one tab for the duration of the capture to read exact network responses (including response bodies), build a single-file MHTML snapshot and take a full-page screenshot. It detaches when the capture ends. Chrome shows its “debugging this browser” banner while this happens.
- Builds the archive locally, re-reads every file to verify it, and saves one
.ziptoDownloads/Source-Capture/.
3. What is stored in your browser
| Data | Where | Contents and lifetime |
|---|---|---|
| Your options | chrome.storage.local | Which checkboxes and mode you selected. Kept until you uninstall the extension. |
| Last capture result | chrome.storage.local | For the most recent capture: the page title and address (URL) of each captured page, the saved file’s path, file counts and sizes, offline-readiness, warnings and any error text. It is replaced by the next capture. You can remove it at any time with “Clear saved data” in the popup, which also resets your options. |
| Progress | chrome.storage.session | The current phase and tab title while a capture runs. Held in memory and discarded when the browser closes. |
This data stays on your device. It is not synced and is never sent to the developer.
4. What leaves your device
Only two things can, and both are your decision or the page’s own traffic:
- Requests to the sites you capture, described in section 2.
- Feedback you choose to send, described in section 6.
The extension contains no analytics, crash reporting, advertising, tracking pixels, remote configuration or remotely hosted code. All code runs from the installed package. The developer does not sell, rent, transfer or disclose user data to anyone, does not use it for advertising or credit decisions, and does not use or transfer it for any purpose unrelated to the extension’s single purpose of saving the page you are viewing. (The developer does not receive it in the first place.)
5. The files you capture
A capture is a copy of what a web page contained when you saved it, and may include personal data, confidential material or copyrighted content that was visible to you, especially if you were signed in.
- By default the extension redacts typed form values, hidden inputs, CSRF tokens in
<meta>tags and cookie and authorization headers in the HAR file, and it never saves password fields. You can turn this off in the popup. - Redaction is best effort. Inline scripts, page text, API response bodies in Deep mode and URLs can still contain secrets or personal data. Review a capture before you share, publish or attach it anywhere.
- Captures are ordinary files in your Downloads folder. They are protected only by your computer’s own security and are not encrypted by the extension.
6. Feedback and “Report a problem”
The “Report a problem” link opens a draft email in your email app, addressed to apex.decoy.scarface.web@gmail.com. “Copy details” puts the same text on your clipboard. The extension itself sends nothing.
The draft contains an empty space for your description, followed by technical details: the extension version, your browser and operating-system string, which options are on, and the outcome of your last capture (file counts, sizes, offline-readiness, and warning or error messages with web addresses replaced by <url>). It is built to leave out page content, page titles, captured file names and URLs, but error text is generated by the browser and the page, so read the draft before you send it; you can edit or delete anything in it.
If you send an email, the developer receives your email address and whatever you include, and uses it only to reply and to investigate the problem you reported. It is kept only as long as needed for that purpose. You may ask for it to be deleted at any time.
7. Why each permission is needed
| Permission | Used for | Notes |
|---|---|---|
| Access to all sites | To read the page you choose to capture and to fetch the CSS, JS, fonts and images it uses, which can be hosted anywhere. | Used only while a capture you started is running. |
scripting | To read the document, frames and shadow roots of the tab you capture. | The extension injects only its own bundled code. |
downloads | To save the finished .zip to Downloads/Source-Capture/ and to show it in its folder. | |
storage | To remember your options and show your last result and progress. | See section 3. |
offscreen | To turn the finished archive into a downloadable file; service workers cannot do this themselves. | The offscreen page loads no remote content. |
webNavigation | To list a tab’s frames so each iframe’s content is attached to its parent page. | |
debugger | Deep mode only: exact network responses, MHTML snapshot, full-page screenshot. | Attached to one tab, only during a Deep capture, and detached afterwards. |
8. Children
The extension is a developer and research tool and is not directed at children under 13. It does not knowingly collect information from anyone, including children.
9. Your rights
Because the developer does not collect or hold data about you through the extension, there is nothing to access, correct or delete beyond any email you sent. For those emails, and wherever the law of your country (for example the GDPR or the CCPA) gives you rights over personal data, you can contact apex.decoy.scarface.web@gmail.com to ask for access, correction or deletion. To remove everything the extension stores in your browser, use “Clear saved data” and then uninstall the extension; delete saved .zip files from your Downloads folder yourself.
10. Changes to this policy
If the extension’s data handling changes, this policy will be updated before the change ships, the version and effective date above will change, and the Chrome Web Store listing will be updated to match. Any change that would involve collecting data from users would be made only in a new version that asks for your consent.