App: CuciQu Kasir Laundry POS (formerly known as CuciQu Pro Kasir Laundry)
Google Play package: com.cuciqu.laundry
Contact: [email protected]
This Privacy Policy explains how Fade Digital Indonesia ("we", "us", the "Developer") collects, uses, stores, and protects your personal data ("you", the "User") when you use the CuciQu Kasir Laundry POS app (also called "CuciQu Pro" or the "App") available on the Google Play Store and the Apple App Store.
By using the App, you agree to this policy. If you do not agree, please stop using the App. This policy forms an integral part of our Terms and Conditions. This English version is a translation; if there is any difference in meaning, the Bahasa Indonesia version prevails.
Contents
- 1. Data We Collect
- 2. Device Permissions
- 3. Geolocation & GPS Attendance
- 4. How We Use Data
- 5. Merchant Payments & QRIS (Indonesia only)
- 6. Third-Party Services
- 7. Data Security
- 8. Retention & Deletion
- 9. Your Rights
- 10. Cookies
- 11. International Transfers & Users Outside Indonesia
- 12. Changes to This Policy
- 13. Contact
1. Data We Collect
We only collect the data needed to provide and improve the CuciQu service:
| Category | Data | Source |
|---|---|---|
| Account data | Full name, email address, phone number, business name, business address | Entered directly by the user |
| Transaction data | Laundry order history, payment amounts, business-customer data | Activity in the app |
| Attendance data | Clock-in/out time, GPS coordinates at the moment of attendance, attendance status | Employee attendance activity |
| Device data | Device model, OS version, push notification token, time zone | Automatically from the device |
| Log data | Anonymous error logs and crash reports (no personal data) | Automatically, to improve the app |
| Photo & video evidence | Photos and short videos (max. 30 seconds, no sound) of item condition for orders/complaints, with a watermark | Recorded by the user and stored in the outlet's own Telegram (see 2.1) |
| Payment data | Payment status of outlet orders for real goods/services and the payment method (card numbers are processed by the payment gateway and not stored by us) | Outlet order transactions for real goods/services |
| AI Assistant questions | Questions you type to the AI Assistant and the answers given | Entered by the user when using the feature |
We do NOT collect: the content of your private messages, your contact list/address book, biometric data, or location information outside the moment of attendance. Note: if you use "Pick from Contacts" to add a customer, the address book is accessed entirely on your device. The contact list is not sent to our servers; only the number you pick is saved as customer data.
2. Device Permissions
The App requests the following permissions, each for a specific purpose:
| Permission | Platform | Purpose | Status |
|---|---|---|---|
| Precise location ACCESS_FINE_LOCATION / When In Use |
Android & iOS | Verify position at attendance clock-in/clock-out | Required* |
| Background location ACCESS_BACKGROUND_LOCATION / Always |
Android & iOS | Not used | Not requested |
| Camera | Android & iOS | Scan order barcodes/QR codes, take delivery proof photos, record order/complaint evidence videos (no sound) | Optional |
| Microphone RECORD_AUDIO / NSMicrophoneUsageDescription |
Android & iOS | Not used (videos are recorded without sound) | Not requested |
| Storage / Photos | Android & iOS | Save reports, receipts, and order photos | Optional |
| Push notifications | Android & iOS | Schedule reminders, order status, transaction notifications | Optional |
| Bluetooth / NFC | Android | Connect to thermal receipt printers | Optional |
| Contacts READ_CONTACTS / NSContactsUsageDescription |
Android & iOS | Pick a customer's phone number from the device address book when adding a new customer. The contact list is not sent to the server; only the number you pick is saved as customer data. | Optional |
| Internet | Android & iOS | Data sync and server communication | Required |
*The location permission is required only for users who enable GPS attendance. All other features work normally without it.
Android: Settings → Apps → CuciQu → Permissions
iOS: Settings → CuciQu → Location / Camera / etc.
Revoking a permission does not affect features that do not need it.
2.1 Order & Complaint Video Evidence
The App offers an optional feature to record short videos as evidence of item condition for orders and customer complaints:
- Only on user action: the camera is active only when you press the record button. The App never records in the background.
- No sound: videos are recorded without audio. The App does not request microphone permission (RECORD_AUDIO / NSMicrophoneUsageDescription).
- Limits: up to 30 seconds and up to 2 videos per order or per complaint. Videos are watermarked to prevent misuse.
- Stored in the outlet's Telegram: this feature works only if the outlet owner connects a Telegram bot/group. Videos are relayed through our server directly to Telegram, and CuciQu servers do not keep the video files; we only store a reference (the Telegram file ID) linked to the order/complaint.
- Control over videos: copies in the Telegram group are controlled by the outlet owner and subject to the Telegram Privacy Policy.
3. Geolocation & GPS Attendance
3.1 Why do we need location access?
GPS Attendance is used solely to verify that an employee is within the work-location radius set by the admin/business owner at the moment of clock-in or clock-out. It replaces manual attendance and prevents attendance fraud.
3.2 How location is taken
- The admin sets the work-location coordinates and a tolerance radius (for example 100 metres) in the settings.
- When an employee presses Clock In or Clock Out, the App takes a single GPS reading (one-time location request), not continuous tracking.
- The coordinates are compared with the location set by the admin.
- Within the radius, attendance is recorded automatically. Outside the radius, the system shows a warning and requires admin approval.
- The GPS coordinates, timestamp, and verification result are stored as an auditable attendance record.
3.3 Location data collected and NOT collected
| Collected | NOT collected |
|---|---|
| Latitude and longitude when the attendance button is pressed | Travel or movement history |
| Timestamp (date and time) of the reading | Location outside the clock-in/clock-out moment |
| Verification status (inside/outside the radius) | Location while the app runs in the background |
| Device GPS accuracy (in metres) | Home location, personal trips, or activity outside working hours |
3.4 Storage of and access to location data
- Attendance GPS coordinates are stored on our servers.
- Only the admin/owner of the business concerned can see their employees' attendance location data.
- Location data is not shared with third parties or advertisers and is not used for commercial analytics.
- Location data is permanently deleted after 12 months or when the business account is deleted, whichever comes first.
3.5 Technical details per platform
- Android: uses the Fused Location Provider API (Google Play Services) with the
ACCESS_FINE_LOCATIONpermission. We do not requestACCESS_BACKGROUND_LOCATION. - iOS: uses the Core Location framework in "While Using the App" mode. We do not request "Always" (background) mode.
3.6 Attendance without GPS: manual entry by the admin
Using GPS for attendance is optional. If an employee does not grant location permission or chooses not to use it, the admin/business owner can still record attendance manually:
- The admin can clock employees in and out directly from the admin dashboard.
- Manual attendance needs no GPS data; only the time and the employee's identity are recorded.
- The admin can edit, correct, or add missed attendance records at any time.
- Attendance reports remain complete without GPS data.
3.7 Business owner's responsibility
Owners/admins who enable GPS Attendance must:
- Inform employees that location data is collected at attendance.
- Obtain employees' consent in line with applicable employment law.
- Make sure this use does not breach privacy regulations where the business operates.
4. How We Use Data
We use the data we collect only for these purposes:
- Service operation: providing, running, and improving the App's features.
- Attendance: recording and verifying employee attendance based on GPS location.
- Payments: processing and managing outlet payment transactions for real goods/services.
- Security: detecting and preventing fraud, unauthorised access, and misuse of the service.
- Notifications: sending reminders, order status updates, and important service information.
- AI Assistant: answering users' questions about their outlet's business. The question and a summary of the relevant business data are sent to OpenAI only when you use this feature. The AI Assistant only reads data and never changes any data.
- Product improvement: analysing anonymous crash logs to improve App stability.
- Legal obligations: meeting regulatory obligations and responding to lawful requests from authorities.
We do not use your data for targeted advertising or commercial profiling, and we do not sell it to third parties. We do not track you across apps (cross-app tracking) and do not use your data to follow your activity in other companies' apps or websites.
5. Merchant Payments & QRIS (Indonesia only)
5.1 Payment terms
| Term | Definition |
|---|---|
| QRIS | Indonesia's national QR payment standard, used by customers to pay a laundry outlet for laundry services. These are transactions for real goods/services. |
| Outlet balance | Settlement of the outlet's sales collected from customer QRIS payments. The balance belongs to the merchant outlet and can be withdrawn. |
| Payout | Withdrawal of the outlet balance to the merchant's registered bank account. Payouts are processed by payment gateway partners licensed by Bank Indonesia. |
| Platform fee | A transaction service fee charged to the merchant outlet for using the digital payment system. It is not the outlet's price for real goods/services but a per-transaction fee for QRIS payments. |
5.2 Customer-to-outlet payment flow (QRIS)
- The customer pays: the customer scans the outlet's QRIS to pay for the laundry service.
- The payment is processed: a payment gateway partner licensed by Bank Indonesia processes the payment and verifies the transaction.
- Settlement to the outlet balance: the funds go to the merchant's outlet balance in CuciQu after deduction of the platform fee.
- The outlet requests a payout: the merchant can request a withdrawal to their bank account at any time.
- The payout is processed: funds are transferred to the merchant's account, usually within 1 business day, at most T+1 to T+3 business days.
5.3 Apple App Store & Google Play compliance
5.3.1 Apple App Store Guidelines
In line with Apple App Store Review Guidelines 3.1.3(e):
- ✅ QRIS payments are for physical goods and services (laundry services).
- ✅ The service is consumed outside the app: customers use the laundry service at a physical outlet.
- ✅ The app acts only as a point-of-sale system for merchants to record transactions.
- ✅ No digital content, premium features, or virtual goods are sold through QRIS.
- ✅ The platform fee is a B2B service fee between CuciQu and the merchant, not a purchase by the end user.
5.3.2 Google Play Payments policy
In line with the Google Play Payments policy:
- ✅ QRIS payments are for physical goods and services consumed outside the app.
- ✅ The app is a business tool (cashier/POS) for merchants, not a consumer marketplace.
- ✅ No digital content or in-app features are sold to end users.
- ✅ Payments are processed by third-party payment gateway partners licensed and supervised by Bank Indonesia.
5.4 Payment data we collect
For QRIS transactions and payouts we collect:
- Merchant data: business name, bank account number, account holder name, national ID/tax number (for KYC verification).
- Transaction data: payment amount, timestamp, transaction ID, payment status, platform fee charged.
- Payout data: payout amount, destination account, payout status, processing date.
5.5 Platform fee & transparency
A platform fee is charged to the merchant for each successful QRIS transaction:
- Fee amount: shown transparently in the merchant dashboard before the transaction.
- Calculation: calculated automatically and deducted from the settlement before it reaches the outlet balance.
- Reports: merchants can see the fee for each transaction in their financial reports.
5.6 Payout policy
- Minimum payout: merchants can request a payout from Rp10,000.
- Processing time: funds usually arrive within 1 business day after the request is approved, at most T+1 to T+3 business days (for example because of bank holidays or disruptions at the bank/payment provider).
- Account verification: the merchant's bank account must be verified and match the KYC data.
- Payout fees: bank transfer fees (if any) are borne by the merchant according to bank policy.
5.7 Merchant responsibilities
Merchants who use QRIS payments must:
- Provide laundry services that match the customer's order.
- Give customers a receipt/proof of payment.
- Resolve customer disputes or complaints about the service.
- Comply with tax regulations and report income as required.
- Not use the payment system for illegal or unlawful transactions.
6. Third-Party Services & SDKs
The App uses the following third-party services, each with its own privacy policy:
| Service | Purpose | Data shared | Privacy policy |
|---|---|---|---|
| Google Play Services | Fused Location API for GPS attendance (Android) | Location request (at attendance only) | Google Privacy |
| Firebase (Google) | Push notifications (FCM), anonymous crash reports (Crashlytics) | Device token, anonymous crash logs | Firebase Privacy |
| Google Maps Platform | Map of attendance location points in the admin panel | Coordinates to render the map | Google Privacy |
| Telegram | Storage of order/complaint photo and video evidence in the outlet's own Telegram bot/group (optional) | Photo/video files and order details (order number, outlet name) | Telegram Privacy |
| OpenAI | AI Assistant: generating answers to users' questions about their outlet's business (only when the feature is used) | The user's question and a summary of the relevant outlet business data (revenue, orders, expenses). OpenAI does not use API data to train its models. | OpenAI Privacy |
| Payment gateway partners | QRIS processing and payout settlement (Indonesian outlets only) by payment service providers licensed by Bank Indonesia | Merchant (KYC) data, transaction metadata, payment status (we do not store card numbers) | According to each provider's privacy policy |
We do not integrate third-party advertising SDKs (such as AdMob or Meta Audience Network) in the App.
7. Data Security
We apply the following technical and organisational security measures:
- Encryption in transit: all data communication uses TLS 1.2 / 1.3.
- Passwords: stored as one-way bcrypt hashes, never as plain text.
- Access control: access is limited on a least privilege basis with role-based permissions (owner, admin, cashier, employee).
- Extra verification: sensitive actions such as account recovery and changes to important settings require a code sent by email.
- Security reviews: we review the security of our infrastructure and application code.
If a data breach affects you, we will notify you no later than 72 hours after we become aware of it, as required by applicable law.
8. Retention & Deletion
| Data type | Retention period | After expiry |
|---|---|---|
| Account & profile data | While the account is active + 30 days after deletion | Permanently deleted |
| Transaction & order data | 5 years (tax/accounting obligations) | Anonymised |
| GPS attendance location data | 12 months from the attendance date | Permanently deleted |
| Video evidence | Files are not stored on our servers; they stay in the outlet's Telegram. File references follow transaction data retention | References anonymised with the transaction data |
| Error & crash logs | 90 days | Deleted automatically |
| Push notification tokens | Until permission is revoked or the account is deleted | Permanently deleted |
Account deletion
You can delete your account in the App → Settings → Delete Account (at the bottom of the screen), through the account deletion page, or by emailing [email protected]. Deletion is processed within 30 business days. Data that must be kept for legal retention periods is anonymised first.
9. Your Rights
Under Indonesia's Personal Data Protection Law (Law No. 27 of 2022), you have the following rights:
- Access: request a copy of the personal data we hold about you.
- Correction: request correction of inaccurate or incomplete data.
- Deletion: request deletion of your personal data (within the limits of legal obligations).
- Portability: request an export of your data in a machine-readable format (JSON/CSV).
- Objection: object to processing for certain purposes.
- Withdrawal of consent: withdraw consent you have given at any time.
10. Cookies & Web Tracking
Our website (cuciqu.com) does not use advertising or analytics cookies and does not install third-party trackers. We only use:
- Network security cookies: set by our website network and security provider (Cloudflare) to protect the website from malicious traffic. They are not used to identify you.
- Referral code (browser local storage): if you open an affiliate link containing a referral code (
?ref=), the code is stored in your browser for 30 days so it can be filled in automatically when you sign up. The code is only passed on to app.cuciqu.com when you open a login/sign-up link, is not used to track your activity, and can be removed in your browser settings.
The mobile apps (Android/iOS) do not use cookies. You can delete cookies and local storage in your browser settings.
11. International Transfers & Users Outside Indonesia
Your data is stored mainly on servers located in Indonesia. Some third-party services (Firebase, Google Maps, Telegram, OpenAI) may process data on servers outside Indonesia and outside your country. We make sure every international transfer is protected by safeguards equal to or higher than Indonesian regulations require. For users in the European Union/United Kingdom, transfers outside those regions are protected by Standard Contractual Clauses (SCCs) or equivalent mechanisms.
11.1 Users outside Indonesia
- European Union / United Kingdom (GDPR): our legal bases for processing are performance of a contract (providing the App), legal obligations (tax/accounting records), legitimate interests (security, fraud prevention, App stability), and consent where required (location, camera, contacts, notifications). In addition to the rights in section 9, you have the right to restrict processing and to lodge a complaint with the data protection authority in your country.
- Malaysia (PDPA 2010) & Singapore (PDPA 2012): you have the right to access and correct your data and to withdraw consent through [email protected].
- Outlet customers' and employees' data: for data that outlets enter about their own customers and employees, the outlet is the data controller and CuciQu is the data processor acting on the outlet's instructions.
- Indonesia-only features: QRIS and payouts (section 5) are available only to outlets in Indonesia.
12. Changes to This Policy
We may update this Privacy Policy from time to time. For material changes, we will:
- Update the "Last updated" date on this page.
- Show an in-app notice for significant changes.
- Email your registered address if a change materially affects your privacy rights.
Continued use of the App after changes take effect means you accept the updated policy.
13. Contact
For questions, concerns, or requests about privacy and your personal data:
Privacy & Data Protection Team
Privacy email: [email protected]
Support email: [email protected]
Website: cuciqu.com
Terms and Conditions: cuciqu.com/terms
Response time: 1–3 business days
This policy is governed by the laws of the Republic of Indonesia, including Law No. 27 of 2022 on Personal Data Protection, Law No. 11 of 2008 on Electronic Information and Transactions and its implementing regulations, without limiting the rights you have under the data protection laws of your country.
Previous versions of this policy are available on request at [email protected].