Reference

Read our Privacy Policy before account access

Our god911 login Privacy Policy explains what we collect, why we use it and how you can ask about your account data before opening access.

Clear data purposesWallet details explainedYour request pathMobile privacy choices
god911 login Read our Privacy Policy before account access
REQUEST HELP

Ask about Privacy Policy and account data

A clear contact path matters when a privacy question affects your login or wallet record.

Privacy request Ask us to explain, correct or remove eligible account details through the support path connected to your god911 login profile. Include your registered phone or email so we can check identity before discussing records, and avoid sending passwords, wallet PINs or full bank credentials.
Wallet record query If your question concerns a DANA, OVO, GoPay or QRIS reference, provide the date and visible status rather than a wallet password. We can compare the account record with the receipt reference while keeping payment credentials outside the request conversation.
Access concern When a sign-in or phone-verification issue may involve personal data, use the account support route before creating another profile. We can connect the request to the existing record and explain the next step where access depends on local law.
DATA HANDLING

Explore how our Privacy Policy works

Our handling process follows the account action that created the record, rather than collecting every detail by default.

Account details

We may hold your registered contact details, phone-verification result and account activity needed to provide access. These fields help us distinguish your profile from another request, and we use them for the stated account and security purposes described in this Privacy Policy.

Device sessions

When you open the lobby on a phone, tablet or desktop browser, we may record device, browser and session signals. This helps us recognise a sign-in pattern and investigate an access concern without treating your device as a separate account.

Cookies

Cookies and similar storage can keep a session active, remember a selected language or record a privacy choice. You can review cookie controls in your browser settings, although switching them off may affect account access or require another phone check.

Security checks

We use phone verification, sign-in records and account matching to reduce confusion around profile ownership. Never send a password, one-time code or wallet PIN in a support message. If a request changes account data, we may ask for additional proof.

Retention timing

We keep records only for the period needed for the purpose described, account security, dispute handling or applicable legal duties. A DANA receipt reference and a phone-verification event may therefore follow different retention paths, depending on the request.

Change requests

You can ask us to access, correct or clarify eligible personal data through the support route connected to your account. Tell us which field is wrong and include the account contact detail; we will explain any identity check or legal reason affecting the request.

Browse Privacy Policy answers for god911 login

These Privacy Policy answers focus on the questions you may search before opening an account from Indonesia. They cover the records created by phone verification, mobile sessions and local wallet references, along with the practical route for requesting a copy, correction or explanation. If your situation involves account eligibility or access, the answer depends on local law. Use the support path linked to your account when a question needs a record-specific response.

It covers account details, phone-verification records, device and browser signals, cookies, support messages and transaction references. The Privacy Policy also explains why we use these records, how retention can vary, and how you can ask about eligible access or corrections.

Yes. The Privacy Policy treats DANA, OVO, GoPay and QRIS references as payment-context data used to match a receipt or status question. We do not need your wallet PIN or password for that check, and you should never send either in support.

Phone verification links an access event to the account contact detail you provide. We may use the result to confirm profile ownership, investigate sign-in confusion and protect account discussions. If you request a change, we may ask for another identity check.

You can contact us through the support path connected to your account and specify whether you want access, correction or clarification. Include your registered phone or email, but not your password or wallet PIN. We will explain the next step and any applicable limitation.

Retention depends on the type of record and the reason it was created. A session signal, phone-verification event, support message and QRIS receipt reference may follow different periods. We keep information for the stated purpose, security, dispute handling or applicable legal duties.

Cookies or similar storage may maintain a mobile browser session and remember a privacy choice. You can adjust them in your browser settings. If you disable required storage, the account may ask for another sign-in or phone check before access continues.

Use the support route shown inside your account and describe the record or policy point you want clarified. For a wallet matter, mention only the visible date and status of the DANA, OVO, GoPay or QRIS reference when requested.