Reference

spin online Privacy Policy for Your Account Data

The spin online Privacy Policy explains what we collect, why we use it and how you can request changes before opening an account.

Clear data purposesWallet privacy checksAccount access rightsMobile-ready policy
spin online spin online Privacy Policy for Your Account Data
CONTACT YOUR WAY

Privacy Questions, Receipts and Account Help

A clear contact route helps when your Privacy Policy question concerns a login record, phone verification or wallet receipt. Tell us the account email or phone reference, the date of the event and the relevant DANA, OVO, GoPay or QRIS reference without sending your password. Our support chat can route privacy requests for account access, correction, deletion eligibility or a status explanation.

Team online

Account data request

Ask our support chat to check the personal data linked to your account. We may ask for a phone verification step before releasing details, so another person cannot receive your account record.

Wallet reference check

For a DANA or QRIS receipt question, share the transaction reference and approximate time. We use that information to locate the relevant record without asking you to disclose a wallet PIN.

Correction or removal

Send the exact field you want corrected or the account data you want assessed for removal. We explain any retention reason when a legal or security need prevents immediate deletion.

HANDLING YOUR DATA

Six Privacy Practices Behind Your Account

We apply the Privacy Policy to the practical moments that matter: account creation, mobile sign-in, wallet checking and support contact.

Account creation

When you open an account, we collect the details needed to create your sign-in record and confirm the contact route you provide. A clear phone verification step helps us connect requests to the right account.

Device and browser

A mobile browser may provide device type, browser version, language and security events. We use these signals to spot unusual sign-ins and protect your account, not to read unrelated files on your phone.

Cookies and sessions

Cookies can retain a session choice and help us identify a failed page or repeated sign-in prompt. Browser controls let you remove or restrict cookies, although some account functions may then need another sign-in.

Wallet verification

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, we use transaction references and status details to match an account request. We do not ask for your wallet PIN in support messages.

Security and retention

We retain account, login and transaction records for the time needed to protect the service, resolve disputes or meet applicable duties. Access to these records is limited to the operational purpose described in this policy.

Your requested changes

You can ask us to view, correct or assess deletion of eligible personal data through support chat. Include your account reference and requested change; we verify identity before making a material account record change.

Privacy Policy Answers Before You Open

These Privacy Policy answers focus on the account decisions you may make before opening access: what data is collected, how wallet references are handled, how cookies work and where to send a request. We keep the wording practical so you can check the policy from a phone, tablet or desktop.

It covers account details, phone verification, login events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

No. Our Privacy Policy explains that support should use a transaction reference and timing for a wallet check. Do not send your DANA, OVO, GoPay or QRIS PIN in a message.

Device and browser details can help us identify unusual account access, repeated sign-in failures or security events. We use those signals for account protection and do not treat them as access to unrelated phone files.

Yes. Send a request through support chat with your account reference. We may complete a phone verification step before sharing data, so the requested record reaches the correct account holder.

Name the field that is wrong and provide the corrected value through our support path. We verify your identity, update eligible records and explain any reason a particular entry cannot be changed.

You can ask us to assess removal of eligible data. Some account, security or transaction records may need to remain for a stated operational or legal reason, and we will explain that outcome.

The policy is written for account and wallet activity in Indonesia, while access depends on local law. If you are unsure about eligibility, check the applicable local requirements before submitting account details.