Privacy Policy

DraftShield is a local form-recovery extension designed to reduce accidental loss of text typed into eligible fields on ordinary HTTP and HTTPS webpages.

This policy covers DraftShield version 1.0.0, including its content script, background service worker, popup interface, local recovery database, checkpoint history, retention controls, pause controls, and restore workflow.

This policy does not govern the websites on which DraftShield runs, Google Chrome, the Chrome Web Store, your operating system, browser-profile backup software, or other extensions. Those products may process information independently.

DraftShield runs a packaged content script on ordinary HTTP and HTTPS webpages so that it can detect eligible editable fields and protect text while the user is typing.

When an eligible field changes, DraftShield prepares a bounded local representation of the form and sends it to the extension background logic. The background logic stores the latest recoverable state and a limited set of checkpoints in chrome.storage.local.

If the page is later reloaded, closed, replaced, or otherwise loses the text, the user can open DraftShield and restore a saved draft back into compatible fields on the page.

To identify, save, display, and restore a draft, DraftShield may process information associated with eligible forms and editable fields on a webpage.

A local draft can include:

• The page URL and hostname.
• The page title used to make a recovery item recognizable.
• A locally generated form identifier or form label.
• Field labels, names, IDs, or other bounded identifiers used to match a saved field.
• The type of an eligible field.
• The text currently entered into that eligible field.
• Creation, update, and checkpoint timestamps.
• A bounded history of recent recovery checkpoints.

The extension processes this information only because it is necessary to provide recovery. DraftShield does not need to understand the semantic meaning of your text.

DraftShield is intentionally conservative around common credential and payment fields. Sensitive-field filtering happens before a candidate field is written into the recovery state.

Version 1.0.0 is designed not to save:

• Password fields.
• Hidden inputs.
• File-upload inputs and local file contents.
• Common payment-card number fields.
• CVV, CVC, CSC, security-code, and similar card-verification fields.
• One-time-code, OTP, verification-code, and similar authentication fields.
• Fields marked with password-oriented autocomplete behavior.
• Fields whose names, IDs, labels, or metadata match known credential or financial patterns.

The sensitive-field matcher includes defensive checks for custom naming patterns such as card-related names that do not use a standard HTML input type.

DraftShield is not designed to collect information for the developer. In normal use, the developer does not receive the local recovery database.

DraftShield does not intentionally collect or transmit:

• Your Chrome account credentials.
• Your saved browser passwords.
• Browser cookies.
• Your full browsing history as a developer-side profile.
• Your bookmarks or download history.
• Your precise physical location.
• Your microphone, camera, contacts, or local files.
• Advertising identifiers or cross-site marketing profiles.

The extension necessarily sees the URL and form context of pages on which its content script is operating, because that information is required to associate a local draft with the correct page. That local association is not uploaded to the developer.

DraftShield uses chrome.storage.local to retain the recovery state in the current Chrome profile. The primary state key used by version 1.0.0 is draftShieldStateV1.

A draft can have a current state and a bounded number of recent checkpoints. Checkpoints allow a user to recover an earlier locally saved version rather than being limited to only the most recent state.

DraftShield applies limits to field size, the number of fields retained for a form, the number of checkpoints, the number of retained forms, and the overall amount of local recovery data. These limits reduce uncontrolled storage growth.

When storage limits are reached, older recovery information can be removed in favor of more recent recoverable drafts.

The default local retention period is 14 days. Version 1.0.0 allows the user to select a retention period of 1, 3, 7, 14, or 30 days.

Expired drafts are cleaned up during normal extension operation. Retention controls apply to DraftShield's own local recovery records and do not affect the original website's data.

A shorter retention period reduces how long recoverable text remains available. A longer period provides a larger recovery window but keeps eligible form text in the local browser profile for a longer time.

DraftShield provides a domain-level pause control. When protection is paused for a site, new draft-save operations for that domain are rejected by the extension's background logic.

The paused-domain preference is stored locally so the choice can continue across browser sessions. The user can later resume protection from the popup.

Pausing protection prevents new recovery data for the paused domain. Existing drafts are not necessarily deleted merely because the site is paused; they remain subject to the normal deletion and retention controls.

DraftShield requests host access to http://*/* and https://*/*. This broad page access is required because automatic form protection must be present while the user types, rather than only after the user manually activates the extension on each page.

The content script uses this access to identify eligible editable fields, observe changes, create local recovery metadata, and restore a draft when requested.

DraftShield does not use these host permissions to scrape websites for a developer database, create a remote browsing-history profile, or inject advertising.

Chrome may restrict extensions from running on certain protected browser pages. DraftShield does not attempt to bypass those browser restrictions.

The storage permission is required so DraftShield can persist local recovery data after a tab closes or the browser restarts.

It is also used for local settings such as retention duration, checkpoint preferences, paused domains, and supporting state needed by the recovery workflow.

Version 1.0.0 uses local extension storage rather than a DraftShield cloud account. Form text is not intentionally synchronized to a developer-operated server.

Recovery is user-controlled. Opening a saved draft in the popup allows the user to review available checkpoints and select which state should be restored.

When a restore is requested, DraftShield sends the selected local field data to the compatible webpage so the corresponding eligible fields can be populated.

Websites may change their form structure between the time a draft is saved and restored. If fields have been removed, renamed, reordered, replaced, or moved into unsupported components, some values may not be restored automatically.

Restoring a draft does not automatically submit the form.

DraftShield version 1.0.0 does not include Google Analytics, Firebase Analytics, Mixpanel, Amplitude, Segment, PostHog, or a comparable third-party analytics service.

It does not include advertising networks, retargeting pixels, behavioral advertising systems, fingerprinting logic, or cross-site marketing identifiers.

DraftShield does not send saved form content to a remote AI service for summarization, classification, generation, or profiling.

The reviewed production package does not use fetch, XMLHttpRequest, or WebSocket to upload the local draft database to the developer.

The websites on which DraftShield runs can make their own network requests and can process the information entered into their forms according to their own privacy practices.

Chrome, the operating system, antivirus software, browser-profile backup tools, enterprise management, or other extensions may also process data independently.

DraftShield does not control those third-party systems. Users should review the privacy practices of the websites where they enter information.

The developer does not sell, rent, trade, license, or provide DraftShield's local recovery database to advertisers, data brokers, marketing companies, or analytics providers.

Because the local recovery database is not normally transmitted to the developer, the developer generally cannot provide a remote copy of those drafts.

If the developer receives a valid legal request, only information actually possessed by the developer can be produced. DraftShield's normal local-only recovery records are not a developer-hosted database.

Users can delete individual saved drafts from the DraftShield interface and can use the control for deleting all saved drafts.

Draft data can also be removed through Chrome's extension-data controls, by removing the relevant Chrome profile, or by uninstalling the extension according to Chrome's behavior.

Deletion of local recovery data may be permanent. Version 1.0.0 does not provide a normal cloud backup from which the developer can recover deleted checkpoints.

Browser-profile backups or operating-system backups created outside DraftShield may retain copies independently. Those systems are controlled by their respective providers.

DraftShield reduces privacy exposure by keeping recovery data local, excluding common sensitive-field categories, limiting retained data, and avoiding a developer-operated draft server.

Local Chrome extension storage is not equivalent to an encrypted password vault. A person or process with sufficient access to the same unlocked browser profile or device may be able to access locally stored extension data.

Users should keep Chrome and their operating system updated, protect the device with appropriate account security, and avoid using DraftShield as a place to intentionally store passwords, card details, authentication codes, or other secrets.

DraftShield is a general-purpose form-recovery utility. It does not provide a social network, public user profile, advertising profile, or account system targeted at children or adults.

The extension does not knowingly maintain a developer-side database of personal information about children. Any recoverable text typed by a user remains subject to the same local processing and controls described in this policy.

DraftShield version 1.0.0 does not operate a developer server that receives the local recovery database during normal use.

Because those drafts are not intentionally uploaded to DraftShield infrastructure, the extension does not ordinarily transfer the local recovery database between DraftShield data centers or countries.

Chrome, operating-system backup services, enterprise management, or websites themselves may have independent international data practices outside DraftShield's control.

This policy may be revised to improve clarity, reflect changes to DraftShield, respond to browser-platform requirements, or describe changes in applicable privacy practices.

If a future version introduces cloud backup, accounts, analytics, remote AI, different permissions, new host access, or materially different data handling, the policy and Chrome Web Store disclosures should be updated accordingly.

The effective date and reviewed extension version are shown at the top of this page.

For privacy questions about DraftShield, use the developer contact information displayed on the Chrome Web Store listing from which you obtained the extension.

When contacting the developer, avoid sending passwords, payment-card information, authentication codes, or other sensitive form content unless it is strictly necessary for the request.