POS untuk UMKM — Web application (Laravel)
This is a deliberately small point-of-sale for micro and small businesses. It records what was sold and by whom — and by default it stores no customer personal data at all.
POS untuk UMKM is software that an organization installs and runs on its own infrastructure. The business owner 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 |
|---|---|
| Sales transactions | Items, quantity, price, discount, payment method, cashier, and timestamp — for receipts and daily/weekly/monthly reports. |
| Product and stock data | Product names, barcodes, categories, prices, and stock levels — business data, not personal data. |
| User accounts | Owner and cashier names, roles, and hashed passwords. |
| Technical logs | IP address, user agent, and action timestamps. |
Customer details are not part of the sales flow. If an operator types a customer name into a transaction note, that data exists only because they entered it, and the operator is responsible for it.
None. There is no payment gateway, advertising network, analytics SDK, or external API. Receipts are printed directly to a thermal printer connected to the local machine, and the barcode scanner acts as a keyboard — neither sends anything over the internet.
The application uses cookies only for functionality:
There are no advertising cookies, no third-party analytics or tracking pixels, and no cross-site profiling. Clearing cookies simply logs you out.
Sales records persist until the owner deletes them, and are normally kept for as long as bookkeeping and tax obligations require. There is no automatic data expiry.
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 system is a staff-facing tool with no consumer sign-up. It is not intended for use by children.
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.