Account closure & retention

Use Privacy requests and specify whether you want an account closed, optional data corrected, public visibility changed or personal records deleted. State the account email and a relevant reference; do not send authentication secrets.

Vexido may verify that you control the account, identify the relevant records and assess any legal, security or dispute-related retention needs. Access should not be given to someone simply because they know a public display name.

Account/profile information, attempts, answers, learning progress, notification preferences, public participant identifiers and associated records can have different dependencies. Active-record removal should address those dependencies rather than just hiding a dashboard.

Some records may need retention for a lawful purpose, such as a transaction dispute or security obligation. Infrastructure backups can have separate expiry and restoration controls. Vexido should explain material limits to a request; it does not promise instantaneous erasure of every historical copy.

Clear local and session storage on a shared device, sign out and remove downloaded reports if you no longer need them. Server-side closure cannot remotely remove copies you or other recipients have already downloaded. You can ask how an outstanding service or public record is affected before requesting closure.