Privacy Policy — Maa jaamiati (ماء جمعيتي)

Last updated: 17 August 2026. Android app eduapptool.purewaterbilling. This is a full translation of the Arabic policy above; the two say the same thing.

1. Who holds the data

The app runs on the association's phone. Subscribers, meter readings, bills and payments are stored on the device, and an association can use the app this way indefinitely with nothing leaving the phone.

Synchronisation is optional. An association that wants it creates a cloud database inside its own Google account, which it owns and can inspect or delete at any time.

We provide a tool, not a data-hosting service. For an association that has created its own database, we hold no copy of its subscriber register and cannot read it — not merely because we promise not to, but because the only access we retain in its project is the database security rules (firebasedatabase.instances.get/update), and Google itself refuses any attempt to read beyond that limit.

Decisions about subscribers — billing, collection, disconnection — belong to the association alone.

2. What data the app handles

Subscribers: full name, meter number, address and phone (both optional), meter readings and consumption, bills, payments, debts and advances.

Users: the email address and name from the Google account used to sign in, or a username issued by the association.

Device: the notification (FCM) token of a device that has enabled notifications, and the link code that binds a subscriber to his own file — a generated code carrying no personal meaning.

3. Why it is used

Managing subscriptions, recording readings, producing bills and receipts as PDF files, tracking payments, letting a subscriber see his own file, and sending the association's announcements.

4. Where the data is kept

By default: on the phone only. For an association that has enabled synchronisation:

The notification (FCM) token is stored only for a subscriber's device that has enabled notifications, and is deleted automatically once that device stops accepting them.

5. Google permissions the app requests

6. Who we share, transfer or disclose data to

We do not sell, rent or trade data, and we pass it to no data broker and no advertiser. The table below is everyone who receives anything, exactly what they receive, and why:

No one else. Beyond the above, data is transferred or disclosed to no party except in three cases:

• At your request or with your explicit consent — for example when you ask for technical help that requires looking.
• A legal obligation — a court order or a valid official request under Moroccan law (Law 09-08), and only to the extent that request compels.
• Protection against abuse — investigating a breach, fraud, or harm to the service or its users.

7. Google user data: who receives what

"Google user data" is what the app obtains from your account through the scopes in section 5.

How it works, in brief: when the president taps "create my database", he is taken to Google's consent screen; once he consents, our server (a Cloudflare Worker) receives a temporary access token and uses it on his behalf to create a Firebase project inside his own account, switch on the services it needs, and write the security rules. Google user data passes through our server for that purpose alone. This is where each item goes:

8. Advertising

The app is free, and advertising is what makes it free. Ads therefore appear throughout the app and for every user — president, collector and subscriber alike: on app open, and on the dashboard, bills, consumption, statistics and subscriber-portal screens. One kind is chosen by the user himself: an ad watched in exchange for downloading a document.

For an association on a paid term, ads stop for the president and the collectors; subscribers continue to see them. That is the only difference paying makes: nothing in the app stops working or is withheld, and it has no bearing on the data or on who receives any of it.

All of them are served through Google AdMob, which may receive technical device information such as the advertising identifier and processes it as its own controller under Google's policy. It receives no subscriber name, bill or payment, and nothing from the Google user data described in section 7. Ad tracking can be controlled under Settings → Google → Ads.

9. Usage statistics

The app uses Google Firebase Analytics to measure how it is used — which screens are opened, device type, and crashes — in order to improve it. These are aggregate figures carrying no subscriber name, bill, reading or payment, and nothing from Google user data.

10. Security

Data travels over an encrypted connection and is stored encrypted. Access rules keep each association separate from every other, and a subscriber sees only his own file.

11. Permissions on the phone

One permission: notifications, so the association's announcements and bill reminders reach the subscriber. Choosing a logo and saving bills go through the Android file picker and need no storage permission.

12. Deleting data

The decision rests entirely with the association, from inside the app itself. There are two options for the cloud database:

• Unlink only — the app stops synchronising and returns to working locally; the database stays in your account untouched.
• Delete the database permanently — the entire project is deleted from your own Google account, the database and everything in it included. It runs on your consent at Google's own page, and it cannot be undone.

To erase the local data on the phone: Settings → Advanced → Factory reset. To delete the association's account with us — including the email address held in the routing table and whatever concerns it in our own project — write to the address below and it is removed within thirty days.

Permissions granted to the app can be withdrawn at any time at myaccount.google.com/permissions.

13. Contact

Questions about the data a particular association holds go to that association. Technical matters and questions about the app itself: support@maajamiati.com