Know what your AQUAWASH license covers.

1. Current activation method

New installations display a device ID and require a signed offline license code before business setup. The user obtains the code from an AQUAWASH provider and enters it in the app. Signature and device checks run locally; the app source does not contact a license server.

The fingerprint is derived from the app package identity and Android ID. A code issued for one fingerprint does not validate for another. Clearing app data removes the locally saved code, and changing devices may require a new code from the provider.

2. Time limit and expiration

The signed license payload contains a license ID, device fingerprint, and expiration Unix timestamp. An expiration value of zero is accepted as no-expiry; a nonzero value remains valid while it is equal to or later than the app’s current timestamp. The code does not define a purchase date, 30-day duration, calendar month calculation, 12-month duration, grace period, or renewal workflow.

Once the code is invalid or expired, startup returns to activation. The local business database is not deleted by the license check, but the app requires valid activation to proceed.

3. Requested license options

4. Features and entitlements

The current verifier recognizes whether a signed code matches the device and its expiry; it does not parse product tiers or feature entitlements. The app does not implement different plan access by SKU. The operator must confirm feature access across product types before claiming plans include identical or different features.

5. Google Play purchases

The current project contains no Google Play Billing library, product IDs, purchase token verification, or restore-purchases workflow. If billing is implemented, the final terms must explain the exact purchase step inside the app, whether and how Google Play user identity is associated with the local device-bound license, when access starts, how purchases are verified, and how restore, device change, upgrade, and refund behavior works.

6. Refunds and revocation

The repository contains no commercial refund policy or billing reversal process. Google Play products are not configured in the reviewed Android source. The operator must publish the actual support route and refund rules and must account for applicable Google Play and Philippine consumer requirements. License revocation after a qualifying refund must be implemented and described before it is promised.

7. Transfer, restoration, and backups

Activation is tied to the device fingerprint, not a Google Play account entitlement. No in-app restoration of Google Play purchases or license transfer is implemented. The app can export and import a local business database archive, but activation is stored separately; restoring a database should not be represented as restoring a license.

8. Data handling and service limits

Shop records are stored locally on the device. Cloud storage, online sync, and remote service availability are not provided by the current app implementation. A no-expiry code alone does not establish that all future updates, support, cloud services, or future features are included forever.

9. Operator contact

Company: AeDev. License support: adriel.dev.123@gmail.com. Postal address: Payatas, Quezon City, Philippines.