Source hierarchy
- Use official government material for the legal framework and state its publication date.
- Use publisher store records for app identity; distinguish that from a hands-on test.
- Use identified card-rule references and disclose meaningful rule differences.
- Use the reference archive only to study navigation and illustrate names, not as proof of app safety or payouts.
Evidence labels
| Claim | Evidence needed |
|---|---|
| Official app | Publisher ownership and a matching product record |
| Latest APK | Authenticated current release metadata |
| Tested on Android | Recorded device, OS, build and actual test results |
| Bonus or withdrawal | Current terms and verification; legal review for money-linked features |
| Author expertise | A real, accountable person and substantiated background |
This delivery does not have those records for a Master APK. We therefore use no official-app badge, fake reviewer identity, security seal or invented testimonial.
AI assistance and originality
This version uses AI-assisted explanatory writing, manually specified worked examples, original SVG reference graphics and a deterministic browser exercise. App icons come from the user-archived third-party reference where indicated. An explanatory guide is not described as a first-hand product review.
Automated text does not establish personal experience. Any future claim of testing should be added only after the operator records and verifies that test.
Corrections and updates
The visible review date refers to preparation of this guide, not a claimed APK release date. Recheck government sources when the law changes and publisher records before changing app claims. Update the page and its structured date only when the content is meaningfully revised.
An editorial contact channel has not been configured yet. See contact information for the details needed to identify an error. Do not send credentials or payment secrets to a third-party guide.
Commercial transparency
This packaged version has no third-party advertising scripts or active affiliate download destination. If a future operator adds a commercial relationship, it should be disclosed beside the relevant link and in this policy. Payment must not be represented as independent evidence of product quality.
Source records instead of empty specification fields
Release claims from a competitor snapshot are labelled with that source and date. Store facts are linked to the exact package. Empty version, size and certificate rows are omitted; the visible table contains only fields for which a value and scope can be stated. The source register records conflicts and excluded claims.