Your data and privacy

Every record carries the workspace it belongs to, and the database refuses to return a row to anybody outside it.

That layer sits beneath the application, so an application bug cannot leak data between customers.

The same mechanism enforces the per-role visibility in Roles and permissions.

• Transcripts are sent to Anthropic for analysis, on your own API key, under terms that prohibit using them to train general-purpose models.
• They are stored in our database so the product can show them back to you.
• Credentials you connect (your Anthropic key, your GoHighLevel tokens) are stored encrypted.

Your prospects appear in transcripts, dossiers and analyses without ever having signed up here.

You decided to record them, so you are responsible for whatever notice or consent the law where you operate requires.

If one of them asks to see or delete what is held about them, the request belongs with you, and we will help you answer it.

Full detail, including the list of subprocessors, is in the Privacy Policy and the Terms of Service.