Conversation Bridge
Privacy Policy

At a glance

• While listening, the app sends microphone audio directly to OpenAI to transcribe speech.
• Conversation text is sent to OpenAI for translation, suggested replies, and spoken responses.
• Your OpenAI API key is stored encrypted on your phone and used to authenticate with OpenAI. It is not sent to Code & Host.
• Code & Host stores registration and activation information, but does not receive your conversation audio or text through the app.
• The Android app does not include advertising or analytics SDKs. The separate registration website may display Google advertisements.

Microphone and conversation information

After you grant microphone permission and start listening, audio is transmitted to OpenAI. Transcripts, typed messages, language choices, and recent conversation context are sent to OpenAI to translate speech, suggest replies, and generate voice audio. This information may include personal details spoken by you or another person.

Let other participants know that their speech will be processed by AI before starting. Listening pauses while the app speaks a reply and stops when you pause it, leave the app, or lock the phone. The app is designed for face-to-face conversations, not telephone-call recording.

Conversation history and replay audio are held in memory, not intentionally saved as transcript or audio files on the phone. They may remain visible when you return to an app still running in memory. Use Clear to remove the current conversation and cached reply. Ending the app process also removes this in-memory session.

Your OpenAI key and data on your phone

Your API key is encrypted using Android Keystore-backed protection in the app's private storage. It is sent to OpenAI for authentication. The app also saves an activation flag, a randomly generated installation identifier, and a preference recording whether the introduction has been shown. Android app backup is disabled.

The file picker reads only the key or activation file you choose; the app does not request access to your entire file library. Copies you put in Downloads remain there until you delete them. Protect those files and delete them when no longer needed.

Use Settings → Remove key to delete the app's stored OpenAI key. Clear the app's storage in Android settings or uninstall it to remove its saved local data. This does not revoke the key at OpenAI or delete server registration records. You can revoke a key in your OpenAI account. Reinstalling or clearing app storage requires a new activation.

Registration and one-time activation

The registration website collects your name and, if you choose to provide it, your phone number. It stores these with a registration identifier, registration time, and a cryptographic hash of the activation key. On activation, the app sends the activation key and its random installation identifier to Code & Host. The service stores the installation identifier and redemption time to enforce one-time use and allow retries from the same installation.

These records support registration, activation, troubleshooting, and prevention of activation-key reuse. There is no recurring activation check after successful activation. The current service does not automatically expire registration records; they remain until manually removed, including in response to a verified deletion request.

The service runs on infrastructure hosted through Amazon Web Services. Web servers may record technical request details such as IP address, requested path, time, browser information, and response status for operations, security, and download statistics. The activation application does not intentionally log request bodies, activation keys, or SQL credentials. Server log retention depends on the hosting configuration; contact us with questions about a particular request.

OpenAI processing

You use your own OpenAI API account. OpenAI processes submitted audio and text and receives technical connection information to provide its services. The app requests that text-generation responses not be saved as response objects, but this does not guarantee that OpenAI retains no data. OpenAI may retain abuse-monitoring logs or other data under its policies and your account settings.

See OpenAI's API data controls for current processing and retention details. Requests about data held in your OpenAI account should also be directed to OpenAI. API usage is billed by OpenAI separately from this free app.

Website advertising and external services

The separate registration website includes Google AdSense code. When you visit it in a browser, Google and its advertising partners may use cookies or similar technologies and receive information such as your IP address and browser details to provide, measure, and protect advertising services. This advertising code is not included in the Android conversation screen or this privacy page.

Read how Google uses information from sites that use its services. Browser privacy controls and any consent choices offered by the website apply to website advertising. Code & Host does not send the app's conversations or OpenAI API key to advertising services.

Request access, correction, or deletion

Email contact@code-and-host.com with the subject Conversation Bridge privacy request. Include your registration name and enough information to locate your record, such as the approximate registration date or the phone number you supplied. Do not send your OpenAI API key, activation-key file, or conversation recordings.

You may request access to, correction of, or deletion of your registration information. We may ask for limited additional information to verify the request before acting. Local app data and data held by OpenAI are handled separately as explained above. Deleting a registration record does not remotely erase data from an already activated phone.

Security and policy updates

The app uses encrypted HTTPS connections for its API requests and encrypted storage for the OpenAI key. No storage or transmission method can guarantee complete security. The app does not request access to contacts, camera, precise location, or telephone-call logs.

We will update this page when the described practices change and revise the date above. Contact contact@code-and-host.com with questions.