Reference

33l Privacy Policy For Your Account

Your account data, wallet details and device choices stay at the centre of our Privacy Policy.

Account data explainedWallet details coveredCookie choices includedAccess requests available

How Our Privacy Policy Applies

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

Our Privacy Policy describes data used to create and protect your account, confirm your phone before access, process wallet activity and keep the lobby secure. This can include your contact details, device signals, login records, payment references and support messages. DANA, OVO, GoPay, QRIS, bank transfer

1
and virtual account references may appear in transaction records, while the payment provider handles its own data practices. We use cookies and similar tools to keep your session open and remember selected settings. Access to 33l and any related service depends on local law, and we
2
apply this policy where local law permits. If you stop using the account, we retain selected records for security, dispute handling and legal duties, then remove or anonymise them when the relevant purpose ends.

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

CONTACT PATHS

Get Help With Privacy Requests

A clear contact path helps when you want to ask about your data, correct an account detail or understand a wallet record. Start from your signed-in account support route and include the email or phone linked to your profile. We may ask for an account step before discussing private details, so a request reaches the right record.

Team online

Data access request

Ask us for a copy of the personal data linked to your account. Include your registered phone or email so we can locate the correct profile before replying.

Correction request

If your contact detail or account record needs changing, send the requested correction through our support path. We may confirm the account step before applying an update.

Wallet record help

For a DANA, OVO, GoPay or QRIS reference, share the date, amount reference and account contact. We use these details to check status without asking for your wallet password.

HANDLING DETAILS

What We Do With Account Data

We keep this Privacy Policy practical by linking each data use to an account task: access, payment checking, fraud prevention, support or legal retention.

Account security

We use phone verification before account access and review device or login signals when activity looks unusual. These checks help protect your profile without asking us to store your wallet password.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to your account. We do not treat a wallet reference as your wallet password.

Cookie controls

Cookies can keep your session active and remember settings between the login page and lobby. You can adjust browser cookie controls, although some account functions may then need another login.

Device behaviour

Our mobile page may record browser, device and session signals needed for access protection. This supports a single path from phone login to the lobby without reading unrelated files on your device.

Retention period

We keep account, payment and support records only for the period needed for security, disputes or legal duties. When that purpose ends, records are removed or changed so they no longer identify you.

Change requests

You can ask us to correct account data, request a copy or raise a concern through support. We may verify your registered phone or email before making a privacy change.

Privacy Policy Answers For 33l

These Privacy Policy answers cover the searches we hear most often about account data, cookies, wallet records and access. Each response points you toward a practical account step, including how to contact us and what details to prepare.

It covers account details, phone verification, device signals, cookies, payment references, support messages, retention and requests to access or correct data connected with your 33l account.

Phone verification helps confirm that you control the account before access or a privacy request. It also supports security checks when a login or device pattern appears unusual.

Yes. The policy explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can be used to match payment status, while each wallet provider follows its own data terms.

Use the signed-in support route and provide the phone or email attached to your account. We may verify that account step before preparing a copy of the data we hold.

Yes. Send the detail that needs correction through support, along with the registered contact and the requested change. We check the account record before updating or explaining the entry.

Cookies can preserve your login session and selected settings between mobile pages. Browser controls let you change cookie choices, though disabling them may require another login for some account steps.

We retain selected account, payment and support records while needed for security, disputes or legal duties. After the purpose ends, we remove or anonymise the relevant records where appropriate.

33l Privacy Policy For Your Account

Get Help With Privacy Requests

Data access request

Correction request

Wallet record help

What We Do With Account Data

Account security

Payment records

Cookie controls

Device behaviour

Retention period

Change requests

Privacy Policy Answers For 33l

01 What does the 33l Privacy Policy cover?

02 Why does 33l ask for phone verification?

03 Does the Privacy Policy cover DANA and QRIS data?

04 How can I request a copy of my 33l data?

05 Can I ask 33l to correct account data?

06 How does the Privacy Policy handle cookies on mobile?

07 How long does 33l keep my personal data?

Related Pages