Reference

Open ssspin with Legal clarity

ssspin Legal sets out how we handle your account, wallet checks and access to the lobby in Indonesia.

Account termsPayment recordsPolicy requestsLocal-law access
ssspin Open ssspin with Legal clarity
POLICY HELP ROUTES

Reach support about Legal questions

A clear contact route matters when a Legal question affects your account or wallet status.

Account access If phone verification blocks account access, contact our support desk through the channel shown in your account. Tell us whether the issue appears before login or after the verification step, and include your registered phone number so we can route the Legal request correctly.
Wallet records For a DANA, OVO, GoPay or QRIS record, send the receipt reference and the approximate transaction time. For BCA, BRI, Mandiri, BNI or virtual account activity, add the transfer reference. We can then check the payment status against your account record.
Policy changes When you want a correction, access request or account closure under our Legal terms, use the policy contact path in your account. State the exact change you want, and keep replies in the same thread so the request history stays together.
ACCOUNT DATA PRACTICE

Protect your account and policy record

Legal handling is not separate from everyday account security. We use the account phone verification step to connect access requests with the right account, and we check payment references before discussing wallet…

Data handling

We use account details, verification results and payment references to operate the requested account service and resolve Legal cases. A support request is easier to match when your registered phone number and receipt reference are supplied together rather than sent across several separate messages.

Cookies

Cookies can help keep your account session and policy pages working between visits. Your browser controls whether cookies remain after you close the page. If a policy page does not load correctly, try the same account path in an updated mobile browser or on desktop.

Account security

Phone verification comes before account access when our account flow requests it. Do not share verification codes or let another person use your signed-in device. If access changes unexpectedly, sign out where possible and contact the account support route with the time of the event.

Record retention

We retain account and payment records for the period needed to operate the account, investigate a payment question and meet applicable Legal obligations. A retention request should identify the account phone number and record type, such as QRIS receipt, bank transfer or verification event.

Correction requests

You can ask us to correct an account detail when the displayed record is wrong. Send the requested correction through the policy contact path, explain what needs changing and provide supporting account or payment evidence. We may need to verify ownership before making an update.

Access and closure

To ask for account access details or closure, use the support route shown after login or the account-help path when login is unavailable. We will confirm the request against the account record and explain any remaining payment or verification step before processing it.

Find answers about ssspin Legal

These Legal answers cover the questions we expect you to ask before opening an account or sending a policy request. They explain the practical steps around account ownership, local access, payment evidence, browser sessions and data requests. If your case involves a specific receipt or verification event, contact support with the account details that let us locate it.

ssspin Legal covers account access, phone verification, payment records, cookies, account security, retention, correction requests and closure requests. It also explains that access depends on local law. Read the notice before opening an account, then contact support if your situation needs a case-specific answer.

Yes. Account and lobby access depends on local law and is available where local law permits. We do not treat a successful page load as permission to use every service. If access is unclear for your location, check the account route and contact support before continuing.

Phone verification helps connect an access request with the account owner and reduces confusion when a new device is used. We may request it before account access or when a policy request involves account data. Never share the verification code with another person.

Use the policy contact path shown in your account and state the exact record you want corrected or changed. Include your registered phone number and supporting evidence, such as a payment reference. We may verify account ownership before changing the stored record.

For DANA, OVO, GoPay or QRIS, send the receipt reference and approximate time. For BCA, BRI, Mandiri, BNI or a virtual account, include the transfer reference. Do not send a wallet password or verification code. These references help us match the case.

The Legal terms apply whether you open the account on a mobile browser or desktop. A new device can prompt another phone verification step, especially after a session ends. Sign out on shared hardware, and contact support if an unfamiliar device appears in your access history.

Send an account-closure request through the support route shown in your account, or use the account-help path when login is unavailable. Include the registered phone number and state that closure is requested. We will confirm ownership and explain any open payment record before completion.