BlaTube
Русский

BlaTube Cookie and Storage Policy

This policy explains how BlaTube uses cookies, localStorage, sessionStorage and similar technologies. They help keep users signed in, maintain guest sessions, operate rooms, remember interface preferences, protect the service, measure usage and support external video players.

1. Contacts

For cookie, localStorage and privacy questions, contact admin@blatube.com.

2. Strictly necessary technologies

These technologies are needed for BlaTube to work and are usually not disabled through consent preferences because the service cannot operate securely without them.

  • Session and authentication: cookies or tokens for login, guest identity, API requests, Sanctum/session, CSRF protection and admin/session cookies if the admin panel is used.
  • Rooms: data about the current room, participant, host/viewer role, connection state, playback synchronization and temporary technical events.
  • Security: request identifiers, rate-limit signals, anti-spam data, request forgery protection and error diagnostics.
  • Preferences: language, theme, interface state, device preferences and hints the user has already seen.

3. LocalStorage and device data

BlaTube may store a guest/auth token, selected language, theme, room state, recent interface preferences, synchronization keys and data that helps you return to a room without repeating setup. If you clear localStorage, log out or use another browser, some preferences and guest access may reset.

4. Analytics

BlaTube uses Yandex Metrica and Google Analytics. Analytics may collect visit events, page views, referrer, page title, clicks, technical browser parameters, device information, approximate geography, errors and product events.

Yandex Metrica may use cookies and localStorage such as _ym_uid, _ym_d, _ym_isad, _ym_visorc_*, yandexuid, gdpr or other Yandex technical keys. Counter settings may include clickmap, trackLinks, accurateTrackBounce and Webvisor. Webvisor may record user interactions with pages for later session replay reports if it is enabled in the counter settings.

BlaTube displays a banner and consent preferences panel for cookies and similar technologies. Users can manage analytics cookies through this interface where the setting is available. Browser settings, blockers or device privacy settings can also be used.

5. Third-party video players

BlaTube displays or starts external videos through YouTube, VK Video, Rutube, Twitch, Vimeo, Dailymotion, PeerTube, OK.ru Video, Dzen, Kodik and other supported sources. When an external player loads, that platform may set its own cookies, localStorage, sessionStorage, pixels or similar technologies. BlaTube does not control the retention periods or purposes of those platforms.

6. Retention

  • Language, theme and interface preferences: until the user changes settings, clears browser storage or the keys are replaced by a new product version.
  • Guest/auth token and session state: while needed for guest session, authentication and room operation.
  • Room data: up to 24 hours after room end or inactivity; the actual period may be shorter.
  • Chat messages: up to 24 hours; the actual period may be shorter. Longer retention is possible only if needed for security, moderation or a lawful request.
  • Last room video: up to 24 hours after room end or inactivity; the actual period may be shorter.
  • Analytics: according to Yandex Metrica, Google Analytics and internal analytics settings where used.

7. Managing cookies and storage

  • Change your browser settings to block or delete cookies.
  • Clear localStorage/sessionStorage for the BlaTube domain in your browser settings or developer tools.
  • Log out to remove some session data from your device.
  • Contact admin@blatube.com if you want to delete server-side account data.
  • Disable third-party cookies or use browser privacy settings to limit external player storage. This may break some videos.

8. What happens if you disable them

If strictly necessary cookies are blocked or localStorage is cleared, BlaTube may lose guest access, room access, theme, language, playback state or authentication. If analytics are limited, shared viewing should continue to work, but BlaTube may receive less information about errors and product quality.

9. Changes

This policy may be updated when cookies, analytics, external players, the extension or browser APIs change. Last updated: May 10, 2026.

First-party counter without external cookies

The internal daily visitors and pageviews counter does not load external scripts and does not set separate marketing cookies. It runs on BlaTube infrastructure and stores only aggregates plus short-lived daily HMAC keys used to distinguish repeated pageviews by the same visitor during a day.

The analytics consent state may be counted only as an aggregate comparison with visitors who allowed external analytics. Rejecting optional analytics does not disable this minimal first-party operational counter.

Cookies, localStorage and analytics

BlaTube uses necessary cookies and localStorage for guest or account sessions, admin CSRF protection, language, theme, profile data, rooms, chat and playback synchronization. This storage is required for stable service operation.

We also use analytics services, including Yandex Metrika, Webvisor, clickmap, trackLinks, accurateTrackBounce and goals, to analyze traffic, improve the interface, detect errors and develop the product. The mc.yandex.ru/metrika/tag.js script may load immediately when the site is visited, before the cookie notice is closed.

The cookie notice has a “Got it” button and stores the dismissal in localStorage. The notice does not provide a separate analytics refusal button. The user can limit, delete or block cookies and third-party scripts in browser settings.