Undocumented opt-out flow

[macco3k]

Microsoft has some documentation about cookie consent here: https://learn.microsoft.com/en-us/clarity/setup-and-installation/cookie-consent. However, it is not clear what these cookies are for. For example, collect calls are still being sent after revoking consent. It's also completely undocumented how to completely stop tracking. We now assume calling window.clarity("start") and window.clarity("stop") is enough, but this is just an assumption based on other issues here in the repo.

It'd be nice if one could inject the script as off by default, and only start it when the user opts in.

[mmonteiroc]

Users tracking will remain with or without cookies. The only problem is that the cookies wont be used, so you wont identify 1 user as itself, but as multiple users ( one per session )

To stop the cookies usage ( which is the important part for GDPR ) you can use window.clarity('consent', false).
Regarding this, I opened yesterday another issue which in fact does not clear the cookies correctly
#567

[macco3k]

If a user does not give consent to be tracked, I assume they don't want their activity to be recorded at all. It'd be nice to have a way to simply disable the whole script. Daniele Maccari

…

-------- Oorspronkelijk bericht -------- Op 04-04-2024 09:34, schreef Miguel Monteiro Claveri :

Users tracking will remain with or without cookies. The only problem is that the cookies wont be used, so you wont identify 1 user as itself, but as multiple users ( one per session ) To stop the cookies usage ( which is the important part for GDPR ) you can use window.clarity('consent', false). Regarding this, I opened yesterday another issue which in fact does not clear the cookies correctly [#567](#567) — Reply to this email directly, [view it on GitHub](#570 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABLI6UKVJ4UJWESJQA5TAH3Y3T67VAVCNFSM6AAAAABFWVO2AOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZWGQYDKOJQGI). You are receiving this because you authored the thread.Message ID: ***@***.***>