Reference

roti123 Privacy Policy for Clear Account Choices

roti123 Privacy Policy explains what we collect when you create an account, complete phone verification, sign in from a mobile browser and use the lobby.

Account clarityWallet contextCookie choicesMobile access

Explore Our Lobby Read FAQ

How Wallet Records Fit Privacy Policy

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

Our Privacy Policy separates information needed for account access from records created when you choose a payment route. A phone number and verification result help us match you to your account, while a DANA, OVO, GoPay or QRIS reference helps us check wallet status without treating

1
your wallet PIN as an account field. Bank transfer and virtual account references may also appear in transaction history. We use these records to confirm requests, investigate mismatched status and protect account access. If you browse from Bandung or elsewhere in Indonesia, the available service path
2
depends on local law. You can ask us to explain a data field, request a correction or ask how long a record is retained through the contact route described below.

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

POLICY HELP DESK

Get Privacy Answers Before Wallet Access

A clear support path helps when you want to understand a data field rather than change a game setting.

DATA HANDLING

Your Data Path From Login to Lobby

We keep the Privacy Policy practical by describing the points where information enters our service. Login, phone verification, wallet status and device behaviour each have a different purpose, while cookies help remember…

Account details

We use the details you provide at account creation to identify your account and support sign-in. Phone verification confirms that an access request is connected to the contact detail recorded for you.

Wallet references

DANA, OVO, GoPay and QRIS may produce a visible payment reference or status. We use that reference to match a request and check a receipt; we do not ask for your wallet PIN.

Cookies

Cookies can remember a selected language, session state or device preference. You can adjust cookie controls in your browser, although limiting them may require you to sign in again.

Device signals

A mobile browser may share basic device and session signals used to keep an account session working and identify unusual access. These signals are assessed for account protection, not used as your wallet password.

Retention timing

We retain account, support and transaction records only for the period needed for the stated service, security and record-keeping purpose. Ask support about a specific record to receive a clearer retention explanation.

Change requests

You can ask us to access, correct or remove personal data through the signed-in support path. We may verify your phone before acting, and we explain any request that cannot be completed.

Privacy Policy Answers for roti123 Accounts

These Privacy Policy answers focus on the questions that arise before account access, wallet use or a request about stored data. We describe the practical path for Indonesian accounts, including phone verification, browser cookies and payment references. Where a request depends on identity or local rules, we explain the next step rather than leaving you to guess.

The roti123 Privacy Policy covers account details, phone verification, cookies, device signals, support messages and payment references from routes such as DANA, OVO, GoPay and QRIS. It explains why each category is used, how we protect access and how you can ask about your records.

Phone verification connects an access request with the account contact detail you supplied. We use it to reduce mistaken or unauthorised account discussions, especially when you ask about a QRIS receipt, wallet status or stored account data. We do not need your wallet PIN for this step.

We may retain a DANA or QRIS reference, amount status and related account step so we can match a payment request or explain a receipt. The Privacy Policy treats these as transaction records, while wallet credentials such as a PIN should remain with your payment provider.

Yes. Use the signed-in support route and identify the field you believe is inaccurate, such as a phone detail or account name. We may complete phone verification before changing it, then confirm whether the correction was made or explain why another check is needed.

Cookies can keep your session, selected settings and device preference available while you move from login to the lobby on a mobile browser. You can restrict them in browser controls, but doing so may sign you out or require repeated account verification.

Retention depends on the purpose of the record, including account support, security checks and transaction history. The Privacy Policy does not treat every record alike. Ask us about a particular login, wallet reference or support message, and we will explain the applicable retention reason.

Use the account support route with your identifier and a short description of the request. You can ask about access, correction, deletion, cookies or payment references. We may verify your phone before sharing personal details, and service access depends on local law.

roti123 Privacy Policy for Clear Account Choices

Get Privacy Answers Before Wallet Access

Your Data Path From Login to Lobby

Account details

Wallet references

Cookies

Device signals

Retention timing

Change requests

Privacy Policy Answers for roti123 Accounts

01 What does the roti123 Privacy Policy cover?

02 Why does roti123 need phone verification?

03 How are DANA and QRIS records handled?

04 Can I ask roti123 to correct my personal data?

05 How do cookies affect my mobile access?

06 How long does roti123 keep account records?

07 Where can I ask about a Privacy Policy request?

Related Pages