Delete the account

Driver App can show Remove account in Profile when the current account and project configuration allow the control. Deletion is destructive and can make the account unavailable. This procedure is pre-action only: it stops at the confirmation and does not authorize or perform deletion.

:::danger Account deletion is not a privacy-erasure receipt

Current service source changes account identifiers and marks the user record deleted. It does not prove erasure of every session, notification token, order, message, media file, log, provider record, backup, or legally retained record. Confirm retention and operational consequences with the account/privacy owner before accepting deletion.

:::

Availability

For a standard Driver account, Remove account appears only when the project configuration explicitly enables Driver account deletion. Other account levels can follow different visibility rules. An administrator can see the control but the Profile button is disabled for that account state.

Visible state	Safe interpretation
Remove account absent	Current level/configuration did not expose the control
Remove account visible	The Profile UI admitted the confirmation entry; API authorization and deletability remain separate
Remove account disabled	Current UI prevents the action; no backend result is implied
Account alert open	Local confirmation is visible; no delete request has been sent

Visibility does not prove that the account is unprotected, has no active work, can be deleted by the running service, or qualifies for complete privacy erasure.

Before you start

• Confirm that the Profile belongs to the intended Driver account.
• Resolve active deliveries, assignments, support cases, payouts, retained records, and access dependencies with the responsible operator.
• Ask the privacy/account owner what data is deleted, deidentified, retained, or handled by third-party providers.
• Do not use deletion as a way to sign out, reset the app, clear storage, or fix a session problem.

Complete the task

1. In Profile, locate Remove account without selecting it if the account or policy is uncertain.
2. When an authorized owner intends to review the final warning, select Remove account once.
3. Read Account alert and Are you sure that you want to remove your account?
4. Stop before accepting the destructive action. Select Cancel or close the alert to return to Profile without sending the delete request.

The destructive confirmation is outside this guide. Do not accept it during documentation review, troubleshooting, testing, or evidence capture.

Verify the result

The only safe result for this pre-action procedure is:

• the confirmation remained unopened; or
• the confirmation opened and was cancelled/closed; and
• Profile remains visible with no delete request intentionally sent.

Observable state	What it does not prove
Confirmation closes	Account deletion, cancellation at the service, or cleanup completion
Profile remains visible	Account still exists in every system or current session is valid
Local data disappears after accidental acceptance	Backend deletion succeeded
App remains signed in after accidental acceptance	Backend deletion failed
Remove account disappears	Deleted account, changed configuration, refreshed role, or privacy erasure

Deletion and cleanup boundaries

If destructive confirmation is accepted, current client source starts the delete request without waiting for it, immediately starts clearing local storage, and only changes root authentication state when an optional root callback is present. The productive Profile does not supply that callback.

These stages can therefore diverge:

1. Confirmation accepted.
2. Delete request sent.
3. Backend parses and authorizes the request.
4. Account identifiers change and the user record is marked deleted.
5. Delete log/plugins/limits settle.
6. Local storage clears, except selected tutorial/language keys.
7. Session state, sockets, notification tokens, Root navigation, and related records reconcile.

No earlier stage proves a later one. Local storage can clear even when the delete request fails, and current UI can remain authenticated after a successful delete response.

States and variations

• A standard Driver needs the exact enablement configuration for control visibility; missing configuration does not enable it.
• The API source permits a non-administrator to delete their own user and an administrator to delete another user, but rejects administrator self-delete and non-administrator deletion of another user.
• Protected accounts and protected administrator policy can block deletion.
• The client does not await or display a deletion receipt before clearing local storage.
• A non-JSON response, network error, parsed error, delayed response, or repeated confirmation can leave local and backend states inconsistent.
• This is a deletion endpoint, not the adjacent profile-update contract. A stale local user/session can remain after either result.

Troubleshooting

Remove account is missing

The Driver deletion configuration can be disabled or absent. Do not try another account level or private route. Ask the operator/privacy owner about the approved deletion process.

Remove account is disabled

The current Profile account state does not admit the control. Do not attempt to bypass it. Use the operator-managed process.

The confirmation was accepted accidentally

Do not repeat the action, clear more data, sign out repeatedly, or recreate the account. Stop using the app and contact the account/privacy owner immediately so they can reconcile backend, session, provider, storage, and retained-data state.

Local data cleared but the account still appears

Local cleanup begins independently of the delete result. Do not treat the empty storage or a later sign-in screen as deletion proof. Ask the account owner to verify the authoritative record.

The app remains signed in after acceptance

The productive Profile lacks the optional root-state callback used by the delete confirmation. Session reconciliation can lag or fail. Do not perform Driver actions; contact the operator.

You need a privacy-data deletion record

Driver App does not provide a complete privacy-erasure receipt. Use the approved privacy/account process for scope, retention, provider coordination, and confirmation.

Related guides: View the Driver profile · Manage account sessions · Edit profile details · Driver App overview