Reference

grahaspin Privacy Policy For Your Account Data

Your account details, wallet records and device activity are handled under the grahaspin Privacy Policy, so you can understand what we collect before opening an account.

Clear data purposesWallet record detailAccount request pathLocal law wording

Explore Our Lobby Read FAQ

How Privacy Policy Covers DANA And QRIS

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

Our Privacy Policy describes the data needed to create and protect your account, including your phone number, verification details, login events, device signals and payment references. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may retain transaction status, reference numbers

1
and receipt details so wallet questions can be checked. We use these records for account servicing, fraud checks, security, legal requests and support responses, not for unrelated purposes. Cookies can remember session preferences and help us understand page performance; your browser settings can control them, although
2
some account functions may then behave differently. We retain records only for the period needed for these purposes or applicable legal duties. Access to grahaspin and any data request depends on local law. Where local law permits, you may ask us to correct, export or remove
3
eligible details through our support path.

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

REQUEST HELP

Three Paths For Privacy Requests

A clear support route helps you ask about the Privacy Policy without searching through account screens.

Account data request Use the support path beside the cashier area to ask what account details we hold, why they are used and which records connect to your phone verification step.

Wallet record question For DANA, OVO, GoPay or QRIS concerns, provide the payment reference and date. We can match the receipt status with your account without requesting your wallet password.

Correction or removal Tell us which detail needs correction or removal and why. We will explain any identity check, legal retention reason or local-law condition before processing the request.

DATA HANDLING

Six Practical Privacy Commitments

The Privacy Policy is supported by practical account controls rather than broad promises. We separate identity checks from payment references, limit internal handling to operating needs and keep a clear route for…

Purpose-based collection

We collect phone and account details to create access, confirm ownership and protect the account. Payment references support receipt matching and status checks rather than unrelated profiling.

Device and session signals

When you sign in from a mobile browser or desktop, we may record device and session signals linked to security. These details help identify unusual access and protect your account.

Cookie choices

Cookies can retain session preferences and show whether a page loads correctly. You can adjust cookie controls in your browser, though refusing necessary cookies may interrupt login or account requests.

Account protection

Phone verification is part of our account access process. Keep your sign-in details private, and contact support if a login event or wallet record does not match your activity.

Retention decisions

We keep personal and transaction records for operational needs, security checks and legal duties. When a record is no longer needed, our handling follows the retention process described in this policy.

Your request route

You can ask about stored details, request a correction or seek eligible removal through support. We may verify your identity before changing account data or disclosing records.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or sending a wallet request. If your situation is not covered, use the support path beside the cashier area and include the relevant account or payment reference.

It covers account details, phone verification, device and session signals, cookies, payment references, retention, security handling and requests to correct, export or remove eligible data.

We use your phone number to create the account, confirm ownership and support secure access. If you ask about a record, we may use it to verify that the request comes from you.

Yes. It explains how we handle DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account status, receipt details and payment support checks.

You can contact support with the detail that needs correction and the reason. We may request an ownership check, then explain the next step or any legal reason a record must remain.

Cookies can retain a session and help us identify page performance. Browser controls let you change cookie settings, but refusing necessary cookies may affect login, verification or policy request forms.

We retain payment references for the period needed for account servicing, security checks, dispute handling and legal duties. The applicable retention period can depend on the record and local law.

Use the support link beside the cashier path and include your linked phone number, request type and relevant reference. Access to records or removal depends on local law and ownership checks.

grahaspin Privacy Policy For Your Account Data

Three Paths For Privacy Requests

Six Practical Privacy Commitments

Purpose-based collection

Device and session signals

Cookie choices

Account protection

Retention decisions

Your request route

Privacy Policy Answers For Your Account

01 What does the grahaspin Privacy Policy cover?

02 Why does grahaspin need my phone number?

03 Does the Privacy Policy include DANA and QRIS data?

04 Can I ask grahaspin to correct my account data?

05 How do cookies affect my grahaspin account?

06 How long does grahaspin keep payment records?

07 Where can I ask about a Privacy Policy request?

Related Pages