Platform Account Risk Checklist: Ownership, Verification, Backups, and Appeal Readiness

By Casey Scott McKay · 2025-10-05

Every business that depends on a platform is one automated decision away from a very bad month, and the work that determines the outcome happens before the suspension, not after it. This checklist runs in seven phases: build the asset register, fix credential and payout governance, assemble the verification packet, enroll in the programs that give you a human to talk to, build the continuity layer, prepare the incident response, and run the appeal. Each box states why it exists, the authority behind it where there is one, and the trap that catches people who skip it. The first five phases take about two weeks of attention and no legal fees. The last two are what you will wish you had rehearsed. A worked matter runs throughout, and the companion article and guide supply the doctrine and the drafting.

IP and Technology > Internet | Checklist | Published 5 October 2025 - Updated 12 July 2026 | Casey Scott McKay - marksy.us

Summary. Every business that depends on a platform is one automated decision away from a very bad month, and the work that determines the outcome happens before the suspension, not after it. This checklist runs in seven phases: build the asset register, fix credential and payout governance, assemble the verification packet, enroll in the programs that give you a human to talk to, build the continuity layer, prepare the incident response, and run the appeal. Each box states why it exists, the authority behind it where there is one, and the trap that catches people who skip it. The first five phases take about two weeks of attention and no legal fees. The last two are what you will wish you had rehearsed. A worked matter runs throughout, and the companion article and guide supply the doctrine and the drafting.

Keywords: platform account checklist, account suspension readiness, seller verification, digital asset register, backup and export, appeal preparation, DMCA counter-notice, repeat infringer strikes, brand registry, escalation path, channel concentration, credential governance, plan of action, retraction letter, marketplace compliance, business continuity, social media handle, payout account, supplier invoices, incident response

How to use this checklist

| Phase | What it covers | Who owns it | When | |---|---|---|---| | 1 | The digital asset register | Operations | Week 1 | | 2 | Credentials, payouts, and governance | Operations + finance | Week 1 | | 3 | The verification packet | Operations + legal | Week 2 | | 4 | Programs, registries, and the escalation path | Legal + marketing | Week 2 | | 5 | Continuity: channels, data, and concentration | Leadership | Ongoing | | 6 | Incident readiness | Operations | Before it happens | | 7 | Running the appeal | Legal | Day of |

Phases 1 through 5 are preventive and inexpensive. Phase 6 is a rehearsal. Phase 7 is the emergency, and it goes badly for businesses that skipped the others. Boxes marked [Gate] should be cleared before moving on.

The matter. Fennwright, a kitchenware company, took eighty percent of its revenue through one marketplace. On a Tuesday its seller account was deactivated with a notice citing unspecified "violations of our policies." Eleven days and one retraction letter later it was back. The boxes below show what it found — and what it wished it had done first.

Phase 1. Build the digital asset register

[ ] List every account on every third-party platform, including ones nobody uses.
- Why. You cannot protect an asset you have not identified, and dormant accounts holding the brand name are exactly what impersonators find.
- Trap. Stopping at the obvious three. The campaign account from four years ago still exists, still carries the brand, and is registered to somebody who left.
[ ] Record the registered email for each account.
- Why. It is the single field that determines who can recover the account, and it is wrong more often than any other.
- Trap. A personal address, a former employee's address, or an address at a domain the company no longer owns.
[ ] Record the recovery phone, backup email, and two-factor method.
- Why. Account recovery runs through these, not through the login.
- Trap. A two-factor secret on a personal phone with no corporate backup, which converts a departure into a lockout.
[ ] Record the payout or bank account behind each revenue account.
- Why. A payout account that does not match the entity is the most common verification failure.
- Trap. A founder's personal account left in place from the first year.
[ ] Assign an internal owner by role, not by person.
- Why. Roles survive departures; names do not.
- Trap. "Marketing owns it," which means nobody does.
[ ] Record revenue attributable to each channel.
- Why. Concentration is the underlying risk and it needs a number.
- Trap. Measuring revenue but not measuring what fraction of customer relationships exist only inside the platform.
[ ] Record what data exists only on that platform.
- Why. It determines the backup schedule in Phase 5.
- Trap. Forgetting reviews, message history, and product content, which are often the most expensive things to rebuild.

Fennwright, Phase 1. Fourteen accounts. Four registered to individuals, two of whom had left the company. One advertising account inside a former agency's business manager. Two dormant social handles nobody remembered creating. The register took a day and a half.

Phase 2. Fix credentials, payouts, and governance

[ ] [Gate] Migrate every registration email to a role address on the company domain.
- Why. It is the highest-value fix in the entire checklist and it costs an afternoon.
- Trap. Migrating the login and forgetting the recovery address.
[ ] Move two-factor secrets into a corporate password manager with documented recovery.
- Why. Otherwise the account belongs to whoever holds the phone.
- Trap. A shared secret with no recovery codes stored anywhere.
[ ] Reconcile every payout account to the operating entity.
- Why. Verification requests compare the platform's file against banking records, and a mismatch reads as a red flag.
- Trap. An account in a trade name the bank recognizes and the state does not. See Entity Name and DBA Checklist.
[ ] Adopt a one-page digital asset policy.
- Why. It makes the register somebody's job and establishes that accounts are corporate assets regardless of who created them.
- Trap. A policy with no named owner, which is a memo.
[ ] Add an account review step to the offboarding checklist.
- Why. Departures create most orphaned accounts.
- Trap. Offboarding that collects the laptop and forgets the handles.
[ ] Put an ownership addendum in every agency, reseller, and fulfillment contract.
- Why. An agency that owns the advertising business manager owns the audience data and, functionally, the account.
- Authority. See Brand Transition Toolkit.
- Trap. Discovering the ownership question during a contentious agency transition.
[ ] Confirm no employee holds a brand handle in a personal capacity.
- Why. It is a dispute waiting for a bad separation, and the legal theories for recovering an intangible account are unreliable.
- Authority. 15 U.S.C. § 1125(a) supports an impersonation report where the handle carries the mark. See Whose Brand Is It?.
- Trap. Assuming the employment agreement covers it. Many do not mention accounts at all.

Phase 3. Assemble the verification packet

[ ] Entity documents: formation certificate, current good standing, EIN letter, name-change filings.
- Why. Verification compares the platform's record to the state's, and any divergence stalls the review.
- Trap. A lapsed good standing nobody noticed because the registered agent's notices went to an old address.
[ ] Beneficial ownership documentation for the individuals the platform will name.
- Why. Platforms collect and verify seller identity information, and the request arrives with a short deadline.
- Trap. An ownership structure on file that no longer matches the cap table.
[ ] A bank statement or letter in the exact entity name.
- Why. Exact-match comparison is automated and unforgiving.
- Trap. "Inc." on one document and "Incorporated" on another.
[ ] Proof of address in the entity name at the registered address.
- Why. A utility bill or lease is the standard evidence.
- Trap. A virtual office that cannot produce one.
[ ] [Gate] Wholesale supplier invoices with full supplier contact details.
- Why. Authenticity reviews turn entirely on this, and retail receipts do not satisfy them.
- Trap. Invoices whose quantities do not reconcile with sales volume, which reads as diversion. See Gray Market Enforcement Checklist.
[ ] Confirm in advance that each supplier will respond if contacted.
- Why. Platforms verify with suppliers, and an unresponsive supplier is treated as a failed verification.
- Trap. Learning this during the review, when there is no time to source alternative documentation.
[ ] Trademark registration certificates and complete chain of title.
- Why. Brand programs and IP dispute processes both require them, and a recordation gap surfaces here first.
- Authority. 15 U.S.C. § 1057; 15 U.S.C. § 1060.
- Trap. A registration still recorded in a predecessor entity's name after an asset purchase. See Trademark Due Diligence Checklist.
[ ] Licenses authorizing your use of any third-party brand.
- Why. A distribution agreement is not a trademark license, and platforms ask for the license.
- Trap. An authorization letter that expired two years ago.
[ ] Calendar a quarterly refresh of the whole packet.
- Why. A packet assembled once fails the same way as no packet.
- Trap. Ownership of the calendar entry sitting with someone who leaves.

Phase 4. Programs, registries, and the escalation path

[ ] Enroll in every brand registry your registrations qualify for.
- Why. Better enforcement tools, faster complaint handling, and a human escalation path.
- Authority. 15 U.S.C. § 1051; 15 U.S.C. § 1057.
- Trap. Assuming a pending application qualifies. Most programs require registration.
[ ] [Gate] File trademark applications now for any brand not yet registered.
- Why. The registration that unlocks the tools takes months, and the problem that requires them arrives without notice.
- Authority. See Trademark Clearance Searching; Trademark Clearance Search Checklist.
- Trap. Filing after the counterfeiting starts.
[ ] Obtain verified business status on each social platform that offers it.
- Why. It reduces impersonation exposure and provides a support tier.
- Trap. Verification tied to an individual's identity rather than the entity's.
[ ] Register an authorized-seller list where the platform supports one.
- Why. It makes unauthorized listings easier to remove and reduces the chance your own listings are flagged.
- Trap. A list that is never updated, so terminated resellers stay authorized.
[ ] Write down the escalation path for each account before you need it.
- Why. Finding out who to call on the day of a suspension costs days.
- Trap. Assuming the general support queue is the only channel. It usually is not.
[ ] Record the platform's published appeal requirements for each account.
- Why. Appeals fail on format as often as on substance.
- Trap. Writing a legal brief for a rubric that wants root cause, corrective action, and preventive measures.

Phase 5. Continuity: channels, data, and concentration

[ ] Own a domain and a site you host.
- Why. It is the one channel a marketplace cannot suspend.
- Authority. See Domain Portfolio Checklist; After .com.
- Trap. A domain registered by a developer who has since disappeared.
[ ] Build an email list in a system you control, continuously.
- Why. The customer relationship is the asset; the platform is the introduction.
- Authority. Subject to privacy obligations. See Marketing Privacy Compliance Checklist.
- Trap. Building the list during the emergency, when you have no way to reach anyone.
[ ] Automate a monthly export of orders, customers, product content, images, and reviews.
- Why. Access degrades immediately after suspension.
- Trap. An export that runs to a folder nobody checks and has been failing since March.
[ ] Track revenue concentration by channel and review it quarterly.
- Why. Concentration is the risk that makes everything else existential.
- Trap. Treating a number above eighty percent as a success metric rather than a risk metric.
[ ] [Gate] Put the platform notice address under a named role and monitor it daily.
- Why. The most common cause of preventable termination is a notice nobody read.
- Authority. Platforms must reasonably implement repeat-infringer termination policies. 17 U.S.C. § 512(i).
- Trap. A notice address at a former employee's mailbox that still auto-forwards nowhere.
[ ] Keep a strike ledger: date, complainant, listing, claim type, response, outcome.
- Why. Platform histories are incomplete, and the appeal will turn on the record you kept.
- Trap. Recording the strike and not recording the decision about how to respond.
[ ] Make a decision on every strike within a set number of days.
- Why. Uncontested strikes accumulate silently toward termination.
- Trap. "We'll deal with it if it becomes a problem." By then it is the problem.

Fennwright, Phase 5. Forty percent of sales had been migrated to its own site eighteen months earlier for margin reasons. That decision, made for entirely unrelated reasons, is why the suspension was a bad month rather than the end of the company.

Phase 6. Incident readiness

[ ] Write a one-page incident procedure and store it outside the platform.
- Why. The first two hours determine the quality of the record you will rely on for weeks.
- Trap. A procedure stored in a system the suspension locks you out of.
[ ] Name the incident owner and the backup.
- Why. Suspensions arrive on days when people are traveling.
- Trap. A single point of contact who is also the person on vacation.
[ ] Pre-draft the preservation step: what to screenshot and export, in order.
- Why. Access degrades within hours and the notice page sometimes disappears.
- Trap. Screenshotting the suspension banner and missing the account health history behind it.
[ ] Pre-identify counsel and confirm they can act within a day.
- Why. The highest-value hour is day one, and it is a lawyer's hour.
- Trap. Starting the engagement conversation after the clock has started.
[ ] Pre-draft the customer communication.
- Why. Silence during an outage costs goodwill you will need later.
- Trap. A message that speculates about cause, which becomes a document.
[ ] Rehearse once.
- Why. A tabletop exercise finds the missing export, the stale credential, and the packet gap in an hour.
- Trap. Never testing whether the backup actually restores.

Phase 7. Running the appeal

[ ] Hour one: preserve. Screenshots, exports, notice text, message history, policy text with date accessed.
- Why. The record disappears while you decide what to do.
- Trap. Drafting before preserving.
[ ] Hour two: classify the suspension type.
- Why. IP complaint, performance metric, authenticity, verification, linked account, and content policy each have a different first move.
- Trap. A compound suspension where an IP complaint triggered an authenticity review, and the appeal addresses only one.
[ ] Day one: identify the complainant in any IP-driven suspension.
- Why. Retraction is faster than any platform process.
- Authority. 17 U.S.C. § 512(c)(3) requires identifying information in a compliant notice.
- Trap. Going to the appeal form before knowing what the complaint says.
[ ] Day one: assess the merits — descriptive use, nominative use, first sale, or actual infringement.
- Why. Three of those four are defenses; the fourth is a fix.
- Authority. 15 U.S.C. § 1115(b)(4); see Raising a Trademark Fair Use Defense.
- Trap. Fighting a complaint you should cure.
[ ] Day one to three: send a retraction letter where the claim is weak.
- Why. A retraction resolves the suspension at the source.
- Trap. A letter to the platform instead of to the complainant.
[ ] [Gate] Day two: evaluate the DMCA counter-notice with the client, in writing.
- Why. It discloses your address and consents to federal jurisdiction, and it applies to copyright only.
- Authority. 17 U.S.C. § 512(g); 17 U.S.C. § 512(f).
- Trap. Filing one against a trademark complaint, where it has no statutory effect at all. See DMCA Takedown Notice Checklist.
[ ] Days two to five: draft the appeal as root cause, corrective action, preventive measures.
- Why. That is the rubric the reviewer applies.
- Trap. Length. Two pages maximum, documents attached and labeled.
[ ] Lead with the retraction if you have one.
- Why. It is the fact that resolves the file.
- Trap. Burying it in paragraph four.
[ ] Submit through one channel, then escalate in sequence.
- Why. Duplicate submissions reset queues and create inconsistent records.
- Trap. Filing through four channels with four slightly different stories.
[ ] Week two: decide about litigation against the complainant, not the platform.
- Why. The platform is shielded for moderation decisions; the bad-faith complainant is not.
- Authority. 47 U.S.C. § 230(c)(2); 17 U.S.C. § 512(f).
- Trap. Spending the litigation budget on a mandatory injunction to compel reinstatement.
[ ] Whatever the outcome: fix the architecture within thirty days.
- Why. The window during which a client will fund continuity work closes as soon as the account returns.
- Trap. Reinstatement treated as resolution.

Fennwright, Phase 7. A trademark complaint over descriptive use of "professional," which triggered an authenticity review. Counsel identified the complainant, attached six of its own listings using the word the same way, cited § 1115(b)(4), and obtained a retraction in three days. The appeal led with the retraction and addressed sourcing separately with wholesale invoices. Reinstated on day eleven; held payouts released on day nineteen.

Phase 8. Account types that follow different rules

Four categories of account behave differently enough that the general boxes are not sufficient. Work the ones that apply.

Payment processors and merchant accounts

[ ] Stand up a second processor before you need one.
- Why. A freeze stops settlement while orders continue, and onboarding a new processor takes weeks.
- Trap. A single processor treated as infrastructure rather than as a counterparty with termination rights.
[ ] Read the reserve provision and model what a rolling reserve does to cash flow.
- Why. Reserves are usually contemplated expressly, which weakens the good-faith argument and makes the cash impact the real issue.
- Trap. Learning what a one-hundred-eighty-day reserve means after it is imposed.
[ ] Monitor chargeback and dispute rates against the processor's published thresholds.
- Why. These are the metrics that trigger reviews, and they are visible in advance.
- Trap. A single product with a high dispute rate dragging the whole account across a threshold.
[ ] Identify the acquiring bank and its complaint channel.
- Why. Payment relationships sit inside regulated banking relationships with their own escalation paths.
- Trap. Escalating only within the processor's support queue.

App stores and software distribution

[ ] Clear and register the app name and icon before launch.
- Why. A trademark complaint against an app name can remove the app, and clearance is far cheaper than removal.
- Authority. 15 U.S.C. § 1051; 15 U.S.C. § 1114. See Running a Full Trademark Clearance Search.
- Trap. A name cleared for the company and never cleared for the app.
[ ] Reconcile store metadata claims with what the product actually does.
- Why. Metadata claims are advertising claims and are reviewed as such.
- Authority. 15 U.S.C. § 45; 15 U.S.C. § 1125(a)(1)(B).
- Trap. Marketing copy written for a website pasted into a store listing with different rules.
[ ] Keep privacy disclosures synchronized with actual data practices and third-party SDKs.
- Why. Disclosure mismatches are a leading removal cause, and SDKs change behavior between versions.
- Authority. See Building a Privacy Compliance Program for a Consumer Brand.
- Trap. A disclosure accurate at launch and stale three releases later.
[ ] Keep a build and release archive outside the store.
- Why. Removal can take the distribution artifact with it.
- Trap. Relying on the store as the archive.

Advertising accounts

[ ] Confirm the business manager or ad account is owned by the brand, not the agency.
- Why. Audience data, conversion history, and pixel history are the assets, and they do not transfer cleanly.
- Trap. An agency transition that ends with the brand rebuilding two years of learning.
[ ] Review ad copy and keyword practice against the platform's trademark policy.
- Why. Advertising policies are stricter than organic listing policies, and a competitor complaint can disable an entire account rather than one ad.
- Authority. See Keyword Advertising Compliance and Enforcement Checklist; Buying a Competitor's Name.
- Trap. A bid strategy nobody reviewed for trademark exposure.
[ ] Substantiate every performance and comparative claim before it runs.
- Why. False advertising exposure travels with the ad, and platform policy enforcement is faster than any court.
- Authority. 15 U.S.C. § 1125(a)(1)(B); see Advertising and Marketing Law Toolkit.
- Trap. A claim approved for a package and reused in an ad with different context.
[ ] Export audiences and conversion data on the platform's permitted terms.
- Why. It is the data most likely to be unrecoverable.
- Trap. Assuming an export exists. For some data types it does not, which is itself worth knowing in advance.

Domains, DNS, and registrar accounts

[ ] Confirm the registrar account is in the entity's name with role-based contacts.
- Why. Losing the registrar account is worse than losing a marketplace account, because it takes the email with it.
- Authority. See Domain Portfolio Checklist.
- Trap. Registrar contacts pointing at an email address hosted on the same domain, which is unrecoverable if the domain lapses.
[ ] Enable registrar lock and auto-renew, and verify both annually.
- Why. Expiration and unauthorized transfer are the two failure modes, and both are preventable.
- Trap. Auto-renew tied to an expired card.
[ ] Record marks in the Trademark Clearinghouse where the portfolio justifies it.
- Why. It enables sunrise registration and notice services across new gTLDs.
- Authority. See After .com; Domain Name and Digital Identity Toolkit.
- Trap. Treating the Clearinghouse as enforcement. It is notice, not remedy.

Phase 9. Impersonation, hijacking, and the accounts that are not yours

The mirror image of losing your account is someone else running one in your name. The response channels are different from the appeal channels, and they are faster if you have the registration.

[ ] Monitor for impersonation accounts, lookalike handles, and copycat storefronts on a schedule.
- Why. Impersonation harms customers first and reputation second, and platforms act quickly when the report is well-made.
- Authority. 15 U.S.C. § 1125(a); 15 U.S.C. § 1114.
- Trap. Monitoring exact matches only. Character substitutions, added words, and translated variants are the common forms.
[ ] Use the trademark reporting channel, not the general abuse channel, where the handle carries your mark.
- Why. Trademark reports route to reviewers with authority to act and require the registration number you already have.
- Trap. A general abuse report that sits in a queue for weeks.
[ ] Preserve evidence before reporting.
- Why. The account disappears when the report succeeds, and you may need the record for a damages claim or a later pattern showing.
- Trap. A successful takedown with no captured evidence of what was taken down.
[ ] Report account takeovers through the compromised-account channel, which is separate and faster.
- Why. Hijacking is treated as a security incident rather than a policy dispute.
- Trap. Filing a general appeal for a security event.
[ ] After any takeover, rotate every credential in the register, not only the compromised one.
- Why. Credential reuse is how one compromise becomes several.
- Trap. Rotating the password and leaving the recovery email that was the actual entry point.
[ ] Where impersonation involves counterfeit goods, run the anticounterfeiting playbook alongside the platform report.
- Why. Removal without disruption of the seller produces a new listing the next day.
- Authority. 15 U.S.C. § 1116(d); 15 U.S.C. § 1117(b). See Trademark Counterfeiting; Anticounterfeiting and Border Enforcement Toolkit.
- Trap. Treating repeat counterfeiters as a takedown problem rather than a litigation problem.
[ ] Track repeat offenders across platforms and keep a pattern file.
- Why. A documented pattern converts scattered takedowns into a viable case.
- Authority. See Schedule A Defendants.
- Trap. Closing each incident without recording the seller identifiers, payment endpoints, and shipping origins that link them.
[ ] Calibrate your own enforcement so it does not generate exposure.
- Why. Careless notices against legitimate resellers create misrepresentation and interference risk, and platforms downweight complainants with poor accuracy records.
- Authority. 17 U.S.C. § 512(f).
- Trap. An automated enforcement vendor firing notices with no human review of the close calls.

Phase 10. The quarterly review

Fifteen minutes a quarter is the entire maintenance burden. Calendar it, assign it, and run these boxes.

[ ] Has any account been added, closed, or changed hands since last quarter?
- Trap. A new marketplace opened by a regional team that never reached the register.
[ ] Has anyone with credentials left the company?
- Trap. A contractor whose access nobody revoked because they were never in the HR system.
[ ] Are the entity records still current — good standing, address, officers, bank?
- Trap. A renewal filing missed because the registered agent's notice went to an old address.
[ ] Did the scheduled exports actually run, and does a restore work?
- Trap. An export that has been silently failing for two quarters.
[ ] Has channel concentration moved, and in which direction?
- Trap. Watching total revenue grow while the share on one platform grows faster.
[ ] Any new strikes, notices, or policy warnings, and was each one decided?
- Authority. 17 U.S.C. § 512(i).
- Trap. A strike logged and never resolved.
[ ] Are all registrations, renewals, and recordations current?
- Authority. 15 U.S.C. § 1058; 15 U.S.C. § 1059.
- Trap. A registration that lapsed for a missed Section 8 filing, taking the brand registry enrollment with it.
[ ] Is the verification packet complete and dated within the quarter?
- Trap. A packet last refreshed before the bank change.

Fennwright, one year later. The quarterly review takes about twenty minutes and has caught three things: a lapsed good standing, an export that stopped running when a credential rotated, and a regional account opened without notice. None of the three would have been visible any other way, and each would have mattered on the day of the next suspension.

Key Authorities at a Glance

| Authority | Proposition | Phase | |---|---|---| | 47 U.S.C. § 230 | Immunity for good-faith moderation | 7 | | 17 U.S.C. § 512(c) | Notice and takedown | 7 | | 17 U.S.C. § 512(g) | Counter-notice and restoration | 7 | | 17 U.S.C. § 512(f) | Misrepresentation liability | 7 | | 17 U.S.C. § 512(i) | Repeat infringer policy | 5 | | 15 U.S.C. § 1051 | Application for registration | 4 | | 15 U.S.C. § 1057 | Certificate as prima facie evidence | 3, 4 | | 15 U.S.C. § 1060 | Assignment and recordation | 3 | | 15 U.S.C. § 1114 | Infringement of registered marks | 7 | | 15 U.S.C. § 1115(b)(4) | Descriptive fair use | 7 | | 15 U.S.C. § 1125(a) | False designation; impersonation | 2, 7 | | 15 U.S.C. § 1116(d) | Ex parte seizure | 7 | | 15 U.S.C. § 45 | Unfair or deceptive practices | 7 | | 9 U.S.C. § 2 | Arbitration agreements enforceable | 7 |

The five things people get wrong

One: they treat the account as property. It is a revocable license under a contract the other side wrote. Everything sensible follows from accepting that — back it up, distribute the risk, own a channel the platform cannot touch.

Two: nobody reads the notice address. The single most common cause of a preventable termination is a series of notices delivered to a mailbox that belonged to someone who left in 2023. Put the address under a role, monitor it daily, and log every strike.

Three: they file the counter-notice reflexively. 17 U.S.C. § 512(g) hands the complainant your name, address, and telephone number and consents to federal jurisdiction. Sometimes that trade is right. It should never be automatic, and it never applies to a trademark complaint.

Four: they appeal before they diagnose. An appeal that addresses the wrong problem burns a submission and sets the file back a week. Spend the first two hours classifying and the first day identifying the complainant.

Five: they fix nothing after reinstatement. The account comes back, the crisis passes, and the concentration, the orphaned credentials, and the missing exports all remain. Thirty days is the window. Use it. See Managing Platform Account Risk.