Paze · Privacy policy
udyan.mePrivacy Policy for Paze
Effective Date: 7 November 2026
Last Updated: 13 November 2026
Applies to: Paze for Android (package com.ironfist.paze), distributed through Google Play.
1. Summary
Paze is a PDF reader, editor, converter and document scanner that does its work entirely on your device. It has no user accounts, no login, and no Paze-operated server. Your documents, scans, signatures, annotations, voice notes and file names are processed locally and never reach us.
Only these things leave your device:
| What | Where it goes | Can you turn it off? |
|---|---|---|
| Anonymised crash reports and usage events | Google Firebase (Crashlytics, Analytics) | Not currently in-app; see §11 |
| Advertising requests | Google AdMob | Personalisation follows your consent choice; see §6 |
| A download request for an OCR language you choose | GitHub (public Tesseract language files) | Yes — don't download OCR languages |
We do not sell personal information, and we do not share it for cross-context behavioural advertising as those terms are defined under the CCPA/CPRA.
2. Who We Are (Data Controller)
Developer: IronFist
Contact e-mail: ironfist.apps@gmail.com
Postal address: Gujarat, India.
Website: https://udyan.me
For privacy questions or to exercise any right in §11, contact the e-mail above. We aim to respond within 30 days.
3. Data We Collect
3.1 Data that never leaves your device
Paze stores the following in its private app storage. It is not transmitted to us or to any third party:
- Your documents and everything you do to them: viewing, annotating, filling forms, signing, redacting, merging, splitting, compressing, converting and OCR. All PDF processing runs in on-device engines (MuPDF, Ghostscript, Tesseract).
- Camera frames and scans from the document scanner, and the text of QR codes and barcodes you scan
- Voice notes you record: audio is captured only while you are recording, saved inside the PDF you are annotating, and played back on the device
- Your saved signatures and initials, the recent-files list, favourites, private page bookmarks, open tabs, thumbnails and reading positions
- App settings (theme, page colour, reading layout, keep-screen-on, installed OCR languages)
- Ad frequency counters (see §6.4)
Paze opens files only through the Android system file picker or when you share or open a file with Paze. It does not scan your storage. Files you save go to the location you choose. Uninstalling the app removes its private data. Files you saved elsewhere remain until you delete them.
3.2 Diagnostics and analytics (Google Firebase)
Paze uses Firebase Crashlytics and Firebase Analytics. Collection is disabled in debug builds and enabled only in the release build distributed on Google Play.
Collected:
- Crash reports: the error type and stack trace, the name of the tool in use (for example
compress), Android version, device model and app version. Error messages and document contents are not sent. - Analytics events, from a fixed list:
open: file type and a page-count rangemode: the viewer mode chosenoutput: tool, number of files, file type and a size rangesetting: which setting changed and its new value- Ad-lifecycle events (
ad_shown,ad_missed,ad_failed,ad_impression)
- Firebase app-instance ID: a pseudonymous identifier for this installation, reset when you clear app data or uninstall
- Install source information via the Google Play Install Referrer
We do not receive: file names, folder paths, document text or images, scanned codes, signatures, or anything you type into a document.
3.3 OCR language downloads
When you choose to install an OCR language, Paze downloads that language's public Tesseract data file from GitHub (github.com/tesseract-ocr/tessdata_fast). As with any web request, GitHub receives your IP address and the name of the file requested. No document content is sent. Recognition then runs fully offline.
3.4 Advertising data
See §6.
3.5 Data we do not collect
Paze does not collect location, contacts, calendar, SMS or call logs, photos from your gallery, health or financial data, or any account or profile information. Microphone audio is recorded only for voice notes you start, stays in your document, and is never sent to us or any third party. There is no sign-up, and we never ask for your name or e-mail.
4. Android Permissions
| Permission | Why it is needed | Data leaving the device |
|---|---|---|
CAMERA | Scan documents, QR codes and barcodes. Requested only when you open the scanner. | No: frames are processed on the device and never uploaded |
RECORD_AUDIO | Record voice notes on a PDF. Requested only the first time you add a voice note. | No: audio is saved in your document on the device and never uploaded |
INTERNET | Ad requests, diagnostics, and OCR language downloads | Yes: see §3.2, §3.3, §6 |
ACCESS_NETWORK_STATE | Check connectivity before network requests | No |
WAKE_LOCK, FOREGROUND_SERVICE | Declared by the bundled Google libraries (Firebase, Mobile Ads) so they can finish background work such as sending a queued crash report. Paze itself runs no foreground service. | No, by itself |
com.google.android.gms.permission.AD_ID and Android Privacy Sandbox ad permissions | Declared by the Google Mobile Ads SDK for ad delivery and measurement | Yes: see §6 |
| Install Referrer service | Declared by Firebase Analytics to attribute the install source | Yes: see §3.2 |
Paze requests no storage permissions and does not request MANAGE_EXTERNAL_STORAGE ("All files access"). It reads only the files you pick through the system picker.
5. How and Why We Use Data
| Purpose | Data used | Legal basis (GDPR Art. 6) |
|---|---|---|
| Provide the PDF, scanning and OCR features you request | Local data (§3.1), OCR downloads (§3.3) | Contract — Art. 6(1)(b) |
| Keep the app stable and fix crashes | Crash reports (§3.2) | Legitimate interests — Art. 6(1)(f) |
| Understand which features are used, in aggregate | Analytics events (§3.2) | Legitimate interests — Art. 6(1)(f) |
| Serve non-personalised advertising | Ad request data (§6) | Legitimate interests — Art. 6(1)(f) |
| Serve personalised advertising | Advertising ID and ad interaction data (§6) | Consent — Art. 6(1)(a) |
Where we rely on legitimate interests, we have assessed that our interest in operating and improving a free app does not override your rights. One reason is that the diagnostics we receive contain no document data. You may object at any time (§11).
6. Advertising
6.1 What we use
Paze is free and supported by advertising from Google AdMob (publisher ID pub-5764447516567914). Ads appear in these places:
- Banner ads on the recent-files screen and some tool screens
- Native ads in the recent-files list and in Settings
- Occasional full-screen ads between tasks and when returning to the app
- An optional rewarded ad you can choose to watch for an ad-free hour
Ads never appear during your first session after install. Full-screen ads are limited per session and per day.
6.2 What advertising partners may collect
Google and its ad partners may collect and process:
- Advertising ID (a resettable identifier you control in Android Settings)
- IP address, and coarse location inferred from it
- Device and app information (model, OS version, app package, screen size)
- Ad interactions: impressions, clicks and viewability
- Signals used for frequency capping, fraud prevention and measurement
See Google's Privacy Policy and How Google uses information from sites or apps that use our services.
6.3 Consent and your choices
- In the EEA, UK and Switzerland, Paze shows Google's certified User Messaging Platform (UMP) consent form before any ad is requested. The form is compatible with the IAB Transparency & Consent Framework. If you decline, you still see ads, but they are non-personalised.
- In US states with applicable privacy laws, Paze shows the corresponding UMP regulations message.
- Where a privacy choice applies to you, you can change it at any time in Settings → Ad privacy options.
- Independently of Paze, you can delete or reset your Advertising ID in Android Settings → Privacy → Ads, and manage Google-wide ad settings at adssettings.google.com.
The Google Mobile Ads SDK starts only after the consent state has been resolved. Paze is not tagged as child-directed (see §9).
6.4 Ad frequency counters
To limit how often ads appear, Paze stores a few numbers on your device: launch count, ads shown today, the time of the last ad, and the end of any ad-free period. They are never transmitted and are erased when you clear app data.
7. Third Parties and Processors
| Service | Role | Data | Policy |
|---|---|---|---|
| Google AdMob / Google Mobile Ads SDK | Advertising delivery and measurement | §6.2 | https://policies.google.com/privacy |
| Google User Messaging Platform (UMP) | Consent collection and storage | Consent state | https://policies.google.com/privacy |
| Firebase Crashlytics | Crash diagnostics | §3.2 | https://firebase.google.com/support/privacy |
| Firebase Analytics | Aggregate usage analytics | §3.2 | https://firebase.google.com/support/privacy |
| Google Play (In-App Review, Install Referrer) | Rating prompt, install attribution and app distribution | Handled by Google | https://policies.google.com/privacy |
| GitHub | Hosts the public OCR language files | §3.3 | https://docs.github.com/site-policy/privacy-policies |
We use no other processors, and no other SDKs for attribution, mediation, tracking or profiling.
Read aloud uses the text-to-speech engine installed on your device. Paze passes the text to that engine on the device. If you have chosen an engine that works online, its own privacy policy applies.
8. Data Retention
| Data | Retention |
|---|---|
| Documents, signatures, voice notes, settings, recent files, favourites and bookmarks (on device) | Until you delete them, clear app data, or uninstall |
| Ad frequency counters (on device) | Until app data is cleared |
| Crash reports | Retained by Google per Firebase Crashlytics defaults (currently 90 days) |
| Analytics events | Retained by Google per the configured Firebase Analytics retention window |
| Advertising data | Retained by Google per its own policies |
We do not run a database of our own, so we hold no copy of your data beyond what Google retains for us in the Firebase and AdMob consoles.
9. Children's Privacy
Paze is a general-audience productivity app and is not directed to children. It is not part of Google Play's Designed for Families programme. We do not knowingly collect personal information from children under 13, or under the age of digital consent where you live (up to 16 in parts of the EEA). If you believe a child has used the app and want associated data removed, contact us (§2).
10. International Transfers
Google and GitHub process data in the United States and other countries. Personal data transferred out of the EEA, UK or Switzerland is covered by the European Commission's Standard Contractual Clauses. Where applicable, the EU-US / UK / Swiss-US Data Privacy Framework also applies.
11. Your Rights
Depending on where you live, you may have the right to:
- Access the personal data held about you
- Rectify inaccurate data
- Erase your data ("right to be forgotten")
- Restrict processing, or object to it, including processing based on legitimate interests
- Data portability
- Withdraw consent at any time, without affecting processing done before withdrawal
- Opt out of sale/sharing and of targeted advertising under the CCPA/CPRA and comparable US state laws (Paze does not sell personal information)
- Non-discrimination for exercising any of these rights
- Lodge a complaint with your local supervisory authority
| You want to… | Do this |
|---|---|
| Change ad consent | Paze Settings → Ad privacy options (shown where a choice applies) |
| Reset your advertising identifier | Android Settings → Privacy → Ads → Delete advertising ID |
| Delete everything Paze holds locally | Android Settings → Apps → Paze → Storage → Clear data, or uninstall |
| Access, delete, or object to diagnostic data | E-mail the address in §2 |
The diagnostics we receive are pseudonymous (§3.2), so we may be unable to link them to you. In that case, under GDPR Art. 11, we may ask for more information to find your data, or explain why we cannot.
12. Security
- Your documents are processed on your device. There is no Paze server that stores them, so there is no central copy to breach.
- All traffic to Google and GitHub uses TLS.
- Password-protected PDFs are opened and encrypted locally. Passwords are never transmitted or stored by us.
- Links found in scanned QR codes open only after you confirm, and only for web, mail and map links.
- Release builds are code-shrunk and obfuscated.
No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
13. Changes to This Policy
We may update this policy as the app or the law changes. Changes will update the Last Updated date above. Significant changes will also be noted in the app or in the Google Play release notes.
14. Contact
Developer: IronFist
E-mail: ironfist.apps@gmail.com
Address: Gujarat, India.
Website: https://udyan.me
If you are in the EEA or UK and are dissatisfied with our response, you may complain to your national data protection authority.