Support and account deletion

The Portal and account center are engineering candidates and must not receive uncontrolled production personal data. Invited testers should use the contact path included with their invitation and share only the minimum diagnostic information.

Never send passwords, recovery keys, complete tokens, payment credentials, full health records, or an entire library export. Support should never ask for those secrets.

Public emailNot configured

Not configuredVerified-domain support and privacy contacts are production gates.

Ticket systemNot configured

Not liveNo ticket number, progress, or completion notice is promised.

Response timeNot configured

No commitmentCandidate conversations are not a production SLA.

Tester contactEngineering candidate

Invitation channelAvailable only to people already invited to the candidate.

1. 01
   Confirm the environment

   Look for engineering candidate, demo, or disconnected labels. Do not put production data in a candidate environment.

2. 02
   Protect local content

   Verify local export and backup before signing out, uninstalling, or erasing. Unexported local content may be unrecoverable.

3. 03
   Check sync and AI scope

   Confirm whether sync was enabled, which region was selected, and what content was authorized for the task.

4. 04
   Record minimal diagnostics

   Device model, OS and app versions, time, and a redacted error are useful. Do not attach the full library.

Cloud-copy deletion only removes user copies from the hosted region. It does not close the account, erase offline local data, or cancel a store subscription.

The engineering candidate provides full-account deletion in both the native apps and account center. It verifies the active authenticated session, blocks on shared-space ownership that needs handover, permits cancellation before the irreversible phase, and exposes waiting, processing, action-required, completed, and failed states. Final identity closure runs through the configured identity-management adapter. Real-provider integration, regional completion times, and completion notices still require production acceptance.

Delete cloud copyEngineering candidate

Engineering candidateThe account center has a request path; server status is authoritative.

Delete full accountEngineering candidate

Engineering candidateRequest, blockers, cancellation, resume, and status tracking exist; real identity provider and regional timing require production acceptance.

Erase local contentEngineering candidate

Per-device actionA cloud request does not remotely erase offline devices.

Cancel subscriptionProduction confirmation required

Separate actionManaged by the purchase channel.

1. 01
   Export what you need

   Check in-app content export, account-data export, and full backup separately.

2. 02
   Review devices and shared spaces

   Resolve offline copies, ownership, and handover before deletion.

3. 03
   Manage subscriptions separately

   Confirm renewal and cancellation with the purchase channel.

4. 04
   Start and verify through the product

   The engineering candidate exposes consistent paths in app settings and the account center using the active authenticated session. Production release still requires real-provider and lost-access recovery validation.

5. 05
   Follow the real request state

   Submitted, scheduled, processing, action-needed, and completed are different states.

6. 06
   Clean local copies on each device

   After cloud completion, local content, exports, and personal backups remain under the user's control.

• If a trusted device remains available, revoke the lost device's future regional-service access. Revocation is not remote local-data erasure.
• If login is unavailable, use the tester invitation channel with the account region, verifiable identity information, and event time. Never send a password or key.
• If exposure is suspected, isolate the device, stop sync and AI tasks, and preserve a redacted timeline. No production incident channel is configured.
• Do not infer 24-hour support, remote wipe, insurance, or compensation from this candidate.

• Verified-domain support, privacy, and security contacts with operating hours and languages.
• Validate account-deletion completion times, notices, appeals, and identity verification without login against real providers in every launch region.
• Subscription cancellation, refund guidance, store links, and billing warnings during account deletion.
• Accessibility, regional languages, data-minimizing ticket forms, and sensitive-data removal rules.
• A real service-status source, incident communications, and service commitments grounded in evidence.