Reference

Open Your ssspin Privacy Policy

ssspin Privacy Policy explains how we use account, device, cookie and payment details while you access our Indonesia service.

Account dataWallet statusCookie choicesSecurity checks
ssspin Open Your ssspin Privacy Policy
CONTACT PATHS

Reach Us About Privacy Questions

A clear contact path helps you act on the Privacy Policy rather than search through account screens.

Account data requests Ask us to explain the account details linked to your profile, including contact information, verification status and recent access records. Include the account identifier you use with us so we can check ownership before discussing private data.
Wallet reference checks For DANA, OVO, GoPay or QRIS questions, send the payment reference and approximate date rather than a PIN or password. We compare the reference with our status record and explain what data was stored for reconciliation.
Cookie assistance Tell us if a cookie choice, login preference or device setting is not behaving as expected. We can explain which browser data supports the page flow and what may change after you clear or restrict cookies.
SECURITY DETAILS

Switch Through Your Data Choices

We treat privacy requests as account actions that need a careful identity check. Our handling process separates profile data, security events, cookie settings and payment references so a request can be routed…

Data handling

We use contact and account details to maintain your profile, verify requested access and send necessary service messages. Login signals help us identify unusual activity, while payment references let us match DANA, OVO, GoPay or QRIS status to the correct account.

Cookie settings

Cookies can remember sign-in preferences, support page navigation and show whether a page or device path is working. You can manage browser cookie controls, although restricting some cookies may require you to repeat account steps.

Account security

Before we discuss private account records, we may ask for details that confirm you control the account. Never send us a password, wallet PIN or one-time code; use the account access path and report unfamiliar sign-ins promptly.

Retention periods

We keep information for as long as it supports account operation, security checks, payment reconciliation or a legal requirement. When a record no longer serves one of those purposes, we delete it or reduce its identifying detail.

Correction requests

If your contact detail or another account record is wrong, ask us to correct it through the support route. We compare the request with the account record first, then explain whether the change affects access or verification.

Policy contact

Questions about this Privacy Policy can include the page name, your account identifier and the specific section you want clarified. We use that context to respond about data handling without requesting unnecessary personal or wallet details.

Browse Privacy Policy Answers

These Privacy Policy questions cover the account and payment situations you are most likely to check before opening an account. We keep the answers practical: what data we use, how identity checks work, what cookies do and how to ask for access or correction. If your question concerns eligibility or access, where local law permits, use the support route with the smallest useful set of account details.

The ssspin Privacy Policy covers account details, verification records, login and device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access and when records may be retained for security, reconciliation or legal needs.

We keep the payment reference, account connection, amount or status detail needed to reconcile a transaction and respond to a receipt question. We do not need your wallet password or PIN for this process. Wallet providers may handle separate data under their own terms.

Device and login signals help us recognise an account access pattern, investigate unusual sign-ins and keep the account path working on mobile or desktop. We use these signals for security and service operation, not as a request for your device password or private files.

Yes. Contact support with the account email or phone and identify the records you want to ask about. We first check that you control the account, then explain what can be provided, how it will be delivered and whether local law limits any part.

Send a correction request through the account support route and name the detail that appears wrong. We may confirm ownership before changing it. If the detail is tied to verification or a payment reference, we will explain any extra account step required.

Retention depends on the purpose of the record. Account and security data may be kept while it supports access or fraud checks, while payment references may remain for reconciliation. We remove or reduce identifying detail when the operational or legal purpose ends.

You can adjust cookie controls in your browser and contact us if you need the Privacy Policy explained. Clearing or restricting cookies may remove saved preferences and require another login step. We will tell you what a requested cookie change affects.