Reference

amatogel Privacy Policy for Your Account Data

Our Privacy Policy explains what we collect when you open an amatogel account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesSecurity steps
amatogel amatogel Privacy Policy for Your Account Data
HELP PATH

Reach Us About Privacy Policy Requests

A clear contact route helps you ask about personal data without explaining the same issue repeatedly. Include your account phone number, the relevant date and the request you want us to handle; never send a password or wallet PIN. We can then direct the matter to the appropriate account or payment-status team.

Team online

Policy questions

Use our support contact path for questions about the Privacy Policy, collected account details, cookie use or the reason a particular record is retained.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, share the receipt reference and account phone number so we can trace the matching record.

Change request

Ask us to correct an account detail through support. We may request account verification before changing personal data, protecting your account from unauthorised edits.

SECURITY PRACTICE

See How amatogel Handles Account Data

We treat the Privacy Policy as an operating process rather than a page you read once. Account creation, phone verification, wallet matching and sign-in activity each create records with a defined purpose.

Account details

We use the details you submit during account creation to identify your account, complete phone verification and respond to a request connected with that account.

Device activity

Sign-in time, browser or mobile device signals may be recorded to detect unusual access. These signals help us protect the account without treating every new device as suspicious.

Cookies

Cookies can keep your session working, remember selected settings and help us understand which policy page brought you to an account step. Your browser controls cookie removal.

Account security

Phone verification is part of the account access path. Keep your verification details private, and contact support promptly if a sign-in or wallet record does not match your activity.

Retention

We retain account, support and payment references for as long as needed for the stated service, account protection, dispute handling or legal duties that apply to the record.

Your requests

You can ask what personal data is held, request a correction or ask a policy question through support. We may verify account ownership before releasing or changing records.

Ask About amatogel Privacy Policy

These Privacy Policy answers address the searches we hear most often before account creation. They cover payment records, mobile access, cookies, corrections and the steps needed to make a request. Where eligibility or access is relevant, it depends on local law.

It covers account details, phone verification, device signals, cookies, support messages, payment references, retention practices and the way you can request access or corrections.

We use DANA and QRIS references to match a payment event with your account, show the correct status, investigate receipt questions and protect the account from unusual activity.

Yes. The Privacy Policy covers OVO and GoPay records in the same practical way, including the payment rail, reference, status and account details needed for a status check.

We may collect the details you submit, phone verification status, sign-in events, device signals and support messages. We use each category for the purpose explained in the policy.

Contact our support path with your account phone number, the detail needing correction and a short explanation. We may verify ownership before changing the record.

Retention depends on the purpose of the record, account protection needs, dispute handling and legal duties. Payment references may remain after a wallet status is resolved.

Yes. Ask support about cookies linked to your session and settings. You can also use your browser controls to remove stored cookies or adjust cookie behaviour.