Cintesa
Operate

Visitor data & privacy

What personal data a Cintesa project stores, where operators see it, and what cleanup does not delete.

Last updated on

Visitor personal data lives in a few places. Operators see it only on this project’s dashboard (and connected tools you turned on). Do not treat conversation logs or the usage log as a second contact list.

Contacts list — visitor personal data you can open

Where personal data is stored

LocationTypical dataWhat you see
ContactsEmail, phone, custom form fields, booking name/emailFull record; fields marked sensitive stay masked until Reveal
Conversation logsMessage text, CTA clicks, session and visitor idsEmails and phones redacted in stored content
Usage logEvent names, traffic source, landing path, CTA labelsEvents — not a full transcript
BookingsVisitor name, email, phone if collectedBooking detail and the linked contact

The platform does not add a hidden “knowledge graph” of visitors. What you ingest and what visitors submit is what you have.

Sensitive fields

  1. In the content section editor, mark form fields as sensitive when they should not sit in the clear.
  2. Those values redact in conversation logs and stay masked on the contact until an operator uses Reveal.
  3. Reveal is an operator action (it is recorded). Copy only what you need.

Use fixture or staff-owned test contacts when you practice this — never a customer’s private data in screenshots or exports you share.

Delete and stop collecting

  • Delete contact on the profile removes that lead record. Archived hides the row without deleting it.
  • Conversation log cleanup (when retention ships) removes old transcripts. It does not delete contacts or form submissions.
  • Turn off live chat under General → Management → Conversations enabled, or put the site Under construction, to stop new sessions — see Project management.
  • There is no bulk “purge all visitor data” control today beyond per-contact delete and (later) log time windows.

Security settings

Organization → Security is the place for future sign-in controls (SSO / MFA). Team access is Team members today.

Plan windows for logs are described on Limits. They are not applied yet. Public privacy copy on the marketing site may still describe a window the product has not started enforcing — follow the dashboard, not an old paragraph.

© 2026 Cintesa. Guide text and screenshots are Cintesa product materials for personal and operator use. Do not scrape or republish them commercially without permission. Terms of Service · Privacy Policy.

On this page