# Store recovery codes where account lockout cannot hide them

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Store recovery codes where account lockout cannot hide them

ID: MHC-D-RESEARCH-0149 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/store-recovery-codes-where-account-lockout-cannot-hide-them

A spare key inside the locked room has limited ambition.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- An account provides backup codes for losing the normal sign-in method.

### Avoid when

- Treat codes as secrets; do not put them in a public repository or send them to a helper. Availability and rules vary by account.

### Explanation

A spare key inside the locked room has limited ambition.

### Steps

1. Create the supported recovery codes and store them securely where the same account failure will not make them inaccessible.
2. Keep track of replacement sets and used codes according to the provider's rules.

### Example

A Google account's new backup-code set invalidates the old one. Updating the secure record matters more than keeping two confidently labelled copies.

### Check

Could you retrieve a valid recovery method without first signing into the account it is meant to recover?

### Limits

- Treat codes as secrets; do not put them in a public repository or send them to a helper. Availability and rules vary by account.

### Evidence and sources

- supports: Google backup codes are single-use recovery alternatives, and generating a replacement set invalidates the previous set. — google-backup-codes. Claim basis: technical_definition. Claim limit: Availability differs by account configuration; treat codes as secrets.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Create and save backup codes; use a code; replacement sets"].
Source note: Account eligibility and recovery options vary; Google Advanced Protection is a stated exception.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Create, save and use backup codes)
- google-backup-codes: Sign in with backup codes — https://support.google.com/accounts/answer/1187538?hl=en

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (use_before): https://vedokrok.com/knowledge/verify-sign-in-recovery-before-wiping-the-old-phone
