Privacy Policy

What Google user data the extension accesses

Auto Auth Filler requests one Google OAuth scope and no others: https://www.googleapis.com/auth/gmail.readonly.

• Google user data accessed: the sender, subject, date and body text of your ten most recent Gmail messages from the last day.
• Why: to locate a verification code, and to check that it was sent by the site you are signing in to.
• Retention: none. Message content is held in memory only while the patterns run over it, then discarded.

Google user data the extension does not access: attachments, contacts, drafts, labels, mail older than one day, any other Google service, and your Google profile or account details. No scope granting those is requested, so the access is refused by Google rather than merely declined by this extension.

The scope is read-only, so the extension cannot send, delete, modify or label mail. That restriction is enforced by Google rather than by this extension's own code.

Page content on sites you visit. To recognise a one-time-code field, the extension inspects form fields on the page: their names, labels, input types, maximum lengths and the surrounding wording. This happens locally, and the results are never recorded or transmitted. It runs on all sites because a verification field can appear on any site.

What is stored, and where

Everything is stored by your browser, on your device.

The refresh token is kept in local storage deliberately, because it must survive a browser restart. Otherwise you would face a Google consent screen roughly every hour. Signing out deletes both tokens and asks Google to revoke the grant, so the extension also disappears from the permissions list on your Google account.

What is not stored

Email content is never written to disk. Message bodies exist only in memory, for as long as it takes to run the code-matching patterns over them and are discarded immediately afterwards. There is no history, no cache and no log of what was read.

One small exception, stated plainly: when a code is entered into a page, a short fingerprint of it is written to local storage against that site's hostname and removed ten minutes later. This stops a code the site rejects from being entered again, which matters because many sites submit by reloading the page. The code itself is not stored, though the fingerprint is a checksum rather than a security measure. It is never transmitted.

What is transmitted

Requests go to exactly three Google endpoints, and nowhere else:

• accounts.google.com, to show Google's sign-in and consent screen
• oauth2.googleapis.com, to exchange, refresh and revoke tokens
• gmail.googleapis.com, to search and read your messages

There is no server operated by the developer of this extension. No analytics, no telemetry, no crash reporting, no advertising and no third-party service of any kind receives your data.

How Google user data is shared, transferred or disclosed

It is not. Auto Auth Filler does not share, transfer, sell, rent, trade or otherwise disclose Google user data to any party, under any circumstance. There is no recipient to name, because there is nobody to name it to:

• No third parties. No analytics provider, advertising network, data broker, crash reporter, error tracker or content delivery network receives any of it.
• No developer. The author of this extension cannot read your mail. There is no server, no database and no logging endpoint, so there is nowhere for the data to arrive even in principle.
• No AI or machine learning. Google user data is never used to train, fine-tune, evaluate or prompt any model.
• No human review. Nobody reads your messages. The only thing that touches them is a set of regular expressions running locally in your browser.

The only network destination that ever receives anything is Google itself, and only to fetch your own mail on your behalf. Google user data is never transferred out of your browser, to another device, another account or another application.

How Google user data is protected

How long Google user data is retained, and how it is deleted

Google user data is retained for no longer than it takes to read a code out of a message, and is never written to disk. A message body exists only in the browser's memory while the code patterns run over it, a matter of milliseconds, and is discarded immediately afterwards. Nothing is archived, cached, backed up or logged, so there is no copy to delete later.

Everything the extension does keep is listed here in full:

How to delete everything yourself. Any one of these removes all Google user data the extension holds, immediately and without contacting anyone:

• Press Sign out in the extension. Both tokens are deleted and the grant is revoked with Google.
• Uninstall the extension. The browser discards its entire storage area.
• Revoke access at myaccount.google.com/permissions, which invalidates the tokens whether or not the extension is still installed.

There is no deletion request to make. Because no data ever reaches a server, the developer holds nothing to delete on your behalf and could not retrieve your data even if asked. Deletion is entirely in your hands and takes effect at once.

Limited Use disclosure

Your control

• Automatic filling can be switched off in Settings, in which case the code is shown and the extension waits for you. On password fields it always waits.
• Individual sites can be silenced through the blocked-domains list in Settings.
• Signing out revokes access immediately.
• You can revoke access at any time, independently of this extension, at myaccount.google.com/permissions.
• Uninstalling the extension removes all stored settings and tokens.

Children

This extension is not directed at children and collects no personal information from anyone.

Changes and contact

Any change to this policy is published here with the date above updated, and the revision history is public in the project's Git repository. Questions can be raised as an issue there.