Reference

Legal choices before your empire29 account

empire29 puts account rules, data choices and payment records in one Legal page before you open access to the lobby.

Account eligibilityData and cookiesPayment recordsContact routes
empire29 Legal choices before your empire29 account
CONTACT PATHS

Where Legal questions reach our team

A clear contact path helps when a Legal question affects your account or payment status. Start from the support link inside your signed-in account and include the registered phone number, the relevant date and the payment reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the correct record without asking you to send a password. For access questions, tell us whether the issue appeared during phone verification or after login.

Team online

Account access

Use the signed-in support path when phone verification, a login restriction or an eligibility question prevents you from reaching your account area. Include your registered phone number, but never send your password or a one-time code.

Payment records

For a Legal question about DANA, OVO, GoPay or QRIS, send the payment reference and date through account support. We can match the record while keeping your wallet credentials outside the support request.

Policy changes

If wording on this Legal page is unclear, contact our policy support route from your account area. Tell us the section and sentence you mean so our team can respond to the exact rule rather than a general topic.

DATA PRACTICES

How we handle your Legal choices

We keep this policy area practical: it tells you what data supports account access, how cookies affect your session and where to ask for a change.

Account data

We use your registered account details and phone verification status to manage access. Keep the phone number connected with your account current, because an outdated contact can delay a request about identity or access.

Cookie controls

Cookies can keep your session connected while you move through account pages. You can ask our support team how a cookie is used or request help with a browser setting without sharing your login password.

Security steps

Never place a password, one-time code or wallet credential in a support message. We may ask for account details and a payment reference, but those checks are separate from secret login credentials.

Record retention

We retain account and payment records for the period needed to maintain account history, resolve disputes and meet applicable legal duties. A retention question can be sent through the account support path.

Correction requests

If a registered detail is inaccurate, tell us which field needs changing and provide the account contact used for verification. We will explain the next account step before applying a permitted correction.

Policy contact

For questions about Legal wording, data handling or access restrictions, name the relevant section in your request. This helps us route the matter to the team handling policy and account records.

Legal answers for empire29 accounts

These Legal answers address the account, data and access questions we expect before registration. They also explain what to include when you contact us about a payment record or a correction. Where a rule depends on your location, access depends on local law and the wording shown on your account.

It covers account eligibility, phone verification, data handling, cookies, payment records, retention and contact routes. The terms apply to your use of the account area where local law permits, and updates appear on this page when the wording changes.

Yes. Access depends on local law and on the eligibility checks connected with your account. We may request phone verification or account details before allowing account actions, so read the displayed terms for your location before continuing.

We use payment references, dates and account details to match activity to the correct record. Send only those details through account support. Do not send wallet passwords, login passwords or one-time codes with a payment question.

You can request a permitted correction through the account support path. Name the inaccurate field and use the registered account contact for verification. We will explain any required account step before changing the stored detail.

Cookies may keep your signed-in session connected as you move between account pages. You can ask support which cookie issue affects your session or request browser-setting help without providing your password or one-time code.

We retain account and payment records for the period needed for account history, dispute handling and applicable legal duties. For a retention question, contact us from your account area and include the record type you mean.

Use the support route inside your account and name the section, restriction or message you received. Include your registered phone number when requested, but keep passwords and one-time codes out of every contact message.