Reference

Privacy Policy for Indonesia Account Access

republik365 Privacy Policy explains how we handle your account details, device signals and payment references when you open the lobby from Indonesia.

Account clarityCookie choicesWallet referencesPolicy requests
republik365 Privacy Policy for Indonesia Account Access
ACCOUNT HELP ROUTE

Where To Ask About Privacy Policy

A clear support path helps you resolve a Privacy Policy question without sending sensitive details through an unsuitable channel.

Policy request Use the account help path to ask what personal details we hold, why a…
Wallet query If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, point it out through…
Access concern When a mobile-browser session or phone verification step raises a privacy concern, tell us…
DATA CONTROL DETAILS

Inside republik365 Privacy Controls

Privacy work is part of the account path, not a separate promise added after payment or login.

Account records

We use contact details and phone verification to create the right account record and protect sign-in activity.

Device signals

A mobile browser or desktop session can produce device, browser and security-event data.

Cookie choices

Cookies can keep a session working, remember selected settings and help us understand security events.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create a reference or status record.

Retention checks

We keep personal records for the time needed to provide account access, settle a payment query, protect the service or…

Change requests

You can ask us to explain, correct or review a personal record through the signed-in support path.

Privacy Policy Questions For Your Account

These Privacy Policy answers address the account and device questions you may have before opening access from Indonesia. We keep the route practical: check the policy page, use your account help path, and provide only the details needed to verify a request. Where eligibility or access is relevant, it depends on local law.

The republik365 Privacy Policy covers account details, phone verification, login activity, device signals, cookies, support records and payment references. It explains why we use each category, how retention works and how you can ask about, correct or restrict a record where the applicable rules allow.

We may receive a DANA or QRIS payment reference, status and limited wallet details needed to match an account action. We do not need unrelated wallet content for that task. If a reference looks wrong, use account support so we can check the linked record.

Phone verification helps us connect the correct contact to your account and respond to private requests safely. The verification result can be retained with account security records. If your number changes, ask through the signed-in support path so we can confirm the request before updating it.

The Privacy Policy allows device type, browser details, session markers and security events to be used for login protection and access checks. We do not need unrelated files or content from your phone. Browser settings can limit cookies, but may affect session continuity.

We keep a record while it supports account access, payment reconciliation, security, support or a legal duty. The period depends on the purpose and applicable requirements. Once the purpose ends and no duty remains, we remove the record or reduce it so it no longer identifies you.

Open the signed-in account help area and describe the field you want corrected, such as a contact detail or phone number. We may ask for account verification before making a change. This step protects your record from an unauthorised request and keeps the correction traceable.

Yes. Send a request through the account support path and identify the account contact used for access. We will explain the relevant records and any processing purpose after verification. Some details may remain where retention is required for security, payment or legal reasons.