Privacy Policy
tubeRepeater is individually maintained. This page describes current practices in plain language; it is not legal advice. Consult a professional if you need guidance for a specific situation.
Traditional Chinese vs English pages
Languages are split by path (e.g. / vs /en/), not a logged-in profile. The static site does not store a “language preference” on a server; whichever URL you open is what loads.
What is live today
The following reflects behavior already shipped in the pages; it is separate from “possible future work.”
YouTube URL you type on the home page
The URL is used in your browser to request an embeddable player. There is no account system here, and the site does not store your watch history server-side. Whether playback works still depends on uploader/YouTube settings.
Google Analytics (why it is used)
The site loads Google’s gtag library with measurement ID G-WCTNFJF3H6 to see approximate traffic, page views, and entry paths for maintenance (for example, whether help pages are read, or which error patterns appear). Google processes this data under its product policies. This site has no account database and does not export raw GA records separately for profiling. Retention details follow Google Analytics / Measurement docs; you can use tracker-blocking extensions, private windows, or Google’s opt-out tools to reduce what is recorded.
Google AdSense (where it loads and why)
Only the home page at https://tuberepeater.com/ and https://tuberepeater.com/en/ includes the async AdSense client script, so ads—when enabled by Google—can fill the reserved area on that page. Help articles, policy pages, 404, and old-URL handoff pages do not include that script. Whether an ad actually renders depends on your account, region, and Google’s policies. When ad scripts load, Google may use cookies or similar technologies as described in Google’s materials.
YouTube embeds and other third-party network calls
Video plays through the YouTube IFrame Player. Thumbnails, sign-in, and any Google/YouTube-side logging follow their policies and whether you are logged in. Even when you are not signed in, playing a public video may still send necessary technical requests to YouTube. For how Google/YouTube may use cookies and similar storage, see Google’s documentation (for example the Google Privacy Policy and How Google uses cookies); exactly what is written depends on your browser, login state, and Google’s live technology.
Cookies and local storage
Identifiers from Google Analytics, AdSense (home page only), and YouTube embeds follow their respective policies. In practice these are often third-party cookies or similar storage set by Google domains; naming, partitioning, and lifetime depend on the service and browser behavior. This site does not add a separate, branded “tubeRepeater” cookie consent banner; you can still clear site data, use private mode, or install blockers in your browser.
Retention and what you can control
There is no sign-in here and no server-side watch history or personal profile files that you can “download or delete” from tubeRepeater. A URL you type on the home page stays in the browser session for the front-end player only. If you care about third-party identifiers, clear cookies/storage for tuberepeater.com and relevant Google/YouTube domains, and read Google/YouTube guidance on retention. If you believe something tied to this site’s pages is mishandled and want the maintainer to investigate, use the email below (see Contact for scope).
Planned or possible changes (not in code until shipped)
If the site later adds ad slots outside the home page, new analytics, or client-side language storage, both this page and the implementation will be updated together so text matches behavior. Until then, the practices above are the ones in effect.
Contact
For privacy questions, email contact@tuberepeater.com (see Contact for response expectations).