Privacy policy

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.

iOS purchases and RevenueCat

Apple processes payments for optional weekly and monthly minute subscriptions and one-time minute packs. RevenueCat validates transactions and manages their subscription status. We send RevenueCat a pseudonymous customer identifier derived by our server, not your raw HearPair device identifier, name, email, audio, or conversation text. RevenueCat and Apple may process transaction identifiers, products, prices, purchase and renewal dates, expiry, refunds, store country, and technical connection information under their respective terms.

Our self-hosted database associates verified store transaction identifiers, product, production or sandbox environment, purchase and expiry dates, granted and remaining minutes, refunds, and purchase-event processing records with the pseudonymous device record. These records deliver minutes, prevent duplicate grants, handle restores and refunds, and are retained as needed for those purposes and applicable accounting or legal obligations. We do not receive your full payment-card information.

Subscriptions renew automatically until cancelled through Apple. Subscription minutes expire with their billing period; one-time credits do not expire. Subscriptions can be restored using the same Apple Account. A consumable credit balance is retained for the existing device identifier; Apple may not restore it on another device. Clearing conversation history does not cancel a subscription or remove purchase records. Contact tech@raketalabs.com for purchase-data questions.

Operational logs and device activity

We use our self-hosted Graylog service to diagnose faults and understand how HearPair is used. Operational records can include fixed screen names, control and settings actions, connection and microphone permission states, audio-route types, error codes and code locations, session and request identifiers, app and operating-system versions, timestamps and duration. The backend associates these records with the same pseudonymous device key used for the allowance, an installation identifier and the IP address observed when a request reaches our service. There is no named user account.

These records allow us to search the activity and error timeline of the same device. They do not contain microphone recordings, conversation text, history previews, device-assigned headphone names, payment-card data, API keys or access tokens. Clearing local conversation history does not remove operational records. Logs are kept in a dedicated index with an 80–90 day retention window. The app may temporarily queue up to 500 events on the device for up to seven days when delivery is unavailable; delivery is retried when possible. Contact tech@raketalabs.com for questions or access and deletion requests.

Mobile usage analytics

The mobile app uses Microsoft Clarity to help Raketa Labs understand usability and improve HearPair. It starts automatically across all screens, including conversation and history screens, and receives masked screen replays, taps and navigation interactions, pseudonymous SDK identifiers, and technical device and connection information, including information such as device model, operating system and IP address. We do not send HearPair quota identifiers, access tokens or conversation identifiers to Clarity.

Capture is paused while the app is in the background. Conversation and history screens remain included with masking. We configure strict text masking across the app. Microphone audio and conversation text are excluded from this analytics integration. Microsoft processes analytics under its applicable service terms and privacy statement, potentially outside your country. For questions about analytics data or deletion, contact tech@raketalabs.com.

We also use Google Analytics for Firebase in the mobile app to measure app opens, sessions, engagement and screen use. Google processes an app-instance identifier, fixed screen names, app version, device and operating system information, language, and approximate geography derived from connection information. We disable advertising ID and vendor ID collection, advertising storage, advertising personalization and ad user data. We do not send audio, conversation text, route parameters, HearPair quota identifiers, tokens or conversation identifiers to Firebase Analytics. Firebase may also automatically measure App Store purchase events, including the product, value, and currency. We do not add a separate purchase-analytics integration to RevenueCat. Google processes analytics under its applicable terms and privacy policy, potentially outside your country.

Store ratings and reviews

After a completed translation, HearPair may request an optional native App Store or Google Play review. To avoid repeated requests, our self-hosted database keeps the request time, app version, and completed session identifier with the existing pseudonymous device key. These records can remain through a normal reinstall; clearing local conversation history does not remove them.

Apple or Google handles any stars or review text you choose to submit under its own store terms and privacy practices. HearPair does not receive the submitted rating or text through this flow, and the store does not tell the app whether the prompt was shown or a review was submitted. You can dismiss the request without affecting your allowance.

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. A first-party hearpair-theme preference cookie stores your light, dark or system appearance choice for up to one year. It is not used for advertising or cross-site tracking. 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.