Privacy
Share button privacy: what leaves your page.
Share beacons and optional aggregate counts support the buttons. Saved preferences stay in your browser. Here is what is used and how to control it.
Last updated 2026-09-14
- 01
No cookies, no identifier
No cookies, visitor identifier or fingerprint. If you save preferred services, their keys are stored in your browser for that site. This site also remembers your selected theme. Neither setting identifies you or synchronizes across websites.
- 02
No page-view tracking
Share tracking runs only after a sharing action. Loading buttons fetches script and icon assets. Enabling count badges also requests the aggregate counts for the page URL.
- 03
Three fields
Service, page URL and a timestamp. The domain comes from the Origin header, never from the body.
- 04
IPs are never stored
The address is hashed with a local salt on arrival and kept only long enough to ignore the same press twice inside a minute.
- 05
Off in one line
Set track: false to disable share beacons. Also set counters: false and remove ats_counter classes to disable count requests, and analytics: false to disable events sent to analytics already installed on the page. Sharing continues to work.
Third parties
Pressing a button opens the destination service — Facebook, X, WhatsApp and so on. From that moment the visitor is on that service's page, under that service's own privacy policy. We have no involvement in, and no visibility into, what happens there.
The site itself loads one webfont from Google Fonts. The widget your visitors load does not: it has no external dependencies at all.
Help and terms
For setup and privacy questions, see the frequently asked questions. What you may do with the widget, and the warranty it does not carry, are set out in the terms of use.
Turn counting off entirely
<script>window.ats_config = { track: false, counters: false, analytics: false };</script>Also remove any ats_counter classes. Script and icon files still need to load.