PLAY FREE

PRIVACY · PLAIN LANGUAGE

Your voice controls the game.
It does not become a recording.

Talk to Tower never stores or retains your microphone audio. A push-to-talk clip may be processed transiently to turn speech into text, then it is discarded after the response.

Effective 23 July 2026 · Public beta
MICROPHONE PROMISE

No saved audio. No voice library. No audio training by Talk to Tower.

The microphone is used only when you deliberately transmit. Talk to Tower does not write the audio to a file, attach it to your account, place it in Supabase, or keep it in application logs.

01

Microphone audio

Before the operating system asks for microphone permission, the game shows a just-in-time notice. On the web, audio is captured in temporary memory only while push-to-talk is active and sent over HTTPS to the configured speech-recognition service. In the Android app, the device speech-recognition service may process the transmission.

Talk to Tower does not retain that audio after transcription and does not use microphone audio to train a model. You may decline microphone access and use keyboard controls.

02

Radio text and AI interpretation

The resulting transcript is text, not stored audio. It can appear in the current radio history, remain in the local saved session on your device, and be sent with the selected aircraft’s game state to the configured interpretation service when a natural-language command needs clarification.

Avoid saying personal or sensitive information over the game radio. ATC clearances should contain only callsigns and game instructions.

03

Guest play, accounts, and progress

You can play without entering a name or email. Guest progress is associated with a random anonymous account identifier and local device storage—not an IP address chosen by Talk to Tower. If you create an account, Supabase stores the email, profile, career progress, airport unlocks, and shift summaries needed for cross-device saves.

04

Product analytics and diagnostics

The game may store limited gameplay and technical events such as a session start, tutorial step, successful landing, separation event, device class, and performance timing. These measurements help diagnose failures and understand whether the game is playable. They are deliberately designed not to contain microphone audio or complete radio transcripts.

05

Services that process data

  • Vercel hosts the web app and server endpoints and may process standard connection and request logs.
  • Supabase provides anonymous/authenticated accounts, career saves, and aggregate gameplay analytics.
  • OpenRouter and model providers may process a short audio clip for transcription or radio text for interpretation when those cloud features are available.
  • Android speech services may process speech in the native Android build according to the device and recognizer configuration.

These services operate under their own terms. OpenRouter says prompt and response content is not logged by default, while request metadata is retained; its downstream model providers can have separate policies.

06

Retention and your choices

Microphone audio has no Talk to Tower retention period because Talk to Tower does not store it. Local progress and radio text remain until you reset the game or clear the app/site data. Cloud account and career records remain while the account is active or as needed to operate and secure the service.

You can play by keyboard, revoke microphone permission in the browser or device settings, reset career progress in the Career screen, or contact the creator about access or deletion through the public profile below.

07

Contact and changes

Talk to Tower is operated as an independent project by Arpan Jha. Questions, corrections, and privacy requests can begin through the linked creator profile or project issue tracker. A material policy change will update the effective date and the notice shown in the game.

This public beta is not directed to children under 13.