1. Accept all, decline or choose separately
Emvadon asks for your permission to use optional analytics and optional session recording to understand and improve selected parts of the Service. Choosing Accept all expressly enables both purposes. Decline rejects both. The settings control beside those buttons lets you choose analytics without recording, or reject both. Both optional purposes are off until you choose to allow them. You can use the Service if you decline.
This version replaces the 17 October 2026 choice notice to align its retention information with the current policy. The choices and collection limits are unchanged. Analytics alone still does not enable recording. Existing saved choices remain unchanged; an earlier analytics acceptance is never treated as permission to record.
2. What you are allowing
Analytics measures selected page views and product events. For signed-in users, it sends the account ID and may send name, email, active organisation name and subscription-plan tier to link selected activity across visits and devices. The data categories and exclusions are described in the optional analytics notice.
Session recording creates a video-like reconstruction of interactions on selected pages, including readable visible text and sampled map images. These can include personal, account, property or location information. Recordings last up to five minutes. Form controls and inputs, other media and marked private content are blocked. Account, authentication, billing, client, document and dynamic-detail routes are excluded. The eligible pages, sampling limits, access restrictions and other exclusions remain those in the session recording notice.
3. Change your choice
Open Cookie Settings in the site or app footer, or from account preferences, to change either choice. Turning recording off stops future recording while allowing analytics to remain on. Turning analytics off stops both. Withdrawal stops future collection and does not itself erase previously collected records. You can ask for earlier erasure through the contact route in our Privacy Policy which also provides controller details, your rights and other processing information.
4. Retention and deletion
The current retention terms replace the earlier no-expiry statements. Session recordings are deleted once they are more than 90 days old, counted from the last part of the recording. Chunks stored for the same native visit are deleted together only once the newest chunk is more than 90 days old. Analytics events, including selected page views, product events and their event properties, are deleted 25 months after each record was collected.
Analytics sessions and their stored account and organisation properties are deleted only when the session is more than 25 months old and no analytics event from the last 25 months or recording from the last 90 days remains for it. A replay-only session can therefore keep its stored properties after the recording expires until the session is more than 25 months old.
A scheduled job runs daily, so expired records are normally removed within about one day. These periods apply to the live analytics database. Copies can remain in encrypted disaster-recovery backups, which are not used for analysis. If a backup is restored, expired records and records already erased at your request are removed again before the restored data is used.
The complete conditions and earlier-erasure request process are described in the current retention notice.