Brayo’s ride through Nairobi

Privacy & your choices

Optional analytics and ads start off. You can play without enabling either.

Updated 19 October 2026. Operator: Julius Kinuthia, OYAA. Public support contact: juliusknth@gmail.com.

Your browser preferences

Ads remain off during setup. These choices do not enable personalised ads or replace Google’s regional consent message. Refusals in that message are also honoured.

What is stored locally

The first time you play, OYAA asks your age; only the age group (under 13, 13–17 or 18+) is kept, on this device, and it is never sent anywhere. For riders under 13, optional analytics, ads, reminders, voice chat and Google sign-in stay off. Your game progress, upgrades, best rides, ghost replay, rider identifier, sound settings and privacy choices use this browser’s local storage. This storage supports game features. Clearing site data removes local progress and choices.

Guest profiles, Google and friends

Every device starts with a generated rider nickname and public OYAA ID. You can choose a validated username in Settings; it appears on leaderboards and to other riders. Use a nickname rather than your real name or contact details. Your Crew stores up to 50 friends’ IDs and nicknames. Share links and private-room invitations are copied for you to send. If your friend has turned on reminders, INVITE also sends them a fixed race-invite notification with your rider nickname and the course. Race invitation messages are fixed. Optional Google sign-in links the guest to your account and restores nickname and friends on another device. Firebase Authentication handles Google account information; OYAA does not publish your Google email, account name or Auth UID. Private profile records in Firestore are accessible only to their signed-in owner. Coins, gear and riding progress remain local to this device.

Online features

Online races send race state and your chosen rider name to the multiplayer service and other racers. Casual leaderboards send your public OYAA ID, rider nickname and scores to Firebase under an anonymous sign-in ID (one entry per rider); these records are public. Race times are personal on this device; authoritative standings are shared inside the race room. Avoid real names or private details in your rider name. Network providers receive connection information such as IP addresses; Firebase Hosting serves the site. Optional ads are not required for these features.

Feedback you choose to send

The Feedback button in the game menu sends your message, category, Firebase account identifier, game version and submission timestamp to private Cloud Firestore records. Guests use an anonymous Firebase account; Google-linked players use their existing account. Feedback is visible to authorised OYAA project administrators, not other players. Your account can retrieve its own submission receipt. Messages are used to investigate bugs and consider improvements, independently of optional analytics; feedback text is never sent to Analytics. Please leave out real names, contact details, passwords and payment information. Feedback remains in Firestore until removed by OYAA; there is no automatic retention deadline. To request deletion, contact support with the reference shown after sending.

Reminders (optional)

Reminders start off. If you turn them on in Settings and your browser allows notifications, OYAA stores a push token from Firebase Cloud Messaging with an anonymous sign-in ID, your rider nickname and OYAA ID, when you last rode, whether your tank was low and which reminders you want. OYAA then sends at most one ride or fuel reminder every two days, in the late afternoon, never on a day you have already played, and stops after two weeks without play. Crew race invites arrive only from riders in a private room. Turn reminders off in Settings to delete this record, or block notifications in your browser. Children should ask a parent or guardian before turning reminders on.

Voice chat with your crew (optional, 13+)

Voice chat is only offered to riders who answered 13 or older, only in private race rooms, and it starts off every time. When you switch it on, your browser asks for the microphone. The race server then checks that you and the other rider have each other in Your Crew and only then passes on the connection details; it never carries, records or stores the audio. Talk travels directly between the two phones (or, on networks that block that, through an encrypted relay that does not keep it). Your crew list is used for that check only while the room is open. Mute your microphone or any rider at any time, and switch voice off to disconnect. Under-13 riders cannot use voice chat.

Optional analytics

Only if you opt in, Firebase/Google Analytics receives gameplay events, such as ride mode, route, time, score and permitted ad outcomes. It may also process browser/device information and identifiers. OYAA disables Google signals and ad personalisation. It does not send precise GPS position or player-entered free text to analytics. You can withdraw consent above; withdrawal stops new collection, but does not erase previously collected provider data.

Advertising and children

Live Google ads are currently disabled. Before activation, OYAA uses child-directed ad treatment and requests non-personalised ads. Optional contextual ads may still involve provider storage or identifiers; non-personalised does not mean data-free. Google’s certified consent messaging must be configured for applicable regions before activation. If your regional consent state is unknown or refused, OYAA does not request live ads. Children should ask a parent or guardian before changing optional choices.

Roadside sponsor artwork is served with the game and does not use third-party ad tracking. Sponsor links open an external site only when selected from a menu or this website. External sites have their own policies.

Privacy requests

Contact OYAA for questions, access or deletion requests: juliusknth@gmail.com. Include the minimum information needed to locate your game record; never send passwords or verification codes. Provider retention and processing are also described in Google’s privacy policy and Firebase privacy information.