Your information, explained

AnyCopy
Privacy Policy

How we handle the screen content you choose to copy, and the information used to run and support AnyCopy.

Effective & last updated:

Developer
xiaofeidev
Contact
xiaofeidev@gmail.com
Android package
com.github.xiaofeidev.omnicopy

01 About this policy

AnyCopy is an Android app provided by xiaofeidev (“we,” “us,” or “our”). It helps you select, edit, copy and share text displayed on your screen using Android accessibility features or optical character recognition (OCR). This policy covers the app and this privacy policy website.

You do not need to create an AnyCopy account. This does not mean that no information is processed: the app uses the third-party services described below, and screen content can itself contain personal or sensitive information.

02 Screen content & permissions

Accessibility mode

After you enable AnyCopy’s Accessibility Service in Android settings, a copy request reads available text and its on-screen position from the current window. This lets the app draw selectable regions. Text extraction is triggered by a copy request; the service does not build a history of every screen you visit.

OCR mode and screen capture

OCR uses Android’s screen-capture authorization to capture an image and Google ML Kit to recognize text on your device. OCR can also be offered when accessibility mode finds no text. The recognition workflow does not upload the image or recognized text to a cloud OCR service. ML Kit separately processes technical metrics described in section 4.

A scan can include more content than you ultimately select. Depending on what is visible, that content could include messages, names, addresses, financial details or other sensitive information. Capture only screens you intend to process. Screenshots and recognized text are used for recognition, selection and editing; we do not use that screen content to target advertisements.

Copy, share and supporting permissions

When you tap Copy, the selected or edited text is written to the Android clipboard. When you choose Share, it is passed through Android’s share chooser to your chosen app. Android, your keyboard or clipboard tools may retain clipboard entries, and a receiving app may store or transmit shared text under its own policy.

The display-over-other-apps permission supports the selection overlay. Foreground services and notifications provide the copy trigger and support screen capture. You can revoke these permissions in Android settings; the corresponding feature may then stop working.

03 Local settings & diagnostic logs

AnyCopy stores your detection mode, first-use prompt status, cached ad-free entitlement and information needed to complete pending purchases in app-private storage. It also stores advertising request, display and interaction timestamps and counters to control ad frequency.

Local diagnostic logs can contain recognized text and its screen position. These entries help diagnose recognition behavior and are written to Android’s system logging facilities. Their access and retention are controlled by Android and any diagnostic tools or bug reports you choose to use. They are separate from an in-app copy history, which AnyCopy does not provide.

Android backup and device-transfer features may back up and restore eligible app settings and locally stored service data, depending on your device and backup settings.

04 Third-party services

The services below receive information to provide advertising, understand app operation, fix errors or supply configuration. Some SDKs can start collecting technical information when the app starts, before you make a copy request. The current app does not provide a separate in-app switch for analytics or crash reporting.

Advertising: Google AdMob, Unity Ads and Meta

AnyCopy uses Google Mobile Ads (AdMob), with Unity Ads and Meta Audience Network integrations for mediated ads. These partners may process device and advertising identifiers, IP addresses and approximate location derived from them, app and ad interactions, and diagnostic information. This supports ad delivery, personalization where enabled, measurement and fraud prevention. The partners involved in a particular request depend on ad availability and mediation configuration.

Google’s advertising SDK may use the Android advertising ID, app set ID and other available identifiers. Unity’s disclosures also cover purchase-related information. These services have their own privacy practices and controls: Google Privacy Policy, Unity Game Player and App User Privacy Policy and Meta Privacy Policy.

Google Analytics for Firebase

Analytics processes app usage and interaction events, app-instance and advertising identifiers, device/app information, approximate location and purchase events. We also record ad-delivery stages and purchase-confirmation outcomes to understand failures and improve reliability. Purchase diagnostics can include a shortened hash of a purchase token, attempt counts and response codes; the hash is an identifier, not a guarantee of anonymity.

See Google’s Analytics data disclosure.

Firebase Crashlytics and Remote Config

Crashlytics processes crash and non-fatal error reports, stack traces, app/device state and installation or session identifiers. Reports can include purchase-processing errors and the purchase-token hash described above. Native crash reporting and Analytics breadcrumbs help diagnose failures.

Remote Config supplies settings such as ad formats and frequency limits. It uses installation identifiers and app/device context, including versions, country, language and time zone. Supporting Firebase Installations and Sessions services manage identifiers and app-quality measurements.

See Firebase Privacy and Security and Firebase’s Android data disclosure.

Google ML Kit

ML Kit performs text recognition locally, but sends Google technical information such as device and app details, installation identifiers, recognition timing, image configuration and sizes, and event/error information. Google uses these metrics to operate, diagnose and improve ML Kit and prevent misuse. This is separate from sending the screenshot or recognized words to Google for recognition.

See ML Kit Terms & Privacy and ML Kit’s Android data disclosure.

05 Purchases

Google Play processes the optional ad-free purchase. AnyCopy receives product and purchase information, including purchase status, acknowledgment status and a purchase token, to grant, restore and confirm the entitlement. Google handles payment details; the app does not receive your full payment-card details.

The app keeps the entitlement and a shortened hash of unfinished purchase tokens locally so it can retry unfinished processing. Purchase-confirmation diagnostics are sent to Firebase as explained above. Google Play retains transaction records under its policies.

Once the app recognizes an ad-free entitlement, it suppresses ads. This purchase does not disable Firebase analytics, crash reporting, ML Kit technical metrics or purchase processing, and does not delete information already received by service providers.

06 Sharing & processing locations

Information is processed by the service providers described in section 4, Google Play for purchases, and apps you choose when sharing or pasting text. We do not sell the screen text or screenshots used by the copying features. Advertising services separately process and share technical and interaction information as described in their policies.

If you contact us, we receive your email address, message and any attachments you send. We use them to respond and resolve the issue. Please avoid including passwords, payment-card details or unrelated screen content. Email delivery also involves your and our email providers.

Information we hold may also be disclosed when required by law or necessary to address fraud, abuse or security incidents. Google, Unity, Meta and their service providers may process information outside your country, including in the United States and other locations where they operate. Their linked policies explain applicable safeguards and privacy options.

07 Secure handling of personal & sensitive data

We protect information through the following measures and boundaries:

  • Local content processing. The copy/OCR workflow processes screen content in device memory and does not upload it for recognition or save a screenshot collection. Content is passed to the clipboard or another app when you choose to copy or share.
  • Permission-based access. Accessibility access requires enabling the Android service, and OCR requires system screen-capture authorization. The screen-capture session is released when the selection activity is destroyed. Android permission and app-component controls restrict access to these features.
  • Private local storage. Operational settings and purchase-processing state use Android app-private storage. Protection relies on Android’s app isolation and your device security; we do not claim separate app-level encryption for these preferences.
  • Protection in transit. Google documents HTTPS/TLS encryption for data transmitted by Google Mobile Ads, Firebase and ML Kit. This policy website is served over HTTPS. Other advertising partners describe their security measures in their own privacy policies.
  • Limited purchase identifiers in diagnostics. The app uses a shortened cryptographic hash, rather than the full Google Play purchase token, in its purchase diagnostic events and local retry tracking.

These measures do not make all copies of information private or immediately erasable. Recognized text can appear in local diagnostic logs. Android backup, clipboard history and apps you share to have separate access and retention controls. No device, storage system or network transmission can be guaranteed completely secure.

For a privacy or security concern, contact xiaofeidev@gmail.com.

08 Retention & deletion

Screen images and working text
Used in temporary app memory for the copy session, without an app-managed saved screenshot or copy-history archive. Memory is reclaimed through the app/Android lifecycle; this is not a promise of immediate secure erasure. Android controls diagnostic log retention.
Settings and local operational records
Remain until replaced, cleaned up by the app, or removed by clearing app storage or uninstalling. Ad-frequency event records are pruned during subsequent frequency checks using the active control window plus one day; they are not deleted by an exact wall-clock deadline when the app is unused. Pending purchase hashes are removed when processing completes or purchase reconciliation finds they are no longer active.
Clipboard, shared text and backups
Manage or delete these through Android, your keyboard/clipboard manager, the receiving app or your backup provider. Clearing AnyCopy’s storage does not erase their copies, and restoring a backup may restore app settings.
Firebase and other service records
Retention depends on the service, its settings and applicable requirements. Google states that Crashlytics begins removing crash records and associated identifiers after 90 days; removal from live and backup systems takes additional processing. Analytics retention follows the configured service retention settings. Installation identifiers and advertising or purchase records have separate provider rules. See Firebase’s retention details and Analytics retention information. Uninstalling does not automatically erase data already held by these providers.
Support correspondence
We retain messages as needed to respond, resolve the issue and meet applicable legal obligations. You may request deletion of correspondence we hold by emailing us.

09 Your choices & privacy requests

  • Disable AnyCopy’s Accessibility Service or overlay access in Android settings, and decline or end screen capture when you do not want that access.
  • Use Android’s app settings to clear AnyCopy’s storage or uninstall it. Separately manage clipboard history and device backups.
  • Use the advertising ID and ad-privacy controls available on your Android version and your Google, Unity or Meta privacy controls. These controls do not necessarily stop all advertising, diagnostics or fraud-prevention processing.
  • Contact xiaofeidev@gmail.com to ask about access, correction or deletion of information we hold, or to raise an objection or other privacy request available under the law where you live.

Please identify AnyCopy and describe your request without sending unnecessary sensitive information. We may need information to verify and locate the relevant record. Because AnyCopy has no user account or server-side copy-history archive, we cannot retrieve or remotely erase text held only on your device or by an app you chose. For information held independently by a provider, use its linked privacy-request options; we can help identify the appropriate service.

The current app has no separate in-app analytics/crash-reporting opt-out or advertising-consent settings screen. Reading this policy does not itself grant consent to optional processing.

10 Children’s privacy

AnyCopy is intended for people aged 13 and older and is not directed to children under 13. Where local law requires a higher age or parental permission, those requirements also apply. If you believe a child has provided personal information through the app or our support channel, contact us so we can review the concern and address information within our control.

11 This privacy policy website

This is a static site hosted on Firebase Hosting. The page does not run analytics, advertising or tracking scripts, set its own cookies or browser-storage entries, load external fonts, or require a sign-in.

Delivering the page still involves technical requests to Firebase Hosting. Google processes request information such as IP addresses to operate and protect the hosting service; its published Hosting policy describes IP retention of a few months. See Firebase Privacy and Security. Following an external policy link takes you to that provider’s site and its privacy practices.

12 Updates & contact

We may update this policy when the app or its data practices change. The date at the top identifies the latest substantive update. Where required, material changes will be accompanied by additional notice or a consent request.

For privacy questions, security concerns or data requests, contact the developer:

xiaofeidev · AnyCopy
xiaofeidev@gmail.com