Privacy

Viewlet counts page views, not people. This policy explains what data the service collects and why.

What we collect

When a Viewlet badge image is loaded, we store one anonymous event containing:

• A hashed version of the page_id from the badge URL.
• The timestamp of the view.
• The Referer header sent by your browser, if any.

The raw page_id is never stored.

What we do not collect

• No cookies.
• No browser fingerprinting.
• No personal profiles or advertising IDs.
• No unique visitor tracking.
• No IP addresses.

How we use the data

We use stored events only to:

• Display the current view count on a badge.
• Show badge owners aggregated analytics (daily, hourly, and referrer breakdowns).

Data is not sold, shared, or used for advertising.

About the Referer header

The Referer header is sent automatically by most browsers when an image is loaded. It usually contains the URL of the page embedding the badge. We store it only for the purpose of showing aggregate referrer statistics to the badge owner.

If your browser sends a DNT: 1 (Do Not Track) or Sec-GPC: 1 (Global Privacy Control) signal, we store the view event but discard the referrer.

You can also limit referrer sending through your browser settings, or use query_only=true in the badge URL to read the count without recording a new view.

Data storage

Events are stored in a local SQLite database on the Viewlet server. Counts are stored as aggregated numeric values.

This policy reflects how Viewlet actually works. If you have questions, open an issue on GitHub.