Reference

Privacy Policy for Your cemara123 Account

cemara123 Privacy Policy shows what we collect when you create an account, verify your phone and use wallet options such as DANA or QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
cemara123 Privacy Policy for Your cemara123 Account
HELP WITH PRIVACY

Get a Clear Route for Data Questions

A privacy question should not be mixed with a general lobby request, so we separate account, wallet and data matters in our support path.

Account data desk Ask us to confirm the account details connected to your verified phone number. We use the signed-in account route to reduce mistaken disclosures and can explain which fields are needed for access, correction or a privacy request.
Wallet record desk If a DANA, OVO, GoPay or QRIS reference appears in your history, tell us the date and visible reference only. We can trace the record for a privacy question without asking you to share a wallet PIN or login password.
Request follow-up For deletion, correction or access questions, send the request through the account contact route and keep your confirmation message. We will explain identity checks, available choices and any retention reason that limits immediate removal.
CONTROL YOUR DETAILS

What We Do With Your Account Data

Privacy on cemara123 is handled through practical account steps rather than hidden settings. Phone verification helps us connect a request to the right account, while sign-in and device signals help identify unusual…

Data collected

We may record your account profile, verified phone number, sign-in events, device signals, support messages and payment references. These details help us provide account access, investigate a security concern and answer a specific Privacy Policy request.

Cookie choices

Cookies can support sign-in continuity, language display and security checks. Your browser may let you restrict them, although necessary settings can affect account access. Our policy explains the purpose of each cookie category and the choices available.

Account security

Phone verification is an account step before access, and we may examine sign-in or device changes when a request looks unusual. We will not ask for your password or wallet PIN as proof during a privacy contact.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can help us reconcile your account activity. We use the reference needed for that purpose and do not ask you to provide private wallet credentials.

Retention questions

Some account, security or transaction records may remain for a period connected to legal, dispute or safety needs. You can ask why a record is retained, what category it belongs to and whether a shorter period is possible.

Change or deletion

You can request a correction or ask about removal through the signed-in account contact route. We may need to verify the phone linked to your account, and we will explain any field that cannot be deleted immediately.

Privacy Policy Answers Before Account Access

These Privacy Policy answers focus on the questions we expect before an Indonesian account is opened or a wallet record is checked. They cover the data connected to your phone verification, the device used for sign-in, payment references and the route for asking us to change or remove details. If your situation is not listed, use the account contact path.

It covers data connected to your account, phone verification, sign-in events, device signals, cookies, support messages and payment references. It also explains why we use each category, how retention works and how you can ask for access, correction or deletion where local law permits.

We use your phone number to complete the account verification step, connect you to the correct profile and help protect account access. It may also help us match a privacy request. We do not need your wallet PIN or login password for that request.

Yes. The policy covers payment references shown in your account when you use DANA, OVO, GoPay or QRIS. Bank transfer and virtual account references may also be recorded for reconciliation. These references are handled separately from private wallet credentials.

Sign in, open the account contact route and ask for a data access request. Include the phone number linked to your profile and the category you want checked. We may verify ownership before responding, so another person cannot receive your account details.

You can request a correction or ask about deletion through the same account contact path. We will check the request against your verified account and explain any records that must remain for security, dispute handling or legal reasons. Availability depends on local law.

On a mobile browser, cookies may support sign-in continuity, security checks and saved policy choices. Your browser controls can restrict them, but necessary settings may affect access. The policy explains the purpose of these files and how to change available preferences.

Use the contact route shown inside your signed-in account and label the message as a privacy request. Share the relevant account category, date or payment reference, but never send a password or wallet PIN. We will explain identity checks and the next response step.