Privacy.

Your account

We use your email address, verification status, account ID and sign-in records to create and protect your account, keep you signed in, and connect you to your saved resident. If you choose email and password, the account service stores a password verifier rather than your readable password. We use your email for account verification, password recovery and responses to requests you send us.

Your sign-in email is not a public resident-profile field. Choose a resident name and profile details you are comfortable sharing.

When you choose Google

Google sign-in gives us a signed identity assertion. We use your Google account identifier, called sub, your email address and Google’s email-verification information to authenticate you. Where available, we also check the verified Google Workspace domain, called hd, to assess email authority and protect account linking or eligible account recovery.

We store the association between your KEKE account and Google identifier, your email and verification state. Short-lived verification records may also contain your Google identifier, email and Workspace domain while a sign-in or account-completion step is pending.

We do not import your Google real name or photo into your resident profile. You create your own KEKE identity. We do not request access to your Gmail messages, contacts, Drive files or calendar. Google ID, access and refresh tokens are not retained in your stored account record; KEKE uses its own necessary session credentials after sign-in.

We use Google account information for sign-in, account linking, eligible recovery and account security. The current world does not use it for advertising or data resale. Google handles its sign-in interface under Google’s Privacy Policy.

Your resident and shared spaces

We save the resident information you provide, including your chosen name, avatar customization, profile text, gender presentation and social links. We also save supported progress, inventory, home settings, friendships, blocks, invitations, permissions and room settings. Shared media selections can include a video or website URL.

Your resident profile and appearance can be shown to people you meet in a room and to accepted friends. Room membership, movement, gestures, chat, shared media and game actions are shared with the people admitted to that room as needed for the experience. Private apartments restrict entry, but their settings and operational information remain accessible to authorized operators.

Current room chat is relayed live and kept as recent messages in participating browsers; the game server does not maintain a durable chat-history feature. Other participants can still copy or record what they receive. Please avoid putting private information in a profile, chat message, media URL or shared screen.

Voice and screen sharing

Voice and screen sharing are optional. Microphone and screen access require browser permission. The world uses browser-to-browser connections, with a relay where available, to send the media to authorized participants. Connection setup can reveal network addresses, including an IP address, to the connection services or other participants.

The world does not include server recording of voice or shared screens. That does not prevent another participant from recording what they hear or see. You can mute, leave voice, stop sharing and use the browser’s permission controls. Choose carefully which tab, window or screen you share.

Cookies and information on your device

We use necessary cookies for your account session, game session and a signed random device identifier that helps limit repeated sign-in requests. The device identifier is a service-protection measure, not an advertising identity.

Your browser also stores local preferences and progress, such as your avatar look, home choices, found items and volume. A pending apartment invitation may be kept for the current browser session. Signing out ends the relevant account access; clearing this site’s browser data also removes locally saved preferences. Blocking necessary cookies or storage can prevent sign-in or saving from working.

Service operation and who receives information

Our hosting and network services, including OpenAI Sites, Cloudflare and the game server’s hosting and email-delivery infrastructure, process information needed to serve the world and send account emails. This can include network addresses, browser/request details and delivery metadata. Authorized operators use service measurements, security records and submitted reports to maintain the world, investigate problems and enforce room rules.

If you submit a problem report, we save your report text, resident ID and relevant context such as room, position, camera, reported frame rate and build. Common email and credential patterns are scrubbed, but this does not detect every piece of private information someone might type.

When a Google sign-in component, YouTube player or other external media is loaded, that provider receives the requests needed for its service and may apply its own cookies and privacy practices. Opening a social-profile link or external website takes you to that service. The KEKE world application does not currently add advertising trackers; external services have their own practices.

How long information stays

Saved accounts, resident data, relationships, room state, reports and operational history remain in the service until they are changed or removed. There is not currently one automatic deletion period for all of these records. Changing a profile does not necessarily erase earlier values held in operational history or backups.

Sessions and verification attempts have expiry limits. Account-email payloads are cleared from the application queue after a successful handoff or final failure, while delivery-state metadata may remain longer. Infrastructure logs and backups can have different retention from the live application. We do not promise that a deletion from the live service immediately removes every backup copy.

Your choices and requests

You can edit the available resident-profile fields, remove social links, manage friendships and blocks, sign out, and change microphone or screen-sharing permissions. You can also review or remove KEKE’s Google connection in your Google Account settings. Removing that connection does not by itself delete your KEKE account, saved resident or an already active KEKE session.

To request access, correction or deletion of your account and associated information, email kb@rundownmedia.com. We may need to verify that the request concerns your account. We will explain any information that must be retained for security, an unresolved dispute or an applicable obligation, and any limits involving backups or information already shared with other participants.

Changes to this notice

We will update this page as the world changes. If a new feature materially changes how your information is used or shared, we will provide an appropriate notice and request any additional permission needed before that use.