AutoFill Anywhere is a browser extension that helps you detect and automate filling form fields from a persistent side panel. This Privacy Policy explains what data the extension collects, how that data is used, where it is stored, and how you can control or remove it. We do not collect or send your saved form data to any remote servers by default.

​

Summary

• The extension reads page form fields only when you explicitly ask it to (for example, when you click “Scan page”, “Autofill”, or use the context-menu “Find in AutoFill Anywhere”).

• Saved form configurations and UI settings are stored locally in your browser using Chrome extension storage.

• No data is transmitted off your device by default. Exported data is only created and downloaded when you use the export feature.

​

What data the extension may store and why

• Saved site configurations (sites):

  • What: When you click “Save” the extension stores a site-specific profile containing selector strings, field labels/types, and the values you chose for each included field.

  • Why: So you can refill those fields later and reuse the configuration per-site.

  • Where: chrome.storage.sync (by default) so users can keep settings across Chrome instances if they use Chrome Sync.

• UI preferences:

  • What: Theme choice (theme), freeze-origin setting (freezeOrigin) and similar UI preferences.

  • Why: To restore your preferred appearance and behavior.

  • Where: chrome.storage.sync.

• Pending context-find (temporary):

  • What: A short-lived pendingFind object (selector, origin, timestamp) used as a fallback when the user triggers a context-menu “Find” and the side panel is not yet ready.

  • Why: To ensure the side panel can focus the correct field immediately after opening.

  • Where: chrome.storage.local (temporary; removed after use when possible).

• Runtime reads (not stored unless you save):

  • What: The extension may read the active tab’s URL (to determine origin) and page DOM elements (inputs, selects, checkboxes) when you initiate a scan or fill.

  • Why: To detect form fields, show options in the side panel, highlight elements on the page, and perform fills.

  • Note: DOM reads are performed by a content script injected into the page only upon user action.​

​

Do we transmit data off your device?

• No. AutoFill Anywhere does not send saved form configurations or page field data to any remote servers by default.

• The only ways data could leave your device are:

  • You use the extension’s Export feature to produce a JSON file and you choose to share or upload that file yourself.

  • In the future, if a cloud backup or opt-in analytics feature is added, that behavior will be clearly described and require explicit opt-in consent.

​

Permissions and why they are needed

• activeTab

  • Purpose: Allows a one-shot interaction with the currently-focused tab after a user action (scan, fill, context-menu).

  • Scope: Only the active tab at the time of user interaction.

• scripting / chrome.scripting.executeScript

  • Purpose: Used to inject the local content script (content.js) as a fallback when it is not already present, so the extension can scan or control the page DOM on the user’s request.

  • Scope: Only runs when the user initiates an action (Scan / Fill).

• sidePanel

  • Purpose: Provides the UI as a persistent side panel so users can manage scans and fills without leaving the page.

• host_permissions (site access)

  • Purpose: Required so the extension’s content script can access page DOM elements on the sites where you want to scan and fill forms.

  • Scope & minimization: You can limit host permissions to specific sites where you want the extension to operate. The extension explicitly skips internal/blocked schemes (e.g., chrome://).

• storage

  • Purpose: Store saved site profiles, theme, and other user preferences locally in the browser.

 

How the extension operates (privacy-respecting behavior)

• The extension only reads page content when triggered by a direct user action (scan/fill/context-menu).

• It does not run background scraping of pages or silently extract data.

• The extension will not attempt to inject scripts into restricted pages (for example, chrome:// pages) and will show a clear status message when injection is not possible.

• The content script that reads or writes page data is shipped with the extension and is injected locally — no remote scripts are loaded or executed.

 

Sharing and third parties

• The extension does not share your saved site profiles or page data with third parties.

• If you export a profile and choose to share it (for example, upload it to a cloud drive or send it to someone), that data is then under your control and no longer restricted by the extension.

• If you choose to enable any optional future features that integrate with cloud services (e.g., cloud backup or sync outside of Chrome Sync), those will be opt-in and explicitly documented.

 

Security & retention

• Data stored in chrome.storage.sync may be synced via your Google account if you use Chrome Sync. That is managed by Chrome/Google and is subject to Google’s privacy terms.

• Stored data persists until you delete it via the extension UI (Delete per-site), via the export/import controls, or by uninstalling the extension (uninstall clears extension storage).

• For temporary operations, pendingFind is removed after it is processed where possible.

 

How to inspect, export, or remove data

• Inspect saved sites: Open the extension side panel → All Sites. You can delete individual saved site profiles there.

• Export data: Use the Export button in the panel to create a JSON file containing your saved data. Only export if you want a local copy.

• Clear all stored data:

  • Quick option: Uninstall the extension from chrome://extensions — this removes extension storage.

  • Programmatic option: In DevTools for the extension page or from a browser console run (developer-only): chrome.storage.sync.clear() and/or chrome.storage.local.clear().

  • If you’d like, the extension can include a “Clear all saved data” button in the UI — tell me and I’ll add it.

• Revoke site access: To change or revoke host permissions, visit chrome://extensions → Details for AutoFill Anywhere → Site access (choose “On click” or “Remove” as desired).

 

Children’s privacy

• The extension is not directed to children under 13 and does not intentionally collect information from children. If you believe a child under 13 has provided personal data, please contact us and we will remove it on request.

 

Changes to this privacy policy

• If the extension’s data practices change (for example, an opt-in cloud backup or telemetry feature is added), we will update this Privacy Policy and inform users in the extension UI and the store listing. Any feature that transmits data off-device will be opt-in.

 

Contact

• If you have questions about this policy or want data deleted and need help, please contact us via the website link in the extension (or the extension’s support contact on the store listing).

 

Legal note

• This Privacy Policy is intended to be clear and user-friendly. It does not constitute legal advice. If you need legally reviewed language for compliance or for a particular jurisdiction, consider having this reviewed by a lawyer.