Privacy

What the widget sends

When a visitor actually shares something, the widget sends three things:

• which service was pressed
• the URL being shared
• the domain the button was pressed on, read from the request's Origin header

Nothing is sent while a page merely loads. No ping, no beacon, no pixel — only a deliberate press produces a request.

What it does not do

• No cookies, no localStorage, no device or visitor identifier.
• No profile of any visitor, and no data sold or shared with advertisers.
• No raw IP addresses in storage. Addresses are hashed on arrival and used only to stop one client from flooding the counter.

Turning it off

Site owners can disable the ping entirely:

<script>window.ats_config = { track: false };</script>

The buttons work exactly the same; only the counter stops.

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.

Contact

Questions about this page can go to the address listed in the repository README.