Reference

Legal terms for your account

We keep the legal side of your account in one place: access rules, data use, record checks, and the path for changes.

Local-law accessData requestsAccount editsRecord checks

What this policy covers

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

This page explains how we handle account records, login activity, device details, cookies, and transaction references tied to your use of rogg777. Where your location, device, or request is involved, access depends on local law and is available only where local law permits. We keep the

1
rules practical: if you need a correction, a copy of stored data, or a review of a closure request, we use the registered email and the last payment rail used to match the file. That can include DANA, OVO, GoPay, or QRIS when those rails appear
2
in the account history. We do not expand the record beyond what we need to verify you, answer the request, and keep the legal trail required by law. When the account is accessed from a new phone or laptop, we may ask you to confirm the
3
device path before we change anything.

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

CONTACT PATHS

How you reach us

For legal requests, we keep three direct paths open: live chat, email, and the Help menu inside your account. That lets you send the request from the same email and device path you use to sign in. If you are checking from Medan, the same process applies on mobile browser or desktop, and our team routes the case to the account desk for a reply within our posted hours.

Team online

Live chat

Send the request in live chat and we route it to the account desk during daily support hours, 09:00-23:00 WIB. Include your registered email, the subject of the request, and any payment reference so we can trace the file quickly.

Email

Write to [email protected] when you need a correction, a copy of stored data, or a closure check. We answer in the same thread and may ask for one login detail to confirm the account.

Help menu

Open Help from your profile on mobile browser or desktop, then submit the request from the account that needs action. That keeps the case attached to the right record and avoids extra back-and-forth.

DATA AND ACCESS

How we handle your records

We treat legal requests as account tasks, not generic support chatter. That means we check the registered email, the last login, and any linked payment rail before we change a record, release…

Data scope

We collect only what we need to run the account: name, email, login time, device marker, and transaction reference. If a request asks for more, we say why before we ask.

Cookies

Session cookies remember that you already signed in, so you do not repeat verification on every page. Clear them in Chrome, Safari, or Firefox if you want a fresh login, but expect the session to end.

Account security

Use one password per account, avoid shared devices, and sign out after you finish. If a login looks wrong, send the time, device type, and city you were in so we can trace it.

Retention

We keep records only as long as needed for disputes, verification, and legal duties under local law. After that period, the record is archived or removed according to the file type and request reason.

Change requests

To correct data, send the exact field you want changed, the current value, and the new value. We match it against the registered email and the latest payment rail, such as DANA or QRIS.

Contact path

Use live chat or email from the address on file when you ask for a copy, correction, or closure. That keeps the request tied to the right account and cuts back-and-forth.

Common questions about this policy

These are the legal questions we hear most when someone wants to check access, change account data, or ask how long we keep a record. Each answer points you to the same contact path we use inside the account, so you know what to send and where it goes.

It covers access rules, record handling, login logs, cookies, retention, and the steps we use when you ask for a copy or correction. If local law does not allow access in your area, we do not open the account flow.

Send the request from the email on file through live chat or the Help menu. Add your full name, the field you want checked, and the latest payment rail linked to the account, such as DANA or QRIS.

We match the registered email, the last sign-in time, and the device type before we touch the record. If those details do not line up, we ask for one more proof point instead of guessing.

We keep records only as long as needed for verification, dispute handling, and any legal duty tied to the account. When that period ends, the file is archived or removed under the retention rule.

Yes. Cookies keep the session open so you do not need to log in again on each page. If you clear them, expect a fresh sign-in and a new device check.

Use the same channel for the same request: live chat for fast routing, email for a written trail, and the Help menu for account-tied actions. Any of them works when you send the right details.

You can send the request from desktop or mobile browser, but use the account email that belongs to you. If the device changed, tell us when you last signed in so we can match the session.

Legal terms for your account

How you reach us

Live chat

Email

Help menu

How we handle your records

Data scope

Cookies

Account security

Retention

Change requests

Contact path

Common questions about this policy

01 What does this legal page cover?

02 How do I ask for my data?

03 How do you verify a correction request?

04 How long do you keep account records?

05 Do cookies affect my account access?

06 Which contact path should I use?

07 Can I request changes from another device?

Related Pages