Protect customer and provider data
Understand the information that must stay out of clients, logs, notes, and ordinary support requests.
Steps
- Use TidyAnswer public references and masked labels when diagnosing a customer issue.
- Keep refresh credentials in native secure storage and short-lived access tokens in native process memory.
- Avoid logging message bodies, phone numbers, call payloads, webhook bodies, APNs material, or provider media URLs.
- Use approved secure escalation paths if authorized support requires sensitive evidence.
If you still need help
Search this Help Center using the exact feature or visible error. If the issue continues, use Call TidyAnswer support from the Help Center navigation. Include any public reference and the approximate timestamp, but never include passwords, access tokens, provider credentials, or raw webhook payloads.