LEGAL REFERENCE

Our Privacy Policy, Written For You

This is the svp88 login privacy policy — the part of the brand where we explain, in plain terms, what we collect when you open an account with...

Account dataVerificationWallet referencesCookiesYour rights
svp88 login Our Privacy Policy, Written For You

How We Handle Your Account Data

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

24/7 SUPPORT

Privacy Contact Paths

Team online

Privacy Inbox

Write to our privacy desk for data export, correction or deletion requests. We confirm receipt the same day and work through the queue in the order requests arrive, with status updates on file.

Live Chat Desk

Open chat from inside your account when you want a quick answer about cookies, verification documents or what's stored against your handle. Our agents escalate policy questions straight to the privacy team.

Account Settings

Head to your account panel to download a copy of what we hold, refresh your contact details, or close the account entirely. Closure requests trigger our retention countdown the moment you confirm.

PLATFORM TRUST SIGNALS

Editorial Trust Behind This Policy

Reviewed Quarterly

Our policy team revisits this page every quarter to keep wording aligned with the lobby you actually see, the wallets...

Plain-Language Drafting

We rewrite legal clauses into sentences you can scan on a phone. If a paragraph needs a glossary, we add...

Named Owners

Each section has an internal owner — privacy, payments, or security — so when you raise a question we route...

Change Log

Material edits are dated and summarised at the foot of the page. You can see what moved, when it moved...

Independent Review

External counsel reads the policy before each major release. Their notes shape the language around verification, retention windows and the...

Reader Feedback

If a clause confuses you, the chat desk logs it as a policy ticket. Repeat questions become rewrites in the...

Consistency Across Our Policy Pages

Privacy Policy
This page — the master document covering what we collect from your account, how long we keep it and the rights you can exercise inside supported Indonesia regions.
Cookie Notice
A sister page focused only on browser storage. It mirrors the definitions used here so a 'session cookie' means the same thing in both documents without drift.
Terms of Service
Where the privacy policy describes data handling, the terms describe account conduct. The two cross-reference each other so obligations don't contradict on either side.
KYC Notice
Verification rules sit in their own document but use identical retention windows. If we change a window here, the KYC notice updates in the same release.
Payment Disclosures
Wallet partners — DANA, OVO, GoPay, QRIS — are listed consistently across this policy and the payments page, so the names you see match the chips inside your account.
Security Statement
The security page explains how we protect what this policy says we collect. Encryption claims and storage regions are written once and quoted in both places.
Complaints Path
Our complaints page references the same privacy inbox you'll find here, so escalating a data concern follows one route regardless of which page you started on.
QUICK SIGNAL

What Defines This Policy Page

01
Section Index A scrollable index sits at the top so you can jump straight to retention, cookies or your data rights. Each anchor matches the heading exactly, which keeps shared links pointing where you expect.
02
Last Updated Stamp Every release prints the date at the head of the document. You'll know whether the version you're reading is the one that applies to your account today or an older snapshot from before the last refresh.
03
Rights Panel A dedicated block summarises the access, correction, export and deletion rights you can exercise. Each right links to the exact form or chat flow inside your account that triggers the request.
04
Retention Table A compact table shows how long each data type stays on file, from session logs to verification documents, so you don't need to read every clause to find a single number.
05
Glossary Drawer Terms like 'processor', 'controller' and 'lawful basis' open into short definitions written in our voice. The drawer keeps the main body short while still answering the technical question if you need it.
06
Contact Footer The footer of the policy carries the privacy inbox, the chat link and the postal route, repeated so you never have to scroll back up to find where to send a question.

Privacy Questions We Hear Often

Your email, phone number, the password hash you set, and any verification details required where local law permits. Once you start moving money, we also store the wallet handle you nominate for DANA, OVO, GoPay or QRIS top-ups.

Most account records clear inside the retention window listed in our table — typically a fixed period after closure. Some financial logs stay longer because payment regulations require it, and the table tells you exactly which categories that covers.

Yes. Open your account panel and request a data export, or write to the privacy inbox. We compile the file, confirm your identity once more, and send it through a secure link inside the response window the policy commits to.

Only what's needed to settle a top-up or withdrawal — usually your handle and the transaction reference. DANA, OVO, GoPay and QRIS partners receive nothing about your lobby activity, and we never sell account data to third parties.

Session cookies keep you signed in; preference cookies remember your lobby layout. Our cookie notice lists each one with its purpose and lifespan, and you can adjust non-essential categories from the banner or your account settings at any time.

Most fields are editable directly in your account. For locked fields like verified name or date of birth, message the privacy inbox with supporting documents and we'll update the record once the change has been reviewed.

Inside supported regions that meet the standards described in our security statement. We name the storage regions in the policy body and update the wording whenever a partner location changes, so the document always matches reality.