Privacy Policy

What the extension handles

• Email addresses: addresses in Gmail headers or displayed near an OTP form.
• Authentication data: a short-lived Google OAuth token, an encrypted Opera renewal session, and extracted verification codes.
• Email content: a bounded set of recent Gmail headers, subjects, snippets, and message text needed to find codes.
• Current website: the origin of an open tab where OTP matching is active. The extension does not create a persistent browsing-history list.
• Verification actions: only a recognized Send code or Resend code action and its timestamp, used to avoid matching an old code to a new request.
• OTP field details: nearby labels and input attributes such as expected length, accepted characters, and a displayed recipient address.
• Extension state: fill preference, Gmail scan cursor, code expiry, applied-code records, and temporary per-tab state.

AutoFill Code does not intentionally collect passwords, payment or financial information, health information, precise location, general click activity, keystrokes, or unrelated page content.

How the data is used

1. Connect to Gmail with read-only access.
2. Check a limited recent-email window for active verification codes.
3. Match a code to the current website, OTP field, recipient, and verification attempt.
4. Offer or fill the code according to the user's selected setting.
5. Prevent expired or previously used codes from being filled automatically.

The data is not used for advertising, analytics, profiling, lending, or any unrelated purpose.

Storage and retention

Product data is stored in extension-local or session storage on the user's device. AutoFill Code also operates a stateless authentication service for Opera token renewal. That service has no user database.

• OAuth tokens are short-lived and removed when Gmail is disconnected.
• Opera stores an opaque, encrypted renewal session locally. The authentication service decrypts its Google refresh credential only in memory while renewing or revoking access, then returns a newly encrypted session. Request-body logging is disabled.
• Cached codes and applied-code records are removed when the code expires.
• The Gmail scan cursor remains locally so the extension can continue from its last completed check instead of rereading the inbox.
• Website, OTP-field, and verification-attempt state is temporary and ends with the browser session or tab cleanup.

Disconnecting Gmail asks Google to revoke the Opera renewal credential, then clears the local token, encrypted session, active-code cache, and Gmail scan state. Removing the extension or clearing its data removes the remaining values.

Sharing and transmission

AutoFill Code communicates with Google OAuth and the Gmail API over HTTPS. Gmail messages are read directly by the extension from Google and never pass through the authentication service.

For Opera, the temporary Google authorization code and OAuth credentials needed for renewal pass through a stateless Cloudflare Worker operated for AutoFill Code. Cloudflare processes those encrypted HTTPS requests as the hosting provider. The service does not receive Gmail messages, website content, extracted verification codes, or browsing activity; it has no user database, advertising, or analytics. Chrome uses its browser-managed OAuth cache, and Firefox does not use this renewal service.

When filling is enabled, the matched code is written into the detected website field. The extension does not submit the form.

AutoFill Code does not download or execute remote code. All executable code and interface assets are included in the published extension package.

Your choices

You can choose automatic filling, confirmation before filling, or disabled filling. You can disconnect Gmail at any time, remove the extension, or clear its stored data through Chrome.

Limited Use

AutoFill Code's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

AutoFill Code also complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. The extension does not allow humans to read user data.

Policy changes

Material changes will be added to this page and the Chrome Web Store disclosures before the related extension update is published. The effective date will also be updated.

Contact

For privacy questions, open an issue in the public privacy repository. Do not include emails, tokens, verification codes, or other personal information in a public issue.