Reference

Privacy Policy for your account

We keep this page focused on one thing: how your data is collected, used, and protected when you open an account with nekatwin.

DANAOVOGoPayQRIS

Explore The Lobby Read FAQ

What this policy covers in Indonesia

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

This policy applies to your account, your device, and the messages you send us from Indonesia. We use the data we need to keep the account working: contact details, login records, device signals, and transaction references from DANA, OVO, GoPay, or QRIS. That helps us confirm

1
requests, prevent duplicate access, and link a payment to the correct profile without asking for extra fields. Where local law permits, we keep records for the period needed to answer disputes, complete verification, and meet record-keeping duties. If you close the account, some records may stay
2
archived instead of being erased at once, because we may need them for security checks or legal requests. If you want a copy, correction, or deletion request, send it from the contact path inside your account so we can match it to the right record.

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

CONTACT PATHS

Where to send privacy requests

The fastest privacy request comes through logged-in chat, because it lets us match your profile, email, and device in one thread.

Live chat Open chat from your account area and send the exact request: copy, correction, deletion, or access. We can match it to your profile faster when you include the email on the account and the last device you used.

Email support Email works well when you need a written trail. Send the request from the address on your account, state the change you want, and we will reply with the next step after a quick identity check.

Account form Use the form inside settings if you want a structured request. It helps us collect the field name, the correct value, and any proof we need before we update the record or explain why we must keep it.

ACCOUNT SAFEGUARDS

How we handle data and cookies

We handle privacy tasks inside the same account flow you use to log in, so requests do not get lost in a separate inbox.

What we collect

We keep contact details, login logs, device signals, and payment references that help us match DANA, OVO, GoPay, or QRIS activity to your account. We only ask for extra details when a request needs confirmation.

How cookies work

Cookies remember your session, language choice, and login state on Chrome, Safari, and Android browsers. If you clear them, you may need to sign in again, and some account screens will ask for a fresh verification step.

Account security

When you change email, phone, or password, we may ask you to log in again and confirm the change from the device already linked to your profile. That helps stop another person from altering your records.

Retention window

We keep account and payment records only as long as needed for disputes, fraud checks, tax duties, and local law. After that period, the field is removed or archived depending on the record type and why we needed it.

Who can request

You can request access or changes from the email on your account, live chat, or the form in settings. We use the same profile details to verify that the request belongs to you.

How to change data

Send the exact field, the correct value, and the account email. If the change affects safety or records, we confirm the request first and then tell you what was updated and when.

Questions about your data rights

These answers cover the parts of Privacy Policy that usually matter first: what we collect, how long it stays with us, which device signals help us keep the account secure, and how you can send a request. If you are unsure which channel to use, the chat inside your account is the fastest place to start. We can then point you to email or the form if your request needs a written trail.

We keep contact details, login logs, device signals, and payment references that help us match your account to DANA, OVO, GoPay, or QRIS activity. We only ask for extra details when a request needs confirmation.

We keep records for the time needed to handle disputes, fraud checks, and local law duties. After that period, the field is removed or archived depending on the record type and why we needed it.

Yes. Send the request from your logged-in chat or the email tied to your profile, and ask for a copy of the stored fields you want to see. We may ask for one short confirmation step first.

Cookies keep your session alive, remember language choice, and help us avoid repeated login prompts. If you clear them, some pages will ask you to sign in again and confirm your device.

Send the correction request through chat, email, or the form in settings. Include the field you want changed, the correct value, and your account email so we can match it to the right record.

Yes. When local law allows a request or share, we follow that rule and only release what the law permits. If a request cannot be completed, we explain the reason and the remaining options.

Privacy Policy for your account

Where to send privacy requests

How we handle data and cookies

What we collect

How cookies work

Account security

Retention window

Who can request

How to change data

Questions about your data rights

01 What data does nekatwin collect from my account?

02 How long do you keep my personal data?

03 Can I ask for a copy of my data?

04 How do cookies affect my login?

05 Where do I send a correction request?

06 Does local law change what you can share?

Related Pages