Data we collect
We may store account profile data, OAuth identifiers, watchlists, alerts, overlays, search history, session data, creator snapshots and technical logs needed to operate the service.
This policy explains what Livecounts.org collects, why it is collected, and how API backlink verification works.
Last updated: May 15, 2026
We may store account profile data, OAuth identifiers, watchlists, alerts, overlays, search history, session data, creator snapshots and technical logs needed to operate the service.
When a third-party site calls the public API, we store the referrer host, a sample URL, request counts, last seen time and backlink verification status. Cron jobs crawl those sites to confirm attribution remains visible.
The site uses necessary session cookies and local storage for preferences such as theme, locale and interface state. Authentication providers may set their own cookies during OAuth flows.
Data is used to render live counters, keep estimates fresh, secure accounts, prevent abuse, verify API attribution and improve search, overlays and dashboards.
Operational records are kept only as long as needed for the service, security, debugging and legal obligations. API referrer records can be removed when a site no longer uses the API.
We do not sell personal data. Limited data may be shared with infrastructure, analytics, authentication or platform providers when needed to deliver the service.
Depending on your location, you may request access, correction, deletion, portability or objection to processing. Requests can be sent through the contact page.
We use practical safeguards such as server-side validation, scoped OAuth flows, access controls and rate limits. No internet service can guarantee absolute security.
For privacy questions or rights requests, use the contact page or the legal contact address shown in the legal notice.