Legal
Cookie Policy
This policy explains which cookies and browser-storage technologies Remio and its providers use, why they are used, and how you can control them.
Cookie and Storage Register
Provider names and durations can change when a provider updates its technology. The consent message is the current source for selected advertising vendors and purposes.
| Name | Category | Provider | Technology | Purpose | Duration | When used |
|---|---|---|---|---|---|---|
| remio_visitor_key | Strictly necessary | Remio | First-party HTTP-only cookie | Recognizes a browser pseudonymously for play counts, reactions, rate limiting, abuse prevention, and service integrity. | Up to 12 months | Created when a player uses a relevant game or reaction feature |
| remio_locale | Preference | Remio | First-party cookie | Remembers the language explicitly selected by the user. | Up to 12 months | Created when a language is selected |
| remio-sidebar-collapsed | Preference | Remio | Local storage | Remembers whether the navigation sidebar is collapsed. | Until local storage is cleared | Used when the interface preference is changed |
| remio-player-games-v1 | Player-requested feature | Remio | Local storage | Stores favorites, recent games, likes, and related local player state without requiring an account. | Until items are removed or local storage is cleared | Used when the player interacts with these features |
| remio-notifications-v1 | Player-requested feature | Remio | Local storage | Stores local notifications and their read state. | Until notifications are removed or local storage is cleared | Used when Remio notification features are available |
| Supabase authentication cookies | Strictly necessary when signing in | Supabase / Remio | First-party authentication cookies | Authenticates an account, refreshes the login session, and protects account access. | Session-based or according to the authentication and refresh-token lifetime | Used only when account functionality is used |
| remio_aid / remio_analytics_anonymous_user_id | Analytics | Remio | First-party cookie and local storage | Provides a pseudonymous identifier for funnels, return activity, attribution, and game-performance analytics. | Up to 12 months | Used only when analytics storage is permitted |
| remio_analytics_session_id / remio_analytics_attribution | Analytics | Remio | Session storage | Measures the current tab session and attributes a game visit to a discovery interaction. | Tab session; recommendation attribution expires after approximately 30 minutes | Used only when analytics storage is permitted |
| Google Privacy & Messaging consent records | Strictly necessary consent management | Cookies, local storage, scripts, and consent strings | Displays the applicable privacy message, records a choice, transmits IAB TCF or other supported privacy signals, and allows the choice to be changed. | As specified by Google and the applicable consent framework | Used to operate privacy choices | |
| Google AdSense and selected ad-technology providers | Advertising and measurement | Google and providers displayed in the consent message | Third-party cookies, local storage, scripts, pixels, and advertising identifiers | Serves, secures, limits the frequency of, personalizes where permitted, and measures advertising. Limited or non-personalized modes may apply after refusal. | Varies by provider and purpose | Controlled by the consent signal and applicable law |
| Embedded game and distribution-provider storage | Game functionality, analytics, and advertising | GameDistribution, GameMonetize, game developers, and other listed providers | Third-party cookies, local storage, SDKs, pixels, game saves, or identifiers | May provide game delivery, saved progress, security, analytics, advertising, purchases, multiplayer, or other features inside the selected game. | Controlled by the relevant game or distribution provider | Loads when the game page or player is opened; gameplay is not conditioned on optional Remio analytics consent |
1. Scope and Controller
This Cookie Policy explains how Peakaso s. r. o. (“Remio”, “we”, “us”) uses cookies and similar browser technologies on remioplay.com. It supplements the Privacy Policy.
Cookies are small files stored by a browser. Similar technologies include local storage, session storage, pixels, SDKs, consent strings, and other identifiers that store or read information on a device.
2. Categories We Use
- Strictly necessary: security, authentication, consent records, fraud prevention, rate limiting, and operation of a feature requested by the user.
- Preferences: choices such as language and interface layout.
- Player-requested features: local favorites, recent games, notifications, reactions, and game state.
- Analytics: measurement of traffic, discovery funnels, reliability, playtime, return activity, and attribution.
- Advertising: ad delivery, personalization where permitted, contextual or limited ads, frequency control, fraud prevention, and reporting.
- Embedded games: storage controlled by a game developer or distributor for functionality, saves, accounts, analytics, multiplayer, purchases, or advertising.
3. Consent and Refusal
Where consent is required, Google Privacy & Messaging presents the applicable choices before optional analytics or advertising storage is enabled. The message identifies selected ad-technology providers and purposes.
If analytics storage is declined, Remio uses a short-lived cookieless operational mode for aggregate page, game-start, availability, and performance measurement. It does not create the Remio analytics cookie or analytics local/session storage and does not store an IP hash, user-agent hash, persistent analytics identifier, cross-page attribution, or retention profile.
Refusing optional storage does not by itself remove access to basic gameplay. Advertising may be limited or non-personalized, and some third-party or personalized features may be unavailable. Strictly necessary and player-requested technologies may still operate.
4. Embedded Games and Third Parties
A selected game may run in an iframe controlled by a separate developer or distributor. The iframe may load when the game page or player is opened, including before or without an applicable initial privacy decision. Loading it sends normal network information such as an IP address and browser headers to its provider.
Third-party providers are responsible for their own cookies, purposes, legal bases, retention, and honoring applicable consent signals. Review the provider's notice when available. Remio cannot delete storage that is controlled only by a third party.
5. Managing Browser Storage
Use the button below or the footer control to reopen the Google privacy message and change an advertising or analytics choice. Withdrawing consent does not affect processing that was lawful before withdrawal.
You can also delete or block cookies and site data in browser settings. Blocking strictly necessary, authentication, preference, or game storage can sign you out, reset preferences or saves, prevent reactions from working correctly, or otherwise reduce functionality.
6. Changes and Contact
We may update this Cookie Policy when technologies, providers, laws, or Remio features change. The current version is dated July 12, 2026.
For questions or privacy requests, contact contact@remioplay.com. Operator: Peakaso s. r. o., Farská 1342/50, 949 01 Nitra, Slovakia, Company ID: 56114044.