Skip to content
OTP Generator

Privacy Policy

Privacy policy for OTP Generator. We do not collect or store 2FA secret keys. Learn what limited data analytics and advertising partners may process.

On this page

Last updated: 2026-11-18

Summary

Secret keys, codes, QR images and anything else you enter into our tools are processed only in your browser and are never sent to us or stored by us.

Information we do not collect

  • 2FA secret keys, otpauth links, QR code images or generated codes
  • Passwords or backup codes created with our tools
  • Accounts: we have no registration or login

Information that may be collected automatically

Like most websites, our hosting provider and analytics tools may process standard technical data such as IP address, browser type, pages visited, referring site and time of visit. We use this only in aggregate to understand usage and improve the site.

Cookies and advertising

We may use Google AdSense to show ads. Google and its partners use cookies to serve ads based on your prior visits to this and other websites. You can opt out of personalised advertising at Google Ads Settings or aboutads.info. Where required by law (for example in the EEA and UK), we ask for your consent before personalised ads or non-essential cookies are used.

Local storage

We store your light/dark theme preference in your browser’s local storage. Nothing else.

Browser extension

The OTP Generator browser extension follows the same rule: codes are calculated inside your browser, and keys, codes and images are never sent to us or anyone else. The extension contains no analytics, no ads and no remote code. It uses two permissions:

  • activeTab: only when you click “Scan QR code on this page”, the extension takes one picture of the visible part of the current tab to find a QR code in it. The picture is processed inside the extension and discarded; it is never saved or uploaded.
  • storage: you choose how long the extension keeps the secret keys you add (with their account names): until you quit the browser (the default: session storage, which lives in memory), on this computer (the browser’s local extension storage), or on this computer, locked with a password (encrypted with AES-256-GCM using a key made from your password with PBKDF2-SHA-256 and 600,000 rounds; the password itself is never stored). Keys are never synced to your browser account and never uploaded. In a private window keys are not stored at all. Your digits, period and algorithm choice are kept in session storage; the extension also remembers which tab you used last, whether you closed its “keep these codes” tip, and how soon it locks again. None of these contain keys. “Clear all” in the popup, or “Remove all codes” in its settings, deletes the keys at once.

Backup files you choose to save are made inside the extension and saved by your browser to your own device, encrypted with a password if you choose. Files you import are read inside the extension. Neither is sent anywhere.

Links from the extension to otpgenerator.com end in utm_source=extension so our site statistics can tell that a visit came from the extension. They carry nothing about you, your keys or your codes.

Children

This site is not directed at children under 13 and we do not knowingly collect their data.

Your rights

Because we do not hold personal data tied to you, there is usually nothing for us to access or delete. For questions, contact contact@otpgenerator.com.

Changes

We may update this policy; the date above shows the latest version.