Reference

Privacy Policy For Your rajalagit77 Account

Our Privacy Policy explains what we collect when you open a rajalagit77 account, sign in from a mobile browser, use DANA or QRIS, and move through the lobby.

Account dataWallet recordsCookie choicesSecurity steps
Explore Our Lobby Read FAQ
rajalagit77 Privacy Policy For Your rajalagit77 Account
CONTACT PATHS

Privacy Help Beside Account Support

A clear contact path matters when a Privacy Policy question concerns your own account rather than a general site query. We ask you to sign in where possible, describe the requested change, and include the relevant account or receipt detail without sending a wallet password. Our support route can then separate identity checks, payment records, cookie questions, and access requests before a response is prepared.

Team online

Account access

Use the account support path when you need to ask which personal details are linked to your rajalagit77 login. We may request a phone verification step before discussing account data, so a request is handled against the correct account rather than an unrelated session.

Wallet records

For a DANA, OVO, GoPay, or QRIS receipt question, include the payment reference and approximate time, but never share your wallet PIN. We use those details to locate the relevant account record and explain what was retained for payment matching.

Privacy requests

Ask through our support route to request access, correction, or removal where applicable. Tell us which data category concerns you, such as cookies, phone verification, or a transaction record, and we will explain the next identity and processing steps.

DATA PRACTICES

Six Ways We Handle Account Data

Privacy work follows the same account path you use every day: sign in, verify your phone, select a wallet route, and return to the lobby.

What we collect

We may collect your phone number, account identifiers, verification result, device and browser details, sign-in timestamps, wallet references, and support messages. When you open Fishing God or another lobby title, the related session record helps us maintain account continuity without needing your wallet password.

Why we use it

Account data supports sign-in, phone verification, payment receipt matching, security checks, and replies to your privacy request. A QRIS reference can help us identify a transaction status, while a browser signal can help us examine an unusual account access event.

Cookies and settings

Cookies and similar browser storage can remember a session, preserve selected settings, and help us understand whether a sign-in step completed. You can manage browser cookie controls, although changing them may require you to sign in again before opening the lobby.

Account security

We use phone verification before account access and examine signals such as device changes, repeated failed sign-ins, and unusual timing. If a security check pauses access, the support route can help after we confirm that the request comes from the account holder.

Retention periods

We keep different records for different operational reasons. A payment receipt or dispute record may remain while its status needs checking, while a temporary session signal can be removed sooner. When a purpose ends, we delete, aggregate, or restrict the record where applicable.

Your choices

You can ask what personal data we hold, request a correction, raise a concern about cookie use, or ask whether deletion is available. Send the request through support and identify the account step involved; we may verify your phone before responding.

Privacy Policy Questions About rajalagit77

These Privacy Policy answers focus on the questions you are most likely to ask before opening or using an account from Indonesia. They explain the practical route for account data, local wallet records, mobile browser sessions, cookies, security checks, and requests for access or correction. Where access is discussed, it depends on local law and applies where local law permits.

It covers account details, phone verification, device and browser signals, cookies, support messages, wallet references, and payment receipt records. It also explains why we use those details for sign-in, security, payment matching, and responding to your requests when you use the site.

Yes. The policy includes references needed to match a DANA or QRIS payment with your account, such as a transaction reference, status, and time. We do not ask for your wallet PIN. These records may remain while a payment question, dispute, or legal need is open.

We use your phone number to create and identify your account, complete the phone verification step, and help protect access from an unfamiliar session. If you request a data change, we may use that verification step to confirm that the request concerns your own account.

You can contact support with the account detail you believe is wrong and explain the correction requested. We may ask you to complete phone verification before changing it. We assess deletion or restriction requests against payment, security, dispute, and legal requirements.

The policy describes cookies and browser storage used to keep a sign-in session, remember selected settings, and check whether an account step completed. You can adjust cookie controls in your browser. Some changes may sign you out or require a fresh mobile browser session.

There is no single period for every record. Session signals may be kept for a shorter operational need, while payment receipts, support exchanges, or security records may stay available for status checks, disputes, or legal duties. We remove or restrict data when its purpose ends.

Use the account support route and state that your request concerns the Privacy Policy. Include the relevant category, such as phone verification, cookies, a GoPay receipt, or account access, without sending a password or wallet PIN. We can then explain the verification and response path.

Related Pages

rajalagit77 Indonesia About Us rajalagit77 Casino ligaspin88 FAQ