Privacy Policy

Last updated: 2026-09-23

This policy covers this website (operated by Enrique Rubio) and Traffic OS, a private internal application also operated by Enrique Rubio, Spain. Traffic OS is not a public product; this policy exists because Traffic OS uses YouTube API Services and Google OAuth 2.0, and because this website is that application's public disclosure surface.

1. Use of YouTube API Services

Traffic OS uses YouTube API Services. By authorizing Traffic OS to access a YouTube channel, the channel owner (the operator, Enrique Rubio) agrees to be bound by the YouTube Terms of Service and the YouTube API Services Terms of Service.

2. Google OAuth 2.0

Traffic OS authenticates against channels using Google's OAuth 2.0 authorization flow. Access is requested only for channels owned by, or explicitly authorized by, the operator. Traffic OS does not request access to any Google Account other than those the operator controls.

3. API data accessed

Through YouTube API Services, Traffic OS accesses:

Channel identity data (via channels.list) needed to verify which channel is being acted on.
Video metadata and status for videos uploaded through Traffic OS (via videos.insert and videos.list).
Status and statistics (view, like and comment counts, where supplied) for videos published through Traffic OS, read via videos.list and collected automatically for the operator's own measurement of those videos. No other YouTube API, including the YouTube Analytics API, is used.
OAuth tokens required to authenticate these requests.

Traffic OS does not access private messages, other users' data, analytics for videos it did not publish, or any YouTube data unrelated to channels the operator controls.

4. Purposes

API data is used exclusively to:

Verify the identity of a channel before any action is taken on it.
Upload video content that has already been reviewed and explicitly approved by the channel owner.
Confirm that an upload finished processing and published successfully.
Measure the performance of videos published through Traffic OS, for the operator's own experiments on channels the operator controls.
Maintain an append-only internal audit history of publications.

API data is never used for advertising, for training generalized machine-learning or AI models, or for any purpose unrelated to operating the channels the operator controls.

5. Storage

OAuth credentials and API data used by Traffic OS are stored on infrastructure controlled by the operator, outside of any source control system, with filesystem permissions restricted to the operator. No API data or credentials are stored in this website's codebase or deployed alongside it. This policy does not publish internal hostnames, file paths, or infrastructure details, since doing so would itself be a security risk.

6. Retention, verification, update, and deletion

Two different kinds of data are kept, and they are treated differently.

YouTube API-derived statistics. These are the view, like and comment counts read via videos.list, the dated historical snapshots of them, and the copies of those figures inside experiment records. Authorized statistical data of this kind may be retained beyond 30 days, and Traffic OS keeps it as operational history for the operator's own experiments while authorization remains valid. It is not deleted on a fixed timer. Instead, at least every 30 days (in practice more often), Traffic OS re-verifies with a read-only request that:

authorization to access the channel has not been revoked; and
the video still exists on the authorized channel.

The result of each check is recorded. A temporary API failure is recorded and retried and never causes data to be deleted. If authorization is revoked or the video no longer exists, Traffic OS stops collecting for it and the operator deletes the stored statistics for that channel.

Our own operational metadata. Publication and video identifiers, experiment state, approval and audit records, and the verification and deletion records themselves are the operator's own records rather than YouTube API statistics. They are retained as an audit history and are not removed by a data deletion request.

Data deletion requests are honored as soon as possible and within 7 calendar days. Deleting Traffic OS's stored data does not delete the video or any data held by YouTube; it removes only Traffic OS's own stored copy.

API data is not shared with any third party. Traffic OS has no external customers, tenants, or partner integrations that receive YouTube API data.

8. No sale of YouTube API data

YouTube API data is never sold, rented, or sublicensed to any third party, for any purpose, in accordance with the YouTube API Services Developer Policies.

9. Security approach

Access to Traffic OS and its stored credentials is restricted to the operator. Credentials are kept outside of source control and outside of any file served by this website, with filesystem permissions restricted to the operator's own account. This description is accurate as implemented; this policy does not claim encryption, compliance certifications, or security controls that have not actually been put in place.

10. Google Privacy Policy

Google's use of information received from Traffic OS's use of YouTube API Services is additionally governed by the Google Privacy Policy.

11. YouTube Terms of Service

Channel access authorized to Traffic OS is subject to the YouTube Terms of Service in addition to this policy.

12. Revoking access

Any Google Account that has authorized Traffic OS can review and revoke that access at any time at myaccount.google.com/permissions. Revoking access there stops Traffic OS from making further API calls for that channel. The operator can also revoke Traffic OS's authorization from within Traffic OS. Once revocation is detected (by the periodic verification described above) or reported, the stored YouTube statistics for that channel are deleted by the operator.

13. Data deletion requests

To request deletion of the YouTube API-derived data Traffic OS has stored for a specific channel, contact hello@enriquerubio.dev. Include the channel identifier so the request can be matched to the correct data. The operator deletes it with a dedicated command, which removes only Traffic OS's stored copy of the statistics and does not delete the video or any data held by YouTube. The operator's own audit records (see section 6) are retained.

14. Operator / contact information

Operator: Enrique Rubio, an individual (Spain). Contact: hello@enriquerubio.dev. See also the contact page.

15. Cookies and analytics

This section describes the use of analytics on this website. We use Google Analytics 4 (GA4) to measure, in aggregate, how the site is used, in order to understand traffic and improve the content and the site itself. This analytics use is optional: it is only activated if the visitor expressly accepts it through the cookie notice.

GA4 is not loaded and sends no data on arrival at the site. Clicking "Accept analytics" grants analytics storage permission (analytics_storage) and GA4 is activated. Clicking "Reject", or making no decision at all, leaves GA4 deactivated and no analytics data is sent. Consent for advertising is always denied — this site does not use GA4 for advertising or ad-personalization purposes. The decision can be changed at any time from the "Cookie preferences" link in the footer.

When analytics is active, GA4 may collect:

Page and activity events (for example, page views or clicks on specific links).
Session statistics (for example, visit duration or pages viewed).
Approximate location (city or region level, not a precise location).
Browser and device information (for example, browser type or screen resolution).

With analytics active, GA4 may create Google's own cookies in the browser, such as _ga and _ga_<property identifier>. How long Google keeps this data on its own servers is governed by the operator's Google Analytics property settings and by Google's own policies — this site does not set or promise a different retention period. More information in the Google Privacy Policy.

This policy may be updated to reflect changes to Traffic OS or to YouTube API Services requirements. Material changes will update the "Last updated" date above.