What cookie-free analytics still needs to explain

No tracking cookies by default

The AntDock Web SDK does not use tracking cookies by default. It uses browser storage to maintain visitor and session identifiers. Storage clearing, private browsing and blocking can change identification. Cookie-free does not mean identifier-free or automatically remove privacy notice obligations.

Analytics covers received events, not visits lost to blocking. Detailed visit records and aggregate reports have different granularity. Describe the fields, retention, access and sharing actually enabled.

Exclude your own browser

Use ?antdock=ignore on the site to exclude this browser on this domain, and ?antdock=track to resume. It does not exclude other devices or retroactively delete records. Local hosts are excluded by default.

Filter DevTools Network with -domain:antdock.com during debugging. This only changes the developer tools display, not collection permission.

Keep public data aggregate

Article counters and widgets display aggregate metrics. Enabling public counts still requires an explicit owner choice. Check the report’s sharing scope before publishing, and keep visitor identifiers and private paths out of marketing screenshots.

Requirements depend on the site and context. Review actual configuration and applicable rules rather than inferring compliance from cookie-free defaults. See the privacy policy and SDK reference.