Privacy Policy

1. Introduction

This Privacy Policy explains how the Android application BeamDoc ("BeamDoc", "the app", "we", "our", or "us"), provided by DigitalLead, handles information when you use it. By installing or using BeamDoc, you acknowledge that you have read and understood this Policy.

BeamDoc is designed around a single principle: documents you scan are yours, and they should stay on your device. Scan images, PDFs, OCR text, titles, folders, and search history are never sent to us, Firebase, or ML Kit servers. Off-device processing is limited to Google ML Kit's technical SDK metrics, optional notification registration, and a rating or review that you choose to submit directly to Google Play, as described below.

2. Information We Handle

BeamDoc does not send your document content or personal profile information to us or to any cloud service. Specifically, BeamDoc does not collect or transmit any of the following:

• Your name, email address, phone number, or any other contact details.
• Account information, sign-in credentials, or user profiles (the app does not have accounts).
• The contents of your scans, photos, PDFs, or recognised text.
• Location data (precise or coarse).
• Advertising ID, IMEI, MAC address, or Android ID.
• BeamDoc screen views, taps, sessions, advertising profiles, or behavioural analytics.
• Crash reports, stack traces, or document-content diagnostic logs sent by BeamDoc.
• Contacts, calendar, microphone audio, SMS, or call logs.

Optional notifications: Notifications are off by default. If you enable them in Settings, Firebase Cloud Messaging and Firebase Installations generate and process a random Firebase installation ID (FID) that identifies this installation of BeamDoc, plus the app version and a Firebase user agent containing general device/app metadata. Google states that an FID does not identify a person or physical device. We use it only to deliver BeamDoc product announcements and important app updates. We do not attach scan titles, document IDs, file paths, OCR text, account data, analytics events, or advertising identifiers to it.

Firebase Analytics, Crashlytics, advertising, attribution, and delivery-metrics export are disabled and are not included in BeamDoc. FCM registration is not started until you opt in.

Google ML Kit technical metrics: When you choose on-device OCR, Google states that the ML Kit SDK may collect device and app information, per-installation or device identifiers, latency and other performance metrics, API configuration, input/output sizes, feature version, event types, and error codes for diagnostics and usage analytics. Images, document text, OCR results, titles, filenames, and PDFs are not included. Google states that this technical data is encrypted in transit and is not shared with third parties.

Optional Google Play rating and review: After you have successfully used BeamDoc, Google Play may show its standard, dismissible in-app review card. If you choose to submit a 1–5 star rating or optional written review, Google Play collects that information to create a Play Store review. BeamDoc's app code does not receive the response you enter, and the review API does not tell BeamDoc whether the card was displayed or whether you submitted a review.

3. Permissions and Why We Use Them

BeamDoc requests only permissions needed for features you choose to use.

3.1 Camera (android.permission.CAMERA)

Why: So you can capture photos of documents, receipts, ID cards, whiteboards, and similar items directly inside BeamDoc.

How it is used: The camera preview and captured frames are processed locally on your device. They are written to BeamDoc's private application storage. They are not uploaded, streamed, or shared with us or any third party.

3.2 Photo Picker (no broad photo or storage permission)

Why: So you can import existing images from your gallery into BeamDoc to convert them into scanned documents.

How it is used: Android's system Photo Picker grants BeamDoc access only to the images you select. BeamDoc does not request broad media-library or external-storage permission, and it does not enumerate, index, upload, or share your gallery.

3.3 Notifications — Android 13 and newer (android.permission.POST_NOTIFICATIONS)

Why: To show optional BeamDoc product announcements and important app updates.

How it is used: The permission is requested only after you turn Notifications on in Settings. If you decline, scanning and every document feature continue to work. Turning Notifications off unregisters this app installation from Firebase and requests deletion of its Firebase installation ID.

3.4 Internet (ML Kit models and metrics, optional notifications)

All document detection, edge detection, perspective correction, image enhancement, OCR (text recognition), and PDF generation happen on your device. BeamDoc bundles its document-detection model. Google Play Services may download an on-device OCR model, and ML Kit sends the limited technical SDK metrics described in Section 2 when OCR is used. If, and only if, you enable Notifications, Firebase also uses the internet to register this app installation and deliver messages. None of these flows uploads document images, scans, OCR text, titles, folders, or PDFs.

Scanning, recognising text, organising documents, searching, and exporting PDFs remain available offline after any required on-device model is present. Notifications naturally require a network connection.

4. Data Storage and Security

All data created by BeamDoc is stored locally on your device, in two places:

• App-private internal storage — image files and generated PDFs are saved inside BeamDoc's sandboxed application directory, which by default is not accessible to other apps on a non-rooted device.
• Room (SQLite) database — document metadata such as titles, folder structure, page order, tags, and recognised text is stored in a local Room database file inside that same private application directory.

Your scans and database are never uploaded to a server controlled by us, Firebase, or any other third party. There is no automatic cloud backup performed by BeamDoc itself. When Notifications are enabled, the unrelated Firebase installation ID is stored by Google for message delivery.

Review-card eligibility: BeamDoc stores only local counters and timestamps for completed workflows, the last app version in which a review request was attempted, and the attempted milestone. This state is used solely to avoid interrupting you or asking too often. It never contains a rating or review, and BeamDoc does not transmit it. "Clear all data" and uninstall remove it.

Note about Android system backup: Android may, at the operating-system level and at your direction, include app data in your Google account backup. That behaviour is controlled entirely by Android settings on your device, not by BeamDoc, and any such backup is governed by Google's privacy terms. By default, BeamDoc opts out of cloud backup and device-to-device transfer.

Security: Because document content never leaves your device through BeamDoc, the security of your scans depends primarily on the security of your device itself — your screen lock, full-disk encryption (enabled by default on modern Android), and the apps you grant permissions to. Google states that ML Kit technical metrics and Firebase notification-registration data are encrypted in transit. We recommend keeping your device updated, using a strong screen lock, and only sharing exported documents through channels you trust.

5. Children's Privacy

BeamDoc is a general-purpose productivity tool and is not directed at children under the age of 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children. ML Kit technical metrics and optional notification registration use only the technical data described in Section 2.

If you are a parent or guardian and have a privacy concern, contact us using the details below. Notifications can be disabled and their Firebase registration deleted from Settings, and all local document data can be erased with "Clear all data".

6. Data Sharing

BeamDoc does not sell, rent, license, or transfer data to advertisers, data brokers, or marketing partners. Google processes the ML Kit technical metrics described in Section 2 to diagnose, maintain, and improve ML Kit. When Notifications are enabled, Google also acts as our service provider for Firebase Cloud Messaging and processes the technical registration data described in Section 2.

Document content leaves your device only when you deliberately choose to share an exported document — for example, by tapping share and sending a PDF via email, a messaging app, or another app of your choice. In that case, the document leaves BeamDoc under your control, and the receiving app's privacy practices apply.

If you voluntarily submit a Google Play rating or written review, Google Play uses it for a public Play Store review. During a closed test, Google may instead make the review privately visible to the developer. Your scan content and local review-eligibility state are not included.

7. Data Retention and Deletion

You are in full control of how long your data lives in BeamDoc. There are three ways to remove data:

1. In-app delete — open any document, page, or folder in BeamDoc and use the delete option to remove it. Deletion is immediate and applies to both the file and its database entry.
2. Settings → "Clear all data" — removes every document, page, thumbnail, OCR result, database row, and local review-request counter created by the app on the device, disables notifications, unregisters the app from FCM, and requests deletion of its Firebase installation ID.
3. Uninstall the app — uninstalling BeamDoc from Android removes the app's private storage and its Room database, deleting everything BeamDoc has saved. (Documents you previously exported and shared elsewhere will remain wherever you sent them.)

We do not hold a server copy of your scans. Google states that after a Firebase installation ID deletion request, data tied to that identifier is removed from Firebase live and backup systems within 180 days.

Clearing BeamDoc data does not delete a rating or review you submitted to Google Play. You can edit or delete that review through your Google Play Store or Google Account.

8. Third-Party Services

BeamDoc uses its bundled model for document detection and Google ML Kit for on-device text recognition (OCR). Images and recognised text are processed on-device and are not sent to Google's servers. ML Kit does send the limited technical SDK metrics listed in Section 2 for diagnostics and usage analytics when OCR is used.

For more information about ML Kit, see Google's terms and documentation: https://developers.google.com/ml-kit/terms.

BeamDoc optionally uses Firebase Cloud Messaging and Firebase Installations for notifications. Firebase auto-initialisation is disabled until opt-in, Google Analytics is disabled, and BeamDoc does not export message-delivery metrics to BigQuery. See Firebase privacy and security information.

BeamDoc uses the Google Play In-App Review library to request Google's standard review card at infrequent, post-task moments. Google Play controls whether the card appears and handles any rating or review you submit. See Google Play In-App Review documentation.

BeamDoc does not include Firebase Analytics, Crashlytics, advertising networks, attribution SDKs, social-login SDKs, or a BeamDoc behavioural-analytics service. This does not disable the technical metrics that ML Kit itself processes as described above.

9. Your Rights (GDPR, CCPA / CPRA, and Other Privacy Laws)

Privacy laws such as the EU General Data Protection Regulation (GDPR), the UK GDPR, the California Consumer Privacy Act as amended by the CPRA, and similar laws around the world give individuals certain rights over their personal data. These typically include the right to access, correct, delete, restrict processing of, port, or object to the processing of personal data, and the right not to be discriminated against for exercising those rights.

We do not have accounts or a server database linking an installation to your identity. Most access, correction, and portability requests therefore have no user profile for us to return. Specifically:

• We have no account-linked profile or server copy of your documents to provide in response to an access or portability request.
• Local document data can be corrected or erased directly in the app.
• The optional Firebase installation ID can be unregistered and deleted through Notifications or "Clear all data" in Settings.
• ML Kit's technical metrics are processed by Google without document content; BeamDoc does not receive a user profile or record that it can retrieve, correct, or delete.
• We do not "sell" or "share" personal information for cross-context behavioural advertising.
• We do not perform automated decision-making or profiling about you.

The data BeamDoc does handle — your scans, OCR text, and metadata — is stored only on your device and is fully under your control through the in-app delete tools and "Clear all data" option described in Section 7.

If you have any privacy concern, question, or complaint, you may contact us at the address in Section 11. EU/EEA and UK users also have the right to lodge a complaint with their local data protection supervisory authority.

10. Changes to this Policy

We may update this Privacy Policy from time to time, for example to reflect changes to the app, to the permissions Android requires, or to applicable laws. When we do, we will update the "Last updated" date at the top of this page and publish the new version at the same URL.

If a future change introduces any material new data practice — for example, optional cloud sync — we will describe that change clearly in the updated Policy and, where required by law, request your consent before the new practice applies to you.

11. Contact Us

If you have any questions about this Privacy Policy or about how BeamDoc works, please contact:

Muhammad Irfan
Email: irfanokr786@gmail.com