Overview
Save drafts as you type in supported web forms. Preview, restore, or clear them from your browser.
``` Sidecar Guard keeps a local copy of text you type into supported web form fields, so you can get it back when you return after a refresh or a closed tab. It saves after a brief pause in typing, and again when you leave, reload or close the page. Text typed in the last second before a crash can still be missed. When there is a draft for the page, you can preview it and choose Restore. Fields are only filled when you ask. After restoring, each field is read back and any field where the page did not keep the text is named; that copy stays stored so you can take it from the popup. If you type in a field again without restoring, the earlier version is kept beside the new text, up to five earlier versions per field. The restore panel keeps offering what it found when the page loaded, and earlier versions are listed in the popup. Guard is off when you first install it. A welcome page opens and explains what is saved, what never is, where it is kept and for how long, and how to view it, clear it or turn the extension off. Nothing you type is saved until you choose Turn on Sidecar Guard on that page. Until then, the toolbar popup says Guard is off and links back to the welcome page. Open the toolbar popup to read everything that is stored, across sites, and to clear it for the current site address or for all sites. You can turn saving off for a site or switch it off entirely in Options. These preferences apply to the hostname that serves the field. Embedded forms on a different hostname use their own settings. Stored text is eligible for automatic deletion after seven days by default, counted for each copy from when it was saved. Set the window to 1–30 days in Options. Cleanup runs at browser startup and on a daily schedule while Chrome is running. Your text and the addresses of the pages it was typed on stay in this browser. The address, including relevant query parameters, is used to match a draft to its page. Password and hidden inputs are excluded, and field labels and other page markup are used to recognize card payment fields, PINs, one-time codes, government ID fields, and security answers. Bank account numbers, IBANs and sort codes are not recognized yet, so they can be saved. Unrecognized sensitive information typed into an ordinary field can still be saved. Card-number patterns are screened out and known payment-provider frames are skipped. Guard works with supported text inputs, text areas, and simple editable text on ordinary web pages. It skips recognized rich editors such as Google Docs, Notion, and ProseMirror editors, including the ChatGPT and Claude composers. When it recognizes an unsupported editor, the toolbar popup can explain what was skipped. Fields built as custom web components (fields inside a shadow root) are not saved either. When you type in one, the toolbar button shows a warning and the popup says so. The same warning appears for text typed in a sandboxed frame, or in a pop-up window that the page fills itself: it cannot be matched to a page, so it is not saved. Text typed in other frames a page fills itself is saved for that page. Matching uses the page address and the field layout. If the address or fields change, return to the original page or copy the text from the popup. A page's address is read once, when the page loads. In web apps that change the address without reloading, your text can be filed under the address the app was opened at. No restore panel appears at the later address, but the text is listed in the popup. Use one tab per form. Concurrent edits to the same page, or cleanup running at the same moment, can overwrite a stored copy. When you uninstall, Chrome can open a feedback page. The visit sends the extension name and version, days since installation when available, and whether anything was ever stored, when known. You can close the page or choose to send a reason and an optional note. What you typed and the page addresses are excluded from feedback. Permissions Site access lets Guard work on supported HTTP and HTTPS pages, including eligible embedded forms. Storage keeps your text, settings, your choice to turn Guard on, and local status. Alarms schedule cleanup. Scripting starts Guard on eligible tabs that were already open when the extension was installed or updated, or when the browser starts. ```
0 out of 5No ratings
Details
- Version0.3.0
- UpdatedNovember 21, 2026
- Size49.1KiB
- LanguagesEnglish
- DeveloperWebsite
Email
simonwork378@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
Sidecar Guard has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
Sidecar Guard handles the following:
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site