Reference

Open With Clear Privacy Terms

DANA, OVO, GoPay and QRIS wallet details are handled only for account checks, transaction matching and support follow-up on logototologin.

Account dataCookie choicesWallet checksWIB support

Browse The Lobby Read FAQ

Explore How Your Data Is Used

logototologin Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Your Privacy Policy starts with a simple rule: we collect only the data needed to create your account, secure your login, match wallet activity and answer your support request. That can include your mobile number, username, device type, IP area, cookie choice, payment rail label and

1
transaction reference from DANA, OVO, GoPay or QRIS. We do not sell your personal data. We may share limited records with payment processors, fraud-screening tools or service staff when that step is needed to run the account, verify a payout request or meet a lawful request.
2
Our access rules follow local law, so availability depends on where local law permits. If you change your phone, update your wallet or ask us to correct a profile detail, we log the request so the next support agent can see what changed and when.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Check Privacy Contact Routes

Privacy questions need a clear path, not a generic inbox. Our support team handles account-data requests every day from 10:00 to 22:00 WIB through live chat, WhatsApp and email.

Live chat Use live chat for quick privacy questions about cookies, login alerts or a recent wallet check. We may ask for your username and the last four digits of the transaction reference to confirm account ownership.

WhatsApp support WhatsApp is available during 10:00 to 22:00 WIB for data correction requests, phone-number changes and privacy follow-up. Do not send card photos; share only the account detail we request in the chat.

Email request Email is better for deletion, export or retention questions because we can attach a case ID. Include your username, registered mobile number and the request category so our privacy handler can respond without delay.

DATA HANDLING

Browse Data Controls Before You Join

Your privacy settings sit close to the account tools you use most. In Account > Privacy, you can check cookie choices, marketing contact status and saved session activity.

Account data

We collect the profile details needed to identify your account: username, mobile number, password hash, referral source if used and support case history. These records help us recover access if you lose your phone.

Payment records

Wallet data is stored as transaction references, timestamps, rail names and status labels for DANA, OVO, GoPay and QRIS. We use it to match deposits, verify payout requests and answer payment privacy questions.

Cookie choices

Cookies keep your session active, remember language preference and measure page errors. You can manage choices from Account > Privacy > Cookie choices; some login cookies stay active because the account cannot work without them.

Device checks

We record device type, browser version, IP area and login time when you access the lobby. These signals help us detect unusual sign-ins before your wallet or game history is changed by another person.

Retention rules

We keep account and transaction records only as long as needed for service, dispute handling, security checks and legal duties. When records no longer serve those purposes, we delete or anonymise them in scheduled cycles.

Change requests

You can ask us to correct profile data, export account records or close data tied to an inactive account. We verify ownership first through your registered mobile number, username and recent account activity.

Check Privacy Answers Before Account Setup

This Privacy Policy is written for the account steps you actually touch: registration, login, wallet matching, cookie choices and support. If a privacy issue is not answered below, contact us during 10:00 to 22:00 WIB and include the account detail linked to your request.

We collect your username, mobile number, password hash, device details, IP area and the wallet rail you use. We also store support case history when you contact us about privacy, access or transaction matching.

We use wallet references to match deposits, check payout requests and resolve disputes. The record usually includes rail name, timestamp, amount status and reference code, not full wallet login credentials.

Yes. Contact live chat, WhatsApp or email with your username, registered mobile number and the detail that needs correction. We verify ownership before changing profile data, wallet labels or contact settings.

Cookies keep you signed in, remember language choice and help us find page errors. You can manage choices in Account > Privacy > Cookie choices, but essential login cookies must remain for account access.

We keep records while they are needed for account service, transaction checks, security monitoring, dispute handling and legal duties. After those needs end, records are deleted or anonymised through scheduled retention work.

Only staff assigned to support, payment checks, security or legal handling can access the case details they need. We log access to sensitive records so requests can be traced internally.

Go to Profile > Security > Sessions and remove the session you do not recognise, then contact support. We may ask for your username, registered mobile number and recent wallet rail used.

Open With Clear Privacy Terms

Check Privacy Contact Routes

Browse Data Controls Before You Join

Account data

Payment records

Cookie choices

Device checks

Retention rules

Change requests

Check Privacy Answers Before Account Setup

01 What personal data does logototologin collect when I open an account?

02 Why do you need DANA, OVO, GoPay or QRIS transaction details?

03 Can I ask for my account data to be corrected?

04 How do cookies affect my privacy on this site?

05 How long do you keep my account and payment records?

06 Who can see my privacy request inside your team?

07 What should I do if I notice an unknown login?

Related Pages