Skip to the content.

SmartFill Privacy Policy

Effective date: 2026-04-17 Last updated: 2026-04-17

SmartFill is designed around a simple promise: your form data stays on your device. This document explains exactly what the extension collects, what it doesn’t, and the choices you control.

This Privacy Policy is a companion to the SmartFill Terms of Service that you accept when you install the extension; the Terms govern use of the software, while this policy describes our data practices.


1. Summary (the short version)


2. Data stored locally on your device

The extension stores the following only on your device, inside your browser’s sandboxed storage:

Kind of data Where it lives How it’s protected
Profile field values (name, email, addresses, cards, etc.) Browser IndexedDB AES-GCM-256 encrypted with a key held by your browser
Extension settings (enabled, backend URL, style) chrome.storage.local Sandboxed per-user
Consent record (which terms you agreed to, when) chrome.storage.local Sandboxed per-user
Classification learn-history (field labels seen on sites, no values) Browser IndexedDB Sandboxed per-user
Anonymous analytics ID (only if you opt in) chrome.storage.local Sandboxed per-user

None of this data is transmitted to us by default. You can delete all of it at any time via Options → Privacy → Delete all my data.


3. Data sent to the classification backend

When SmartFill detects form fields on a page, it sends only field metadata to the backend server that classifies them:

It never sends the values you have typed into those fields.

By default, this backend runs on localhost on your own machine. If you configure a remote backend URL (e.g. your own Railway deployment), that metadata is sent to whatever server you pointed SmartFill at — choose carefully.


4. Anonymous product analytics (optional, opt-in)

SmartFill can optionally share anonymous usage signals with us via PostHog, a privacy-oriented analytics platform, to help us improve classification accuracy and performance. This is off by default.

4.1 Exactly what we collect if you opt in

4.2 Exactly what we never collect

4.3 How we use analytics

We do not use analytics for advertising, profiling, or sale to third parties, and we do not try to re-identify users from these signals.

4.4 How to turn it off

You can turn analytics off at any time:

When you toggle off, SmartFill stops sending events immediately and clears the anonymous ID from your device.

4.5 Data processors

4.6 Retention

Event-level analytics data is retained for up to 180 days, after which we keep only aggregate counts. Your anonymous ID is not linked to any identity, so deletion requests generally don’t apply — but if you want historical events removed, contact us (see § 8) with your anonymous ID (visible in Options → Privacy after opting in).


5. External LLM calls

When the classifier cannot resolve a field via local rules or the local zero-shot model, it may fall back to an external large-language-model provider (Anthropic Claude or OpenAI) to classify that field. In those requests:

LLM provider data handling is governed by their respective terms: Anthropic (privacy) and OpenAI (privacy).


6. Children

SmartFill is not directed to children under 13 (or under 16 in the EU/UK). We do not knowingly collect data from children. If you believe a child has used SmartFill and we hold their anonymous analytics ID, contact us (§ 8) and we will remove the associated events.


7. Your rights

Depending on where you live, you may have rights under the GDPR (EU/EEA/UK), CCPA/CPRA (California), or similar laws — including rights to access, correct, delete, export, or object to processing of your data. Because the only personal-adjacent data we hold is (optionally) your opted-in anonymous ID, exercising these rights is straightforward:


8. Contact

Questions, requests, or concerns about this policy can be sent via the support channels published with the extension on its Chrome Web Store listing.


9. Changes to this policy

We may update this Privacy Policy as SmartFill evolves. Material changes will be surfaced through the extension or by bumping the Terms of Service version, which will prompt you to review and re-accept. The “Last updated” date at the top of this document always reflects the most recent change.