Reference

Your Privacy Policy, in one place

We tie this policy to the actions you actually take: opening an account, confirming your email, using DANA, OVO, GoPay or QRIS, and moving between mobile and desktop.

Account dataCookie useDevice logsChange requests

Browse Lobby Read FAQ

What this policy covers

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

This policy covers the data that moves when you create an account, confirm your email, match a wallet name, browse on Android or iPhone, and send a message to support. We collect only the details needed to run sign-in, keep sessions secure, record consent choices, and

1
answer requests through email or the in-account form. Payment rails such as DANA, OVO, GoPay and QRIS appear here only as context for transaction logs and account matching; we do not use them for extra profiling. We keep the retention window tied to support and record-keeping,
2
then archive or remove data when it is no longer needed. If local law conflicts with a request, local law controls. Where local law permits, you can ask for access, correction, or removal, and we will answer through the same address or inbox you used before.

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

HELP ROUTES

How to reach us on privacy matters

The cleanest path is the in-account form, because it attaches your request to the right record without asking you to repeat everything.

PRIVACY CONTROLS

How we handle your account data

We build the policy around the account steps you actually take: login, wallet matching, device checks, cookies, and support requests.

Data we keep

We store the details you enter at signup, the email tied to your account, wallet matching markers, login timestamps, device type, and the privacy message you send. We avoid extra fields unless they are needed for the request.

Cookie use

Our cookies handle sign-in, language choice, and session length. On Android, iPhone, or desktop, they help you stay logged in safely until you sign out or clear the browser session.

Account checks

When you reset a password or switch devices, we may ask for a fresh login code or a recent account detail. That step helps us stop unauthorised access without slowing your own access.

Retention window

We keep records only as long as they are needed for account support, dispute handling, audit checks, or lawful requests. After that period ends, we remove or archive the data under our internal process.

Who sees it

Only trained staff who handle support, finance, or security checks can open the records tied to your request. We do not share them with unrelated teams, and we do not publish them on public channels.

How to change it

Send a request from Account > Settings > Privacy, or email the address linked to your profile. If we need to confirm ownership, we may ask for the login email and one recent transaction marker.

Common privacy questions for your account

If you are checking how this policy works before you open an account, these are the points that usually matter most: what we keep, how you can ask for changes, how long we retain records, and how we confirm your identity before we act. We keep the answers tied to account use, device behaviour, and the support channels above, so you can decide what to share and when.

We collect the details needed to create and secure the account: email, phone number if you add it, login history, device type, and the wallet name or payment marker that matches your request. We do not ask for more than we need.

Cookies keep your session alive, remember language choices, and store simple preference settings. They also help us tell a fresh login from a suspicious one, so we can protect access without making you repeat the same steps.

Yes, where local law permits. Send the request from the email on your account or through Account > Settings > Privacy, and we will use that path to check the record and reply with the next step.

Send the corrected detail and the matching account email, and we will compare it with the record before we update anything. If the change affects security or wallet matching, we may ask for a second check.

We keep it only as long as needed for account operation, support history, dispute handling, and lawful retention. After that period ends, we remove or archive it under our internal process.

Use the in-account form first, or email the address listed in the support section. That gives us the cleanest trail for access requests, corrections, cookie questions, or deletion requests where local law permits.

Your Privacy Policy, in one place

How to reach us on privacy matters

How we handle your account data

Data we keep

Cookie use

Account checks

Retention window

Who sees it

How to change it

Common privacy questions for your account

01 What data do you collect when I open an account?

02 Why do you use cookies?

03 Can I ask for a copy of my data?

04 How do I correct wrong details?

05 How long do you keep my data?

06 Who should I contact about privacy?

Related Pages