
Written and reviewed by the team operating TempMail Cloud. Product claims are checked against our live service and our editorial standards.
Treat a TOTP setup QR code as a reusable authentication secret. Someone who copies it may be able to generate the same future codes. Closing the setup page or waiting for one displayed code to expire does not invalidate the QR's secret.
Setup image, current code and recovery code are different
| Item | What it represents | After exposure |
|---|---|---|
| Setup QR or Base32 key | The secret used to generate future codes | Replace the affected authenticator enrollment through the provider |
| Current rotating code | A short-lived authentication value | Do not assume it is harmless while it may still be accepted |
| Provider recovery code | A separate recovery credential with provider-defined rules | Replace or revoke it using that provider's process |
The QR commonly carries an otpauth URI with a secret and enrollment parameters. The issuer or account label is descriptive; it does not make an otherwise exposed secret safe. See the Google Authenticator key-URI format.
Enroll without creating unnecessary copies
Open the account's official security settings on a trusted device and check the account identifier. Scan into the intended authenticator, confirm the requested code and save the provider's recovery options securely. Avoid displaying the QR during screen sharing or saving it to an ordinary photo gallery.
Check whether screenshots, screen recordings or clipboard history synchronize elsewhere. A private browser window does not stop operating-system capture or another participant recording a shared screen.
Worked scenario: a QR appears in a support recording
Suppose you record a staging setup flow and notice that the test account's QR is visible. Restrict access to the recording and remove unnecessary copies, but do not treat deletion as proof that nobody copied the secret. Replace that staging account's enrollment, verify the replacement works and retire the old authenticator entry.
For an important account, follow its official recovery instructions before disabling your only factor. Record the incident without including the replacement QR, setup key or recovery codes. This scenario is illustrative and is not a report of an actual breach.
Two devices scanning one QR
Both devices may generate matching codes because they possess the same secret. That can be intentional in a controlled recovery design, but it does not provide separate user identities or independent revocation. Removing one person's device does not change a secret already copied elsewhere. Prefer the service's individual user accounts and supported factor-management controls for team access.
TempMail Cloud calculation and storage
Our 2FA tool calculates codes in the browser, but Save Key has separate behavior: guest keys are stored in browser storage, and signed-in keys sync to the account service. Sharing is another explicit workflow. Clearing the input or closing the page does not remove those saved or shared copies.
Do not submit a real QR or secret to TempMail Cloud support. Use authenticator troubleshooting for setup problems and online-generator safety before experimenting with a convenience tool.