If someone has used your personal information, act in a planned order: contain the damage, secure your accounts, document what happened, report the incident, and monitor for follow-up activity. This identity theft recovery checklist explains what to do first, what to track over time, and how to revisit your records until each issue is resolved.
Overview
Identity theft can involve a stolen password, an unfamiliar credit account, a tax filing made in your name, medical records used by another person, or personal information exposed in a data breach. The right response depends on what was accessed and where fraudulent activity appeared, but the first principles are consistent: stop further access, preserve evidence, contact the affected provider through a trusted channel, and create a written record.
Do not wait for perfect certainty before taking protective steps. An unfamiliar login, account notification, debt-collection message, or security alert may be a mistake, but it deserves verification. Contact the organization by typing its known website address, using an official app, or calling a number from a genuine statement or card. Avoid links and phone numbers supplied in an unexpected email, text, or call.
If money is actively leaving an account, a device is under someone else’s control, or you face immediate safety concerns, contact the relevant financial provider or emergency service promptly. Recovery procedures differ by country, state, provider, and type of identity theft. Treat this guide as an organizing plan, then confirm current requirements directly with the affected institution and applicable consumer-protection authority.
What to track
1. The incident itself
Start an incident log before deleting messages or resetting devices. Record the date you noticed the problem, how you discovered it, the affected account or service, and every action taken. Save screenshots, suspicious emails, text messages, transaction details, letters, case numbers, and confirmation emails in a secure folder. Keep original message headers or sender details when possible, but do not open suspicious links again just to collect evidence.
Useful incident-log fields include:
- Date and time of discovery
- What information or account may be compromised
- Unauthorized transactions, applications, logins, or profile changes
- Organization contacted and the verified contact method used
- Representative name or department, case number, and promised follow-up
- Documents submitted and the date sent
- Next deadline or check-in date
- Current status: open, disputed, secured, monitored, or closed
2. Accounts and access
List accounts that may be affected, including email, banking, payment apps, shopping accounts, mobile service, workplace systems, cloud storage, and social networks. Change passwords from a known-clean device, beginning with the email account because it may control password resets elsewhere. Use unique passwords and enable multi-factor authentication where available. Review recovery email addresses, phone numbers, trusted devices, active sessions, forwarding rules, app permissions, and recent login history.
If a password was reused, assume every account using that password may need attention. Do not share one-time security codes with a caller or texter. If a phone, laptop, wallet, or authentication device was lost, ask the provider about account lockout, replacement credentials, remote logout, or number-transfer protections.
3. Credit and financial activity
Check bank accounts, card statements, payment apps, loans, and credit reports for unfamiliar activity. A credit freeze or fraud alert may be appropriate, depending on your location and circumstances; confirm the current process with the relevant credit-reporting providers. A freeze can help restrict access to a credit file, while an alert asks businesses to take additional steps before extending credit. These tools do not replace reviewing existing accounts or disputing transactions.
Track each unfamiliar inquiry, account, balance, collection notice, and disputed transaction separately. Ask the provider what documentation it requires, how to secure the account, and when you should expect a decision. Keep copies of everything you submit.
4. Government, tax, medical, and employment records
If a government identifier was exposed or used, follow the instructions of the responsible authority rather than relying on an unsolicited “recovery specialist.” Tax-related identity theft may require a different process from fraudulent credit activity. Medical identity theft can affect bills, insurance records, prescriptions, or clinical information; contact the provider’s privacy or billing department and request correction of records where appropriate. If an employer or workplace account is involved, notify the security or IT team through an internal channel and preserve relevant logs.
| Problem | First actions | Ongoing evidence to track |
|---|---|---|
| Compromised online account | Change the password, end unknown sessions, enable multi-factor authentication, and inspect recovery settings. | Login alerts, device list, password-reset messages, and support case numbers. |
| Fraudulent credit activity | Review credit files, contact the creditor, consider a freeze or alert, and dispute unfamiliar accounts. | Inquiries, account numbers, dispute dates, documents, and response deadlines. |
| Exposed government identifier | Use the responsible authority’s verified reporting and replacement or protection process. | Confirmation numbers, forms, identity checks, and required follow-ups. |
| Medical identity theft | Contact the provider or insurer’s verified privacy or billing channel and identify incorrect records. | Invoices, explanation-of-benefits notices, record-correction requests, and responses. |
| Tax or employment identity theft | Notify the relevant tax authority or employer security team using an official channel. | Notices, filings, payroll records, case references, and submission dates. |
Cadence and checkpoints
Use a short, structured schedule instead of checking everything continuously. During the first day, secure the email account and other high-risk accounts, contact the financial provider if funds or payment details are involved, and preserve evidence. During the first week, review connected accounts, start appropriate credit-monitoring or protective measures, submit disputes, and report the incident through verified official channels.
After that, set a weekly checkpoint until active disputes and account-recovery tasks have clear outcomes. At each checkpoint, review new statements, credit activity, login alerts, mailed notices, and open support cases. Update the incident log immediately rather than relying on memory.
Once the situation is stable, a monthly review can be sufficient for unresolved matters. Keep a quarterly privacy check for password reuse, old accounts, recovery settings, app permissions, and breach notifications. The exact cadence should be more frequent if a provider has given you a deadline or if new activity appears.
Use this simple status system:
- Open: suspicious activity is unresolved or access remains uncertain.
- Submitted: a report, dispute, or correction request has been sent.
- Waiting: the provider has acknowledged the case but requires review.
- Secured: access controls changed and no new unauthorized activity is visible.
- Closed: the provider confirmed its action and you have saved the confirmation.
How to interpret changes
A new alert does not always prove a new theft event. It may be a delayed notification, a legitimate inquiry you forgot about, or a duplicate case. Verify the source and compare it with your log before responding. Conversely, the absence of alerts does not prove that the problem is finished. Some misuse may appear later through a statement, collection notice, account verification request, or official letter.
Escalate your tracking when you see a pattern: repeated password resets, new recovery details, multiple unfamiliar credit inquiries, recurring payment attempts, mail redirected without your permission, or contact from several organizations about accounts you did not open. Ask each provider what action is complete, what remains pending, and whether additional documentation is required.
Be cautious of follow-up scams. After an identity-theft incident, criminals may impersonate banks, investigators, insurers, or support teams and claim they can recover your money or remove your name from a report. Do not pay with gift cards, cryptocurrency, wire transfers, or unusual payment methods to “secure” an account. Verify every contact independently. For related warning signs, see the bank text scam guide and the guide to checking suspicious messages and calls.
Useful contact templates
Account-security request: “I believe this account may have been accessed or changed without my authorization. Please secure the account, end unknown sessions, review recent changes, and tell me what verification and documentation you require. My case reference is [number].”
Fraud dispute: “I am disputing the following activity because I did not authorize or benefit from it: [date, amount, account, and description]. Please confirm receipt, explain the next steps, and provide the response deadline or case number.”
Record-correction request: “The following information appears inaccurate or does not belong to me: [specific item]. Please review the record and tell me how to submit supporting documents and receive the outcome in writing.”
When to revisit
Revisit this plan whenever you receive a breach notice, discover an unfamiliar account, lose a device or wallet, see an unexplained transaction, or receive a collection or government notice that does not match your records. Reopen the incident log whenever a provider sends a new letter, changes a case status, or requests more documents.
Even after closure, schedule a monthly review while any account, credit, tax, medical, or employment issue remains unresolved. Perform a broader quarterly check of passwords, multi-factor authentication, recovery details, financial statements, credit activity, and old accounts. Review this article when the services you use change their recovery requirements or when local reporting and credit-protection procedures are updated.
Your next action is simple: create the incident log, secure the email account first, list every affected service, and assign a date for the next checkpoint. A written record turns a confusing identity-theft event into a series of verifiable tasks—and makes it easier to spot new activity before it becomes a larger problem.