Reference

Privacy Policy for Your terimaqq Account

Our Privacy Policy explains what account, device and payment details we collect when you open or use terimaqq.

Account clarityWallet data contextCookie choicesContact route
terimaqq Privacy Policy for Your terimaqq Account
HELP WITH YOUR DATA

Privacy Questions Reach Our Support

A clear contact path helps you act on this Privacy Policy when a login record, payment reference or account detail needs attention.

Account access If you cannot complete phone verification or reach your account, contact support through the listed channel and explain the device path you used. We may ask for account details needed to confirm ownership before discussing personal data or changing contact information.
Wallet record For a DANA, OVO, GoPay or QRIS reference that appears incorrect, send the date, amount reference shown in your account and the related receipt. We use those details to investigate the record while limiting exposure of your wallet credentials.
Privacy request To request access, correction or deletion where available, label the message as a Privacy Policy request and describe the record involved. We check account ownership first, then explain the action we can take and any legal reason a record must remain.
DATA HANDLING DETAILS

Inside terimaqq Privacy Controls

We keep this Privacy Policy practical by linking each data use to an account task: phone verification supports access, device signals help investigate sign-in issues, and payment references help reconcile wallet status.

Data we receive

We may receive contact details, phone verification status, sign-in timestamps, device and browser signals, support messages, and payment references. These details help us connect a request to the correct account instead of treating every wallet or login question as anonymous.

Cookie handling

Browser cookies or similar storage can keep a session active and remember choices between the login page and lobby. You can review cookie controls in your browser settings, although removing required storage may interrupt account access or make a device path ask you to sign in again.

Account security

We use phone verification and account checks before discussing private records or changing access details. Never send a password or wallet PIN in a support message. If an unfamiliar device appears in your sign-in history, report the event with the time and device path.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may be stored as a reference for account reconciliation. We use the reference to check status and receipts, not to request your wallet password or take control of your external payment account.

Retention timing

We keep personal records for the period needed to provide account support, investigate security events, reconcile payment history or meet a legal requirement. When a record is no longer needed for those purposes, our handling process removes or de-identifies it where available.

Changing your details

You can ask us to correct an inaccurate contact detail, review information linked to your account or request deletion where available. Include the account step involved, such as phone verification or wallet status, so we can validate ownership before making a change.

Privacy Policy Questions for Indonesia

These Privacy Policy answers focus on the questions you may have before opening an account or contacting support from Indonesia. We explain the practical records connected with login, cookies, wallet references and account requests, without asking you to share private credentials in public. If your situation is not covered here, use the support path and identify the relevant account step. Access and eligibility depends on local law, and any request is handled through the current process described by our team.

It covers account details, phone verification status, device and browser signals, cookies, support messages and payment references connected with your use of terimaqq. It also explains why we use those records, how retention works, and how you can request access, correction or deletion where available.

The policy can cover references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We may use a reference, receipt detail or status record to investigate account reconciliation. We do not need your external wallet password or PIN for that check.

We may retain the phone number linked to your account and the status showing whether verification was completed. This helps us protect account access and confirm ownership during support requests. If the record is inaccurate, contact support and ask for a correction through the stated process.

Cookies or similar browser storage may remember your session and settings when you move from login to the lobby on a phone. Your browser lets you manage these controls. Removing required storage can sign you out or require phone verification again on that device.

You can request deletion where available by contacting support and identifying the account record involved. We first check account ownership, then assess whether the data is still needed for account security, payment reconciliation, operational support or a legal requirement before explaining the result.

Send support the account identifier you can safely share, the linked email or phone, and the specific field that needs correction. Mention whether it concerns phone verification, device access or a wallet reference. We validate ownership before changing the record and confirm the available outcome.

Yes. Access, eligibility, retention duties and some privacy requests can depend on local law. We apply the process available for your location and explain any restriction that affects your request. When needed, contact support from the account path shown on terimaqq so we can assess it.