← Back to Sezarr ยท Mirza Games
PDF Maker Privacy Policy
Last updated: 7 October 2026 (usage statistics with Firebase Analytics, from version 1.0.2)
PDF Maker is an Android app published by Mirza Games ("we", "us"). This policy explains what the app does with your data.
The short version
- Your files stay on your phone. The app does not upload your PDFs, photos, scans, signatures or text to us or to anyone else. All the work is done on your phone.
- There is no account and no login. We run no server that receives your data. The app only downloads a public list of exam photo and signature sizes from our website (see below).
- The only data that leaves your phone is sent by parts made by other companies, listed below: Google Play (purchases), Google ML Kit through Google Play services (scanning and reading text), Firebase Crashlytics (crash reports), Firebase Analytics (usage statistics, from version 1.0.2) and AppLovin (ads, once ads are switched on).
- Usage statistics count which tools are used and whether they worked. They never contain your files, file names, page text or pictures.
Your files
PDF Maker works on files you choose with the Android file and photo pickers, on pictures you take with the Google document scanner, or on files another app shares with it. It asks for no storage, camera, contacts or location permission.
- Everything the app makes (reduced PDFs, merged PDFs, photos, passport photos, text files) is saved in the app's own private folder, shown in the app as "My files". Other apps cannot read that folder.
- When you tap "Save to Downloads", the app copies that file into the Downloads/PDF Maker folder of your phone. When you tap "Share", the file goes to the app you pick in the Android share sheet. That is your choice and happens only then.
- Files shared to the app from other apps are copied into the app's temporary cache for the work and cleaned up later.
- The app does not back up to Google Drive: Android Auto Backup is switched off for this app. Your results are not copied to a new phone; Pro comes back through Google Play (Restore purchases).
- Deleting a file in "My files", clearing the app's storage or uninstalling the app removes the app's copies. Copies you saved to Downloads or shared stay where you put them.
Scanning and text reading (OCR)
- Scan to PDF uses Google's document scanner, which is part of Google Play services. The scanning happens on your phone.
- Text from image uses Google ML Kit text recognition through Google Play services. The text is read on your phone; your picture is not sent to us. Google Play services downloads the text-recognition model once, and Google may collect basic usage and performance information about this service under Google's own terms.
Exam size list
To keep the exam presets (for example SSC, railway, banking, UPSC, NEET, PAN and passport photo and signature sizes) up to date without an app update, the app may download a small public file, mirzagames.com/data/pdf-presets.json, from our website. This is a plain download: the app sends nothing about you, your files or your use of the app, and no account or ID is attached. Like any website request, our hosting provider sees your IP address and basic technical details (such as the time of the request) in standard server logs, which are used only to run and protect the website. If the download fails, the app uses the list built into it. Any sizes you change yourself stay on your phone.
Purchases
Pro can be bought in the app. Payment is handled by Google Play Billing; we never see your card or payment details. The app keeps only a local note on your phone that Pro is on (for example the end date of a 7-day pass). Subscriptions renew automatically until you cancel them in Google Play (Play Store > Payments and subscriptions > Subscriptions).
Crash reports
The app sends crash reports to Firebase Crashlytics (Google) so we can fix bugs. A report contains technical information about the error and your phone (model, Android version, app version, a crash log and a random Crashlytics installation ID). It contains no files and no file names. Crash reports run in every copy of the app and cannot be turned off in the app.
Usage statistics (Firebase Analytics)
From version 1.0.2 the app uses Google Analytics for Firebase to count how the app is used, so we can see which tools people need and where they fail. It records events such as "the app was opened", "a PDF was made from 3 pictures taken with the camera", "a PDF was reduced to 196 KB with a 200 KB target in 5 seconds", "an exam size preset was used (by its preset ID, for example ssc_photo)", "a file was saved or shared", "a job failed because the file was too big" and "the review card was shown". The app also records the screen and session information Firebase collects by default (for example the first open, session start, app version, device model, Android version, language and country), any in-app purchases made through Google Play, and a random app-instance ID.
- Events carry only a tool name, counts, sizes, times and short codes. They never carry your files, file names, folder names, the text of your pages, pictures or signatures. The app checks this before anything is sent.
- Analytics does not read your advertising ID in this app and sends no ad-personalisation signals. Google derives an approximate country or city from your IP address; the IP address itself is not stored by Google Analytics.
- The data is used only for analytics: to improve the app and fix problems. It is not sold and not used for ads.
- Google keeps Analytics data for the retention period set for our Firebase project (14 months at most). See firebase.google.com/support/privacy.
Ads
Free users may see ads; Pro removes them. While ads are not switched on in a version of the app, no ad code runs and no ad request is made. When ads are on, the app uses AppLovin MAX, which works with ad networks. The ad SDKs can collect your advertising ID, approximate location (from your IP address), information about how ads are shown and used, and diagnostic data, to show ads, measure them and prevent fraud. In the EEA, the UK and other regions where the law asks for it, the app first shows a consent form, and you can open it again in Settings (Ad privacy choices). You can reset or delete your advertising ID in Android settings at any time.
Children
PDF Maker is not directed at children under 13, and we do not knowingly collect data from them.
Third parties
How to request deletion of your data
PDF Maker has no accounts, and your files never leave your phone, so there is nothing of yours for us to delete on a server. To remove data:
- Files, settings and Pro status on your phone: delete the files in "My files", clear the app's storage, or uninstall the app.
- Crash data and usage statistics (Crashlytics installation ID, Analytics app-instance ID, device model, Android version, crash logs and usage events) are held by Firebase. To have them deleted, email sezarr.com@gmail.com with the subject "PDF Maker data deletion request" and your device model. We delete the crash and usage data linked to your app installation within 30 days and confirm by email.
- Advertising identifiers are controlled by Android. Reset or delete your advertising ID in Android Settings > Google > Ads. Once ads are switched on, AppLovin handles requests about the advertising data it holds under its own privacy policy.
- Purchase records are held by Google Play under its own policy.
Contact
Email: sezarr.com@gmail.com
Changes
We will update this page when the policy changes and note the date above.