koloBETA

KOLO · WEBSITE AND BETA APP · VERSION BETA-2026-09-24

Privacy Notice.

Last updated September 24, 2026

This notice covers the Kolo website and beta services. Builds are being updated; email recovery and chat are described below as features that apply when enabled. Publishing this notice does not open public downloads or automatically record account consent.

1. Information Kolo uses

Accounts. Kolo processes login names and passwords for authentication, and stores salted password hashes, account identifiers, and session information. When email features are enabled, it stores an email address, verification status, and short-lived verification or reset-token records. Policy acceptance may record the terms/privacy version, an eligibility declaration, and a timestamp. The current age declaration does not require a full birth date.

Characters and saves. The service stores character names, identifiers, chosen regions, synchronized game saves, and trade or transfer recovery records. Saves can include trainer and Pokémon names, party and PC contents, money, items, badges, and story progress. These records allow continued gameplay and help prevent an interrupted transaction being executed twice.

Online play. Kolo processes game-map coordinates, appearance and follower descriptors, and party/trade summaries needed for multiplayer. Game-map positions are in-game coordinates, not GPS locations.

Read-aloud. When online reading is enabled, detected game dialogue is sent to Kolo’s speech service to generate audio. Dialogue can contain player-chosen names. Returned audio may be cached on the device. This online feature is not entirely on-device processing.

Chat, when enabled. Kolo processes the message text, channel, sending character, game-map context, message identifier, and time to deliver messages. Chat is not end-to-end encrypted; service operators can access systems that process it.

Technical and support information. Servers and hosting services process network addresses, request information, and operational logs. Support messages may include email addresses, device/build details, screenshots, and anything else you choose to send. Do not send passwords, authentication tokens, or ROMs to support.

2. What other players can see

Online players may see your public character name, ghost appearance, follower, and information shown in interaction and trading screens. Regional activity screens can show player counts and character rankings based on accepted saves, including species caught/seen and badge counts where supported. These rankings are not lifetime capture counts and do not expose raw saves or account credentials.

Local chat reaches players in the same map and supported nearby connected maps; a message may appear in their chat box and above your visible character. Global chat appears in the chat box across the online service. Recipients can copy, screenshot, or otherwise retain messages. Do not put personal or confidential information in chat or public character names.

3. ROMs, artwork, and device storage

You supply your own game ROMs. The normal import and multiplayer flows do not upload those ROMs to the game server. Online saving uploads save data, which is different from the ROM.

The app keeps imported ROMs in its local storage. When FireRed USA 1.0 is imported or you choose to create Liquid Crystal, the app applies its included patch locally and stores a separate generated Liquid Crystal game file. The original FireRed and saves are preserved; neither ROM is uploaded by this operation. Supported builds read follower artwork from your imported SoulSilver ROM for use with supported games. Updated builds generate this artwork in memory and do not retain the generated follower pack on disk; older builds may have a cache that is removed by the update. Local saves, recovery journals, preferences, and protected credentials may also remain on the device. Uninstalling can remove local data.

Separately authorized development backups are not part of routine multiplayer uploads. We do not require your Apple Account password to operate Kolo.

4. Why information is used

We use information to authenticate accounts, deliver multiplayer and requested speech/chat features, maintain save and trade continuity, prevent abuse, troubleshoot faults, answer support requests, and operate and protect the service.

The beta is free. Kolo does not add advertising or analytics scripts to this website, does not sell personal information, and does not use it for targeted advertising. This website currently has no account-registration form.

5. Hosting, email, and disclosures

This website uses OpenAI Sites hosting and Cloudflare infrastructure. Our hosting and network providers process requests to deliver and secure the website and game services. Support email is handled through Zoho Mail; enabled account email delivery uses the configured email provider. Authorized Kolo operators may access records needed to run the service or investigate reports.

We may disclose information when reasonably necessary to comply with applicable law, respond to lawful requests, address security incidents or abuse, or protect people’s rights and safety. We do not use this as permission for unrelated marketing.

Apple, Android, AltStore, and other installation or platform services have their own practices and policies. Information you provide directly to those services is governed by their policies. Infrastructure providers may process information outside your state or country.

6. Retention during the beta

Accounts, accepted saves, save history, and transaction/recovery records are retained to maintain characters, recover interrupted operations, and investigate faults or abuse. The beta does not yet apply a fixed automatic deletion schedule to all of these records. Historical test backups can remain after live data changes. Support correspondence is retained for handling requests and follow-up; it is not automatically erased when an account stops playing.

The new chat service does not write a persistent server chat-history archive. It retains bounded, temporary delivery and retry information in memory; the app keeps a bounded session chat history. Copies included in support reports or retained by recipients are separate. Older builds without chat do not collect chat messages.

Operational logs and hosting records follow the applicable server or provider retention settings. Deletion from active systems does not imply immediate erasure from every backup. A deletion request may require keeping limited records for security, legal obligations, or unresolved transactions; we will explain applicable limitations when handling the request.

7. Your choices and requests

Contact support@koloemulator.com to request access, correction, or deletion, or to report a privacy concern. We need to verify account ownership before releasing or changing account information; we will not ask you to send your password. There is currently no self-service account-deletion screen.

Verified-email recovery applies only when enabled and after the email address is verified. Until then, do not assume an email password reset is available. You can choose not to use optional reading or chat features, avoid including personal information in public names/messages, and stop using the beta.

8. Age and security

The US beta is intended for people age 13 or older; minors need parent or guardian permission. It is not offered to children under 13. Contact support if you believe a child under 13 has provided personal information so we can investigate and take appropriate action.

Kolo uses TLS, authentication, password hashing, and protected credential storage to reduce risks. No system can guarantee complete security. Never include passwords or tokens in public bug reports.

9. Updates and contact

We will update this notice when practices change and identify the revision date and version. Material changes may require a renewed in-app acknowledgment. Kolo is the operating brand; support and privacy requests go to support@koloemulator.com.