Data and privacy

Privacy Policy

Last updated: 2026-07-15. How Clivon handles pilot data, property materials and operational information.

What data can be collected

Clivon is an assisted marketing platform for real estate flow operations.

  • Contact, identification and commercial details used for order handling.
  • Property materials, files, links, notes, and flow usage data.
  • Information needed to operate the pilot, support, review and assisted delivery.
  • Technical navigation data and attribution parameters present in the access, such as UTM, fbclid and gclid.

Payments

  • Payments are processed by an external provider, including Mercado Pago.
  • Full card details are not stored in Clivon static pages.

Use of data

  • Data is used to run the pilot, provide support, prepare deliverables and improve the service.
  • Attribution parameters and navigation events may be used to measure the source and continuity of the journey.
  • Clients should provide materials with valid usage rights.

Cookies, local storage and integrations

  • Local storage keeps the visual theme preference. Return and intake pages may also keep the payment attempt's external reference locally to recover status and continue the flow.
  • Session storage keeps a technical session identifier for attribution and journey events. Checkout V1 uses IndexedDB to keep a technical bootstrap identity and markers for actions already processed, helping prevent duplicate actions across tabs. These identifiers and markers are not full card details.
  • Essential cookies may support checkout continuity and attempt resumption. Attribution cookies such as _fbp and _fbc may be read when present, and parameters such as UTM, fbclid and gclid may accompany the journey.
  • When enabled, the Meta integration may receive navigation or conversion events. Payments are processed by an external provider such as Mercado Pago. Clivon does not store full card details in its static pages.