Submit privacy requests and prospect corrections
Request access, correction, deletion, restriction, objection, or customer-account deletion through support.
When to use this
Use this for a wrong prospect record, a personal-data request, or deletion of a Leama customer account.
Requirements and availability
- Settings has no self-service customer-account deletion button.
- Provide enough context to locate the record without sending secrets or unnecessary personal data.
- Identity verification may be required.
How to do it
- Open Contact support.
- State access, correction, deletion, restriction, objection, or account deletion.
- Provide account email or exact prospect/company record and the disputed information.
- Include a supporting public source when available.
- Stop using disputed personal data while reviewed.
Fields and controls
| Control | What it does |
|---|---|
| Contact support | Public path for privacy, correction, and account deletion. |
| Prospect detail | Provides company, contact, profile, and run context. |
What happens next
The relevant record can be located, identity verified when needed, and the request assessed. Some information may be retained where required or for suppression.
States you may see
| State | Meaning |
|---|---|
| Submitted | The request reached support. |
| Identity verification required | More evidence is needed before sensitive action. |
| Completed or limited | The response explains action taken or a limitation. |
Credits and usage
Privacy, correction, and account-deletion requests do not use credits.
Common problems
| Problem | What to check |
|---|---|
| The record cannot be located | Provide exact company, contact, account email, and relevant URL or run context. |
| A secret was included | Rotate it and send only safe identifying context. |