1. Introduction & Application Identification
This Privacy Policy outlines how the “QIWAM” (قِوام) mobile application for Android handles your personal and financial information. We firmly believe that full technical transparency and legal precision are the keystones of digital trust.
QIWAM is engineered with a strict “Privacy by Design” philosophy. All financial records and transactions are processed and stored locally on your device within an isolated application environment, with zero data routed to any developer-owned central servers. When you optionally enable Google cloud services, your sync data resides exclusively in your own private, isolated space on Google Drive.
2. Categories of Data Processed
QIWAM processes only data strictly essential for its accounting and financial tracking functions, distinguishing between the following categories:
A. Financial & Operational Data Manually Entered by the User:
• Financial Transactions: Amounts, timestamps, categories, and operation types (expenses, debts owed/receivable, contributions, settlements).
• Financial Containers: Names of cash boxes, bank accounts, personal wallets, opening balances, and chosen currencies.
• Counterparties & Entities: Names of individuals, community funds, or projects with which transactions are recorded.
• Notes & Commitments: Reminders and scheduled pledge dates entered voluntarily.
• Attachments & Receipts: Invoice snapshots and bank transaction slips attached by the user.
B. Technical Identifiers & Account Credentials (Optional Cloud Feature):
• Google Account Information: Upon optional Google Sign-In, the app retrieves the user's email address, display name, and unique Google User ID strictly to derive cryptographic isolation tokens and separate local/cloud databases.
• Installation UUID: A randomly generated on-device identifier used to uniquely tag sync delta bundles and prevent sync collision when accessing the ledger from multiple devices.
3. Methods of Data Collection and Access
All data is collected solely through direct, voluntary user input within the app user interface.
The app does not collect background telemetry, does not access device geolocation, and does not scan broad external storage or browsing history.
4. Local Storage & Database Architecture (Drift / SQLite)
QIWAM is built upon an Offline-First architecture powered by SQLite and managed through Drift:
• Offline Functionality: Full bookkeeping features operate without network connectivity or Google account sign-in. In default offline mode, data is kept in qiwam_default.sqlite.
• Local Account Isolation: When signing in with a Google account, a dedicated database file is created based on a SHA-256 hash of the account identifier (e.g., qiwam_account_{hash}.sqlite), preventing cross-account contamination.
• Security at Rest: Databases are stored within Android's sandboxed private storage. We candidly disclose that active local SQLite databases are unencrypted at rest; protection relies on Android's operating system sandbox and device lock screen security.
• Encrypted Backup Archives: When exporting a manual backup (.qiwam.bak), the archive is encrypted using AES-256 PBKDF2 cryptography, with recovery keys secured inside the hardware-backed Android Keystore.
5. Google Account & Google Drive Cloud Synchronization
Cloud synchronization is an entirely optional feature adhering to stringent architectural constraints:
• Isolated Application Data Folder (appDataFolder): QIWAM does NOT request access to your personal Drive files. It operates strictly within the hidden appDataFolder, invisible to other apps and users.
• Cloud Package Formats: Data is uploaded in structured JSON bundles: cumulative Delta updates (qiwam_delta_...) and periodically validated state Snapshots (qiwam_snapshot_...).
• Scope Boundaries: Cloud synchronization synchronizes accounting ledger entries and metadata; it does NOT automatically upload locally cached image attachments in the current version.
• Cryptographic Guard: The sync engine enforces a security check rejecting any cloud file whose token signature fails to match the currently authenticated device session.
6. Google OAuth Scopes & Incremental Authorization
QIWAM rigorously abides by the Principle of Least Privilege and Incremental Authorization guidelines mandated by Google:
| Scope | Category | Purpose | Request Timing |
|---|---|---|---|
| Non-sensitive | Verifying account identity to isolate databases locally and remotely, preventing cross-account data pollution. | Requested strictly during initial Google sign-in. | |
| https://www.googleapis.com/auth/drive.appdata | Non-sensitive | Storing and synchronizing delta bundles and state snapshots within the hidden appDataFolder. | Requested strictly during initial Google sign-in. |
| https://www.googleapis.com/auth/drive.file | Non-sensitive | Creating and writing manual backup archives to user-designated Drive storage. | Incremental request only upon initiating manual Drive backup. |
| https://www.googleapis.com/auth/spreadsheets | Sensitive Scope | Populating and updating a dedicated Google Sheets workbook with statement exports. | Incremental request strictly when enabling Google Sheets sync. |
7. Contact Picker Integration & Phone Numbers
To simplify associating counterparties with names and contact numbers, QIWAM provides an optional contact picker:
• Native System Intent (ACTION_PICK): The app invokes Android's native system picker interface.
• No READ_CONTACTS Permission: QIWAM does NOT declare or request the READ_CONTACTS permission in AndroidManifest.xml. It cannot read contacts in the background and never uploads address books.
• Isolated Data Receipt: The app receives only the single contact name and number deliberately tapped by the user inside the OS dialog.
8. Optical Character Recognition (OCR) & Image Handling
The app offers an on-device utility to assist in parsing numbers from receipt and invoice images:
• 100% On-Device Processing: OCR is executed locally on the device processor using Google ML Kit Text Recognition. Neither image files nor extracted texts are transmitted to external servers.
• Recognition Scope: The on-device ML model targets Latin numbers and text. Users are always prompted to review and verify parsed figures before committing transactions to the ledger.
9. Financial Statements, PDF Generation & Sharing
• On-Device Document Generation: Statements and balance summaries in PDF or CSV formats are rendered locally on the handset without third-party document APIs.
• Voluntary Sharing: QIWAM never shares financial reports automatically. Distribution via email or messaging apps is governed entirely by the user via Android's native Share Sheet.
• Visual Privacy Mode: An interface obfuscation mode masks on-screen balances in public environments; this is a display feature only and does not alter exported PDF statement data.
10. Third-Party Services & Zero Tracking Commitment
We operate under a strict zero-telemetry policy:
• No Advertising SDKs: QIWAM contains zero advertising frameworks or commercial trackers.
• No Telemetry / Analytics: The app incorporates neither Firebase Analytics nor Firebase Crashlytics.
• No Cookies: We employ zero tracking cookies.
• No Data Commercialization: We never sell, rent, or monetize personal or financial information.
External interactions are confined exclusively to verified Google APIs (Google Sign-In, Google Drive API, Google Sheets API) activated voluntarily by the user under Google's Privacy Policy (policies.google.com/privacy).
11. Security Architecture & Protective Safeguards
• Android Application Sandbox isolation.
• High-grade AES-256 symmetric encryption for exported .qiwam.bak backup archives.
• Key storage secured in the hardware-backed Android Keystore via secure system storage.
• Biometric authentication (Fingerprint / Face Unlock / Screen Lock) via local_auth.
• Candid Security Posture: We acknowledge that local ledger security depends fundamentally on operating system integrity and user device passcode strength.
12. Data Retention & Deletion Mechanisms
• Local Data: Retained on your device as long as the application remains installed. You can permanently wipe all records instantly via: Android Settings > Apps > QIWAM > Storage > Clear Storage.
• Cloud Data on Google Drive: Sync files remain in your personal cloud until you erase them. You may delete hidden cloud data anytime by visiting Google Drive on the web: Settings > Manage Apps > QIWAM > Options > Delete hidden app data.
• Revoking Access: Google account authorization can be revoked at any time via: myaccount.google.com/permissions without impacting your offline records.
13. Google API Services User Data Policy Compliance (Limited Use)
QIWAM's use and transfer of information received from Google APIs adheres strictly to the Google API Services User Data Policy, including the Limited Use requirements:
1. Data received from Google APIs is used strictly to provide and improve user-facing features described in this policy.
2. Transfers of data to third parties are prohibited, except as required to deliver essential app functions or comply with legal mandates.
3. Google user data is NEVER used to train or fine-tune generalized Artificial Intelligence (AI) or Machine Learning (ML) models.
4. Humans are prohibited from inspecting Google user data, unless affirmative user consent is granted for security troubleshooting or required by law.
14. User Rights and Data Autonomy
• Right of Full Inspection: Instant, unrestricted viewing of all ledger entries, counterparties, and running balances.
• Right of Data Portability: Unrestricted export of all records into PDF reports, Google Sheets, or encrypted .qiwam.bak archives.
• Right of Rectification & Erasure: Immediate on-device modification or deletion of any transaction, counterparty, or container, reflected across cloud sync upon next synchronization.
15. Children’s Privacy
QIWAM is designed for general adult audiences managing personal or organizational finances. It is not directed toward children under the age of 13, and we do not knowingly collect personal information from minors.
16. Amendments to this Privacy Policy
We may periodically revise this Privacy Policy to reflect engineering updates or Google Play regulatory amendments. Material changes will be accompanied by an updated effective date at the top of this document and highlighted in the app settings interface.
17. Contact & Developer Information
For technical inquiries, compliance questions, or data autonomy requests:
• Official Support & Privacy Email: [SUPPORT_EMAIL_REQUIRED]
• Developer & Legal Entity: [DEVELOPER_ENTITY_REQUIRED] (Achraf Lezhari)
• Official Web Address: https://lezach.com/qiwam
18. Effective Date & Version Endorsement
This policy is effective as of November 15, 2026, serving as the definitive technical and compliance standard for QIWAM v1.4.1 and above.