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

Who this policy is from

This policy covers the Android application PaperLite: PDF Scanner & OCR (shown as PaperLite on your home screen), distributed through Google Play under the package name com.bumustudios.paperlite. It is written by the app's developer, BumuStudios, an independent developer. Questions can be sent to the address in Contact.

The controller of the personal data described in this policy — the party responsible for it under data protection law, including the GDPR and Türkiye's KVKK — is Burak Gökgöz, who publishes the app as BumuStudios, in Türkiye. Contact: bumustudios@gmail.com.

What the app does

PaperLite is a document scanner. It captures paper documents with Google's document scanner (edge detection, cropping, perspective correction, filters, multi-page), or takes photos you pick from your gallery or share to it from another app. It keeps them in a library with folders, reads the text on every page on your device so you can search, view and copy it, and exports documents as searchable PDFs (optionally protected with a password) or as JPEG images. There is no watermark, no page limit and no subscription.

Your scans and files stay on your device

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

• Scans are never uploaded. The app has no backend of its own. It does not transmit your page images, the text recognised on them, your document or folder names, or your exported files anywhere, and the usage statistics and crash reports described below never contain them: a crash report shows where in the code a crash happened, not your documents.
• Capture runs in Google's document scanner, not in the app. When you tap Scan, the app opens the Google ML Kit document scanner, a screen provided by Google Play services. The camera is operated inside Google Play services' own process, under Play services' own camera access. PaperLite itself holds no camera permission and never sees the camera feed; it receives only the finished page images, once you confirm them in the scanner, and copies them into its private storage straight away. The scanner also lets you add photos from your gallery from within its own screen.
• Photos are read through the Android Photo Picker. Where the scanner cannot run (for example on a device without Google Play services), and whenever you choose Import photos, you pick the specific photos you want in the Photo Picker. The app is granted access only to those items and does not browse your gallery. If the scanner is unavailable you then straighten each photo yourself with the app's own crop screen, on the device.
• Images shared to the app. When you share one or more images to PaperLite from another app, it reads only the images you shared and turns them into a new document.
• Imported images are stored as clean copies. Every page is decoded, turned upright, reduced to at most 3,508 pixels on its long edge and saved again as a JPEG in the app's private storage. Only the picture is kept: metadata of the original photo, such as the location it was taken at or the camera model, is not copied.
• No storage permission is requested on any Android version. The scanner, the Photo Picker, share intents, MediaStore and the system file picker make one unnecessary.

Saving, sharing and exporting

A scan leaves the app's private storage only when you export it, and only to where you send it:

• Save to device writes the file through MediaStore into Documents/PaperLite (PDFs) or Pictures/PaperLite (JPEG pages) on your device's own storage. On Android 7 to 9, and whenever the shared folder refuses a file, the app saves into its own folder on the device instead; the result screen tells you so, warns that files there are removed if the app is uninstalled, and offers "Save as…".
• Save as… opens the Android system file picker, and the file is written only to the location you choose there. If you choose a cloud storage provider, that provider's own terms and privacy policy apply to the copy you give it.
• Share opens the Android share sheet. The app prepares temporary copies in its private cache for this, and they are deleted before the next share. What the app you share to does with the file is governed by that app.
• Copy page and Copy all text in the page viewer place the recognised text on the Android clipboard, so that you can paste it into another app.

An exported PDF contains your page images and, when searchable, an invisible layer with the recognised text. Its document properties contain the document's title, the creation date and "PaperLite" as the creating application.

Optional PDF password. If you protect a PDF, the password you type is used only to encrypt that one file (AES-128, the PDF standard security handler) while it is written. It exists only in the app's memory while the export screen is open: it is never saved on the device, never sent anywhere and never seen by the developer, so it cannot be recovered if you forget it.

What the app stores locally

Everything below is kept in the app's own private storage on the device, which other apps cannot read, and none of it is sent anywhere:

• your scans: the page images, in the folder docs of the app's private storage;
• the library database: document and folder names, dates, page order and rotation, the OCR language chosen for a document, and the text recognised on each page with its position, plus a search index over that text;
• pages you deleted from a document, kept so that Undo can restore them until you leave that document (at the latest, until the app next starts);
• the queue of background text-recognition jobs that are still pending;
• your theme, text size, language, OCR language, default page size and quality, library sort order, and whether the welcome screen has been completed;
• whether the one-time "remove ads" purchase is active, when a one-hour ad-free period earned with a rewarded ad ends, and a counter of how many interstitial ads have been shown, used to keep ad frequency low;
• if you postpone an app update offered through Google Play, which version that was and when, so the offer is not repeated for a few days.

The app's backup rules (backup_rules.xml for Android 7 to 11 and data_extraction_rules.xml for Android 12 and later) exclude the scans, the library database with the recognised text, the settings files and all preference files from Android cloud backup and from device-to-device transfer, so they are not copied to your Google Drive or to a new phone. Exported files that the app saves into its own folder (Android 7 to 9, or when the shared folder refuses a file) are excluded in the same way, and the temporary copies the scanner hands to the app are deleted as soon as they have been imported. 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, these identifiers and the app's own export folder included. Files you saved to Documents/PaperLite, Pictures/PaperLite or another location with "Save as…" are your own files and stay where you put them.

Scanning and text recognition — Google ML Kit

The app uses two Google ML Kit features, both provided through Google Play services:

• Document scanner — the capture screen described above. Its code is downloaded by Google Play services (the app asks Play services to fetch it during the welcome screen, so the first scan does not wait for it).
• Text recognition (OCR) — reads the text on your pages in the background after every import, with Latin-script, Japanese and Korean models. The script follows the app language and can be changed in Settings or per document.

Both run on your device. Your images and the recognised text are processed locally and are not sent to Google or to the developer. The recognition models are not built into the app: Google Play services downloads them (the app asks for the Latin, Japanese and Korean models to be fetched at installation) and keeps them on the device. Under Google's ML Kit terms, these components may send Google limited metrics about how the ML Kit features are used and how they perform, such as device and app information and response times, to maintain and improve them. These metrics never contain your images or the recognised text.

Advertising — Google AdMob and its mediation partners

The app is free and is supported by ads served through 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. When ads are served, AdMob and Google's advertising partners may collect and process:

Mediation partners

The app also contains the software of two other ad networks, which AdMob can call on through its mediation feature. When the app requests an ad, AdMob may pass that request to one of these partners, and the partner that serves the ad then receives the same categories of data listed in the table above (advertising ID, approximate location derived from your IP address, device information and ad interaction events) and processes it under its own privacy policy:

• Unity Ads — Unity Game Player and App User Privacy Policy
• Liftoff Monetize (formerly Vungle) — Liftoff Privacy Policy

In the answers they publish for Google Play's data safety section, Unity Ads says its software may also collect purchase history, user IDs, app interactions (such as taps inside its ads), app usage times (only when Unity's optimisation features are turned on) and diagnostics, for advertising, analytics, fraud prevention and app functionality; Liftoff Monetize says it collects approximate location, for analytics, app functionality and advertising. The app's data safety section on Google Play includes these answers.

Which partner, if any, serves a given ad is decided by AdMob. Your choices in the consent form described under "Your advertising choices" are passed to these partners through the standard consent signal that Google's consent tool stores on the device.

The app does not request GPS or any location permission, and it does not send your scans, recognised text, document names or file contents to AdMob or to any partner. The developer receives no personal data from AdMob or the partners — only aggregated, anonymous reporting such as impression and revenue totals.

Where ads appear

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

• Banner — at the bottom of the Library and of a document's page grid. Never on the scanner, the crop screen, the page viewer or its text, the export screen, the result screen, Settings or the welcome screen.
• Interstitial (full screen) — at most one, after a "Save to device" or "Save as…" export has finished and before its result is shown. A card first says that your file is saved and that a short ad comes next; the ad plays only when you tap Continue (or press Back), never by itself. Your first two exports never show one, two are always at least three minutes apart, and none is shown before the share sheet or during scanning, text recognition or editing.
• Rewarded (opt-in) — only if you choose "An hour without ads" in Settings or on the result screen: you watch one ad and the app shows no ads for the next hour. It never unlocks or gates any feature.

How Google handles this data is governed by Google's 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

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 scans or their text. Neither service receives your name, your email address or any account details.

When they run. Both services start on the first launch of the app, in every region, before any consent form has been answered: the app does not hold them back until you answer. Outside the EEA, the UK and Switzerland, Analytics runs by default. In the EEA, the UK and Switzerland, once you answer the consent form described below under "Your advertising choices", Analytics follows your answer, both for storing its identifier on your device ("analytics storage") and for using the data for advertising ("ad user data") and ad personalisation; those two advertising uses stay off there until you agree. You can change your answer at any time from Settings → Privacy options; the entry appears where it is required. Crash reports are sent whatever you answer: Crashlytics relies on the developer's legitimate interest in finding and fixing crashes.

The app has no separate switch for the usage statistics or the crash reports. To object to them, write to the address in Contact; uninstalling the app 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 — Google Play Billing

The app offers one optional, one-time, non-consumable purchase that permanently removes ads, available in Settings and on the export result screen. 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. Your handling of payment data by Google is covered by the Google Privacy Policy and Google Play's terms.

Updates — Google Play

The app uses Google Play's In-App Updates library. It asks Google Play whether a newer version of the app is available and, when there is one, lets Google Play offer it to you, download it and install it. It is covered by the Google Privacy Policy.

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, including for the ad partners listed above. Your choice is stored on your device by Google's component and is respected on later launches.

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, search and export your documents, and ads may still be shown in a non-personalised form. Your answer there also applies to Google Analytics for Firebase, as described above; it does not switch off the crash reports.

If you are in a US state with a privacy law

Where a US state privacy law applies (for example in California), the same Google consent tool can show a notice about the use of your information for targeted advertising and let you opt out of its sale or sharing. Where it applies, the Settings → Privacy options entry appears and opens your choices again. Your rights there are described under Privacy rights in US states below.

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. A one-hour ad-free period earned with a rewarded ad stops them for that hour.

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, Android's advertising-services permissions, and permissions to keep background work running. The app asks you for no permission at all while you use it, and it does not request the camera, storage, photos and media, contacts, microphone, location, notifications or account permissions on any Android version. The camera used for scanning belongs to Google Play services, as described above.

Children

This app is a general-purpose utility. It is not directed at children under 13 (or under 16 in the EEA), 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. Your scans, their text and your settings stay on your device until you delete them in the app, clear the app's data or uninstall the app. 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. Data collected by Google through AdMob, ML Kit and Google Play is retained according to Google's own retention schedules, described in the Google Privacy Policy, and data collected by a mediation partner according to that partner's policy, linked above.

Legal bases and your rights

Where the GDPR (EU/UK) applies, the legal basis for personalised advertising, including by the mediation partners, 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 and crash reports rely on the developer's legitimate interest in keeping the app working and understanding, in aggregate, how it is used; in the EEA, the UK and Switzerland, Analytics' storage of its identifier on your device and any advertising use of the data rely on your consent (GDPR Art. 6(1)(a)) once you answer the consent form; until you answer, Analytics already runs from the first launch. Scanning and text recognition are performed on your device at your request, and the developer receives none of that data.

Under the GDPR 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 at any time, and you may lodge a complaint with the data protection authority of your country. Users in Türkiye have the rights described under Users in Türkiye (KVKK) below.

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 concerned, as the party that holds it, using the tools in the policies linked above. For anything else, or for help finding the right route, write to the address below.

Security

Your scans, their text and the library database are kept in the app's private storage, which Android isolates from other apps. The app has no account and no server, so there is no copy of your documents elsewhere that could be exposed. Data sent to Google and to the ad partners travels encrypted (TLS). A PDF you protect with a password is encrypted with AES-128. No method of storage or transmission is perfectly secure; keep your device locked and up to date, and take care where you save or share exported files.

Transfers outside Türkiye and the EEA

The developer works from Türkiye and has no server. The data described in this policy goes from your device directly to the providers below, which process it outside Türkiye and outside the European Economic Area, notably in the United States. The developer reads the usage statistics and crash reports in the Firebase console from Türkiye.

• Google (Google Ireland Limited / Google LLC): AdMob, Google Analytics for Firebase, Firebase Crashlytics, Google Play Billing and the ML Kit metrics — Google's data transfer frameworks, Privacy and security in Firebase;
• Unity (Unity Ads) — Unity Game Player and App User Privacy Policy;
• Liftoff (Liftoff Monetize, formerly Vungle) — Liftoff Privacy Policy.

These providers state in their policies that, for transfers from the EEA, the UK and Switzerland, they rely on safeguards such as the European Commission's Standard Contractual Clauses and, where they are certified, the EU–US Data Privacy Framework. The details are in their policies linked above.

Users in Türkiye (KVKK)

The controller is Burak Gökgöz (BumuStudios), Türkiye. Under Law No. 6698 on the Protection of Personal Data (KVKK) you may apply to the controller to learn whether your personal data is processed and to request information about it; to learn the purpose of the processing and whether the data is used for that purpose; to know the third parties in Türkiye or abroad to whom it is transferred; to have it corrected if it is incomplete or inaccurate, and erased or destroyed under the conditions of KVKK Article 7; to have those corrections and erasures notified to the third parties it was transferred to; to object to a result against you that arises solely from automated analysis of the data; and to claim compensation for damage caused by unlawful processing (KVKK Article 11). You may also withdraw your explicit consent at any time.

Apply first to the controller, by email to bumustudios@gmail.com. Your application is concluded within 30 days at the latest and, as a rule, free of charge (KVKK Article 13). If it is refused, if you find the answer insufficient or if no answer comes in time, you may complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu) within 30 days of learning the answer, and in any case within 60 days of your application (KVKK Article 14). The full information notice in Turkish (KVKK Aydınlatma Metni) is in the Turkish version of this page.

Privacy rights in US states

This section is for residents of California and of the other US states with a consumer privacy law, to the extent those laws apply to the developer.

• What is collected, and from where: identifiers (the advertising ID, the Firebase, Analytics and Crashlytics installation identifiers, and your IP address); internet or other electronic network activity (usage events and ad interactions); approximate geolocation (country or region, derived from the IP address); commercial information (the one-time "remove ads" purchase: product, name and price); device information and crash reports; the ML Kit usage and performance metrics described above. All of it comes from your device, through the app and the software components in it. No sensitive personal information is collected.
• Why: the purposes described above — serving and measuring ads and preventing fraud, keeping the app working and finding crashes, understanding in aggregate how it is used, and processing your purchase.
• Sale and sharing: the developer does not sell personal information for money. The ad components in the app — Google AdMob, Unity Ads and Liftoff Monetize — receive identifiers, network activity and approximate location to serve and measure ads, which can include cross-context behavioural (targeted) advertising. Under California law this counts as "sharing", and other state laws can treat it as a "sale" or as targeted advertising. The developer does not knowingly sell or share the personal information of consumers under 16.
• Your choices: you can opt out of the sale or sharing of your personal information and of targeted advertising: where Google's privacy message applies, through Settings → Privacy options in the app; on any phone, by deleting your advertising ID in Android's Settings → Privacy → Ads; or by writing to us.
• Your rights: to know what personal information is collected, used and disclosed, to access it, and to have it deleted or corrected. Send requests to bumustudios@gmail.com. The records carry only random identifiers, so we may ask for information that lets us find the ones concerned. You may use an authorised agent. If we refuse a request, you can appeal by replying to our answer.
• No discrimination: using these rights does not change how the app works for you or what it costs.
• Retention: as described under "Data retention" above.

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.

The first version of this policy was published with the first release of the app.

The update of 1 November 2026 describes version 1.0.1: the interstitial after a save is now announced by a card and plays only when you tap Continue, and the app no longer shows app-open ads.

The update of 4 November 2026 describes version 1.0.1: AdMob's mediation partners are now only Unity Ads and Liftoff Monetize (see "Mediation partners" under Advertising). The app no longer contains the software of the other ad networks listed before.

A second update on 4 November 2026 names the controller; describes more precisely when the usage statistics and crash reports run (from the first launch, in every region; in the EEA, the UK and Switzerland, Analytics follows your answer in the consent form once you give it); adds the transfers outside Türkiye and the EEA, the rights of users in Türkiye (KVKK) and in US states and the Google Play libraries used for updates; and removes the sentence that treated continued use as acceptance of a revised policy.

Contact

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