1. Controller and scope

The person responsible for the game is Jesús Enrique Moncada Jimenez, operating under the Moncada Studio Solutions brand. This policy applies to Between Kilometers - Together (Between Kilometers), also called Entre Kilómetros, with Android package identifier solutions.moncada.betweenkilometers.

It describes the Android application and its shared-room services. It also explains how saving data differs in the web version. The game does not require you to create an account with an email address and password: rooms use a nickname and session identifiers.

2. Information we use

Preferences and progress on Android

We store your language, graphics settings, chosen nickname, saved journey, distance traveled, discoveries, radio passport history, and photos taken inside the game on your device. These let us remember your preferences and continue your experience. The Android journal does not automatically synchronize with the web journal.

Rooms and social features

When you create or join a room, the service receives your nickname, participant and session identifiers, room code and name, seats, presence, journey settings, and actions needed to synchronize the game. If you use chat, reactions, questions, social games, or shared music, we also process your messages, answers, votes, reactions, song or video requests, and music permissions.

Participants can see the information shared within their room. Public rooms display their title, availability, and general journey information to people browsing rooms. A private invitation lets anyone with the code join if a seat is available; avoid publishing that code if you want to keep the group private.

Connection and security data

Connections to online services allow the server and its technical providers to receive your IP address and request metadata, such as the date, requested path, and technical client information. These are used to deliver the service, maintain sessions, detect errors, and limit abuse. For certain request limits, the game uses identifiers derived from the IP address through a hash function; this does not mean that the network infrastructure stops receiving the original IP address.

Web version journal

If you play in a browser, saved virtual photos, their discoveries, progress, and station visits may be stored on the server under a browser identifier. Photos are not automatically published in rooms. This web storage is separate from Android's local storage.

Permissions and purchases

The game uses the Internet for online features and requests microphone access so you can speak. It does not request access to GPS location, contacts, SMS, or the physical camera. The in-game camera captures the virtual world. When you save or share a photo, you use Android's picker or the applications you choose; those applications receive the file you share.

If you buy the game on Google Play, Google handles payment and billing information under its own terms. The game does not request or receive your full payment card number.

3. Microphone and voice chat

The room may enable incoming voice so you can hear other participants without turning on your microphone. Listening does not authorize capturing your voice. To transmit it, you must turn on the microphone and grant the relevant permission. You can mute it, turn it off, or revoke permission in Android settings.

Audio is transmitted in real time using WebRTC with encryption in transit. The game does not include a feature to record or store voice conversations. Participants receiving the audio may, however, record it using external means; we cannot control those actions.

Voice connections may be direct between participants using Google's STUN servers, or may use a TURN relay when the service is configured for it. The relay provider processes connection metadata to transmit the encrypted audio. The connection service receives network information, and a direct connection may reveal your IP address to other participants' devices, even if you are only listening. Technical messages used to establish the connection are temporarily handled on the game's server.

4. External services and recipients

We do not sell your data or integrate AdMob or another advertising system of our own in this version. Online features involve these services and recipients:

• Game infrastructure: hosting through Sites and Cloudflare services allows us to deliver the website, manage rooms, and store the online data described here. These providers process requests and technical data needed to operate the service. See the policies of OpenAI and Cloudflare.
• Other participants: they receive your messages, shared actions, and, when you enable it, your audio, to make the social journey possible.
• YouTube / Google: the official player loads after you enable YouTube through the in-game notice. Google may process IP addresses, device data, playback information, cookies, and other identifiers, and show ads. Requested videos are shared with the room and become part of its state. The game does not request your Google credentials. See the Google Privacy Policy and YouTube Terms of Service.
• Internet radio: when you play a station, your device connects to its servers, which receive your IP address and technical playback data. Each station may include advertising and apply its own privacy practices. The catalog uses Radio Browser. Music bundled locally with the application does not need to connect to an external station.
• Sharing applications: they receive a photo only when you choose to share it with them.

We may also disclose information when necessary to comply with a valid legal obligation or protect the safety of the service and individuals. Infrastructure and content services may process information outside your country.

5. Cookies and device storage

We use local storage for preferences and progress, session storage for journey access, and functional cookies to recognize visitors and protect online features. The visitor cookie is configured to last up to 30 days; the web journal cookie, up to one year. Their duration is not the same as the retention period for data on the server.

Enabled external services, such as YouTube, may use their own cookies or identifiers. This HTML page does not include analytics, advertising, players, or forms that submit information; its hosting server may log the requests needed to serve it.

6. Data retention

• Local Android data: it remains until you delete it using the available options, clear the application's storage, or uninstall it. Images exported outside the application remain where you saved them.
• Rooms: closing a room deletes its state and associated records from the active service. Rooms with no active participants are deleted through checks performed when the service is accessed. Leaving a room that remains active does not immediately delete your earlier messages.
• Messages, votes, and answers: records older than 24 hours are deleted during cleanup tasks triggered when rooms are created or joined. Technical voice signals are cleaned up after five minutes and reactions after one minute, using the same mechanism. These are cleanup thresholds, not guarantees of deletion at an exact time: if no activity triggers cleanup, records may remain longer.
• Web journal: photos are retained until deleted or replaced. Web progress and collections currently have no automatic expiration configured. Clearing cookies does not delete those records from the server and may cause you to lose access to them.
• Technical logs and infrastructure copies: retention depends on the provider's configuration and practices. Deleting a record from the active service does not guarantee immediate deletion of a technical copy. Retention required by a legal obligation is limited to that purpose.

7. Your choices and deletion requests

1. Microphone: use the in-game microphone button or revoke permission in Android Settings → Apps → Entre Kilómetros → Permissions. Labels may vary by phone.
2. Local data: delete photos from the journal. To erase all local saved data, use Android Settings → Apps → Entre Kilómetros → Storage → Clear data. First export anything you want to keep.
3. Rooms: you can leave a room; its host can close it. Closing the room deletes its associated data from the active service, but not copies made by other people.
4. Web data: delete photos from the journal. To request deletion of other data stored on the server, use the privacy contact below. Submit your request before clearing cookies if you need to identify your journal.

You may request information about your data, access, correction, or deletion, and exercise other rights provided by applicable law. To locate the records, state that your request concerns Between Kilometers / Entre Kilómetros and include the platform, nickname, approximate date, and room code, if known. Do not send passwords, cookies, or session tokens. We may ask for minimal additional information to verify that the request concerns your data. If we cannot identify the records, we will explain that limitation.

There is no registered email-and-password account that you need to close to stop playing. This does not prevent you from requesting deletion of online information we can identify.

8. Security and social features

Communication with the game's API uses HTTPS, and voice uses WebRTC encryption. We apply access controls to rooms and photos, request validation, and usage limits. No system offers an absolute guarantee of security.

Avoid sharing sensitive information in nicknames, room names, chats, answers, or voice conversations. Social features allow communication with other people. If you are a parent or guardian and believe a minor has submitted personal information that should be deleted, contact us so we can review the request and locate the available data. We do not request a date of birth as part of the game.

9. Changes to this policy

We will update this page when features or information handling change. The date at the top identifies the latest revision. When a change requires additional notice or consent, it will be requested before the corresponding new use begins.

10. Privacy contact