This policy covers the Rubileap studio website (rubileap.com) and all the browser games hosted at play.rubileap.com, which are listed on the Games page.
Game saves and your preferences
The browser games save progress and settings on your device using localStorage. Depending on the game, this includes completed levels, scores, your current puzzle, in-game items and cosmetic choices, audio settings and reduced-motion preferences. These standalone games do not upload those saves to a Rubileap account or sync them across devices.
The browser games do not show ads or load an advertising service. Where a game offers a “Watch ad” button, the web version gives the in-game reward straight away without showing an ad.
If you choose an appearance on either website, that site saves your choice in localStorage. On the studio website you can choose Dark, Light or System; without a saved choice it uses its dark appearance. In the games on play.rubileap.com, choosing System removes the saved appearance choice and follows your device setting. Each website stores its preference separately.
The studio website is available in English and Ukrainian. If you choose a language with the language switch, the site stores your choice in a cookie named lang (value en or uk) for one year. This cookie is strictly necessary to show the site in the language you chose; it is not used for analytics or advertising and is not shared. Without it, visitors whose connection Cloudflare locates in Ukraine are shown the Ukrainian version, and other visitors the English version. For this, the site uses only the country that Cloudflare derives from the request and does not store it.
You can remove local saves and preferences, including the language cookie, by clearing the relevant site’s data in your browser. Clearing data for play.rubileap.com can remove progress from all games hosted there. Browser restrictions, private browsing or clearing site data can prevent saves from persisting. Apart from the language cookie, our site and game code does not use cookies, sessionStorage or IndexedDB for these features.
Camera games and online duels
Camera games ask for permission before using your camera. Video frames, face landmarks and raw tracking measurements are processed on your device and are not uploaded. The tracker and its model load from the game itself. Your calibration and camera-related settings are saved locally; you can remove them by clearing the game site’s data.
An online duel sends a compact representation of expressions and head movement, a chosen character and a nickname made from predefined words to our Cloudflare duel service and your opponent. It does not send camera video or an image of your face. The browser stores a random identity and signed token in localStorage under rubileap.identity.v1 to reconnect and join rooms. There is no account, and we do not collect your date of birth; the age choice stays on your device.
The service temporarily stores room participants’ random identities, nickname choices and match state, including scores. Friend rooms expire ten minutes after fewer than two players remain; empty quick-match rooms expire within thirty seconds, and a quick room is removed when both players leave. Incompatible rooms retained during an upgrade are removed within ten minutes of detection. Finished-round statistics contain only aggregate gameplay details, without player identities, nicknames, room codes or expression samples. Optional analytics opt-outs do not stop the network messages needed to play an online duel or these server-side operational totals.
Hosting and analytics
Both websites are hosted through Cloudflare Pages. Cloudflare processes technical request information, such as IP addresses, browser information and requested URLs, to deliver and protect the sites. See Cloudflare’s privacy policy for its handling of this information.
The studio website and the game pages on play.rubileap.com use Cloudflare Web Analytics to measure visits and page performance. The service sends page and referring-page information and performance measurements to Cloudflare. According to Cloudflare’s documentation, its analytics beacon does not use cookies or browser storage, and the analytics service discards the source IP address at the nearest Cloudflare data center rather than storing it in its core databases or logs. This describes analytics processing, separately from hosting and security.
Apart from the language cookie, no cookies were observed during our checks of either website; this is not a guarantee about every hosting or security response.
Anonymous statistics
To learn what visitors find interesting, the studio website records a few anonymous events: how long people stay (in total and with the tab in sight), page views, Play button clicks, switches between English and Ukrainian, external links followed, gameplay previews watched and press kit downloads. They carry only broad details that many people share: the site language, whether the device is a phone, tablet or computer, the browser family and a range of window widths. If the website’s own code fails, we get a report with the same broad details plus the error type and message, a technical stack trace and the version number.
The standalone games on play.rubileap.com send the same kind of anonymous statistics: sessions, screens opened, buttons pressed, level progress, the language chosen and whether this browser has played the game before (read from its saved progress). If a game fails, it also reports the crash: the error message, a technical stack trace, the game version, the device type and the browser family. Our games on YouTube Playables send us nothing.
These statistics use no cookies or browser storage and no identifier that outlasts a visit: each one gets a random session ID that exists only in the page’s memory. They go to our own service on Cloudflare (Workers Analytics Engine), which does not store IP addresses, only the country Cloudflare derives from the request, and deletes the data after three months. We look at totals only. If your browser sends Global Privacy Control or Do Not Track, nothing is sent.
If you email us
If you contact hello@rubileap.com, press@rubileap.com or support@rubileap.com, we receive your email address and the information you choose to share. We use it to respond and manage the conversation. Cloudflare Email Routing forwards messages sent to these addresses, which is covered by Cloudflare’s privacy policy. Email is then handled through Gmail and is subject to Google’s privacy policy. Please avoid sending sensitive information.
External websites and platforms
Links to YouTube and other external services lead to sites covered by their own privacy policies. This policy describes the public browser versions of our games. A game running within YouTube Playables uses YouTube’s platform services, including its save system, and is subject to Google’s privacy policy. This does not mean that every game shown here is published on YouTube.
Questions and changes
Contact hello@rubileap.com with privacy questions or to request deletion of correspondence you have sent us. Local saves can be cleared in your browser’s site-data settings. We will update this page when the practices it describes change.