Paze · Privacy policy

udyan.me

Privacy 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:

WhatWhere it goesCan you turn it off?
Anonymised crash reports and usage eventsGoogle Firebase (Crashlytics, Analytics)Not currently in-app; see §11
Advertising requestsGoogle AdMobPersonalisation follows your consent choice; see §6
A download request for an OCR language you chooseGitHub (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:

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:

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

PermissionWhy it is neededData leaving the device
CAMERAScan documents, QR codes and barcodes. Requested only when you open the scanner.No: frames are processed on the device and never uploaded
RECORD_AUDIORecord 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
INTERNETAd requests, diagnostics, and OCR language downloadsYes: see §3.2, §3.3, §6
ACCESS_NETWORK_STATECheck connectivity before network requestsNo
WAKE_LOCK, FOREGROUND_SERVICEDeclared 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 permissionsDeclared by the Google Mobile Ads SDK for ad delivery and measurementYes: see §6
Install Referrer serviceDeclared by Firebase Analytics to attribute the install sourceYes: 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

PurposeData usedLegal basis (GDPR Art. 6)
Provide the PDF, scanning and OCR features you requestLocal data (§3.1), OCR downloads (§3.3)Contract — Art. 6(1)(b)
Keep the app stable and fix crashesCrash reports (§3.2)Legitimate interests — Art. 6(1)(f)
Understand which features are used, in aggregateAnalytics events (§3.2)Legitimate interests — Art. 6(1)(f)
Serve non-personalised advertisingAd request data (§6)Legitimate interests — Art. 6(1)(f)
Serve personalised advertisingAdvertising 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:

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:

See Google's Privacy Policy and How Google uses information from sites or apps that use our services.

6.3 Consent and your choices

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

ServiceRoleDataPolicy
Google AdMob / Google Mobile Ads SDKAdvertising delivery and measurement§6.2https://policies.google.com/privacy
Google User Messaging Platform (UMP)Consent collection and storageConsent statehttps://policies.google.com/privacy
Firebase CrashlyticsCrash diagnostics§3.2https://firebase.google.com/support/privacy
Firebase AnalyticsAggregate usage analytics§3.2https://firebase.google.com/support/privacy
Google Play (In-App Review, Install Referrer)Rating prompt, install attribution and app distributionHandled by Googlehttps://policies.google.com/privacy
GitHubHosts the public OCR language files§3.3https://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

DataRetention
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 reportsRetained by Google per Firebase Crashlytics defaults (currently 90 days)
Analytics eventsRetained by Google per the configured Firebase Analytics retention window
Advertising dataRetained 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:

You want to…Do this
Change ad consentPaze Settings → Ad privacy options (shown where a choice applies)
Reset your advertising identifierAndroid Settings → Privacy → Ads → Delete advertising ID
Delete everything Paze holds locallyAndroid Settings → Apps → Paze → Storage → Clear data, or uninstall
Access, delete, or object to diagnostic dataE-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

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.