This Privacy Policy explains how Unity Bridge Solutions Ltd ("Cleverly Lingo," "we," "us," or "our") collects, uses, shares, retains, and deletes information when you use the Cleverly Lingo mobile app, companion app, keyboard extension, the Cleverly Lingo extension for Google Chrome, and related services (collectively, the "Service").
Privacy at a glance
- Ordinary typing stays on your device. Cleverly Lingo does not transmit every keystroke or operate as a keylogger.
- Text is sent to our cloud services only when you deliberately use a cloud feature such as Translate, Enhance, Summarize, or another AI action.
- Cloud actions are disabled in password and other protected text fields.
- Camera and live-voice features process an image or audio only when you choose to use those features.
- We do not sell personal information, show third-party advertising, or use personal information to track you across apps and websites owned by other companies.
- You can delete your Cleverly Lingo account and associated cloud data from inside the app. Deleting the account does not cancel an App Store subscription; subscriptions are managed separately through Apple.
- The Cleverly Lingo extension for Chrome has no account and sends nothing to us. See Cleverly Lingo for Chrome below.
Information we collect and process
The information involved depends on which features you use.
Account and authentication information
If you create or sign in to an account, we process an account identifier and your primary email address. If you choose Sign in with Apple or Google sign-in, the relevant provider and our authentication provider process the information needed to authenticate you. Apple may provide a private relay email address if you select that option.
We use this information to authenticate you, keep your synced content separated from other users' content, support account recovery, and process account deletion.
Text you deliberately submit for cloud features
When you tap a cloud action such as Translate, Enhance, change tone, or Summarize, the text selected for that action and the options you choose are sent to our backend and relevant AI or translation provider. We process that text to return the requested result.
We may temporarily cache the submitted text and generated result to provide the feature efficiently and prevent repeated processing. AI enhancement cache records are configured with a seven-day expiry and are deleted sooner when you delete your account.
Notes and translation history
Notes and translation history can be stored locally on your device. When you are signed in and synchronization is enabled, they are also stored in our cloud database so they can be restored and synchronized. These records may include note titles and bodies, source and translated text, source and target languages, feature type, timestamps, and a device-scoped identifier used for synchronization.
Camera and image translation
When you choose camera or photo translation, the selected image is sent for optical character recognition and translation. Our backend does not retain the original image. It may retain an image hash and the extracted and translated text, language information, and text-region metadata to return results and avoid duplicate processing. Non-favorite image-translation results are eligible for cleanup after 30 days; saved or favorite results remain until you remove them or delete your account.
Voice and live translation
When on-device dictation is available and selected, speech recognition is performed on your device using Apple's speech services. When you deliberately use cloud voice or live translation, audio is streamed to our speech relay and Google Cloud speech services to produce transcription and translation. We do not store the streamed audio in our application database. We retain limited usage records such as session duration, audio processed, character counts, languages, provider, and timestamps for reliability, abuse prevention, and cost control.
Subscription and purchase information
If you view, start, restore, or manage a subscription, Apple and RevenueCat process purchase information. We receive subscription and entitlement details such as an opaque billing identifier, product identifier, transaction identifier, subscription status, store environment, and purchase, renewal, or expiration dates. We do not receive or store your full payment-card details.
Usage, security, and diagnostic information
We process limited operational data needed to run and protect the Service. This may include feature type, request counts, text or audio length, token or character counts, timestamps, language choices, response status, error categories, app configuration, and pseudonymous account, session, or device identifiers. Our logs are designed to record metadata rather than the content you type, say, or translate.
Our infrastructure providers may process network information such as IP address and request headers as necessary to transmit requests, prevent abuse, and keep their services secure.
How we use information
We use information to:
- provide translation, writing assistance, notes, camera, voice, and keyboard features you request;
- authenticate accounts and synchronize content across devices;
- determine subscription access and restore purchases;
- maintain service security, prevent fraud and abuse, enforce usage limits, and diagnose failures;
- measure aggregate service usage and control infrastructure costs;
- comply with legal obligations and enforce our agreements; and
- respond to privacy, support, and account-deletion requests.
We do not use your content for third-party advertising or sell it to data brokers.
When information is shared
We share information only as needed to operate the Service, complete actions you request, protect users and the Service, or comply with law. Our principal service providers are:
- Apple: App Store purchases, Sign in with Apple, device permissions, and Apple speech services where applicable.
- Clerk: account authentication and user management.
- Supabase: hosted database, authentication-token verification support, and serverless backend functions.
- RevenueCat: subscription entitlement and purchase-status management.
- Google Cloud and Google Gemini services: text enhancement, translation, image text recognition, speech recognition, and live translation where those features are used.
These providers process data under their own terms and privacy commitments and, where they act for us, under contractual data-protection obligations. They may use subprocessors to provide their services.
We may also disclose information when reasonably necessary to comply with law, respond to valid legal process, protect rights and safety, investigate fraud or security incidents, or complete a merger, financing, acquisition, or sale of assets. If ownership changes, personal information will remain subject to applicable law and any notice required for the transaction.
Retention and deletion
We retain information only for as long as reasonably necessary for the purposes described in this Policy:
- Local notes, history, settings, and other app data remain on your device until you remove them, delete the app, or use an available reset or deletion control.
- Synced notes, translation history, account information, preferences, and user-linked AI results remain until you delete the relevant content or your account, unless a shorter expiry applies.
- AI enhancement cache entries are configured to expire after seven days.
- Non-favorite image-translation results are eligible for cleanup after 30 days. Favorite or saved results remain until you remove them or delete your account.
- Streamed cloud audio and original camera images are not stored in our application database after processing, although service providers process them long enough to provide the requested feature under their applicable terms.
- Purchase, security, fraud-prevention, audit, and accounting records may be retained for longer where reasonably necessary to protect the Service, resolve disputes, satisfy legal obligations, or preserve accurate financial records.
When you delete your account, Cleverly Lingo deletes user-linked content and private billing mappings from its active systems and requests deletion from the relevant authentication and subscription systems. Some minimized, non-identifying, or one-way hashed records may remain where necessary to prevent a deleted identity from being silently recreated, record completed deletion work, maintain security, or comply with law. Deletion may take additional time to propagate through provider systems and limited backup-retention cycles, unless preservation is required by law.
Your choices and rights
Depending on where you live, you may have rights to request access to, correction of, deletion of, restriction of, or a portable copy of your personal information, and to object to or withdraw consent for certain processing.
You can:
- avoid cloud processing by not invoking cloud actions;
- deny or revoke camera, microphone, speech-recognition, photo-library, or keyboard Full Access permissions in iOS Settings;
- delete individual notes or history where the app provides that control;
- delete your Cleverly Lingo account from the app's account settings; and
- contact us at [email protected] for a privacy request.
Withdrawing permission may prevent the related feature from working. Account deletion does not cancel an Apple subscription. You can manage or cancel an Apple subscription in your Apple Account subscription settings.
Cleverly Lingo for Chrome
This section covers Cleverly Lingo for Chrome, our free extension for the Google Chrome browser. It works differently from the iPhone app: it has no account, we operate no server for it, and it contains no analytics, telemetry, or advertising. We receive no information from the extension at all, so we have nothing from it to sell or share. The sections above about accounts, cloud features, sharing, and retention describe the iPhone app and its cloud services, which the extension does not use. The sections below on children's privacy, changes to this Policy, and how to contact us also apply to the extension.
Text you choose to process
Nothing is sent anywhere until you start an action, such as a rewrite, a translation, a tone change, a summary or another transform, or the correction step of dictation. What happens next depends on the AI connection you choose:
- Local AI: your text is processed on your computer and is not sent anywhere.
- OpenAI: the text you selected or typed, the language and tone you chose, and the instructions for the task are sent directly from your browser to OpenAI (api.openai.com) over an encrypted connection, using your own API key. OpenAI processes them under your OpenAI account and OpenAI's own terms and privacy policy.
- Claude: the same information is sent directly from your browser to Anthropic (api.anthropic.com) over an encrypted connection, using your own API key, under your Anthropic account and Anthropic's own terms and privacy policy.
We are not a party to these requests and never see your text or the results. OpenAI or Anthropic bills your own account for what you use.
Your API keys
If you choose OpenAI or Claude, you enter your own API key. The extension stores it in its local storage on that computer only; it is not copied to Chrome sync. The key is sent only to the provider that issued it, with your requests and once when you save it, so the extension can check that it works.
Local AI model download
If you choose Local AI and download a model, the extension downloads Google's Gemma open model files (about 3 to 5 GB, depending on the size you choose) from Hugging Face (huggingface.co and its file servers on hf.co) and keeps them on your computer. As with any download, Hugging Face receives your IP address and standard request information under its own privacy policy. None of your text is sent to Hugging Face.
Microphone dictation
Dictation is optional and off by default. The extension asks for microphone access only after you choose to set it up. Your speech is turned into text by Chrome's built-in speech recognition:
- On-device (the default): recognition runs on your computer. If your language needs it, Chrome may download a speech pack for that language from Google during setup.
- Online: if you select it, Chrome sends your microphone audio to Google's speech recognition service while you dictate, under Google's privacy policy.
The resulting transcript is then corrected with the AI connection you chose, as described above, and inserted into your text field. The extension does not store your audio or transcripts.
What stays on your computer
The extension keeps the following in Chrome's storage for the extension on your computer. None of it is sent to us.
- your rewrite history (the original text, the result, the action used, and the time), until you clear it;
- your templates and template categories;
- your preferences and themes;
- your API keys, as described above; and
- the Local AI model, if you downloaded one.
After each change to your templates, the extension also saves a backup file (cleverly-lingo-templates-auto-backup.json) to a folder in your Downloads folder, or to a folder you choose. It contains only your templates and is never uploaded. You can turn this off with Back up automatically in Settings > Templates.
Chrome sync
A few preferences are saved in Chrome's synced extension storage: your output language, recently used and quick-pick languages, tone and quick-pick tones, Fast mode, and whether the floating button appears when you select text. The extension also keeps a backup copy of your templates there. If Chrome sync is turned on, Google stores this information with your Google Account and copies it to the other computers where you use Chrome with that account, under Google's privacy policy. If Chrome sync is off, it stays on your computer. Your API keys, history, themes, dictation settings, and the downloaded model are never synced.
Web pages and permissions
The extension runs on the pages you visit so it can show its button and menu next to text you select and insert results where you are writing. It reads page text only when you select text and start an action, and then only the selected text or the text field you are working in. It never reads password fields, does not record which pages you visit, and does not track your clicks or keystrokes. It checks a tab's address only to skip pages where extensions cannot run, such as Chrome's own pages, and does not store or send it.
No analytics or advertising
The extension contains no analytics, telemetry, crash reporting, tracking, or advertising, and we do not sell any data. Links from the extension to cleverlylingo.com include a tag (utm_source=chrome-extension) that marks the visit as coming from the extension; it is added only when you click such a link and contains nothing about you.
Limited Use
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Cleverly Lingo for Chrome's use of information complies with that policy: it uses your data only to provide its single purpose of writing and improving text, sends it only where this section describes, and never uses or transfers it for advertising, to determine creditworthiness, or for lending purposes. We never read your data, because it never reaches us.
Deleting your data
You can:
- clear your rewrite history with Clear history in Settings > View Rewrite History;
- delete templates in Settings > Templates;
- remove the downloaded model with Remove model in Settings > AI Connection;
- replace a saved API key in Settings > AI Connection, or revoke it at any time in your OpenAI or Anthropic account; and
- uninstall the extension, which deletes everything it stored in Chrome on that computer, including your API keys, history, templates, and the model. Backup files you saved to your own folders stay until you delete them.
If you use Chrome sync, you can also delete synced data from your Google Account in Chrome's sync settings. Because we hold no data from the extension, there is nothing for us to delete, but you can contact us at [email protected] with any privacy question.
Legal bases for processing in the UK and EEA
Where UK or EEA data-protection law applies, we rely on one or more of the following legal bases:
- Contract: to provide features, synchronization, authentication, and subscription access you request.
- Consent: for optional permissions or processing where consent is required; you may withdraw consent through device settings or by stopping use of the feature.
- Legitimate interests: to secure, maintain, troubleshoot, and improve the reliability and efficiency of the Service, provided those interests are not overridden by your rights.
- Legal obligation: to retain or disclose information where applicable law requires it.
International data transfers
Our service providers may process information in the United Kingdom, European Economic Area, United States, or other countries where they or their subprocessors operate. Where required, we and our providers use recognized transfer mechanisms and safeguards for international transfers.
Security
We use technical and organizational measures designed to protect information, including encrypted network connections, access controls, row-level database authorization, platform data-protection features, restricted server credentials, content-minimized logging, and in-app account deletion. No system can guarantee absolute security.
Children's privacy
Cleverly Lingo is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to us, contact [email protected] so we can investigate and delete it as appropriate.
Changes to this Policy
We may update this Policy when the Service, our providers, or legal requirements change. We will change the "Last updated" date and provide additional notice when required. Material changes will apply prospectively unless the law permits or requires otherwise.
Contact us
The data controller responsible for Cleverly Lingo is:
Unity Bridge Solutions Ltd
Email: [email protected]
If you are in the UK or EEA, you may also complain to your local data-protection authority. We encourage you to contact us first so we can try to resolve your concern.