1. Who we are
Safha is developed and published by Uvro Labs, an independent app studio. This policy explains what the Safha app (“Safha”, “the app”) does with data, what it deliberately does not do, and the choices you have. For questions, contact us at uvrolabs@gmail.com.
2. Your documents stay on your device
Everything you scan, import, edit, or export with Safha is processed and stored locally on your device:
- Scanned pages, imported photos and PDFs, and every edited version of them.
- Document names, folders, tags, favorites, and drafts.
- Text recognized from your pages (OCR). Recognition runs on your device.
- PDFs, images, and other files created when you export or share.
- Your in-app settings.
Safha has no server for this content. We cannot see, receive, or recover your documents, and we do not collect them, transmit them, or use them for any purpose — including advertising or training.
3. What leaves your device, exactly
Safha uses two services from Google LLC (“Firebase”) to keep the app reliable:
- Firebase Crashlytics — if the app crashes or hits an internal error, it sends a technical report: the stack trace, the app’s internal state at the time (for example which screen was open), app version, device model, and operating system version.
- Google Analytics for Firebase — anonymous usage events, such as “a document was scanned (3 pages)”, “a PDF was exported”, or “the compress tool was opened”, plus which screens are used. Events contain counts and feature names only.
These reports never include your content. No page images, no recognized text, no document names, no file paths, and nothing you type. We enforce this in the app’s code: reporting is routed through a single component that only accepts counts and fixed feature names.
To make these services work, the Firebase SDKs collect limited technical identifiers on our behalf:
| Data | Purpose | Service |
|---|---|---|
| Crash logs and stack traces | Diagnosing and fixing crashes | Crashlytics |
| Diagnostic device info (model, OS version, free memory at crash) | Reproducing device-specific bugs | Crashlytics |
| App usage events and screen views | Understanding which features matter and which fail | Analytics |
| App-instance ID and Crashlytics installation UUID (random identifiers tied to the installation, not to you) | Grouping reports from the same install | Both |
| Coarse location derived from a masked IP address (country/region level; the IP itself is not stored) | Aggregate regional statistics | Analytics |
On Android, Safha explicitly disables Advertising ID collection. Safha shows no ads and does not track you across other companies’ apps or websites. On iOS, Safha does not use the App Tracking Transparency framework because no tracking, as Apple defines it, takes place.
Data sent to Firebase is encrypted in transit (TLS). Google processes it on our behalf as a service provider under the Firebase Data Processing and Security Terms; Google’s own privacy policy is at policies.google.com/privacy. We require that this third party protects your data to the same standard described in this policy, and we share nothing with anyone else. We do not sell any data.
4. Your choices and controls
- Turn diagnostics off: Settings → Privacy & security → “Share usage and crash reports”. Switching it off stops both Analytics and Crashlytics collection on your device. The scanner works exactly the same either way.
- Delete your documents: deleting a document in Safha moves it to the in-app Trash; emptying the Trash (or letting its retention window expire, 7–90 days, configurable) permanently removes the document, its pages, and its thumbnails from your device. Uninstalling the app removes all app data stored by Safha on the device.
- Request deletion of diagnostics: crash and usage data is not linked to your name or any account, so we usually cannot single out “your” records. If you contact us at uvrolabs@gmail.com we will help, including deleting analytics data for an app instance where Firebase supports it.
5. Permissions Safha asks for, and why
| Permission | When it’s requested | Why |
|---|---|---|
| Camera | The first time you start a scan | Capturing document pages. Images go straight into your local library. |
| Photos (picker) | When you import from your gallery | Safha uses the system photo picker, which shares only the photos you select. It does not read your photo library. |
| Files | When you import or save a file | The system file picker shares only the files you choose. |
| Photo library (add only) | When you save pages to Photos | Writing the images you chose to export. |
| Notifications | Only if you opt in (draft reminders, “notify me” for upcoming tools) | Local notifications scheduled on your device. There is no push server. |
| Face ID / biometrics | Only if you enable the app lock or lock a document | Authentication happens entirely in the operating system; Safha only learns “unlocked or not”. |
Declining any permission never blocks unrelated features.
6. Purchases
Safha Premium is sold through Apple’s App Store and Google Play billing. Payment details are handled entirely by Apple or Google; Safha never sees your payment information. The app receives only the store’s confirmation of what you are entitled to. Purchase outcomes (for example “purchase completed” or “restore succeeded”) are counted in our anonymous usage statistics without any payment details.
7. Data retention
- Your documents: kept on your device until you delete them or uninstall the app. We hold nothing.
- Crash reports (Crashlytics): retained by Firebase for 90 days.
- Usage statistics (Analytics): identifier-linked event data is retained by Firebase for up to 14 months; aggregate statistics may be kept longer in de-identified form.
8. Security
Your documents are stored in the app’s private storage area, protected by your device’s operating-system sandboxing and whatever device encryption and screen lock you use. Diagnostics are transmitted over encrypted connections (HTTPS/TLS). No system is perfectly secure, and we avoid promising otherwise — but the most effective protection in Safha’s design is that your documents are never transmitted at all.
9. Children
Safha is a general-audience utility and is not directed at children under 13. We do not knowingly collect personal information from children; the app collects no personal profile from anyone.
10. Your rights
Depending on where you live (for example under the GDPR or CCPA), you may have rights to access, correct, delete, or object to the processing of personal data. Because Safha keeps your content on your device and our diagnostics are not linked to your identity, most of these rights are already in your hands — but we will help with any request: uvrolabs@gmail.com. You also have the right to complain to your local data-protection authority.
11. Changes to this policy
If we change what the app actually collects — for example, if a future optional cloud-backup feature is added — we will update this policy first, change the effective date above, and explain the change in the app before it applies. We will never silently expand data collection.
12. Contact
Uvro Labs — privacy contact: uvrolabs@gmail.com. We answer privacy questions and requests from this address. See also our contact and support page.