Overview
Privacy in one minute.
Circo does not continuously record your screen. A capture begins only after you use the shortcut, floating pill, or tray action. Circo does not sell personal information or screen captures to advertisers or data brokers.
The destination of a selection depends on the action you choose. Local OCR stays on your PC. Visual search sends the selected crop to Google Lens. Translation sends extracted text—not the screenshot—to Microsoft Azure Translator.
01
Screen capture and product actions
| Action | What is processed | Where it goes |
|---|---|---|
| OCR | Your selected image may be written to a uniquely named temporary file while Windows OCR processes it. Circo deletes that file after processing. | Your PC |
| Visual search | The image crop you selected is uploaded over HTTPS. | Google Lens |
| Translation | OCR runs locally. Extracted text is sent in bounded requests. The screenshot is not sent to the translation provider. | Microsoft Azure Translator |
| Audio identification | No recognition request is made because this feature is disabled. | Not applicable |
Do not select passwords, authentication codes, financial details, health information, confidential business material, or other content you do not want processed by the service used for that action.
02
Accounts and sign-in
Firebase handles Google and phone sign-in. Circo receives an account identifier, email address or phone number, authentication tokens, tier, entitlement status, and account usage events.
Google may process and store phone numbers for SMS verification and abuse prevention. reCAPTCHA may process device and interaction information to protect phone sign-in.
On Windows, Circo stores its session and refresh tokens using Electron safeStorage when Windows credential encryption is available. The app sends account tokens over HTTPS when verifying sign-in, usage, or paid access.
03
Information stored on your PC
- Settings: shortcut, pill, display, appearance, language, and related preferences.
- History: up to 50 recent entries, which can include text and a compressed image thumbnail. You can clear the full history in Circo.
- Usage: local guest and account allowance information.
- Installation identifier: a random app-generated identifier used for local continuity, release reliability, installation counts, and aggregate product analytics. It is not derived from hardware serial numbers.
- Logs: limited application diagnostics written locally.
04
Operational metrics and optional product analytics
Circo collects limited operational measurements needed to understand whether the website, downloads, releases, and Windows app are working. The website counts page views, website sessions, and installer-download clicks using a random identifier kept only for the browser session. The app counts installations, launches, updates, update failures, and crashes using its random installation identifier. Crash events contain only a bounded process type and reason category—not error messages, stack traces, file paths, or screen content. Circo hashes identifiers again on the server and stores aggregate daily counters.
Completed product-action counts are optional. If you enable Share anonymous action counts in Preferences, Circo also counts completed Circle, Text, Text+, and Translate actions by type.
Analytics events do not contain screenshots, recognized or translated text, search queries, payment details, email addresses, phone numbers, IP addresses, or hardware serial numbers. IP addresses may be used briefly in memory for abuse-rate limiting but are not written to the analytics database.
04
Checkout and payments
Razorpay processes payment details, fraud checks, refunds, and disputes. Circo does not receive or store your complete card, UPI, wallet, or bank credentials.
Circo receives payment references, the account attached to the purchase, the plan and access period, currency, payment status, and information needed to activate or reverse access. Circo’s server supplies the checkout currency and price. Razorpay may offer payment methods based on its own availability rules.
05
Service providers
| Provider | Purpose |
|---|---|
| Google Cloud / Firebase | Authentication, reCAPTCHA, account records, usage allowances, entitlements, and aggregate analytics |
| Google Lens | Visual-search processing for the crop you select |
| Microsoft Azure Translator | Translation of extracted text when you invoke translation |
| Razorpay | Payment processing, fraud prevention, refunds, and disputes |
Each provider applies its own terms and privacy practices to information it receives.
06
How long information is kept
- Local history remains until you clear it or remove the application data, subject to the 50-entry limit.
- Temporary OCR files are deleted after processing completes.
- Account, usage, entitlement, payment, refund, dispute, and aggregate analytics records are kept as needed to operate the service, prevent abuse, reconcile payments, and understand product usage.
- Google Lens, Firebase, Microsoft Azure Translator, and Razorpay set their own retention periods for information they process.
07
Your choices and requests
You can turn optional completed-action analytics on or off from Preferences → Optional Product Analytics. You can also clear history in the app, uninstall Circo, stop using network-backed actions, or schedule permanent account deletion from Account → Delete account after a recent sign-in. Circo immediately signs out and locks the account and clears local history and account counters on that PC. You may restore the cloud account by signing in again within three days, although cleared local history cannot be recovered. After the recovery deadline, Circo removes the Firebase sign-in identity, account, usage, and entitlement records. You can also request access to, correction of, or deletion of account data by emailing contact@trycirco.com.
We may need to verify the request through the associated account. Payment, refund, dispute, fraud-prevention, and accounting records may need to be retained where law permits or requires it; after the recovery deadline, Circo removes the account identifier from retained Circo payment-order records and blocks them from restoring account access. Privacy rights differ by location, and Circo will respond to applicable requests without reducing mandatory rights available to you.
08
Security
Circo uses HTTPS for network requests, Firebase token verification for authenticated actions, and Windows credential protection for local tokens when available. No system is perfectly secure. Keep Windows updated, protect your account, and download Circo only from trycirco.com.
09
Contact and changes
Email privacy questions to contact@trycirco.com. If this notice changes, the updated date will change here. Material changes may also be explained in the app or release notes.
Published notice: https://trycirco.com/privacy