Privacy notice

Who operates the site

HeyloBuddy is an independent game website operated by Amruth at heylobuddy.com. This notice covers the website and installable web experience, including optional accounts, multiplayer rooms, and chat features when enabled.

For privacy questions or requests about your information, email heylobuddy7@gmail.com. The Contact page also explains how to report a game problem or content concern.

Information used to run games

Online games store room codes, player display names, game state, scores, and player-session identifiers so the server can coordinate turns and reconnect the right player. Content you enter into a shared game, such as quiz questions, category answers, drawings, or room messages, is available to the relevant participants.

Use a nickname and share room invites only with people you want to join. Room codes provide access to games; they should not be treated as a secure place for confidential information. Some games allow voluntary public leaderboard submissions, including a display name and result.

Optional accounts and messages

Signing in uses an email address or a supported Google sign-in flow. The sign-in provider is Supabase. HeyloBuddy stores an account identifier, profile display name, and saved Quizzly history. Authentication cookies maintain the signed-in session.

Buddy chat, when enabled, stores messages, buddy relationships, and game invitations. Messages are shared with their participants. Account deletion controls remove the profile and saved history; results already shared in active quiz rooms may remain available until those rooms expire.

Support correspondence

When you email HeyloBuddy, we receive your email address and the information you choose to send. The support inbox uses Gmail, provided by Google. This correspondence is used to respond to your request, investigate problems, and handle related follow-ups. Please do not include passwords, sign-in codes, or unnecessary sensitive information.

For a request about your account or information, we may need to verify that the request comes from the appropriate person. Email heylobuddy7@gmail.com to ask about support correspondence or other records held by HeyloBuddy.

What stays in your browser

Games use browser storage for settings, sound preferences, saved room identities, local best scores, and game progress. The 100 mobile web app caches its files for offline solo play after the first load. These local records do not automatically sync across browsers or devices.

You can remove local records through your browser’s site-data controls. Doing so may sign you out, remove progress, and prevent you from resuming a room as the same player. Clearing local data does not by itself delete records already held on the game server.

Voice chat

The 100 offers optional microphone-based room audio. Microphone access starts only after you enable it and grant browser permission. Audio is exchanged through browser peer connections. Connection-signaling information passes through the game service, and a Google STUN service helps establish those connections. Other participants may receive connection information such as an IP address as part of establishing peer communication.

The game does not implement server-side audio recording. Other participants or their devices may still record what they hear. Use the microphone control or browser permission settings to stop sharing audio.

Service providers and technical requests

Cloudflare hosts the site and multiplayer data. Like other hosting services, it processes technical request information such as IP addresses to deliver and protect the service. Supabase supports optional authentication. Some pages request fonts from Google Fonts, which receives the network information needed to deliver those fonts.

PostHog is used by the server to evaluate game and chat availability flags using a shared site identifier. The site’s current code does not load a PostHog browser analytics or session-replay SDK. Provider processing is also governed by their own privacy notices: Cloudflare, Supabase, PostHog, and Google.

Advertising

The current release does not load the Google advertising script. A publisher verification tag and ads.txt entry identify the site's AdSense account without themselves serving ads.

If Google advertising is enabled in a future release, Google and other advertising vendors may place and read cookies, use web beacons, and process IP addresses, device identifiers, and information about visits or ad interactions to deliver and measure advertising. Cookies may also be used to serve ads based on earlier visits to this or other websites. Google’s advertising cookies allow it and its partners to personalize advertising across sites. You can manage personalized advertising through Google My Ad Center and learn about participating vendors’ choices at AboutAds. Read How Google uses information from sites or apps that use its services for details. Advertising and consent settings must be configured before that release begins serving ads.

How long information remains

Most multiplayer rooms stop accepting access after 24 hours. Access expiry does not necessarily mean that the underlying stored record is immediately erased. Persistent features, such as account history and submitted leaderboard entries, can remain until removed. Local browser records remain until the browser removes them or you clear site data.

Use Your account to view account history, sign out, edit your display name, or delete the account. Game guides identify which progress is stored locally and which results are shared. Do not put sensitive personal information into game answers, names, drawings, or chat.

Changes to this notice

This page will be updated when the site's data features change. The date above identifies the current notice. For practical help with accounts and local storage, see Help.