Hi Auth0 Community,
We’re preparing UNIFAM, a native iOS app using Auth0 with Authorization Code Flow + PKCE. Users need to permanently delete their own account after reauthentication.
We understand that privileged Management API credentials must remain on the backend and must never be exposed to the mobile app. Our backend will also handle deletion of application data.
Before implementing the final integration, we’d appreciate clarification on:
- The Delete a User documentation lists delete:current_user. Is this permission available for native applications using PKCE? If so, how is it obtained and restricted to the authenticated user?
- If a backend Machine-to-Machine application with delete:users is required, can Auth0 restrict that permission to a particular connection or subset of users, or is it necessarily tenant-wide?
- What architecture does Auth0 recommend to minimize the impact of a compromised backend credential while supporting self-service deletion?
- How should deletion handle linked email/SMS identities and existing sessions or refresh tokens?
Our intended flow is: fresh reauthentication → backend verifies the requesting user → durable cleanup of application data → deletion of that user’s Auth0 account. The target identity would come from verified authentication, not a user-supplied account ID.
An official reference or a working example of the recommended approach would be very helpful.
Thank you!