Muluwin Privacy Policy

How the Muluwin app handles your data, in plain words: what it collects, the permissions it needs, how that data is guarded, and the rights you keep.

Back to Muluwin

What we collect

Data we collect

Installing the official app from Muluwin pulls together a short list of details, and this privacy policy walks through each one so nothing stays murky. You supply part of it at sign-up: the name on the account, a contact email or phone, a birth date to confirm you're 18 or older, and a password only you should know. The rest the app reads off your handset — the device model, its Android or iOS version, and which build of the app you've got running.

Some of what the app records happens quietly, in the background, and it stays purely technical. Think crash logs when a screen misbehaves, the approximate area your connection points to, an install source noting where the file came from, and timestamps for the last time you checked for a newer build. A single log line reads as noise. Pooled across every install, it tells us which builds sit stable on which devices and which need a patch.

The guiding rule is restraint. We ask for what the account and the app need to work, then stop. Where a field is optional, the form says as much, and leaving it empty has no bearing on how the app behaves on your handset. Age matters more than any single field here: the date of birth you type in is the check that keeps the platform to adults, not a throwaway box.

How we use it

How data is used

Every scrap of that data earns its keep somewhere. Most of it goes into keeping the app running and the account firmly yours. Your device model and OS version let the hub serve the build meant for your phone rather than one that stutters through every screen. The email or number on file is the channel a security notice or an update prompt travels down. Sign back in, and those same details prove the account still answers to you.

Diagnostics carry real weight here. When the Muluwin app reads crash reports and version data across the whole user base — with no one account picked out — it shows which release behaves and which trips over a particular device. That's what steers the next fix and the next update. The same signals feed security, catching a login attempt that rings false or an install that looks tampered with.

One boundary holds firm. We won't put what the app learns about you up for sale, and we won't feed it to advertisers chasing a better-aimed pitch. Bring in an outside firm for part of the job — hosting the servers, screening for fraud, serving the download itself — and it works only to a written brief from us, holding on to none of it afterwards. Any partner that slips below the bar we set gets dropped without much ceremony.

Security

App permissions

Here's the part unique to an app: the permissions it asks your phone for. The Muluwin app keeps that list short and tied to a plain purpose. Network access, so it can load the platform and check whether a newer version has shipped. Storage access, so the install file and a handful of cached assets have somewhere to sit. Notification access, so an update alert or a security message can actually reach you.

Just as telling is what the app leaves alone. It doesn't reach for your contacts or camera unless a specific feature you switch on genuinely needs it — and when that happens, the app asks first and says why. You stay in charge of all of them. Open your device settings, look over what's been granted, and pull back anything you'd rather withhold; the app steps down gracefully instead of locking you out.

The permissions tie back to the deal you accept when you install the app, and that deal is written out in full as the Muluwin Terms and Conditions. Set the two next to each other — one lays out what you agree to by putting the app on your phone, the other explains what each permission actually does once you grant it. Revoke one in your settings and the app may prompt for it again when a feature next needs it, so an occasional look keeps you current.

Data security

Locking the data down is steady, unglamorous work for the crew that keeps the app running, never a box ticked once. The connection the app opens to our servers is encrypted end to end, so what passes between your phone and us can't be read in transit. On our side, only staff whose job needs a given record can open it. Passwords are never kept in plain form — they're run through a one-way hash we can't reverse.

One safeguard matters more for an app than for a website: the build is signed. Every official Muluwin release carries a cryptographic signature your phone verifies before the install goes ahead, which is how the device confirms the file genuinely came from us and hasn't been altered en route. Download only from the official hub and that check quietly works in your favour. Take a copy from some random mirror and you've thrown the protection away.

Plain beats grand here. No app can honestly pretend it'll shrug off every attempted intrusion, and any service that swears its defences are impregnable is bluffing. What we can promise is narrower and truer: constant effort. Weak points get patched and unusual activity gets chased down early; a slow response isn't something we'd accept from ourselves. If a real incident ever reached your account data, we won't handle it by going dark and hoping the news never gets to you.

Your rights

What the app holds about you is yours, and that's the starting point. Ask to see whatever the app has on file, or put a mistaken detail right. You can also have the lot wiped once no law or working need still calls for keeping it. Where the rules in your state let you cap or object to a given use, you can bring that to us too. It needn't be a production — a line or two naming what you'd like is enough to get it moving.

To get any of this moving, reach out through Muluwin Contact and tell us in plain words what you're after. Rather leave a written trail? Send it across; [Data-protection contact email] reaches the data-protection team direct. We'll run a sensible identity check before acting on one, so no stranger can pose as you and prise open your record.

A closing note on the formalities. [Legal entity name] stands behind this policy, the governing law is that of [Governing state, India], and it's effective from [Effective date]. We'll revise the wording as the app matures and the rules around it shift, and the current text stays published for anyone who cares to look. When a change actually matters, we'll flag it in clear terms rather than let it pass unmarked.