Reference

Open aura33 Privacy Policy Before Account Access

Our Privacy Policy explains how aura33 handles the details linked to your account, wallet activity and device access before you enter the lobby.

Account dataWallet recordsDevice choicesPrivacy requests

Browse Our Lobby Read FAQ

Read How We Handle Account Details

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

This Privacy Policy covers data created when you open an account, complete phone verification, sign in, contact support, or use wallet options connected with the lobby. We may record account identifiers, verification results, transaction references and technical details such as device type, browser path, approximate location

1
and sign-in events. We use these details to provide account access, check payment status, protect the account and answer privacy requests. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in payment records, but we do not use this policy to change your
2
bank or wallet terms. Access depends on local law, and where local law permits, we apply this policy to your activity through aura33. The policy may change when our data practices change; we will show the updated date on this page.

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

REQUEST PATHS

Ask Us About Your Privacy Policy

A clear contact route helps you ask what data we hold, why it is used, or how to correct an account detail. Send your request through the support contact route available from our account area, and include the phone number or account identifier connected with your request. We may ask for an account step before discussing private data. This helps us avoid sending wallet or sign-in details to the wrong person.

Team online

Data access request

Ask us for the account data connected with your aura33 profile, including verification details and sign-in records. We will first match your request to the phone number or account identifier supplied through the support contact route.

Correction request

Tell us which account detail needs changing and why it is inaccurate. For a wallet reference involving DANA, OVO, GoPay or QRIS, include the relevant transaction reference without sending your wallet PIN or private login code.

Deletion question

Ask whether selected account data can be removed and which records must remain for account, payment or legal reasons. We will explain the practical effect before processing a deletion request connected with your profile.

DATA PRACTICES

Check How Your Account Data Stays Managed

We keep this policy practical by connecting each data use to an account action you can recognise. Phone verification supports account access, device signals help us identify unusual sign-ins, and payment references…

Account collection

When you open an account, we collect the details needed to create your profile and complete phone verification. We use those details for sign-in, account messages and requests that must be matched to the correct account holder.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference data such as amount, status and time. We use those references to trace a cashier result, not to request your wallet PIN.

Device signals

Your browser and device can provide technical signals such as operating system, session details and sign-in time. These signals help us spot an unusual account path and investigate access questions without reading unrelated files on your device.

Cookie choices

Cookies can keep your sign-in path, language setting and page session consistent. You can adjust cookie controls in your browser, although blocking some cookies may require you to repeat an account step when returning to the lobby.

Retention periods

We retain account, verification and payment records only for as long as needed for the stated purpose, account protection or a legal requirement. When a record is no longer needed, we remove it or separate it from your account where practical.

Change requests

For a data access, correction or deletion request, contact us through the available support route and identify the account safely. We may request extra proof before changing private details, and we will explain any request we cannot complete.

Browse Privacy Policy Answers Before Joining

These Privacy Policy answers focus on the account and wallet questions you may have before opening an aura33 profile. We explain the data connected with phone verification, mobile access, payment references and requests for changes. If your question concerns eligibility or access from Indonesia, the answer also depends on local law and the route available to your account.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain, and how you can ask for access, correction or deletion.

Phone verification helps us connect account access with the correct phone number and reduce mistaken or unauthorised sign-ins. We may use the result when you open an account, recover access or submit a request about private account data.

Yes. The policy covers references created when you use DANA, QRIS, OVO, GoPay, bank transfer or virtual account options. These can include status, time and transaction reference details, while your wallet PIN remains with your payment provider.

We may receive browser, operating system, session and sign-in details from the device you use. On mobile, this helps us understand an account access path and investigate unusual activity; it does not give us access to unrelated files or contacts.

Use the available support contact route and state that you want an account data access request. Include your account identifier or verified phone number, but do not send a wallet PIN or sign-in code. We may check ownership first.

You can request a correction or ask whether deletion is possible for selected records. We may need to retain account, verification or payment details for account protection or a legal requirement, and we will explain that point before acting.

Access and eligibility depends on local law. Where local law permits, this policy applies to your aura33 account activity from Indonesia, including mobile sign-in and local wallet references. Contact us if you need the policy position for your account route.

Open aura33 Privacy Policy Before Account Access

Ask Us About Your Privacy Policy

Data access request

Correction request

Deletion question

Check How Your Account Data Stays Managed

Account collection

Payment references

Device signals

Cookie choices

Retention periods

Change requests

Browse Privacy Policy Answers Before Joining

01 What does the aura33 Privacy Policy cover?

02 Why does aura33 need phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What device data can aura33 collect?

05 How can I request a copy of my aura33 data?

06 Can I ask aura33 to correct or delete my data?

07 Does this Privacy Policy change based on my location?

Related Pages