Laundry App — Android application backed by Firebase
The Laundry App tracks orders from drop-off to pickup. It stores the minimum a laundry business needs — who the order belongs to, what is in it, and where it is in the process.
Laundry App is software that an organization installs and runs on its own infrastructure. The laundry business operating a given installation decides what data is entered into it and is the data controller for that installation. This page documents what the application itself collects and processes by design; it is the reference policy for the software, and an operator may publish additional terms on top of it. As the developer, I have no access to any production database unless an operator explicitly grants it for maintenance.
| Data | Why |
|---|---|
| Customer name and phone number | Identifying whose laundry is whose, and contacting you when the order is ready. |
| Order details | Item types, weight, service chosen, price, estimated completion, and the QR tracking code. |
| Order status history | Received → washing → ready → picked up, with timestamps — for tracking and for daily revenue reports. |
| Push token | A per-device Firebase token used to send the “ready for pickup” notification. |
| Staff accounts | Name, outlet, role, and hashed credentials. |
| Device & technical data | Device model, OS version, and app version, for troubleshooting. |
| Service | What it does |
|---|---|
| Google Firebase Privacy policy ↗ | Authentication, cloud database, and file storage. Data is stored on Google servers in the project owned by the operator. |
| Firebase Cloud Messaging Privacy policy ↗ | Delivers push notifications. Uses a per-device push token that is regenerated when the app is reinstalled. |
Order data is visible to the staff of the outlet handling it and to the owner across outlets. It is not sold or shared with advertisers.
Order records are kept for as long as the business needs them for reporting and customer history. A customer can ask the outlet to remove their contact details; past orders then remain as anonymous entries in the revenue report.
The application applies standard protections: passwords are stored as one-way hashes (never in plain text), access is limited by role, and all traffic between client and server is expected to run over HTTPS/TLS.
No system is perfectly secure. Server hardening, backups, and access management for a live installation are the responsibility of the organization operating it.
The app is a service-counter tool. It is not directed at children, and customer records are created by staff.
You have the right to ask for access to, correction of, or deletion of your personal data, and to object to certain processing.
Because your data lives in the installation run by the organization you deal with, address those requests to that organization first — they hold the data and can act on it. If you cannot reach them, or you believe the application itself is at fault, contact the developer at mhdlutfidev@gmail.com and I will assist technically.
If this policy changes, the “Last updated” date at the top of this page will be revised. Material changes will be reflected in the application release notes.
Questions, complaints, or privacy requests about this application:
I aim to respond within 7 business days.