Privacy Policy — «ماء جمعيتي» (Maa jaamiati)
Effective: 1 August 2026
«ماء جمعيتي» is an application designed for drinking-water associations.
1. Data Roles and Ownership (Who holds the data)
The Association as Data Controller: The drinking-water association using this app is the Data Controller under international privacy laws. The association owns, manages, and bears full legal responsibility for all subscriber data (names, readings, bills, and payments) entered into the app. Decisions regarding billing, collections, and disconnections belong solely to the association.
The Developer as Technology Provider: The developer acts strictly as a software provider, not a data service. The developer has no access to subscriber information and cannot view or read the contents of an association’s database.
Data Storage Controls: By default, the app operates entirely on the phone. All data is stored locally on the association's device.
Optional Cloud Synchronization: Associations may optionally enable cloud synchronization. If enabled, the association creates and connects its own cloud database inside its personal Google account, which it owns and can inspect, modify, or delete at any time. The developer stores only the minimal account details required to run the application infrastructure (the association’s app account, subscription status, and database routing address).
2. Types of Data Handled
The app processes the following categories of data:
Subscriber (Member) Information: Full name (required for billing), meter number (optional), and phone number (optional).
Usage and Financial Records: Meter readings, water consumption logs, bills, payment records, outstanding debts, and advances.
3. Legal Basis and Purpose of Use
Data is processed based on Contractual Necessity to fulfill the service requested by the subscriber from the association. The data is used exclusively for:
Managing water subscriptions and recording meter readings.
Producing invoices, bills, and payment receipts as PDF files.
Tracking financial payments, debts, and balances.
Allowing subscribers to view their personal files and sending official association announcements.
4. Where the Data is Kept (Data Transfers)
By default, data remains strictly on the local device. If an association explicitly enables cloud synchronization, data is routed to the following third-party infrastructure:
Google Firebase: Used for cloud storage and synchronization. This database is hosted inside the association’s own Google account on secure servers.
Cloudflare: Used to securely verify sign-in credentials and route each association to its correct isolated database.
Google Drive: Used for automated backups, stored exclusively inside the association's private Google account (only if enabled by the user).
Google AdMob & Firebase Analytics: See Sections 6 and 7.
5. Data Security
Encryption: All data is encrypted in transit using industry-standard protocols and is stored encrypted at rest.
Isolation: Strict database access rules ensure each association's data is fully isolated from all other users. Subscribers can only access and view their own personal file.
Backup Security: Local and cloud backups are encrypted using a key derived from the association's private security codes.
Disclaimer: While we implement robust, industry-standard protections, no digital system is completely secure. No absolute guarantee can be given against unauthorized third-party breaches or data loss.
6. Advertising and Third-Party Tracking
The app displays advertisements through Google AdMob to support the platform.
AdMob may automatically collect technical device data, such as your mobile device’s advertising identifier.
Zero Data Sharing: No subscriber names, billing details, water consumption data, or payment records are ever shared with the advertising network.
User Control: Users can opt-out or manage personalized ad tracking at any time via their mobile device settings (Settings → Google → Ads).
7. Usage Statistics and Analytics
The app utilizes Google Firebase Analytics to collect anonymous, aggregate data regarding app performance (e.g., screens visited, device types, software crashes).
This data is used solely to troubleshoot bugs and improve user experience.
No Personal Data Collection: No subscriber names, bills, water readings, or financial histories are ever transmitted to Firebase Analytics.
8. App Permissions
To maintain data minimization, the app requests minimal system permissions:
Notifications: Required to deliver critical announcements and billing updates to the subscriber.
File Management: Generating PDF bills, receipts, or selecting an association logo utilizes the native Android file picker, requiring no permanent device storage permissions.
9. Data Sharing and Third-Party Rights
No Commercial Sharing: Subscriber data is never sold, rented, leased, or shared with third parties for marketing purposes.
Internal Access Control: Within an association, subscriber information is strictly restricted and visible only to authorized personnel (the president and designated collectors) and the individual subscriber.
10. Data Subject Rights (Access, Correction, and Deletion)
Under international privacy regulations, individuals have the right to access, correct, or request the permanent deletion of their personal data.
How to Exercise Rights: Because the developer does not hold or control subscriber data, subscribers must submit all requests for data access, correction, or deletion directly to their respective Water Association.
Account Deletion: When an association deletes a member profile or removes their own app account, the corresponding data is immediately wiped from the local device and the linked cloud database.
11. Contact Information
Data Privacy Inquiries: Questions regarding specific data held by an association must be directed to that association's administration.
Technical Support: For technical inquiries regarding app functionality or data security architecture, please contact the developer via the support option located inside the application.