Reference

Privacy Policy For Your ligalgo Account

Our Privacy Policy explains how ligalgo handles the details connected with your account, including contact data, wallet status and mobile access.

Account clarityWallet recordsMobile accessDirect requests

Explore Home Lobby Read FAQ

How Your Account Data Is Used

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

We collect only the account details needed to open, secure and operate your access, such as your contact details, verification status, device signals, sign-in events and payment references. A DANA, OVO, GoPay or QRIS record may show a reference, amount, status and time, while bank transfer

1
or virtual account activity may add a bank-side reference for matching. We use these records to confirm a request, identify unusual access, resolve a wallet question and keep an auditable account trail. Cookies help us remember session choices and measure page function. Where local law permits,
2
location or device checks can help apply access rules. Data may be shared with payment or service partners only when needed for the stated account task, security control or legal request. You can contact us to ask what we hold, request a correction or ask about
3
deletion where applicable.

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

CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact route matters when a wallet record or account detail looks unfamiliar.

Account access If you cannot reach your account, tell us the sign-in email or phone and the device path you used, such as a mobile browser. We can separate an access problem from a privacy request before discussing any account record.

Wallet record For a DANA, OVO, GoPay or QRIS record, include the displayed reference and date rather than your wallet password. We use those details to locate the relevant entry without asking you to expose private payment credentials.

Privacy request To ask for a copy, correction or deletion where applicable, write Privacy Policy in your message and describe the exact data involved. We may request an account check so a private record is released only to you.

DATA HANDLING

Six Checks Behind Our Privacy Policy

Our handling process follows the account action that created each record. Opening an account creates an identity trail; signing in creates device and session events; a wallet action creates a payment reference…

Account data

When you open an account, we may keep your contact details, verification result and account status. These fields help us identify the correct record when you ask for access or correction through the Privacy Policy contact route.

Cookies

Cookies and similar session tools can remember whether your mobile browser is signed in and help us see whether a page works. You can manage browser cookie settings, though changing them may interrupt the account path.

Device signals

A phone or desktop sign-in can create time, browser and security signals. We use them to spot account access that does not match your usual path, not to read unrelated content stored on your device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can leave matching references and status records. We use those entries to reconcile a request while avoiding storage of wallet passwords or one-time codes.

Retention

We keep records for as long as their account, support, security or legal purpose requires. When a purpose ends, deletion or restriction is considered subject to unresolved requests and duties that apply where local law permits.

Your request

You can ask what data we hold, request a correction, question a payment reference or ask about deletion where applicable. Send the request through our listed support contact and complete the identity check we return.

Privacy Policy Questions About ligalgo

These answers cover the searches we hear most often about the ligalgo Privacy Policy. They explain the account step, mobile browser signals, wallet references, cookies, retention and the contact route in plain terms. If your situation involves a specific record, use the support path above and give us enough detail to locate it without sending a password or one-time code.

It covers account details, verification status, sign-in events, device signals, cookies, support cases and payment references. It also explains why we use each category, how we restrict access, how long records may remain and how you can request access or correction.

We may collect the contact details you submit, the account step you complete, verification results and security events linked to sign-in. We do not need your wallet password or one-time code to match a DANA, OVO, GoPay or QRIS reference.

Yes. The Privacy Policy covers payment references, status, time and matching details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us resolve a request without storing private wallet credentials.

A mobile browser session may create sign-in time, browser type, device signals and cookie status. We use these details for session function and account security. We do not use the Privacy Policy as permission to read unrelated files or content on your phone.

Yes. Send a correction request through the listed support contact, identify the account email or phone, and describe the field that needs changing. We may ask you to confirm identity before editing the record, especially when it relates to account access or payments.

Retention depends on why the record exists, whether a support or security matter remains open, and legal duties that apply where local law permits. When those purposes end, we consider deletion or restriction according to the request and applicable requirements.

Use the support contact shown beside this Privacy Policy and write the request type clearly, such as access, correction, deletion or a wallet reference question. Include the account email or phone and relevant date, but never send a password or one-time code.

Privacy Policy For Your ligalgo Account

Where To Ask About Privacy Policy

Six Checks Behind Our Privacy Policy

Account data

Cookies

Device signals

Payment references

Retention

Your request

Privacy Policy Questions About ligalgo

01 What does the ligalgo Privacy Policy cover?

02 What data is collected when I open a ligalgo account?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What does ligalgo record when I use a mobile browser?

05 Can I ask ligalgo to correct my personal data?

06 How long does ligalgo keep account and payment data?

07 How do I contact ligalgo about a Privacy Policy request?

Related Pages