1. What this version changes
This version supersedes the optional-analytics statements in the 15 October 2026 Umami notice and the identified-analytics update of 16 October 2026. It adds a separate optional Session Replay choice. The rest of our privacy information continues to apply.
You can read the preceding notice at Privacy Policy version 2026-10-16-umami-identified.
Controller and Processor Roles. Emvadon remains the controller for accounts, authentication, and payments, as well as billing, security, support and consented product analytics. Where an organisation provides Customer Content containing third-party personal data, that organisation is normally the controller and Emvadon acts as processor on its documented instructions; a data processing agreement may be requested for Enterprise orders. Do not upload special-category personal data without a defined written agreement and lawful basis.
We process billing legal name, billing address, VAT/tax identification number where provided, invoice and tax records. Our payment processor provides invoicing and tax compliance support. The preceding notice identifies operational recipients used for transactional email delivery, MaxMind login risk and geo enrichment, Cloudflare Turnstile and the first-party browser/device security signal during sign-in, organisation sign-in (SSO), and related MFA flows. It also identifies HERE mapping, Cal.com scheduling, and Instatus status communications. The security technologies support account protection and are independent of your analytics choice. Where transfers occur outside the EEA, the preceding notice describes use of the EU–US Data Privacy Framework, Standard Contractual Clauses, an adequacy decision, or another lawful transfer mechanism as applicable.
2. Optional identified analytics
We use a self-hosted Umami instance to measure selected page views and product events only after affirmative analytics consent. Guests are measured anonymously. For a signed-in user, the selected activity can use a pseudonymous stable analytics identifier to link visits and devices. It is derived from an internal account value using a versioned one-way hash; a hash is still an identifier for this processing and does not make the data anonymous.
We do not send your raw account UUID, name, email address, organisation identifier, authentication or security fingerprint, raw search query, free text, exact coordinates, parcel or property identifier, full dynamic URL, URL fragment, title, or raw referrer to Umami for this analytics purpose. We do not use analytics cookies or browser storage for this measurement.
3. Optional Session Replay
Session Replay is an optional video-like reconstruction of interactions with selected pages. It is separate from optional analytics. We do not start replay collection unless you make the separate Replay choice in Cookie Settings; agreeing to analytics alone does not authorise Session Replay.
Replay is limited to the public homepage, About and pricing pages, and the signed-in dashboard, Portfolio, listings index, Market Intelligence and Planning Explorer. The recorder masks all on-page text and form inputs before recording and blocks media, maps and content marked sensitive. Account, authentication, billing, client, document and dynamic-detail routes are excluded from replay.
Each replay recording is limited to five minutes and starts only after the person has expressly consented. Heatmaps are not enabled. Replay is available only to the existing restricted owner role. Masking and route blocking limit what the recorder can collect; they do not mean that future page changes are automatically safe to record.
4. Purpose, access and retention
We use optional analytics and Session Replay to understand how selected parts of the Service are used and to improve them. Access to replay is limited to the existing restricted owner role. The account-to-analytics-identifier mapping remains within Emvadon and is available only through restricted operator tools.
Analytics and replay records in our self-hosted Umami instance have no automatic expiry under the current configuration, and there is no current automatic deletion schedule. You may use the contact route in section 6 to make an applicable data-protection rights request.
5. Your choices
You can reject or withdraw analytics and Session Replay choices separately at any time in Cookie Settings in the site or signed-in app footer. Withdrawing Replay consent stops future replay capture. Withdrawing either choice does not itself delete records already collected or affect the lawfulness of processing before withdrawal.
These preferences do not affect essential cookies needed for login, security or remembering your privacy choice. They do not control the separate security technologies described in the preceding notice.
6. Contact and rights
Applicable rights include access, rectification, erasure, restriction, Data portability, objection and Withdraw consent. For questions about this processing or to exercise applicable data-protection rights, contact . Use Cookie Settings to withdraw optional analytics or Replay consent. The preceding notice's retention terms, including up to 12 months for security, login and operational logs and up to 7 years for contract, acceptance, withdrawal, invoice, tax, refund and dispute evidence, continue to apply.