Deleting users

This capability is under development. Supacharger does not yet expose a managed account-deletion action because deletion policy is a product and compliance decision, not a safe universal default.

The planned configuration will let an application choose between:

• deactivating an account while retaining records required for audit, billing or legal obligations;
• permanently deleting the Auth user and application data after an explicit confirmation and recovery window.

A future Supacharger skill will help developers declare which product tables and Storage paths belong to a user. It will use that ownership map to plan foreign-key cascades, deliberate archival or anonymisation, and file deletion without guessing relationships.

Until that contract is available, design deletion as an application-specific, reviewed server workflow. Revoke sessions first, authorise every step, avoid a browser-callable service-role boundary, inventory external processors, and test both partial failure and retry behaviour.