Support teams can usually investigate an issue with a reference number, timestamp and a description. They rarely need your password, login OTP, API secret, payment PIN or full card details.
Before submitting
- Mask phone numbers, email addresses or customer names that are not relevant.
- Remove passwords, API tokens, session cookies and database credentials from logs or screenshots.
- Use order numbers or message IDs where possible instead of including an entire customer list.
- Send only files relevant to the reported problem.
Protect purchased datasets
Keep purchased files in access-controlled storage, limit access to authorised team members and use them only within the product terms and applicable law. Do not upload complete databases to a public ticket or share them in an unsecured link.
Account and API security
Rotate credentials if they may have been exposed. Store secrets on the server, restrict permissions, and use current integration documentation. Never place permanent API keys in a public repository or browser code.
Privacy request
For questions about personal information or account data, contact support through a ticket and describe the request without including sensitive credentials. See the website’s Privacy Policy for the current terms.
Let us know if you still need help with this topic.
