Your alert history is stored on your device. Online translation and nearby sharing require separate permission. Model preparation and SDK diagnostic data have their own network behavior described below.
This policy covers CodeClear, an Android app for reading, saving and translating emergency-alert messages, and its optional CodeClear translation service. The privacy contact is the CodeClear developer at gokirito12@gmail.com.
Alert collection and private device history
With your separate in-app consent and Android notification access, CodeClear filters messages from reviewed system emergency-alert receiver apps. Android notification access can make other notifications available to the listener, but CodeClear does not retain unrelated notifications. With separate accessibility consent, it reads the individual message field, title and pending count in reviewed system alert dialogs. It does not press buttons, dismiss system warnings or record screenshots. This accessibility service is not a disability assistance tool.
Local history contains alert originals and titles, source and collection timestamps, available alert-type evidence, collection observations and translations. Alert text can itself contain names, telephone numbers, addresses or other personal information. Identical originals are grouped, with their individual collection observations preserved. Settings and preparation state are also stored locally. CodeClear does not require an app account and does not read your SMS inbox, contacts, microphone or camera.
Records stay in the app’s private storage until you delete them. App backup and device-to-device app-data transfer are disabled. This is private app storage, not a claim that the entire database is separately encrypted. You can delete an individual original and its grouped translations/observations, clear history, or clear the app’s storage in Android settings. Turning collection off stops new collection; it does not delete existing history.
On-device translation and language models
ML Kit translates alert text on the device after you permit the required model preparation. Downloading models needs an internet connection. Google’s SDKs collect diagnostic and usage information, including device and app information, installation identifiers, performance and error events, and identified/configured languages. Local text translation does not mean that the SDK sends no network data. See Google’s ML Kit data disclosure and Google’s privacy policy.
If you enable compatible Android system translation, text is passed to the installed system translation service through Android’s on-device translation API. Availability and language preparation depend on that service. Its provider’s data practices also apply.
Optional online translation
Online engines in Labs are off until you separately enable and authorize the particular service. When you select an authorized online engine, new captured alerts and requested history or nearby-message translations can send the original and selected language information over HTTPS. CodeClear does not silently switch to an online engine. You can withdraw each permission to stop new requests; this cannot recall information already received by a provider.
MyMemory (Translated). MyMemory receives the original text, language pair and normal connection metadata, including your network IP address. Its terms state that submitted segments are retained long term and can be processed by translation partners to provide or improve their services. CodeClear’s anonymous integration does not request a MyMemory account or API key and does not provide an in-app deletion API for that provider. See MyMemory’s terms and privacy information.
CodeClear service and Groq. Configured builds offer a fixed service with separate, default-off sending permission. Updated builds automatically create a random installation identifier, protected with Android Keystore-backed encryption. No access code entry is required; older builds may use a separately supplied code. The service receives the original, target language and installation identifier or legacy credential, then forwards inference to Groq. Provider keys remain on the server. Enabled MyMemory takes priority; disabling it selects CodeClear only with existing service permission. Provider errors or quotas never trigger automatic fallback.
The service cache is private to its installation or legacy client, rather than a public translation archive. It stores the original, validated translation and issuer fields, model and prompt information, measured processing time, bounded usage metadata and creation/expiry information. Cache reuse avoids repeated provider requests. Results expire within 30 days of creation, without extending expiry on a cache hit. Body-free rate-limit and deletion-generation records serve abuse prevention and prevent stale requests from restoring cleared cache entries.
Hosting and network infrastructure process IP addresses and ordinary request metadata to deliver and secure the service. Operational logs and backup copies have retention separate from active translation-cache expiry. Cache expiry is not a guarantee that every infrastructure copy is physically erased at that time. Such records are used for service operation, security, abuse prevention and applicable legal obligations. Contact the privacy email for information about these copies or to request access or deletion; do not include private identifiers or access codes in your message.
Use the separate server-cache clear action before resetting the private connection, clearing app storage or uninstalling. It clears only that connection’s scope, including pending result leases. Turning sending off, deleting local history or resetting the connection does not erase existing server data. A new identity cannot clear the previous identity’s cache; old results expire within 30 days. New installations do not share cache scopes. Legacy devices using the same credential may share a scope. Contact the privacy email for help without sending identifiers, access codes or alert bodies. CodeClear cache deletion cannot recall copies already processed by Groq.
Groq says inference inputs/outputs are not retained by default, but reliability or abuse investigations can retain them for up to 30 days or longer if legally required. Usage metadata is retained separately. Account data controls can change these practices; CodeClear does not claim that Zero Data Retention is enabled. Groq describes retained customer data as stored in the United States. See Groq’s data-handling information.
Nearby sharing, notifications and speech
Optional Bluetooth sharing requires Labs consent and Android permissions. If you enable sending, nearby CodeClear users can receive freshly captured originals, titles and timestamps, with a temporary random occurrence identifier. These broadcasts are intended to be readable by nearby users and are not a confidential messaging channel. Received messages have unverified origin and remain in a bounded temporary inbox until you explicitly save them. They are never automatically translated, spoken or forwarded. Same-body replays are suppressed for 15 minutes; this does not authenticate a sender. Explicitly saved peer originals stay in private device history until deletion. CodeClear does not collect location coordinates or determine your location. Android 11 requires foreground location permission and system location for Bluetooth discovery while the app is visible. Sharing pauses when you leave the app. CodeClear does not request background location permission. Android 12 and later use Nearby devices permission and can continue sharing with a persistent, user-stoppable foreground-service notification. Android may stop background operation; reopen the app to resume.
Result notifications and optional app overlays can show alert originals or translations. Android notification and lock-screen settings affect visibility. Copy/share actions send the selected content to the clipboard or app you choose; that recipient then handles the content under its own practices.
Manual speech passes the chosen text to the installed speech service. Updated builds also offer a separate, default-off option to read new translations of fresh local captures while the app is visible and focused. Leaving the app or losing audio focus stops playback and clears pending automatic work. History and nearby messages are not automatically read. CodeClear selects installed voices reported as requiring no network, never downloads voices automatically and does not fall back to a network-only voice. The speech-service provider remains responsible for its own implementation and privacy practices.
Support, security and your choices
CodeClear does not include advertising or a first-party advertising profile. Optional services and SDK diagnostics are described above; do not treat this as a promise of zero data collection. The app uses Android permission controls and private storage; remote translation connections use HTTPS. Nearby sharing has the separate public-to-nearby behavior described above.
If you email support, we receive your email address and the information you choose to provide for support or privacy requests. Avoid sending alert bodies, access codes or provider keys unless a specific, necessary request has been agreed.
Support correspondence is retained while needed to handle your request and necessary follow-up or legal obligations. You may request deletion through the privacy contact. CodeClear is a general-purpose safety utility intended for users aged 13 and above; it does not request an age, personal profile or child account.
You can revoke Android notification/accessibility access, turn off each translation permission, stop nearby sharing, remove downloaded models, delete local records, clear the authorized server cache, or clear/uninstall the app. Local removal does not erase data held by external providers or chosen sharing recipients. Email the privacy contact for questions, access or deletion requests concerning the CodeClear-operated service; do not email secret credentials.
This policy website
This policy website is hosted on GitHub Pages. GitHub records visitor IP addresses for service security under its privacy statement. These pages add no analytics, advertising scripts or remote fonts. Visiting the policy does not upload your app history.
Policy updates
The updated date appears above. Material changes to optional data transmission require the corresponding updated in-app disclosure and permission. You can review the current policy here or contact the privacy email with questions.