1. Use of the YouTube API Services
GameInflux uses the YouTube API Services to obtain public information about channels and videos.
2. Data accessed and collected
Only public data, obtained by API key on public endpoints, and the results we derive from it in the private pilot described in section 4. No YouTube user authentication is requested, and no private account data is accessible. What follows is the complete list — not a summary.
From a YouTube channel
- identifier, title, description, custom URL, avatar image URL;
- subscriber, video and view counts;
- the creation date, the country and the language that the channel itself declares — never a location or a language we observe or infer;
- the identifier of the channel’s uploads playlist. It is collected but never displayed: it serves only to list that channel’s videos;
- the three dates of our own cycle — when a value was collected, when it is due to be refreshed, when it expires. These three are shown on the channel page;
- five internal markers: the dates of the last enrichment and last complete uploads scan, the number of failed scan attempts, the date of the last attempt and the earliest retry date. Our jobs produce them; they are never displayed and are deleted with the channel.
From a video
- identifier, and the identifier of the channel that published it;
- title, and description — the description is collected and stored, but never displayed;
- publication date, and thumbnail image URL;
- the language and the original audio language that the video itself declares;
- view, like and comment counts. A count a channel chooses to hide stays absent; it is never replaced by a zero.
How we found a channel
We run our own search queries, written by hand. For each result we keep the query and the strategy used, the page and the position of the result, and the identifiers YouTube returned. This provenance is kept for at most 29 days, is never refreshed, and is never shown to anyone: not as an affinity, not as a filter, not as any way of browsing the site.
What we derive from a video title
- for each video of the private pilot described in section 4: its identifier, the result of comparing its title with our independent game reference — which game was identified, if any — and the reason for that result;
- the evidence behind that result — including a normalised copy of the title and the entries of our game reference that it matched —, the versions of that reference used, and two dates: when the result was computed, and when it expires. None of this appears on a public page. On a private page, an authorised operator can see which videos were associated with each game of the pilot; the reason, the evidence, the versions and the dates are never displayed.
What we collect from you
- one first-party cookie, valid for one year, holding a random token that stands for your acceptance of this policy. The language of a page is chosen by its address — French pages are under /fr — and is never stored on the public site: a second first-party cookie, valid for one year and holding a language choice, is set only on the private pages reserved to authorised operators;
- a server-side record of that acceptance: a fingerprint of the token, the policy version, and two dates. The token itself never reaches our database, which therefore cannot tell who accepted;
- nothing else. No IP address, no user agent, no referrer, no account, no browser fingerprint, no audience measurement, no third-party tracker. Your searches, filters and sort orders travel in the address bar and are never recorded.
No audiovisual content is downloaded. Images are displayed from the URLs provided by YouTube, without copy or rehosting: your browser requests them directly from YouTube’s own image hosts, and is told not to send the address of the page you are on.
Some fields are requested only so that we can validate YouTube’s answer, and are then discarded — the hidden-subscriber flag is one. From the step that lists a channel’s uploads we keep nothing at all: no playlist entry, no title, no thumbnail, no position. No pagination token is stored.
3. Storage, retention and deletion
Every value keeps its collection date, its refresh deadline and its expiry deadline. The durations actually applied are the following:
- refresh due: 21 days after collection;
- expiry and removal from display: 29 days after collection, before the 30-day refresh-or-delete limit of the YouTube API Services;
- physical deletion by an automatic process run every hour in the database.
An expired value is never presented as current: it is removed from display before its physical deletion. No history beyond this window is kept, and a channel or a video YouTube stops returning expires at once, without waiting for its deadline. A result derived from a video never outlives it: it expires no later than that video, and is deleted by the same hourly process.
Three things are deliberately kept longer, and we would rather name them than let a reassuring sentence stand in their place:
- the removal register — a channel identifier, the date, and an opaque case reference — is kept with no time limit. Erasing it would let the channel be discovered and indexed again, which would undo the very removal it records;
- the record of a privacy-policy acceptance is kept beyond the year during which it is valid;
- our operational records — the log of API calls, quota counters, job and deletion runs — are kept with no time limit. They hold no data obtained from the YouTube API Services: an endpoint name, a cost, a status, a normalised error code, plus the retry date and technical reason for suspended calls.
4. Use and processing
Values are rendered as received, for consultation. No score, ranking, categorisation or derived metric is computed from this data, with one exception: the private pilot described below.
Within a bounded private pilot limited to two games, SCUM and Valheim, GameInflux compared the titles of 216 videos it had already collected, from 18 channels, with its independent game reference, to identify the game named in each title. Only the title is used — not the description, nor the search through which the channel was found. For each channel, the games identified in its sample are listed with no weighting, frequency, main game or ranking. The pilot serves to examine this attribution in private: no new data was collected for it, its results are kept no longer than their videos (section 3) and are not published, and only an authorised operator who has accepted this policy can consult them, on a private page, while the pilot’s authorisations are valid.
5. Sharing and processors
No data obtained from the YouTube API Services is sold, redistributed, or shared with a third party for that party’s own use. No export, no download and no replication interface are offered.
Two providers process this data on our behalf, on our instructions, and for no purpose of their own:
- Vercel hosts the application, runs its server code, and triggers the scheduled jobs that collect and refresh the data;
- Supabase hosts the PostgreSQL database in which the data is stored, and runs the hourly deletion job inside it.
We name them rather than describe them vaguely: an application that runs on hosted infrastructure has processors, and claiming otherwise would be inaccurate. This policy states what our own repository establishes about their role, and nothing beyond it.
6. Authorized Data
GameInflux handles no Authorized Data: no OAuth authorisation is requested, and no data specific to a YouTube account is accessible.
You can review and revoke access granted to third-party apps on your Google Account connections page. GameInflux currently requests no such access, so there is no GameInflux YouTube authorisation to revoke.
7. Your rights
A user of the service may request deletion of the data concerning them; it happens within seven days. A creator whose public channel appears in our index may request its removal: we honour any verified request where retention is not legally required, and remove the channel within seven days of verifying the request.
For deletion or removal requests, or questions or complaints about our privacy practices, contact us at privacy@gameinflux.com. Writing to us necessarily discloses your own address: we use it to answer you and to handle your request, and for nothing else. Once the matter is settled, the removal register keeps only what section 3 names — a channel identifier, a date, and an opaque case reference — never the address you wrote from.
Deleting data held by GameInflux does not delete or change data held by YouTube. To delete data on YouTube, use YouTube’s own tools.
8. Security and internal access
Access to data is restricted by distinct database roles. Deletion of data obtained from the YouTube API Services has a single technical path, reserved to a dedicated identity. Administration operations are logged without creating a historical copy of this data.