WEB ARCHIVE PILOT PRIVACY POLICY
Privacy Policy
This Privacy Policy explains how WebArchive Pilot handles information when you use the extension
to save webpages as .webarchive files, reopen archived files in Chrome, and manage
your downloaded archive library.
Overview
WebArchive Pilot is a Chrome extension published by Boni Aditya. It saves webpages you choose as .webarchive files, can bundle selected tabs into .zarc files, and lets you view, search, export, and organize saved archives. This policy explains what information the extension processes, where it is stored, when it is shared, and how you can remove it. Questions or deletion requests about feature-request messages can be sent to boni.aditya@gmail.com.
What information the extension handles
When you choose to capture a page, WebArchive Pilot reads that tab's URL, title, favicon URL, and loaded webpage content. The capture can include text, images, links, styles, scripts, and other page resources. Depending on the page you choose, this content could contain personal or sensitive information. For a multi-tab action, the extension reads the tabs in the current window to identify which tabs you selected and processes the selected pages. It does not upload captured webpages to a WebArchive Pilot server.
To manage your library, the extension reads information about supported archive downloads and files you choose to open, including file names, local file paths, download IDs, sizes, dates, existence status, original page URLs and titles, and archive contents needed for viewing and search. It also handles folder names and assignments, previously opened file history, and interface preferences. Searches and page-text indexing run locally in the extension; search terms and indexed page text are not sent to the publisher.
If you choose to submit a feature request, you provide your email address, a title, a description, an optional related page URL, and an optional image. The extension also includes its version number. Your description or image may contain other information that you choose to include. Sending a feature request is optional and separate from saving or viewing archives.
How the information is used
WebArchive Pilot uses selected page content and metadata to create archive files, identify them in the library, display offline previews, search saved content, export files, and perform actions you request. It uses download records to find supported archive files, show their status, and locate or delete a file when you choose those actions. Folder data and preferences make the library and viewer work across sessions. Feature-request information is used to deliver your request to the publisher and, if needed, reply to you. The extension does not use this information for advertising, profiling, credit decisions, or sale to data brokers.
Where information is stored
Captured .webarchive and .zarc files, exports, and a JSON library backup are saved on your device through Chrome's download system. The backup contains library metadata, folder assignments, opened-file history, and details of supported downloaded archives, including local paths; it does not contain the archived page files themselves. The extension records the backup's location in chrome.storage.local and only creates an automatic backup when it cannot find an earlier one. A manual backup can be created when you choose Back up library.
Chrome's local extension storage holds archive metadata, folder information, opened-file history, the backup location, and some interface settings. A session-only flag is used to avoid repeating the store-rating prompt during the same browser session. Search indexes are built in the current extension page while you use search. Local extension storage is tied to the Chrome profile; downloaded archive and backup files are separate files on your device. WebArchive Pilot does not provide a cloud account or its own archive-sync service.
Sharing and third parties
Archive captures, archive files, library metadata, folder data, and search terms are not sent by WebArchive Pilot to the publisher, FormSubmit, advertisers, or analytics providers. They remain in Chrome's local extension storage or files on your device unless you choose to export or share them yourself. WebArchive Pilot does not sell user data.
The exception is the optional feature-request form. When you press Send feature request, the form sends your email address, request title and description, related page URL if provided, extension version, and any image you attached over HTTPS to FormSubmit (formsubmit.co), a form-delivery service. As with other web requests, FormSubmit may also receive connection information such as your IP address and browser details. FormSubmit forwards the submission to Boni Aditya at boni.aditya@gmail.com. The publisher can read and respond to the submitted request. Google operates the recipient Gmail service and may process the delivered email under its own privacy terms. These are the parties to whom a feature request is shared. FormSubmit states in its documentation that it retains form submissions for 30 days; uploaded-file handling differs. An email copy may remain in the publisher's Gmail account until it is deleted. See FormSubmit's privacy information at https://formsubmit.co/privacy.pdf and Google's privacy policy at https://policies.google.com/privacy.
If you open a live website or follow a link from an archive, that website receives the normal browser request and applies its own privacy practices. A saved page may also contain links, scripts, or resources that contact the original website when viewed; those requests are subject to that website's practices. The public Blogger copy of this policy is hosted by Google; visiting that page may be processed by Google under its privacy policy. The extension does not receive Blogger visitor data.
Your choices, retention, and deletion
You choose which pages and files to capture or open. You can use the archive features without submitting a feature request. You can delete archive entries from the library; where offered, that action may also remove the downloaded file and its Chrome download-history entry. You can remove local extension data through Chrome, including by uninstalling the extension. Downloaded archives, exports, and JSON backups are separate files and are not automatically removed by uninstalling the extension; delete those files from your device if you no longer want them. A previously created backup can still contain older library metadata until you delete or replace that backup.
For a feature request already sent, email boni.aditya@gmail.com to ask the publisher to delete the message from its inbox. FormSubmit and Google apply their own retention and deletion practices to copies processed by their services. Data may also be retained where required by law or to address security or abuse.
Security
Feature requests are transmitted to FormSubmit over HTTPS. Archive creation, viewing, and search run locally in the browser. Local files and Chrome profile data are protected by your device, operating system, and Chrome profile settings; anyone with access to those files or that profile may be able to read them. Do not archive or attach information you do not want stored on your device or included in a feature request.
Chrome permissions and limited use
The extension uses activeTab and pageCapture for a page you choose to capture; tabs for selected multi-tab actions and page metadata; downloads for saving, finding, exporting, revealing, and deleting supported files; storage for local library data and settings; contextMenus for right-click actions; notifications for save status and the session-limited rating request; file:///* access, if you enable it, for opening local archives; and access to https://formsubmit.co/* only to submit a feature request you choose to send. Information obtained through Chrome APIs is used only for the extension's described archive features and related operations, in accordance with the Chrome Web Store User Data Policy's Limited Use requirements.
Children and updates
WebArchive Pilot is a general utility and is not directed to children. The publisher does not knowingly solicit children's personal information through the feature-request form. This policy may change when the extension's practices change; the Last updated date will be revised.
Contact
Boni Aditya — boni.aditya@gmail.com
Comments
Post a Comment