This policy explains, honestly and in plain terms, what personal data Livecounts.org processes — including the public metrics of creators and public figures — why we process it, who it is shared with, and the rights you can exercise, including how a creator can request removal. It is written to comply with the EU and UK GDPR, the ePrivacy rules on cookies, and French law.
Last updated: 26 June 2026
The data controller is the publisher of Livecounts.org, a private individual domiciled in Normandy, France, whose identity is held by the hosting provider as set out in the Legal Notice. The controller decides why and how the personal data described below is processed. You can reach the controller for any privacy matter through the contact page linked in the footer, or at the contact address shown in the Legal Notice.
The main purpose of Livecounts.org is to aggregate and display publicly available metrics about creators, channels and communities on supported platforms (YouTube, TikTok, Instagram, Twitch, X, Reddit, Discord, Roblox). For each profile we may collect and store the public handle, display name, platform account identifier, avatar image, description, country, category, verification status, and statistics such as subscriber, follower, member, viewer, video and view counts, together with their history over time and derived growth figures. We may also link the publicly listed accounts that appear to belong to the same person across different platforms in order to present a unified profile. This information is gathered from public profiles, public platform interfaces and public APIs; we do not access private or login-protected content of the people concerned. Where these individuals are identifiable, this is their personal data, and we process it on the basis of our legitimate interest (Article 6(1)(f) GDPR) in operating a public-metrics information and comparison service of value to our users. We have weighed this interest against the rights of the individuals concerned: the data is already public, limited to professional/public-presence metrics, and never used to contact or profile people for marketing. If you are a creator and object to this processing, you may request removal at any time — see the section on your rights below.
When you browse Livecounts.org we process only what is needed to run the site. This includes strictly necessary cookies and local storage for your preferences (language, theme and interface state) and an on-device favourites list that never leaves your browser. Our servers and our hosting provider keep standard technical logs (such as IP address and browser information) for security and operation. When a request reaches our public API, the caller's IP address is stored briefly in our database to enforce rate limits and prevent abuse, then automatically deleted. We do not currently offer user accounts or logins, so we do not collect account profiles, passwords or social sign-in data from visitors; if account features launch in the future, this policy will be updated before they go live.
When a third-party website or application calls our free public API, we record the referring domain, a sample request URL, request counts, the time it was last seen and whether the required attribution backlink to Livecounts.org is present. An automated job may visit those referring sites to verify the backlink. The purpose is to enforce the conditions of the free API on the basis of our legitimate interest. Where a referring site belongs to an individual, this constitutes their personal data and is processed for the same purpose.
We use a small number of strictly necessary first-party cookies and browser storage that do not require consent: a language cookie (lc_lang), a theme cookie, a session cookie, and local storage for your theme and your on-device favourites. These keep the site working and remember your preferences. Optional cookies — set by Google Analytics for audience measurement and, in the future, by Google AdSense for advertising — are governed by Google Consent Mode, which is configured to deny analytics and advertising cookies by default. Analytics runs in a cookieless mode unless and until you grant consent. We are transparent that a full consent banner is still being rolled out; while advertising is enabled on a profile-by-profile basis in the future, the AdSense script may load on pages, but ad and personalisation cookies remain governed by the default-denied consent signal. This policy and our cookie controls will be updated as the consent mechanism is finalised.
We use Google Analytics 4 to understand aggregate usage of the site, such as which pages and creator profiles are viewed. Some analytics events include the creator identifier, platform and handle associated with the page being viewed, which means that public creator data is transmitted to Google as our analytics provider. We also include the Google AdSense script in anticipation of displaying advertising; no advertising is served at this time, and any future ad personalisation will depend on the consent signal described above. Google acts as our processor for analytics and as an advertising partner for any future ads.
We use the data above to display and estimate live counters and historical charts, to power search, rankings and trending sections, to cache avatars so images stay stable, to keep figures reasonably fresh between updates, to secure the service and prevent abuse, to enforce the attribution terms of our free API, and to measure aggregate audience and (in the future) serve advertising subject to consent. We do not use the data to make decisions that produce legal or similarly significant effects on individuals, and we do not sell personal data.
We share data only with the providers needed to run the service. Cloudflare hosts the website and stores creator data, the short-lived API rate-limit records and the API referrer records in its database and object storage, and keeps edge logs. Google Cloud Run runs our data-update and scraping scripts, and Google Analytics and Google AdSense provide measurement and advertising. To collect public metrics reliably we route some outbound requests through third-party proxy networks acting as technical processors for that traffic. Source platforms and their public APIs (for example Google/YouTube and Twitch) are contacted to read public data. We do not sell personal data and we do not share it for the independent marketing purposes of any third party.
Our hosting and analytics providers, including Cloudflare and Google, are based in the United States, and some processing therefore takes place outside the European Economic Area and the United Kingdom. Where personal data is transferred internationally, it is protected by appropriate safeguards, namely the European Commission's Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework and its UK extension. Proxy and infrastructure routing used for data collection may also involve cross-border transfers protected by the same mechanisms.
We keep data only as long as needed for each purpose. API rate-limit records containing a caller's IP address are deleted automatically within roughly 24 hours. Public creator profiles, avatars and historical count snapshots are retained for as long as the profile remains part of the service so that history and charts stay meaningful; they are updated or removed when sources change or upon a valid removal request. API referrer records are kept while the referring site continues to use the API. Server and edge logs are retained according to our hosting providers' standard periods.
We do not sell personal data and do not engage in cross-context behavioural advertising based on data we collect. Beyond the processors listed above, we may disclose data only where required to comply with a lawful request from a competent authority, to protect the security and integrity of the service, or to establish, exercise or defend legal claims.
Depending on where you live, you have the right to access your personal data, to have it corrected or deleted, to restrict or object to its processing, to data portability, and to withdraw consent for analytics or advertising at any time. Creators and public figures whose public metrics we display have a specific and important right to object (Article 21 GDPR) and to request removal: on request through our contact page we will delist the profile and delete the associated avatars, identity links, snapshots and counts from our database and storage. We commit to handling such requests without undue delay. You also have the right to lodge a complaint with a supervisory authority — in France, the Commission Nationale de l'Informatique et des Libertés (CNIL). To exercise any right, use the contact page linked in the footer or the contact address in the Legal Notice; we may ask for information to confirm your request relates to you or to the profile concerned.
We apply practical safeguards appropriate to a service of this kind, including server-side validation, access controls, rate limiting, encrypted connections and restricted handling of any operational credentials used to collect public data. No method of storage or transmission is completely secure, but we take reasonable steps to protect the data we hold and to limit who can access it.
For any privacy question, to exercise your rights, or to request the removal of a creator profile, please use the contact page accessible from the site footer or the contact address shown in the Legal Notice. This is the official channel for reaching the data controller, and we aim to respond promptly.
