Kingsclap processes comments that sometimes contain names, phone numbers and order details. This page explains what we do with that data, what we do not do, and the controls you have.
Over an encrypted connection from a connector, import or webhook.
Phones, emails, order IDs and card fragments replaced with tokens.
Themes, sentiment and severity extracted from the masked text only.
Comments and results encrypted at rest, scoped to your workspace.
Role and location based access decides who reads what.
Personal details found in comments, such as phone numbers, email addresses, order and booking numbers, and partial card numbers, are masked before the comment is analysed. Themes and reply drafts are produced from the masked text. The original is kept only so authorised users can read the full comment when needed, and can be switched off per source.
Your comments are used to analyse your workspace only. They are not used to train models shared with other customers.
Public review data is collected and used according to each source’s terms, through official access where it is offered.
Choose how long raw comments are kept. Aggregated theme counts can be kept after raw text is deleted.
Export everything at any time. On request, or when you leave, your workspace data is deleted from active systems.
All traffic to and from Kingsclap uses TLS. Connectors use each source’s secure API.
Comments, results and connector credentials are encrypted at rest.
Admin, analyst, approver and viewer roles, scoped to brands, regions or locations.
Logins, exports, theme edits and approved replies are logged with who and when.
Connector tokens are stored encrypted and never shown again after setup.
Each customer’s data is logically separated and access-checked on every request.
No reply is posted without a person approving it. This cannot be turned off.
Scale customers can request our security questionnaire responses and a review call.
Data is stored with established cloud infrastructure providers. Scale customers can discuss regional hosting requirements with us.
Yes. Per source, you can choose to keep only the masked text, so the original comment with personal details is never stored.
Access by our staff is limited to support and troubleshooting you request, and is logged.
Use the contact page and mark the message as a security concern. It is routed to the people responsible straight away.
Tell us what your team needs to see. We will walk through data flows, redaction and access controls on a call.
