Manage personal privacy data
To manage personal privacy data, start with a signed-in account and a documented reason for the security or governance task. In Admin, request personal data export, request account deletion, and review request status. Use the least access needed, verify the subject and scope, and keep secrets and personal data out of notes and support evidence.
Before you start
- A signed-in account and a documented reason for the security or governance task
- The current user’s own email or identity when the task is personal
Steps
- Open /settings/privacy as the signed-in person whose data request is being made.
- Choose personal data export or account deletion; read the displayed scope and consequences before submitting.
- Confirm only the intended request once and retain its returned status or reference.
- Review request status on the same page; do not submit duplicates while a request is pending.
Expected result
The selected export or deletion request returns a visible reference or status for the signed-in person. Pending requests remain identifiable, and opening the page or reviewing status does not create another request.
Permissions
- Personal privacy settings are authenticated and apply to the currently signed-in person; export and deletion requests do not authorize acting for another user.
Troubleshooting
An export or deletion request cannot be submitted.
Read the displayed scope and validation, confirm the request belongs to the signed-in person, and submit once. Do not send another request while the first status is unknown.
A privacy request remains pending or cannot be found.
Review status on /settings/privacy and retain the returned reference. Escalate through the privacy or Support channel with the reference, request type, and time; do not attach exported personal data.
Related articles
Enroll the signed-in user’s trusted authenticator without exposing the QR secret or one-time code.Review audit and communication history
Filter and preserve scoped audit or communication evidence without treating the history as editable data.Review access approval requests
Review one access request and approve only the justified scope or reject it with a recorded reason.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback