Data rights and deletion requests
This page explains how Nexus Evo handles access, correction, and deletion requests for account and website data.
Authenticated account-deletion requests are now created from the signed-in account page. Each request starts a seven-day cancellation window before deletion runs automatically.
Request types
- Access request for personal data tied to the account.
- Correction request for inaccurate account data.
- Erasure request for account, website, and account-linked gameplay data where legally applicable.
- Restriction or objection request where applicable.
What an erasure request should cover
- Auth account records, refresh tokens, reset tokens, and active session artifacts.
- Support/contact records tied to the identified person unless a narrower legal-retention basis applies.
- Account-linked gameplay ownership data, characters, vaults, inventories, and public ranking visibility.
- Internal audit or anomaly rows that still contain directly identifying account fields, unless a documented legal or security hold applies.
What may be retained narrowly
Abuse, fraud, and security records may need limited retention when required for service defense or legal claims. The architecture target is to minimize those records and anonymize them once direct identification is no longer necessary.
Operational process
- Verify identity through strong account authentication or support verification.
- For self-service erasure, create the request in the signed-in account area.
- Start a seven-day cancellation window before execution.
- After the window expires, execute the deletion workflow and stop exposing the user through account or ranking surfaces.
- Keep only narrowly justified fraud or legal-hold records where retention is required.