Plain-English privacy

Your data stays yours

OttoKey runs entirely in your browser, and the source is public. Here is exactly what that means — no legalese maze.

Last updated: August 3, 2026

The short version

What OttoKey can access

OttoKey connects to the inbox providers you choose — Gmail and Outlook/Hotmail — using each one's official sign-in. You can link up to five inboxes at once. For each, OttoKey requests permission to read and tidy mail:

Here is exactly how that access is used, described the way the code actually works:

OttoKey never sends email as you, never permanently deletes anything, and never touches an email it did not read a code from.

Don't take our word for it

Every line of OttoKey is public at github.com/amogus0471/OttoKey, under the MIT licence. You do not have to read all of it to check the claim that matters — manifest.json lists every server the extension is permitted to contact, and there are exactly two: Google's mail API and Microsoft's. Chrome itself enforces that list, so the extension cannot send your mail anywhere else even if it wanted to. There is no analytics library, no error reporter and no third-party code in the extension at all.

What OttoKey does with it

Strictly one thing: find your 2FA code and fill it in. That means:

Where your data lives

On your computer, in your copy of Chrome. OttoKey has no database and no backend.

Data security

We take reasonable measures to keep your information safe:

Data retention & deletion

OttoKey keeps data only as long as it is needed to do its job, and no longer:

Google API compliance

OttoKey's use of information from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

Staying in control

You can cut off OttoKey's access whenever you like from your account's connected-apps settings — for example Google or Microsoft. Uninstalling the extension removes its access and deletes all of its local data too.

Questions?

Email the developer directly at [email protected].