Manage profile, security and privacy

Profile details and avatar

Profile edit supports name, username, email, phone and short biography. Username and phone are checked for uniqueness. Email or phone changes update related identity and recovery information. Avatar upload accepts supported JPEG, PNG or GIF images within the form size limit; you can replace or remove it. Use contact details you control.

1. Edit the profile fields that need correction.
2. Resolve uniqueness or validation errors shown.
3. Upload or remove an avatar and confirm the profile.

Password and sign-in security

Changing an existing local password requires the current password and a confirmed new password meeting the displayed policy. Federated users without a local password must satisfy reauthentication conditions to create one. Profile security exposes available multi-factor and identity controls. Complete genuine authentication prompts; use supported recovery rather than bypassing a factor.

1. Open Password or Security and read its requirements.
2. Complete current-password or reauthentication checks shown.
3. Set a compliant password and verify the sign-in method.

Sessions and connected access

Sessions can list web sessions, connected application tokens and trusted devices, with controls to revoke an item or other sessions. Revocation can sign out a device or require an application to authenticate again. Normal and SSO login flows share protected profile functions; SSO sessions use SSO-specific session routes. Recent-authentication and factor checks remain required for protected actions.

1. Identify the session, application or device to revoke.
2. Choose individual revoke or revoke-others intentionally.
3. Complete any genuine recent-authentication or factor prompt.

Export personal data

The profile privacy control builds and streams a ZIP archive of account data. The export is a sensitive copy: store it securely, limit access and remove unnecessary copies. Export is a download, not account deletion or a profile change. If interrupted, request it again from the protected profile area; do not attach the archive to a support request.

1. Choose data export while signed in to your account.
2. Save the archive in a protected location.
3. Check it opens; retry from the profile if interrupted.

Request or cancel deletion

Deletion requires the explicit confirmation field. Active subscriptions and outstanding balances block a request. Resolve them through the available customer or support process before trying again. An accepted request enters the deletion process; it is not simply sign-out. The profile provides a cancellation action while the request remains cancellable.

1. Check subscriptions and outstanding invoices first.
2. Submit deletion only after confirming the consequences.
3. Use Cancel deletion if you change your mind.

Deactivate SSO access

SSO deactivation is a separate confirmed action that deactivates the account and connected SSO access, ends the current session and redirects away from the dashboard. It differs from exporting data or requesting deletion. Save information you need first. If you need access later, use the supported identity or account recovery process.

1. Choose deactivation rather than deletion only if intended.
2. Submit the required confirmation to end connected access.
3. Expect sign-out; use supported recovery if needed later.

Frequently asked questions

Related pages

• Understand pricing before you order
• Place and track customer orders
• View subscriptions and billing
• Create and protect API keys
• Configure customer webhooks
• Manage organisation membership
• Manage notifications