Reference

amergg Privacy Policy for Indonesia Accounts

Our Privacy Policy explains how amergg handles the account, device and wallet details you provide when you open access to the lobby.

Clear data purposesWallet record contextDirect request path
amergg amergg Privacy Policy for Indonesia Accounts
PRIVACY HELP

Get Privacy Answers Before Opening Your Account

A privacy question should not leave you guessing, so we keep the contact route close to your account and wallet path.

Account data request Ask through the account support route when you want to know which profile, phone…
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account queries, share the transaction…
Access concern If a mobile browser or desktop sign-in looks unfamiliar, contact support through the account…
DATA CONTROL

What Our Privacy Process Covers

We keep the Privacy Policy practical by linking each data purpose to an account action you can recognise.

Data we handle

We may handle your phone number, account settings, sign-in events, device details and payment references. We use these categories to provide account access, resolve wallet questions and protect the record from misuse.

Cookies and browser use

Cookies can remember session state and selected preferences so a mobile browser can return to the correct account step. You can manage browser cookie controls, though some account functions may then need another check.

Account security

Phone verification, sign-in timestamps and device signals help us identify unusual access. If you move from mobile to desktop, we may ask for an additional account check before showing protected wallet or profile details.

Retention of records

We retain account and transaction records only for the period needed for service, security, dispute handling and legal duties. When a retention period ends, records are deleted or separated from direct account identification where practical.

Who receives a request

Our support route is the first place for Privacy Policy questions. We may need to confirm your account phone number before discussing personal records, and we do not ask you to disclose a wallet PIN or verification code.

Changing your details

Request a correction when your phone, profile or account detail is inaccurate. For deletion or access requests, we first verify ownership, explain any records we must retain, and respond according to applicable local law.

Privacy Policy Answers for amergg Accounts

These Privacy Policy answers focus on the account steps Indonesian customers ask about most often. They explain wallet references, browser activity, security checks and request handling without asking you to share sensitive credentials. If your situation is specific, use the support path with the smallest useful amount of account detail.

It covers account details, phone verification, device and browser events, cookies, payment references and support requests connected with your amergg access, where local law permits.

A DANA or QRIS transaction reference may be stored to match payment status and resolve disputes. We do not need your wallet PIN, and your external provider controls its own records.

Phone verification helps confirm account ownership before protected details are shown. It also supports security checks when your sign-in changes device, browser or location within the access record.

Yes. Contact support through your account path, identify the records you want, and complete an ownership check. We explain the available copy format and any lawful limits before processing.

Send a correction or deletion request through support with your account phone number. We check ownership, update eligible details, and explain records that must remain for security, disputes or legal duties.

Yes. The policy covers mobile browser sessions, cookies, device signals and sign-in timestamps. Moving from a phone to desktop may create a new security event and require another account check.

Yes. Account access and data requests depend on local law. We apply the Privacy Policy where local law permits and explain any restriction when a request cannot be completed as submitted.