Reference

Open the legal page for Indonesia

Our legal page keeps account rules, data handling, and request steps in one place for Indonesia.

Local law firstAccount data useDesktop and mobile web

Browse lobby Read FAQ

Browse jurisdiction rules and account access

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

These rules define how we treat access, account data, and change requests for Indonesia. We check each case against local law first, then ask for the smallest set of details needed to confirm the account: registered name, current contact route, and the device you used when

1
the request was sent. If the location or eligibility test does not fit the law that applies to you, we stop the request instead of carrying it forward. That same rule stays in place on mobile web and desktop, so switching devices does not change the
2
outcome. For context, the chips below point to the local rails many accounts use in Indonesia: DANA, OVO, GoPay, and QRIS. They are shown here so support can match wallet records when a question touches account history, not because payment choice changes the legal rule.

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

REQUEST CHANNELS

Switch to our legal request channels

When a legal request needs a human reply, we keep three routes open: live chat, email, and the in-account form.

DATA AND ACCESS

Explore how we handle data requests

We treat legal requests as account records, not casual chat, so each one follows the same traceable path.

Data scope

We collect only the details needed to manage access, answer legal requests, and keep a trace of the change history. That usually means your account name, contact route, device type, and the message thread tied to the case.

Cookie control

Browser cookies remember your session on mobile web and desktop, plus language and form state. Clear them in your browser whenever you want a fresh start; the next visit will ask you to set those choices again.

Account security

When you switch from phone to laptop, sign out of the old device before asking for a change. We check the latest login record so a request from a shared device does not affect the wrong account.

Retention

We keep legal request logs only for as long as we need them for access control, dispute handling, and recordkeeping. After that window, the file is archived or removed according to the rule that applies to the case.

Change requests

If you need a correction, send the exact field, the updated value, and a short reason. Clear requests help us update name, contact, or device details without extra back-and-forth.

Contact routing

For any legal question, use live chat, email, or the form inside your account. We route the message to the team that handles policy, access, and data changes, so you reach the right person faster.

Open common questions about this policy

If you need the shortest route to an answer, start here. We keep the same legal rules on desktop and mobile web, and the answer does not change when you move from phone to laptop. When local law does not permit access or a request, we stop there; when it does, we use the account data you send to us.

Access is available only where local law permits. If the law in your location does not allow it, we do not open the account or continue a request, even if you can reach the page.

We keep the data needed to match the account and record the case: account name, contact route, device type, and the message thread. We do not ask for extra details unless the request cannot be verified.

Yes. Send the exact field, the updated value, and a short reason through email or the in-account form. That gives us a clean record and helps us update the right file without delay.

We keep request records only as long as needed for access control, dispute handling, and legal recordkeeping. After that, the file is archived or removed under the rule that applies to your case.

Live chat works for quick checks, email is better for a written trail, and the in-account form helps when the request belongs to your profile. Use the channel that matches the change you need.

Sign out of the old device, clear cookies if you changed browser settings, then sign in again before sending the request. That keeps the account trail linked to the latest session.

They can help us match the account history when the case touches wallet activity, but they do not change the local-law rule. Access still depends on where you are and what the law allows.

Open the legal page for Indonesia

Switch to our legal request channels

Explore how we handle data requests

Data scope

Cookie control

Account security

Retention

Change requests

Contact routing

Open common questions about this policy

01 Who can access mansion77 from Indonesia?

02 What data do you keep for legal requests?

03 Can I correct my account details?

04 How long do you keep request records?

05 Which channel should I use for legal help?

06 What should I do after changing device or browser?

07 Do DANA, OVO, GoPay, or QRIS records affect legal checks?

Related Pages