Privacy and consent

Read the support matrix before you build a consent banner on top of any of this. The behaviour genuinely differs between SDKs, and the difference is the kind that is discovered late.

The four mechanisms:

• Opt-out — a hard local switch. Every SDK has it.
• The consent gate — delivery is withheld until consent is granted. Browser, Node, Go, Swift and Android implement a real gate. In Python and Java, consent is a signal, not a gate: it is recorded and stamped on events but does not stop delivery. If you need blocking there, do not send the event.
• Per-purpose filtering — keeping strictly-necessary events while dropping analytics ones. A browser plugin only; no other SDK has an equivalent.
• Do Not Track — a browser signal, honoured by the browser SDK. No server SDK reads it, and neither mobile SDK does, because neither platform emits one.

Anonymous mode sends neither a device id nor a session id and refuses identify(). Where it exists it is the strongest setting short of not sending at all.

Per-SDK reference

Each page's §13 covers opt-out, anonymous mode, the consent gate and Do Not Track.

• Browser
• Node.js
• Python
• Java
• Go
• Swift
• Android

React: React §8 Consent.