Freeze the store listing
Record the listing URL, exact app name, publisher, category, age rating, version and update date. Search position and screenshots are discovery clues, not identity evidence.
This page is a decision worksheet built around a specific search task. It separates observable records, first-party wording and unresolved claims so the conclusion can be checked again after a material change.
Match the publisher trail
Follow the developer website, privacy policy and support links. They should identify an entity and domain that can be reconciled with the service’s current legal documents.
Read the privacy label critically
List data linked to identity, tracking claims and stated purposes. Treat the label as publisher-supplied disclosure and compare it with permissions requested after installation.
Check device and region support
Confirm minimum iOS version, iPhone/iPad compatibility and Australian store availability. A listing in another storefront does not prove local account eligibility.
Verify the account hand-off
Before signing in, inspect the final hostname opened by registration, KYC or cashier actions. Stop if the app requests passwords, one-time codes or payment data through an unrelated domain.
A store review is not a legal or payout guarantee
App Store distribution can reduce some installation risks, but it does not establish that an online casino service may lawfully be offered to a person in Australia or that withdrawals will succeed. Keep app identity, operator status and payment evidence as separate decisions.
Questions this page resolves
Can an iOS app use a different name from the casino?
It can, which makes publisher, support-domain and legal-entity matching essential.
Does an App Store privacy label prove what the app collects?
It is useful disclosure, but compare it with observed permissions and the current privacy policy.
What should I save before an update?
Record the listing, publisher, current version and any account or transaction references needed for support.