Reference

Open manara4d Privacy Policy for Your Account

This page explains how we collect, use, store, and share account data when you open an account, use DANA, OVO, GoPay, or QRIS, or ask support for help.

Account dataCookie useLocal lawContact path

Browse lobby Read FAQ

Explore What This Policy Covers

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

This policy covers the data we touch when you create an account, enter the lobby, make a payment, or ask us to change a record. That can include your name, phone number, email, device signals, cookie IDs, and the payment rail you choose, such as DANA,

1
OVO, GoPay, or QRIS, so we can match the request to the right account. If we need to mention access, sharing, or retention, the rule depends on local law and is available only where local law permits. We keep records only for the time needed to
2
run the account, handle disputes, meet legal duties, and answer your request. When a record is no longer needed, we reduce it or remove the parts we do not need. If the request comes from a new device, we may ask you to confirm from the
3
registered email or phone number first.

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

CONTACT ROUTES

Browse manara4d Privacy Contact Paths

If you want a copy, correction, or deletion request, start with in-account chat so we can match it to the right record.

In-account chat Open the chat panel from your account menu and send the privacy request you want handled. We use it for access questions, correction requests, and record checks, and the thread stays tied to your registered account.

Footer form Use the form linked in the footer when you want a written trail. Add your registered email, phone number, and the change you want, and we route it to the right support queue.

Support inbox Send a clear message from the email on file if you need a copy, correction, or deletion request logged. Include the date, channel, and payment rail name so we can match the account faster.

DATA HANDLING

Switch to Our Data Handling Rules

We keep the policy process practical: collect only what is needed for login, payment matching, device access, and support history.

Collection scope

We collect account, contact, device, and payment-reference data only when it helps us process login, deposits, replies, or dispute handling. We avoid asking for extra fields that do not support the request you made.

Cookie use

Cookies help us keep your session active, remember language choice, and spot repeated login attempts. On Android Chrome, iPhone Safari, or desktop browsers, you can clear cookies any time from browser settings.

Account security

If you change your phone number or email, we ask for a fresh check from the old contact and the new one. That step protects account control and keeps a clear trail for later requests.

Retention

We keep support threads, device logs, and payment references only as long as needed for operation, dispute handling, or legal duties. After that, we reduce the record or remove the parts no longer required.

Your requests

You can ask to access, correct, or delete data tied to your account by using the registered email, in-account chat, or the footer form. We answer in the same language you used when you wrote to us.

Change handling

Our support team and account-verification team handle privacy requests together. If we need more detail, we ask for the exact date, channel, or payment rail, such as DANA, OVO, GoPay, or QRIS.

Open Common Privacy Questions

These answers explain what data we keep, how you can ask for a copy or correction, and what happens when cookies are cleared on phone or desktop. We match every request to your registered email or phone number, because that is how we protect the account from mix-ups. If a request depends on local law, we say so before we proceed.

It covers the account, device, cookie, and payment-reference data we use when you join, contact support, or move through the lobby. It also explains when we share a record with service partners or legal authorities.

We may ask for your name, email, phone number, device details, and the payment rail you use, such as DANA, OVO, GoPay, or QRIS. That lets us match your request to the right account.

Use in-account chat, the footer form, or the registered email on file. We will verify the request from the contact details tied to the account before we change anything or send a copy.

Yes. Cookies keep your session active, remember language choice, and help us spot repeated login attempts on Android Chrome, iPhone Safari, and desktop browsers. You can clear them anytime in browser settings.

We keep support threads, session logs, and payment references only for as long as we need them for account operation, dispute handling, or legal duties. After that, we reduce or remove the parts we no longer need.

Start with in-account chat if you are already signed in, or use the footer form if you want a written trail. If needed, send the same request from the email or phone number on file.

Yes, when local law permits, we can confirm what we hold and process a request to access, correct, or delete the parts linked to your account. We may ask for a fresh check before any release.

Open manara4d Privacy Policy for Your Account

Browse manara4d Privacy Contact Paths

Switch to Our Data Handling Rules

Collection scope

Cookie use

Account security

Retention

Your requests

Change handling

Open Common Privacy Questions

01 What does this privacy policy cover?

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

03 How can I ask for a copy or correction?

04 Do cookies work on mobile and desktop?

05 How long do you keep my records?

06 Who should I contact about privacy changes?

07 Can I access my data if local law allows it?

Related Pages