Legal Documentation • Audited Against Codebase
Privacy Policy
Effective Date: Pending Production Release Sign-off • Package: dev.syaahi.app (v1.0)
1. Summary: Two Clear Operational Modes
Syaahi is engineered offline-first. Rather than claiming “zero data is ever processed anywhere,” this policy distinguishes honestly between:
- Core Android App v1.0 (Strictly On-Device): In the audited Android build (
dev.syaahi.appv1.0),android.permission.INTERNETis explicitly removed at manifest merge usingtools:node="remove", andandroid:allowBackup="false"is enforced. Camera captures, gallery images, Hindi/English OCR text, PDFs, ZIPs, QR codes, and saved toolchains stay locally on your device. - Website & Optional Companion Cloud Services (Opt-In / Submitted Data): Visiting this website's Support & Feedback form or using future optional account/notification features processes specific fields through our backend infrastructure described below.
2. Data Processed On-Device vs. Optional Cloud Paths
| Surface / Feature | Data Processed | Where Processed | Purpose & User Control |
|---|---|---|---|
| Document Scanner, OCR & PDF/Image/ZIP/QR Tools | Selected photos, camera frames, extracted Devanagari/Latin text, generated PDFs/ZIPs/QRs | On-device storage & Room database (Downloads/Syaahi) | Pure local utility. You can delete individual files anytime or clear history inside Settings. |
| Local Preferences & App Lock | Theme mode, preferred language, saved local profile label, biometric lock toggle | Android DataStore Preferences & Android Keystore / BiometricPrompt | UI customization & local lock. Biometric templates never leave Android OS hardware security. |
Public Website Contact Form (/contact) | Inquiry type, subject, description, optional contact email, optional app version string, locale | Vercel serverless proxy → Backend PostgreSQL database | Triages bug reports, feature requests, support questions, and privacy/deletion inquiries. |
| Optional User Accounts (when enabled) | Email address, display name, Argon2id password hash, verification status, session refresh metadata | Backend PostgreSQL database (TLS in transit) | Optional sign-in without gating offline document tools. Can be revoked or deleted permanently. |
| Optional Device & FCM Notifications (when enabled) | App-generated UUID, Android OS/app version, FCM registration token, inbox view/dismiss/click flags | Backend PostgreSQL & Firebase Cloud Messaging | Delivers service announcements reliably and stops repeated popups after dismissal. |
3. Audited Android Manifest Permissions
Every permission declared in app/src/main/AndroidManifest.xml is listed below alongside its offline fallback:
| Android Permission | Purpose | Denial / Fallback Behavior |
|---|---|---|
android.permission.CAMERA | Captures live pages in the Document Scanner screen only when the user opens Camera capture. | Users can decline Camera permission and select existing images via Choose from Gallery. |
READ_MEDIA_IMAGES / READ_MEDIA_VIDEO / READ_EXTERNAL_STORAGE (<= API 32) | Allows picking photos and media for OCR, PDF generation, Batch Studio, and image filters. | System Storage Access Framework (SAF) document picker works on an explicit file-by-file basis. |
WRITE_EXTERNAL_STORAGE (<= API 29) | Writes exported PDF, image, QR, and ZIP outputs on legacy Android 8–10 devices; modern devices use scoped Downloads/Syaahi & MediaStore. | Falls back cleanly to app-private external files directory if Downloads write conflicts occur. |
android.permission.POST_NOTIFICATIONS | Requested contextually for local background WorkManager progress/completion notices. | App startup never forces notification permission; all features run normally if denied. |
android.permission.USE_BIOMETRIC | Powers optional on-device BiometricPrompt app lock configurable inside Settings. | Disabled by default; zero biometric templates leave the Android Keystore/Biometric API. |
android.permission.VIBRATE | Subtle tactile feedback on scanner edge snapping and UI controls. | Controlled automatically by Android system haptics settings. |
android.permission.INTERNET (tools:node="remove") | Explicitly removed during manifest merge to neutralize transitive ML Kit telemetry transport. | Enforced in automated debug & release ManifestPermissionTest CI checks. |
4. Bundled SDKs & Third-Party Service Providers
| Component / Provider | License / Role | Verified Data Behavior |
|---|---|---|
| Google ML Kit Text Recognition (Latin & Devanagari 16.0.1) + Barcode (17.3.0) | Google APIs Terms / Android ML Kit | Bundled on-device recognition. Transitive transport-backend-cct INTERNET permission is stripped in merged AndroidManifest.xml. |
| AndroidX CameraX (1.5.0-alpha03) | Apache-2.0 | On-device camera viewfinder, auto-focus, EXIF correction, and high-resolution frame capture. |
| PDFBox-Android (2.0.27.0) + Noto Sans Devanagari | Apache-2.0 / OFL-1.1 | Local PDF reading, page merge/split/compression, watermark rendering, and Unicode Hindi text embedding. |
| Zip4j (2.11.5) & ZXing Core (3.5.3) | Apache-2.0 | On-device multi-file ZIP creation and vector QR code matrix encoding. |
| AndroidX Room (2.7.1) & DataStore Preferences (1.1.3) | Apache-2.0 | Stores local recent-file history, saved workflows, UI theme polarity, language, and review cooldown locally. |
| Google Play In-App Review (play:review-ktx 2.0.2) | Google Play Core SDK | Provides native review sheet APIs with market:// Play Store fallback when offline. |
| Optional Cloud Infrastructure (Backend & Website) | Render / Vercel / Firebase Admin SDK | Used ONLY if visiting the public website /contact form, or when future online releases enable optional accounts, remote config, or FCM push notifications. |
5. Retention, Security Controls & Your Deletion Rights
- Local Device Data: Remains on your Android device solely under your control. Clearing local history in Settings → Account → Cancel Local Profile & Clear History erases Room records and DataStore preferences; uninstalling removes app-private files. Files exported explicitly to
Downloads/Syaahipersist in shared storage until you delete them in Android Files. - Optional Accounts & Website Inquiries: Active user sessions and deleted accounts revoke refresh tokens and cascade-delete account credentials, session records, and device links. Security & compliance audit logs retain redacted event records for operational accountability without storing plaintext passwords or private document contents.
- Exercise Deletion Rights: Visit our Account & Data Deletion guide or submit a deletion request via Contact Support.