No accounts, ads, or tracking
Runbound does not create user accounts and does not use advertising, analytics, telemetry, social-login, or tracking SDKs. A player name saved in Settings is a local scoreboard label.
Information used for online multiplayer
When you deliberately create or join an online room, Runbound sends information to the Runbound online service:
- Your chosen display name.
- Room configuration, including room code, seat count, chase target, bot settings, game number, and connection status.
- Gameplay actions and the authoritative match state required to operate and restore the room.
- Event timestamps, request and seat identifiers, and a cryptographic hash of the temporary membership token. The database does not store the plaintext membership token.
Service providers
The service runs on Amazon Web Services Elastic Beanstalk at api.runbound.live. Online room records are stored in a Supabase-hosted PostgreSQL database. AWS and Supabase process this information as infrastructure service providers for Mayukha.
Hosting infrastructure may transiently process standard network information, such as an IP address, to establish and protect a connection. We do not use it for advertising, profiling, or analytics.
How online data is used
We use online data only to create and join private rooms, authenticate room members, synchronize matches, validate actions and timers, reconnect interrupted players, prevent stale or duplicate actions, and diagnose service failures. We do not sell this information or use it for advertising.
Retention
Operational online-room records are automatically deleted approximately six hours after room creation. Deleting a room also deletes its members, match snapshots, and accepted-action events. Infrastructure providers may retain limited security logs or backups for their documented recovery and security periods.
Offline and nearby play
Solo and pass-and-play matches remain on the device. Nearby multiplayer sends the chosen display name, room messages, and seat-specific game state directly between participating phones on the same Wi-Fi network or hotspot. Nearby traffic is encrypted and is not relayed through the online service or stored in Supabase.
Settings, a resumable match, local scorecards, and nearby recovery metadata can be stored on the device. Nearby guest tokens are protected with Android Keystore, and Android cloud and device-transfer backup are disabled for this data.
Security
Online traffic uses HTTPS and secure WebSockets. Nearby-room traffic is encrypted and authenticated. No storage or transmission method is completely risk-free, but access and retention are limited to operating the game.
Deletion and contact
Uninstalling Runbound removes local app data. Online-room records are automatically removed after approximately six hours.
For earlier deletion of an active online room or a privacy question, email support@runbound.live with the room code and approximate creation time. Never send a membership token, password, or authentication secret.
Children
Runbound is intended for audiences aged 13 and over and is not directed to children under 13.
Changes
We may update this policy when the game or its service providers change. The effective date identifies the latest version.
Effective date: 25 August 2026