Write like you normally do
Type into a supported text field, textarea, or compatible editable area. DraftGuard saves after a short pause.
DraftGuard helps recover text you were writing when a page reloads, a tab goes missing, or a session expires. It quietly saves supported drafts on your device, so a frustrating restart doesn't have to mean starting over.
No account. No cloud sync. No paid API. Your drafts stay in your Chrome profile.
A draft was found
Your unsent text may still be here. Want to put it back?
How it works
DraftGuard stays out of your way until you need it. You keep writing; it keeps a local copy of supported text fields.
Type into a supported text field, textarea, or compatible editable area. DraftGuard saves after a short pause.
A refresh, closed tab, or expired session can happen. When you return, DraftGuard checks for a matching saved draft.
Choose whether to restore or discard the draft. You stay in control of what goes back into the page.
Small by design
After you enable protection for a tab, supported drafts are saved locally as you type—with no account setup and no separate save button to remember.
Search saved drafts, copy their text, revisit the source page, export a backup, or delete them when you're done.
Pause autosave, exclude websites, choose a retention period, and remove stored drafts from the vault.
Privacy, plainly
DraftGuard is designed to keep draft text inside your browser profile. There is no DraftGuard account, cloud inbox, analytics service, or external API in this build.
DraftGuard does not ask for access to every website. Click the extension and enable protection on the current tab; Chrome grants temporary tab-scoped access so DraftGuard can save supported text locally. To protect a different site, enable that tab separately.
What it isn't
Being clear about the limits is part of building something you can trust.
Drafts are stored in Chrome local extension storage and are not encrypted by DraftGuard. Avoid highly confidential information and shared computers.
Standard text fields and textareas are the most reliable. Some embedded frames, custom editors, or complex web apps may behave differently.
DraftGuard is best-effort recovery. Review restored text before submitting, and use a site's own save or draft feature when available.
Try a tiny demo
Write something, simulate losing the page, then restore the text. This demo runs only on this landing page; it does not connect to the installed extension or store anything on a server.
A saved draft was found in this demo.
Illustrative demo only. Your text stays in this page's temporary JavaScript state.
Questions, answered
No. The current build stores drafts in Chrome local extension storage and does not include a DraftGuard server, analytics, or external API calls. It does store draft text and limited page/field metadata locally.
No. It works best with standard text inputs and textareas. Some custom rich-text editors, embedded frames, and complex single-page applications may not restore perfectly. Rich-text formatting may be lost.
Yes. You can stop protection for the current tab or add domains to the exclusion list. DraftGuard only runs on tabs you explicitly enable.
DraftGuard skips common password, authentication, and payment fields and uses other heuristics to avoid sensitive areas. No detector is perfect, so don't use it for highly confidential information.
You can choose a retention period in the settings. Expired drafts are cleaned up automatically, and you can delete individual drafts or clear them from the vault.
Privacy & data practices
What DraftGuard stores, why it needs website access, and how you can manage or delete saved drafts.
DraftGuard is designed to keep saved drafts in Chrome's local extension storage on your device. It runs only on tabs you explicitly protect, using Chrome's temporary activeTab permission; it does not request blanket access to every HTTP/HTTPS website. The packaged extension does not include an account system, a DraftGuard server, analytics, advertising trackers, or external API calls. Text you type can still be collected separately by the website you are using, according to that website's own behavior and policies.
When you explicitly enable protection for a tab, DraftGuard detects supported text fields on that tab. It does not automatically inspect every website. When you type into a supported field, it may save:
Stored page URLs omit query strings and fragments. They contain the page's origin and path, which can still reveal information about the page you visited. The field signature may contain attributes such as an element's name, ID, placeholder, or accessible label when present.
DraftGuard does not intentionally collect general browsing history. It accesses a page to identify supported text fields and save or restore text associated with those fields.
The extension uses locally stored text and metadata only to provide its core features: autosaving supported drafts, matching a saved draft to a page and field, displaying recovery options, searching and managing saved drafts, exporting a backup when you request it, applying your settings, and removing expired or deleted drafts.
DraftGuard does not use draft content for advertising, profiling, credit decisions, or AI training.
DraftGuard uses Chrome's activeTab permission to get temporary access to the current tab after you explicitly invoke the extension, and the scripting permission to inject its bundled scripts into that tab. It does not request broad host permissions for all HTTP/HTTPS websites. It also uses Chrome's local storage for drafts and preferences, session storage to remember tabs protected during the current browser session, and alarms to clean up expired drafts.
DraftGuard attempts to reattach after a reload on the same origin during the current browser session. Navigating to a different origin can revoke temporary access, in which case you must enable protection for that tab again. You can stop protection for a tab, turn protection off in settings, or exclude domains. Tabs you have not explicitly protected are not monitored.
DraftGuard attempts to avoid common credential, authentication, payment, and other fields identified by their field type, name, label, or related attributes. It also avoids fields in forms that contain password inputs and has default exclusions for selected sign-in or payment-related domains.
Drafts and preferences are stored using chrome.storage.local in the browser's extension storage area. DraftGuard does not encrypt these records itself. Anyone who can access your unlocked browser profile or device may be able to access locally stored extension data. Keep your device and browser profile secure, and avoid using this tool on shared or untrusted computers.
The extension has a local cap of 500 saved drafts to limit storage growth. You can export a JSON backup through the extension's interface; any exported file becomes subject to the storage and security controls of the location where you save it.
You can select an automatic retention period of 1, 7, 14, or 30 days. DraftGuard periodically removes expired drafts and also limits the vault to the 500 most recently updated records. Empty fields may have their associated draft removed during cleanup or subsequent editing.
You can delete individual drafts or clear saved drafts using the extension interface. You can also pause protection or exclude a website to stop new drafts from being saved there. Exported JSON backups are not automatically deleted by DraftGuard; you must remove those files yourself.
Uninstalling the extension or removing your Chrome profile may affect or remove its locally stored data. Export any drafts you need to keep before uninstalling.
The packaged DraftGuard extension does not contain a DraftGuard backend, analytics SDK, advertising service, AI integration, or external API call that uploads saved draft content. DraftGuard does not sell or transfer saved drafts to a third party.
Chrome and your operating system manage the local browser profile and its storage. If you export a draft and choose to share or upload that exported file, you control that action and the recipient's subsequent use of the file.
DraftGuard cannot prevent the website itself from transmitting text you type into its page. A website may autosave, process, or transmit the same text using its own code and services; review that website's privacy policy for details.
The DraftGuard landing page includes a demonstration where sample text can be typed, cleared, restored, or discarded. The demo uses temporary page JavaScript state only; it is separate from the extension and does not send the demo text to the extension or to a DraftGuard server.
The static landing page is not designed to collect form submissions and does not include analytics or advertising scripts. The web hosting provider may process standard technical request information, such as IP address, user agent, and request time, as part of serving the webpage. Hosting-provider practices are governed by that provider's terms and policies.
You can control DraftGuard's handling of drafts by enabling or stopping protection for individual tabs, turning the global setting off, excluding websites, choosing a retention period, deleting individual or all stored drafts, or uninstalling the extension. If you contact the developer by email, the email and any information you choose to include will be processed to respond to your request.
This policy may be updated if DraftGuard's functionality or data practices change. The “Last updated” date at the top will be revised when changes are made. Material data-handling changes should be reflected in this policy and the extension's store disclosures before the affected version is distributed.
DraftGuard is published by Suraj Dev. For privacy questions or requests relating to this policy, contact:
Email: hello@surajdev.com
Website: surajdev.com
This document describes the current DraftGuard build and is provided as a transparency notice, not as legal advice. Review it again whenever the extension's permissions or data practices change.