Writing a Custody and Recovery Plan Before You Lose Access

Most people only think about recovery after the problem has already happened: the phone is gone, the SIM has been replaced, the email account is locked, or the authenticator app no longer opens. At that point every decision is rushed and every missing detail costs time. This guide is about doing the calm work in advance, while everything still works, so that a future loss is a procedure you already wrote down rather than a crisis you improvise. The plan you build here is not a promise that any recovery request will be approved, and it is not a substitute for reading the official help centre pages that describe current procedures. It is a personal document: an inventory of what you hold, a map of how you get in, a record of what you have already verified, and a short list of drills you can run so the steps are familiar. Keep it offline, keep it current, and treat it as something you revise whenever you change a phone number, an email address, or a security key. The goal is simple: if you lose one access path, you should be able to open your own notes and know exactly what to check next, in what order, and what information you will be asked to provide.

Start with a plain inventory of what you actually hold

Before writing any recovery steps, list what exists. Include the OKX account itself, the email address tied to it, the phone number used for codes, any authenticator app entries, any hardware security key, and any device that stays signed in. For each item, write where it lives, who else could physically reach it, and what would happen if it disappeared today. This sounds obvious, but most people discover during an incident that they cannot remember which email address they used, or that the phone number on the account belongs to an old SIM sitting in a drawer. The inventory turns those guesses into facts you can check now.

Add a second column for dependencies. Your OKX login may depend on an email account, which itself depends on a recovery phone number, which depends on a carrier account. Draw those links honestly, because a single weak link at the bottom can block everything above it. If your email recovery goes through a number you no longer control, that is the first thing to fix, not the last. Record the date you last confirmed each dependency, so a stale entry is visible rather than assumed.

Map every access path and mark the single points of failure

For each way you can reach the account, write the exact steps in order: which device, which app, which factor, which confirmation screen. Include the boring ones, such as a browser where you are still signed in, because those are often the fastest route when a phone is lost. Then mark the paths that share a single dependency. If two paths both require the same email inbox, you do not really have two paths; you have one path with two doors. The point of this map is to see, on paper, where a single loss would cut you off completely.

Note which factors are device-bound and which are not. An authenticator entry stored only on one phone is a single point of failure; the same entry also present on a second device or exported according to the official instructions is more resilient. Do not invent your own backup method. Follow what the help centre describes for the specific factor you use, and write down which official page you followed and when. If a factor cannot be backed up, say so plainly in your notes so you do not rely on it as your only route.

Write the recovery procedure as numbered steps, not intentions

A plan that says 'contact support' is not a plan. Write the actual sequence: which page you open first, what you check before contacting anyone, what information you will need to have ready, and what you will do while waiting. Include the order you will try things, because trying factors in a random order can lock you out further or waste a limited number of attempts. If a step depends on something you must verify on the official site, write 'check the current procedure on the verification page' rather than a fixed description of a screen, since interfaces change.

Add stop conditions. Decide in advance what you will not do: you will not send funds to an address you cannot independently verify, you will not share codes or seed phrases with anyone who contacts you first, and you will not act on instructions from a chat message that you did not initiate. Write these as explicit lines, because under stress the temptation to shortcut is strong. Also write what you will record after each attempt: the date, the channel you used, the reference number if one is given, and what you were told. That log becomes the backbone of any follow-up.

Run a drill and keep the plan alive

Once the plan is written, test the harmless parts. Confirm you can still sign in from a second device, confirm your email recovery still works, confirm the phone number on the account is one you control today. Do not test anything that could trigger a lockout or a security review; if you are unsure whether a step is safe to rehearse, check the help centre first or skip it and mark it as unverified. A drill that breaks your access is worse than no drill, so keep the tests conservative and reversible.

Schedule a review. Once a quarter is usually enough, or after any change to a phone, email, device, or security key. During the review, update the inventory, re-check the dependencies, and delete anything you no longer use so the plan does not become a list of dead ends. Store the plan where you can reach it without the very device you might lose, and do not keep it in the same place as your credentials. The plan is a map, not a key; keeping it separate is what makes it useful when one path fails.

Risk boundary: OKX Referral Terms Guide

Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat. A referral link only records attribution; it does not guarantee access, pricing, rewards, approval or investment results. Availability can differ by residence, legal entity and product, so no regional access is assumed from language or branding alone.

Scenario checkpoint

• List every access path to the account and mark which ones share the same email inbox or phone number.
• Write the recovery steps in numbered order, including what to check before contacting support.
• Record the date you last verified each dependency, such as email recovery and the phone number on file.
• Decide and write your stop conditions, including never sharing codes or seed phrases with anyone who contacts you first.
• Keep a log template ready for date, channel, reference number, and what you were told after each attempt.
• Store the plan separately from your credentials and review it after any change to a phone, email, device, or security key.