LuraPDF for Android

App Privacy Policy

Last updated:

LuraPDF is built so that your documents never leave your phone. This policy covers exactly what the Android app handles, what it sends to third parties, and how you stay in control.

At a glance

  • Files never uploaded

    Every PDF, scan and signature is processed on your phone.

  • No account

    No sign-up, no login, no profile about you.

  • No ads, no data sales

    We do not show ads and we never sell your data.

  • Minimal diagnostics

    Only anonymous usage and crash data, to keep the app stable.

1. Who we are

LuraPDF for Android (the “App”) is developed and published by Metal Devs (“we”, “us”). This policy explains what information the App handles, why, and the choices you have. It applies only to the mobile App. The LuraPDF website has its own privacy policy.

2. Your documents stay on your device

LuraPDF is an on-device PDF toolkit. Scanning, OCR text recognition, signing, form filling, editing, redaction, compression, encryption and conversion all run locally on your phone.

  • We do not operate any server that receives, stores or reads your files.
  • Your PDFs, scanned pages, images, signatures and form entries are never uploaded by the App.
  • Text recognized by OCR stays on your device.
  • Files only leave the App when you choose to share or save them — for example through the Android share sheet or by saving to your Downloads folder.

3. Information stored on your device

To work, the App keeps the following in its private storage on your phone:

  • Documents you create or import, and a local index of them (file name, size, page count, dates).
  • Signatures you save for reuse.
  • Your recent files and app settings, such as light or dark theme.

This data never leaves your device through the App, and we cannot access it. It is removed when you delete it in the App, clear the App’s storage, or uninstall the App. If you have Android backup turned on, Android may include App data in your personal Google backup — that is controlled by your device settings, not by us.

4. Device permissions

Permissions are requested only when you use the feature that needs them, and you can revoke them at any time in Android Settings.

PermissionWhy the App uses it
CameraTo scan paper documents into PDF. Camera images are processed on your device.
NotificationsTo tell you when a file has been saved. Notifications are generated locally.
Storage (Android 9 and older)To save exported files to shared storage on older Android versions.
Files and photos you pickWhen you choose a PDF or image, Android’s system picker gives the App access to that item only.

The App does not request access to your location, contacts, microphone or phone calls.

5. Information collected automatically

To understand which features are used and to find and fix crashes, the App uses two Google services. Neither receives the content or names of your documents on purpose.

Google Analytics for Firebase

  • App usage events, such as first open, sessions, screens viewed and app updates.
  • Device and app information: device model, Android version, app version, language.
  • Identifiers: a Firebase app-instance ID and, where available, the Android Advertising ID.
  • Approximate location (country or region), which Google derives from your IP address. Your precise location is never collected.

Firebase Crashlytics

  • Crash reports and error reports: stack traces, the state of the App when the error happened, device model, Android version and app version.
  • A Crashlytics installation ID, used to count how many devices a crash affects.

Error reports are technical. They are designed to describe what went wrong in our code, not what is in your files, but an error message may occasionally include a file name. We only use reports to fix bugs.

6. Other network requests

  • Fonts. On first launch the App downloads its interface font from Google Fonts and then caches it. As with any web request, Google receives your IP address and basic device information. See the Google Fonts privacy FAQ.
  • Google Play services.The document scanner and text recognition use Google’s on-device ML Kit. Google Play services may download the required component the first time you use these features. Your documents and images are processed on your device and are not sent to Google.

7. How we use information

  • To provide the App’s features on your device.
  • To measure which features are used, so we can improve them.
  • To detect, diagnose and fix crashes and errors.
  • To comply with legal obligations.

Where the GDPR applies, we rely on our legitimate interest in keeping the App stable and improving it to process analytics and crash data.

8. Sharing and selling

  • We do not sell your personal information, and we do not share it for advertising.
  • The App contains no ads and no advertising SDKs.
  • Google acts as our service provider for Firebase Analytics, Crashlytics and Google Fonts, under the Firebase privacy terms and the Google Privacy Policy.
  • We may disclose information if required by law, or to protect our rights or the safety of users.

9. Data retention

DataHow long it is kept
Documents, signatures, settingsOn your device until you delete them or uninstall the App.
Firebase Analytics event dataUp to 14 months, then deleted automatically.
Crashlytics crash reports90 days, then deleted automatically.

10. Your choices and deleting your data

  • Delete individual documents or saved signatures inside the App at any time.
  • Clear everything the App stores on your phone from Android Settings → Apps → LuraPDF → Storage → Clear storage, or by uninstalling the App.
  • Reset or delete your Advertising ID from Android Settings → Privacy → Ads (the exact path varies by device).
  • To ask us to delete analytics or crash data linked to your device, email support@lurapdf.comwith the subject “Data deletion”. Because we hold no account for you, we may ask for your Firebase app-instance ID so we can find the data.

11. Security

Your documents are kept in the App’s private storage, protected by Android’s app sandbox. Analytics and crash data are sent to Google over encrypted connections (TLS). PDFs you password-protect in the App use AES-256 encryption, and we never see or store your passwords. No method of storage or transmission is completely secure, but we design the App so that your documents never need to leave your device.

12. Children

The App is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact us and we will delete it.

13. International transfers

Google may process analytics and crash data on servers outside your country, including in the United States. Google applies safeguards such as the EU Standard Contractual Clauses to these transfers.

14. Your privacy rights

Depending on where you live — including the EU, the UK and California — you may have the right to access, correct, delete, restrict or object to the processing of your personal information, and the right to data portability. Californian residents have the right to know what personal information is collected and to request its deletion; we do not sell or share personal information as those terms are defined under the CCPA.

To exercise any of these rights, email support@lurapdf.com. We will respond within 30 days. You can also lodge a complaint with your local data protection authority.

15. Changes to this policy

We may update this policy when the App changes or when the law requires it. The date at the top of this page shows the latest version. If a change significantly affects how we handle your information, we will highlight it in the App or in the Google Play release notes.

16. Contact us

Questions about this policy or your data? Email support@lurapdf.com. Developer: Metal Devs.