Privacy, in plain words.

Who we are

HearPair is provided by Raketa Labs. For privacy questions, support, or requests about your information, contact tech@raketalabs.com. This policy covers the HearPair mobile app and this website.

Live audio and OpenAI

When you start a live conversation, the headphone and phone microphones send speech to separate OpenAI translation sessions. OpenAI processes that speech to return translated audio and text. The selected languages, technical connection information, and a pseudonymous safety identifier are also processed to provide and protect the service.

HearPair does not create audio recording files or store a centralized audio or transcript history. Audio leaves your device for online processing. Our model sessions request that session storage be disabled; this does not mean all provider security, abuse-monitoring, legal, or operational retention is zero. OpenAI processes data under the applicable API service terms and data controls.

Speech may include personal information that you or the other participant choose to say. Make sure the other person understands that online translation is being used.

Written history on your device

When saving is enabled, source and translated text, languages, conversation time, and duration are stored in application files on your device. The interface and sharing view show translated text. HearPair does not upload your saved conversation history to a central history service or synchronize it between devices.

You can turn off saving for new conversations in Settings. This does not delete older records. Delete one conversation from History, or use Settings → Clear history to remove saved conversations. If you share translated text, it is sent to the app or recipient you choose and is also subject to that destination’s practices.

Language, appearance, guide completion, and other preferences are stored on the device. The iOS app excludes its conversation-history directory from system backup; Android app backup is disabled.

Device identifier and free allowance

No name, email, or account is needed to use HearPair. To enforce the one-time allowance, the iOS app uses an app-specific random identifier held in Keychain. The Android implementation uses the system-provided app-scoped device identifier. The value is sent to our backend, which stores a key derived through a one-way keyed transformation rather than the raw identifier in its database.

This is pseudonymous information: it does not contain your name, but it can connect usage to the same device. It is intended to preserve the allowance through a normal reinstall. Clearing local history or uninstalling the app does not erase the server usage record or renew the allowance.

Our self-hosted Supabase database stores this device key, platform, total and remaining allowance, session identifiers and states, timestamps, time used, and provider session identifiers needed to close interrupted sessions. These records manage the allowance, coordinate sessions, and protect the service from misuse. Audio and conversation text are not written to those quota tables.

Connection information and permissions

Network services process connection information such as IP addresses to establish connections, deliver requests, and enforce rate limits. Service requests also include the app version and platform. The app reads public version, maintenance, and announcement settings from our service.

The HearPair application backend has request-content logging disabled and does not log audio, transcripts, API keys, or access tokens. Hosting, network infrastructure, and service providers may process technical connection and security information as part of providing the service.

Microphone access captures speech. Bluetooth access supports compatible headphone discovery and audio routing. You can change these permissions in your phone’s settings; live translation needs the required access. We do not use advertising identifiers or advertising tracking in this version.

Retention and your choices

Local written records remain on your device until you delete them through the app or remove the application data. Server device and allowance records are kept for as long as they are needed to enforce the one-time allowance, manage and resolve session closure, protect the service, and meet applicable obligations. Clearing local conversation history does not clear those server records.

Provider processing and retention are subject to the applicable service terms and account controls. The app’s session-storage setting is not a promise that all third-party processing is transient or that data is processed only in your country.

Contact tech@raketalabs.com with questions or requests about access, correction, or deletion. Because there is no account registered to a name or email, we may need to establish which device record your request concerns. Do not send API keys, access tokens, or private conversation content. We will explain what is needed and what we can do for your request, including any records that must be retained for a legitimate ongoing purpose.

Service providers and this website

OpenAI provides online speech translation. Operator-managed Supabase and hosting infrastructure provide device quota, session accounting, and public app configuration. These service providers may process information outside your country under their applicable service arrangements.

This website has no advertising, analytics integration, contact form, or tracking cookies. Contact links open your email app. If you email us, we receive the address and information you choose to include and use them to respond and handle the request. Hosting services may process technical connection information when you visit.

If our data practices change, we will update this page and the date above.