Reference

protogel 008 Privacy Policy: Your Account Data

Your phone verification, wallet records and browser choices are covered clearly in the protogel 008 Privacy Policy.

Phone verificationCookie choicesContact route
protogel008.club page image
POLICY CONTACT PATH

When Account Data Needs Help

A clear contact path helps when a privacy question appears beside a login or wallet-status issue. Tell us the account step involved, such as phone verification, a QRIS receipt or a mobile-browser session, and we can direct the request to the right record without asking you to share a password. If you are in Jakarta, use the same policy route and include the relevant reference.

Team online

Account records

Ask us to check the account identifier, phone-verification record or sign-in event connected with your request. We use the details you provide to locate the correct account without requesting your password.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the payment reference and receipt status. We use that reference to separate a privacy request from a cashier-status query.

Change requests

Use our policy contact route to request a correction, access copy or clarification about retention. We may ask for an account step that confirms you control the account before making a change.

OUR DATA PRACTICE

How Cookies And Account Data Work

We keep this policy practical by linking each data use to an account action you recognise.

Data handling

We use account identifiers, phone-verification results, device signals and payment references for access checks, status matching, fraud prevention and support. We do not need a wallet password to investigate a DANA or QRIS reference.

Cookie controls

Cookies can remember a session and selected account path on your mobile browser or desktop. Clearing them may require another sign-in, while changing browser settings can affect the session records we receive.

Account security

Phone verification before account access helps us connect a request to the right account. We also examine sign-in and device signals when a login pattern needs confirmation or a wallet status appears unusual.

Retention timing

We retain account, receipt and support records for the period needed for the stated purpose, account protection, dispute handling or a legal request. Records no longer needed are removed or changed so they cannot identify you.

Who receives requests

Our policy support route receives questions about access, correction, cookies and retention. Cashier-status details can be passed to the relevant account-support team, but the request remains tied to the privacy purpose you state.

Requesting changes

You can ask for a copy, correction, deletion assessment or explanation of a record. Include your account identifier and the relevant step, such as phone verification or a GoPay receipt, so we can check ownership.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the records you create through account access, wallet references and support contact. We keep the route specific so you know what to send, what we may verify and how local requirements affect a request. The policy applies to mobile-browser and desktop sessions used from Indonesia where local law permits.

It covers account identifiers, phone verification, sign-in and device signals, cookies, payment references, receipts and support messages. It also explains purposes, retention, security practices and ways to request access or correction.

No. We use payment references and receipt status to match a DANA, OVO, GoPay or QRIS action to your account. We do not ask for a wallet password through our policy contact route.

Send a request through the policy contact route with your account identifier and the relevant step, such as phone verification or a mobile-browser sign-in. We may confirm account control before providing records.

Yes. State which record appears wrong and provide the account step or receipt reference that helps us locate it. We assess the request, confirm ownership where needed and update the record when appropriate.

A mobile-browser cookie can keep your session and selected account path available while you move between login and the lobby. Clearing cookies may end that session and require phone verification again.

We keep payment references, receipts and related account records only as long as needed for their stated purpose, account security, dispute handling or a legal request. We remove or change records when that need ends.

Yes. Access and eligibility depends on local law. A request may therefore require an ownership check or a different handling step when Indonesian requirements apply to the account, device or payment record.