Legal

Privacy policy

Last updated: 11 July 2026

MudFlow ("the app") is developed by Mes3oud. This policy explains what information the app collects during closed testing, how it's used, and who to contact with questions.

Information collected

MudFlow is a field logging tool for drilling fluids data. It may collect and store:

Mud property readings you enter — mud weight, rheology (Fann readings, PV/YP, gels), alkalinity (Pf/Mf), filtration and sand content, and any notes attached to them.
Basic account information if you sign in (e.g. name and email address associated with your Google account).
Standard technical data such as device type, OS version, and crash or performance logs, used only to fix bugs during testing.

How information is used

Data you log is used to run the app's core features — storing your reports, generating rheograms, and flagging contamination trends. Technical and crash data is used solely to diagnose problems during the closed testing period and to improve the app before wider release.

Sharing

MudFlow does not sell personal data. Information is not shared with third parties except service providers strictly necessary to operate the app (such as cloud storage or crash reporting), and only to the extent needed for that purpose.

Data retention

Logged reports are kept for as long as your account is active, so you can review historical wells and reports. You can request deletion of your data at any time using the contact details below.

Your choices

You can request a copy or deletion of your data at any time.
You can leave the closed testing program at any time by uninstalling the app and opting out on Google Play.

Contact

Questions about this policy or your data can be sent to the developer via the "App support" section on the MudFlow Google Play listing.

Note: this is a starting template for closed-testing purposes. Replace the contact details above with a real support email, and have it reviewed before wide release — especially the data retention and third-party sections, once you've finalized what backend/analytics services MudFlow actually uses.