BumuStudios·Türkçe sürüm·ImageToPdf policy·PdfPages policy

Who this policy is from

This policy covers the Android application Polyglance, distributed through Google Play under the package name com.bumustudios.linguasnap. It is written by the app's independent developer, BumuStudios. Questions can be sent to the address in Contact.

What the app does

Polyglance translates the text in photos and the text you type. You can scan a sign, a menu or a page, pick a photo, type or paste up to 5,000 characters, share an image or text into the app from another app, or select text in any app and choose Translate with Polyglance. The app reads the text, works out its language and draws the translation over the photo, block by block, with a copyable list of every block and its original. It supports 59 translation languages, keeps a searchable history with favourites on your phone, and has no usage limits and no subscription.

Your photos and text stay on your device

This is the most important section, so it is stated plainly:

• Photos and text are never uploaded. The app has no backend of its own. It does not transmit your photos, the text recognised in them, the text you type or paste, or your translations anywhere, and neither the ML Kit diagnostics, the ads nor the usage statistics and crash reports described below contain them.
• Scanning uses Google's document scanner, not the app's own camera access. Scan opens the ML Kit Document Scanner, a screen provided by Google Play services that takes the picture (or imports one from your gallery) inside Play services itself. The app does not hold the camera permission and never accesses the camera; it receives only the one finished image you confirm.
• Photos are picked through the Android Photo Picker. You choose one photo; the app is granted access to that item only and does not browse your gallery.
• Shared content. When you share an image or text into the app, or choose it from another app's text-selection menu, the app receives only that image or text. When you share a translation out, it goes through the Android share sheet to the app you pick; Polyglance notes only that a share took place, not where. Copy places the text on your device's clipboard.
• A private working copy. To read a photo, the app makes a private JPEG copy in its own storage, scaled down so its longest side is at most 2,048 pixels and turned upright. The copy is re-encoded from the pixels alone, so metadata of the original file, such as location tags, is not carried over. The copy lives in the app's cache and is deleted when you leave a translation that is not saved (or at the next start); it is moved into the app's private files only when the translation is saved to History, and it is deleted with that History entry.
• No camera or storage permission is requested on any Android version. The document scanner and the Photo Picker make both unnecessary.

History

Finished translations are saved to History on your device: the original text, the translation, the languages (and whether the source was detected automatically), the position of each text block on the photo, the date, whether it is a favourite, and the private copy of the photo. History can be searched, entries can be deleted one by one, and Clear history removes every entry except favourites, together with their photos.

You can turn this off with Settings → Keep history. While it is off, new translations are not saved; a translation you star is kept anyway, as a favourite, and taking the star back in the same session removes it again. Entries saved earlier stay until you delete them.

What the app stores locally

Besides History, the app keeps a small amount of state in its own private storage on the device. None of it is sent anywhere:

• your theme, text size and app language choices, the selected source and target languages and a short list of recently used languages;
• the Download languages on Wi-Fi only, Keep history and completion-sound settings;
• whether the one-time "remove ads" purchase is active, and until when a rewarded "24 hours without ads" period runs;
• a counter of how many interstitial ads have been shown, used to keep ad frequency low.

History, its photos and the settings above are deliberately excluded from Android cloud backup and from device-to-device transfer (the app's backup rules exclude its database, its photo folder, its settings files and its shared preferences), so they are not copied to your Google Drive or to a new phone. Downloaded language models are managed by ML Kit and are downloaded again when needed. Google's advertising and consent components also keep their own settings on the device, under Google's control, and the Google Firebase components described below keep three random identifiers in the app's private storage: a Firebase installation ID, the Analytics app-instance ID and a Crashlytics installation ID. Unlike the list above, these identifiers travel with the usage statistics and crash reports. Uninstalling the app or clearing its data removes everything the app has stored — History, photos, settings, downloaded language models and these identifiers included.

On-device recognition and translation — Google ML Kit

The app's text recognition, language detection and translation are done by Google ML Kit, which runs on your device. Your photos and text are processed locally and are not sent to Google or to anyone else.

• Text recognition (Latin, Chinese, Japanese, Korean and Devanagari scripts) uses recogniser modules that are installed through Google Play services. The Latin one is requested when the app is installed; the others are downloaded the first time a photo needs them. The Wi-Fi only setting applies to these downloads too.
• Language identification uses a model built into the app and works offline from the first launch.
• Translation uses a language model of about 30 MB per language, downloaded once from Google's servers when you first need that language or from Offline languages (English is built in). The download request asks for the model file only; your text is not part of it. Downloaded models stay on the device, can be deleted from Offline languages, and then translate with no connection. By default models are downloaded only on Wi-Fi or another unmetered network; on mobile data the app asks first.

As stated in Google's ML Kit terms, ML Kit itself sends Google limited diagnostic and usage information over HTTPS: device information (such as model and operating system version), the app's package name and version, a device identifier used for diagnostics and usage analytics, performance metrics and error codes, and — for language identification and translation — the languages involved (the detected language, and the source and target languages selected). It never includes the images or text being processed. Google describes this in the ML Kit terms and the ML Kit data disclosure.

As ML Kit's translation terms require, results carry a "Powered by Google Translate" note, and the translation is basic machine translation: fine for signs, menus and the gist of a text, not for documents where accuracy matters.

Advertising — Google AdMob and its mediation partners

The app is free and is supported by ads served by Google AdMob (Google Ireland Limited / Google LLC, depending on your region). AdMob is embedded in the app as a software development kit, and it does collect data, independently of the developer.

The app also contains the mediation adapters and SDKs of six partner ad networks: AppLovin, Unity Ads, Liftoff Monetize (Vungle), Meta Audience Network, Mintegral and Pangle. Through mediation, AdMob may pass a given ad request to one of these partners when that partner can fill it. The partner that receives the request then collects the same categories of data as AdMob, listed below, and processes them under its own privacy policy. When ads are served, AdMob, its partners and Google's advertising partners may collect and process:

The app does not request GPS or precise location permission, and it does not send your photos, recognised text or translations to AdMob or to any ad partner. The developer receives no personal data from AdMob or its partners — only aggregated, anonymous reporting such as impression and revenue totals.

Because ads require an advertising identifier, the app declares the com.google.android.gms.permission.AD_ID permission. The ad formats and where they appear:

• Banner — at the bottom of the Home and History screens, below the navigation bar; on History only once it holds at least one translation.
• Interstitial — only when you leave a result after a translation made in that session was saved or shared. Your first two such moments never show one, two are always at least two minutes apart, and none appears when you merely reopen an old History entry or when leaving the result closes the app.
• Rewarded — optional, in Settings → 24 hours without ads: watching a short video turns ads off for 24 hours. The entry appears only when a video is ready.
• App open — when you return to the app, at most once every four hours; never on a fresh start, never right after the scanner, photo picker, share sheet, purchase screen or a browser that the app itself opened, and never when the app is opened to translate something shared into it.

No ad ever stands in front of scanning, text recognition, translation, copying, History or language downloads.

How Google and the partners handle this data is governed by their own policies, not by this one:

• Google Privacy Policy
• How Google uses information from sites or apps that use our services
• AdMob and third-party advertising
• AppLovin Privacy Policy
• Unity Game Player and App User Privacy Policy
• Liftoff (Vungle) Privacy Policy
• Meta Privacy Policy (Meta Audience Network)
• Mintegral Privacy Policy
• Pangle Privacy Policy

Usage statistics and crash reports — Google Firebase

To see how the app is used and to find and fix crashes, the developer has built two Google Firebase services into it: Google Analytics for Firebase and Firebase Crashlytics. Google provides them as the developer's data processor, and they are active only in the version of the app distributed through Google Play. The app adds nothing of its own to what they collect — no custom events, no user ID or user properties, no custom keys or log messages — so only their automatic collection applies:

Analytics records that a screen was shown and for how long, not what you do on it, and a crash report shows where in the code the crash happened, not your content: no photo, recognised text or translation is part of either. Neither service receives your name, your email address or any account details.

In the EEA, the UK and Switzerland, the consent form described below under "Your advertising choices" also covers Analytics: your choices there decide whether Analytics may store its identifiers on your device and whether the data may be used for advertising. Use of the data for advertising ("ad user data") and for ad personalisation stays off there until you consent. You can change your choice at any time from Settings → Privacy options; the entry appears where it is required. The app has no separate switch for the usage statistics or the crash reports; uninstalling it stops both.

Analytics keeps data linked to an installation's identifiers for no longer than 14 months; aggregated reports that contain no identifiers may be kept longer. Crashlytics keeps crash reports for 90 days.

Google processes this data on the developer's behalf, as its data processor, under the Firebase and Google Analytics data processing terms. It may be processed on Google's servers outside your country, including in the United States, and it is encrypted in transit (TLS).

Google describes these services here:

• Privacy and security in Firebase
• Google Privacy Policy

Purchases and updates — Google Play

The app offers one optional, one-time, non-consumable purchase that permanently removes ads. There is no subscription and nothing recurring.

The transaction is handled entirely by Google Play Billing. The developer never sees or receives your card number, bank details, billing address or full name. Google Play reports only aggregated sales figures, and Google Analytics for Firebase records that a purchase was made — product, name and price, with no payment details (see above). Inside the app, the purchase is recorded as a single true/false flag on your device, restored from your Google Play account when you reinstall or move to a new device. The app also uses Google Play's in-app update service, which checks with Google Play whether a newer version is available and downloads it in the background. Your handling of payment data by Google is covered by the Google Privacy Policy and Google Play's terms.

Your advertising choices

If you are in the EEA, the UK or Switzerland

Before personalised ads are requested, the app shows a consent form built with Google's User Messaging Platform, where you choose what you allow. Your choice is stored on your device by Google's component, is respected on later launches, and is passed on to the mediation partners through the industry-standard consent signal (IAB TCF) that they read.

You can change your decision at any time: open the app, go to Settings → Privacy options, and the same form reappears. You may withdraw consent there. Withdrawing consent does not disable the app; you will still be able to scan and translate, and ads may still be shown in a non-personalised form. The same choices also apply to Google Analytics for Firebase, as described above.

If you are in a US state with a privacy law

Where US state privacy laws apply, the same Google consent tool can show a notice that lets you opt out of the sale or sharing of your personal information for advertising. Where it does, Settings → Privacy options lets you review that choice later.

Everywhere else

The privacy options entry appears only where a consent choice is legally required, so you may not see it. You can still control advertising at the operating-system level: open Android Settings → Privacy → Ads (the exact path varies by manufacturer and Android version) to reset your advertising ID, or to delete it entirely, which stops apps from receiving a stable advertising identifier.

Removing ads completely

Buying the one-time ad removal stops ad requests from the app altogether, to AdMob and to every mediation partner. A rewarded "24 hours without ads" period does the same for its 24 hours.

Permissions the app requests

These are the permissions the app declares itself. The Google and ad-network components built into it add a few more that Android grants at installation without asking you, such as Google Play's billing and install-referrer permissions, Wi-Fi state, wake lock and vibration used by the ad SDKs, and Android's advertising-services permissions. The app does not ask for notification permission and runs nothing at device start-up, and it requests no camera, storage, photos, contacts, microphone, precise location or account permissions on any Android version. The camera used by Scan belongs to Google Play services' document scanner, as described above.

Children

This app is a general-purpose utility. It is not directed at children under 13 (under 16 in the EEA, or the equivalent minimum age in your country), it is not listed in a children's category, and it is not designed for or marketed to children. The developer does not knowingly collect any personal information from children. If you believe a child has provided personal information through the ad, analytics or crash-reporting services in this app, contact the address below and contact Google, whose services would hold it.

Data retention

The developer runs no server and keeps no user data of its own. The usage statistics and crash reports are held by Google on the developer's behalf: Analytics data linked to an installation's identifiers for no longer than 14 months (aggregated reports without identifiers may be kept longer), and crash reports for 90 days. History, its photos and everything else held on your device stay there until you delete them in the app, clear the app's data or uninstall the app. Data collected by Google through AdMob, ML Kit and Google Play, and by the mediation partners, is retained according to their own retention schedules, described in the policies linked above.

Legal bases and your rights

Where the GDPR (EU/UK) applies, the legal basis for personalised advertising is your consent, collected through the form described above and withdrawable at any time. Non-personalised advertising, fraud prevention and the security of the ad services rely on legitimate interests. Processing your purchase is necessary to perform the contract you enter when you buy ad removal. The usage statistics, crash reports and ML Kit diagnostics rely on the developer's legitimate interest in keeping the app working and understanding, in aggregate, how it is used; storing Analytics identifiers on your device and any advertising use of the data follow your choices in the consent form.

Under the GDPR, and under Turkey's KVKK (Law No. 6698) on equivalent terms, you have the right to ask whether your personal data is processed, to access it, to have it corrected or erased, to restrict or object to its processing, to data portability, and to withdraw consent. You may also lodge a complaint with your national data protection authority — in Turkey, the Kişisel Verileri Koruma Kurumu (KVKK).

The usage statistics and crash reports are pseudonymous: they carry random identifiers, never your name or email address, so the developer cannot tell which records are yours. Where the consent form is shown, you can withdraw consent at any time in Settings → Privacy options, and you can object to this processing, or ask about it, by writing to the address below. You can reset or delete your advertising ID in Android's settings at any time. Uninstalling the app or clearing its data ends the link to the old identifiers, and data already sent then expires on the schedule above. Requests concerning advertising data must be directed to Google, or to the mediation partner, as the party that holds it, using the tools in their privacy policies linked above. For anything else, or for help finding the right route, write to the address below.

Security

History, photos and settings are kept in the app's private storage, which Android isolates from other apps, and they are excluded from backups. Everything the app's components send over the network — language model downloads, ads, Google Play, ML Kit diagnostics and Firebase — travels encrypted (HTTPS/TLS). No method of storage or transmission is perfectly secure, but the most sensitive part, your photos and text, never leaves the device in the first place.

Changes to this policy

If the app's data practices change — for example if a new third-party service is added — this page will be updated and the "last updated" date at the top will change. Material changes will also be reflected in the app's Google Play listing. Continuing to use the app after an update means you accept the revised policy.

This is the first version of the policy, published on 9 October 2026 for the app's first release.

Contact

For any question about this policy or about privacy in this app, write to: