Reference

menara118 Privacy Policy Explained

Our Privacy Policy explains how menara118 handles the details you provide when opening an account, signing in and checking wallet records.

Account dataCookie choicesPayment referencesMobile sessions
menara118 menara118 Privacy Policy Explained
PRIVACY HELP ROUTE

Get Help With a Privacy Request

A clear request helps us find the right account record without exposing it to the wrong person.

Access request Ask us for the personal details connected with your account, including sign-in, phone verification…
Correction request If your contact detail or account record is wrong, tell us which field needs…
Receipt question For a DANA, OVO, GoPay or QRIS receipt question, send the reference shown in…
DATA CONTROL POINTS

Six Ways We Handle Your Records

Our handling steps are designed around the moments that create a privacy question: account opening, phone verification, mobile sign-in, wallet matching, cookie use and a request to change stored details.

Data we collect

We may collect the contact details you enter, phone-verification status, sign-in events, device information, cookie choices and payment references. These details help us operate your account path, investigate access issues and match a cashier record without asking for your wallet password.

Cookie handling

Cookies can remember a session, language preference or security setting so you do not repeat the same account step on every page. You can manage cookie permissions through your browser; refusing some cookies may affect sign-in continuity or saved choices.

Account security

Phone verification and sign-in signals help us identify an account request before we discuss its records. Keep your password and one-time code private, and contact support through the account help route if a device you do not recognise appears in your activity.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep the reference needed to check a receipt or status. We do not need your wallet password for that check, and we do not present a reference as the full payment credential.

Retention period

We keep personal records for as long as needed for the stated service purpose, account protection, dispute handling or a legal duty. When a record no longer needs retention, our process is to remove it or separate it from direct account identification.

Your change request

You can ask for access, correction or deletion through the support route shown in your account help area. Tell us the request type and matching contact detail; where local law permits, we explain the result and any record that must remain.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened or a payment record is questioned. We keep the wording practical: what we collect, how we confirm identity, what happens on a phone, and how you can ask for a copy or correction. If a request depends on a legal requirement, we explain that limit through the account support route.

The menara118 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, payment references and requests about stored data. It explains why each category is used, how long records may remain and how you can ask for access or correction.

We use payment references to match DANA, OVO, GoPay or QRIS activity with an account record. We do not ask you to send a wallet password or one-time code to support. For a receipt question, provide only the reference shown in your account.

Phone verification helps us connect an account request to the contact detail you supplied before discussing personal records. It also supports account protection when a new device signs in. Keep verification codes private; support will not need your code to explain this policy.

Use the support route in your account help area and state that you want an access request. Include the account email or phone detail used during setup. We check that detail first, then explain which records can be provided under local law.

Yes, you can request a correction or deletion through the same account support route. Identify the field or record and explain the change. Where local law permits, we process the request; some records may remain when account security, disputes or a legal duty requires them.

The Privacy Policy applies when you sign in from a phone or tablet, including a session used to reach the lobby from Yogyakarta. We may record device and session signals for security, while cookies can preserve sign-in choices according to your browser settings.

Yes. Access to the service and the response to a data request depends on local law. Where local law permits, we explain the records connected with your verified account, the purpose for keeping them and any reason a record cannot yet be removed.