AQUAWASH

Terms

Terms and conditions

Working draft covering use of the AQUAWASH Android app and website.

Draft for review — not final legal policy

These terms are not ready for publication. Actual purchase rules, warranty and liability language, support process, and governing law must be completed and reviewed by qualified counsel.

Working draft · Last reviewed 24 October 2026

These terms are a draft for the AQUAWASH Android laundry operations app and its marketing website. They do not replace the published license agreement, consumer rights, Google Play rules, or advice from legal counsel.

1. Provider and acceptance

Provider: AeDev. Postal address: Payatas, Quezon City, Philippines. Support contact: adriel.dev.123@gmail.com. The terms acceptance flow must be confirmed before release.

2. Product description

AQUAWASH is an Android app for local laundry business operations, including orders, customers, payments, services, inventory, expenses, reports, and staff workflows. The app currently stores business records on the device, offers user-initiated Bluetooth receipt printing and ZIP backup export, and does not provide a cloud account, cloud synchronization, or remote data storage.

3. License and activation

The current source requires a signed offline license code for a new installation. A code is checked on-device and tied to a device fingerprint. Existing installations with an initialized business database are grandfathered by current startup logic. This code implementation is not itself a published consumer pricing or purchase policy.

The requested one-month, one-year, and lifetime Google Play products, their prices, exact validity periods, included entitlements, account association, restoration and upgrade behavior, and billing terms are not configured in the reviewed Android project. Do not publish those as live terms until the app and Google Play product setup match.

4. Purchases, billing, and refunds

No Google Play Billing implementation or product identifiers were found in the reviewed project. The operator must add verified price, tax and currency display, purchase verification, consumer cancellation and refund handling, qualifying refund and revocation rules, support escalation, and any relevant Google Play policy references before publishing payment terms. No refund approval or time period is promised by this draft.

5. Expiration and data

When an offline code is expired or invalid, the app returns to activation. The current app data is not deleted by license expiration; it remains in local device storage unless the user clears AQUAWASH app storage or uninstalls the app. Access to app functions requires valid activation. The user manages database backup and restoration through app backup files. The app can export a ZIP backup without app-level encryption; keep exported files in a secure location. Activation information is stored separately from the business database.

6. Account, device, and transfer rules

The current app creates local owner and staff sign-in profiles with PIN access; these are not central online accounts. Staff profiles can be deactivated, but the reviewed interface does not permanently delete a profile or provide a user account-deletion request flow. A local profile is removed from the device when app storage is cleared or the app is uninstalled. License codes are tied to the activation device fingerprint; the operator must define how device replacement, transfer, lost-device recovery, and code reissue work. The app project does not implement Google Play account entitlement restoration.

7. Acceptable use and business records

Users are responsible for lawful use, accurate transaction entry, securing device access and exported backups, and having an appropriate basis to enter customer information. Users should not attempt to bypass license checks, reverse engineer signed licensing material, or use the app unlawfully. The operator must review these restrictions and their enforceability.

8. Intellectual property

AQUAWASH name, app code, logo, design assets, and other content are owned or licensed by their respective rights holders. Ownership, third-party notices, permissions, and precise license grant language must be confirmed by the operator.

9. Availability and updates

The app depends on the Android device and its local storage. Cloud sync is not currently implemented. The operator must define support coverage, maintenance, compatibility, product changes, app updates, any service discontinuation notice, and any data-export period before publication.

10. Suspension and termination

The operator must state when activation may be refused, suspended, or terminated, how users can export records, how refunds are handled where applicable, and how lawful and consumer rights are protected. These details are not specified in the current source.

11. Warranties and liability

Warranty disclaimers, consumer guarantees, limitation of liability, indemnity, and any exceptions must be drafted for the actual operator and reviewed under applicable law. This draft makes no attempt to limit rights that cannot legally be limited.

12. Governing law and dispute process

Governing law, venue, and dispute-resolution procedures require confirmation by the operator’s legal entity and Philippine counsel. Add the final approved language here.

13. Changes and contact

Effective date: 24 October 2026. Provider: AeDev, postal address Payatas, Quezon City, Philippines. Support: adriel.dev.123@gmail.com.