1. Scope and fresh choice
This supplement replaces only the optional identified analytics description in our Privacy Policy version 2026-10-17-umami-identified-v2 after you make a fresh affirmative analytics choice for this version. That Privacy Policy continues to provide our controller details, other processing information, rights and contact route. Registration privacy-notice records and the separate Session Replay purpose are unchanged. An earlier analytics acceptance does not authorise the expanded collection; an earlier rejection remains respected.
2. What we send to Umami
Only after affirmative analytics consent, our self-hosted Umami instance measures selected page views and product events. Guest activity carries no account profile. For signed-in users, we send the account ID and, where available, display name, email address, active organisation name and subscription-plan tier (Solo, Team or Enterprise) as identified session properties. We retain the existing stable, hashed analytics identifier to link activity across visits and devices. This may associate earlier recorded activity linked to the same identifier with these account details. This is identifiable personal data, not anonymous data.
The organisation and plan come from the authenticated account context when activity is collected. A trial or confirmed manual grant may carry its actual plan tier; an account without a reported subscription or confirmed manual tier carries no plan value. Pending or failed context lookups pause signed-in analytics rather than guessing a plan or reusing another organisation's details. These properties describe the latest reported session context. They are not payment evidence, an entitlement decision, an organisation-change history or proof that someone is currently online.
Account and organisation details are confined to identified session properties. We do not send organisation IDs, authentication credentials, security fingerprints, raw searches or arbitrary event text, exact coordinates, parcel or property identifiers, full dynamic URLs, URL fragments, titles or raw referrers for this purpose. Session Replay retains its separate choice and existing limits.
3. Purpose, access and retention
We use this information to recognise which consenting account performed selected activity and understand use by organisation and plan. Access remains limited to the existing restricted analytics owner role. Values are stored with sessions in our self-hosted Umami instance. Properties show the latest values reported for each session; unavailable optional values known to be absent are stored as empty strings. Already collected properties can remain visible after sign-out, a profile or organisation change, or withdrawal. Analytics records currently have no automatic expiry or deletion schedule. The rights and contact route in the linked Privacy Policy apply to this processing.
4. Your choice
Reject or withdraw optional analytics at any time in Cookie Settings in the site or signed-in app footer. Choosing not to allow it does not prevent use of the Service. Withdrawal stops future optional analytics and replay capture; it does not erase previously collected records or affect the lawfulness of processing before withdrawal. Essential login, security and privacy-choice cookies remain independent. Analytics measurement uses no analytics cookies or browser storage. Session Replay requires its own separate choice; accepting this update alone does not enable it.