graha spin Casino & Sportsbook Data Care Statement

This page describes what we collect when you use graha spin and how we keep that data protected while access to services is available only where local law permits.

We set a contrast between traditional bank virtual-account rails and faster e‑wallet QR rails: established transfers through BCA, e-wallet, mobile banking and local payment sit alongside instant top-ups via online payment, e-wallet, mobile banking, local payment, online payment and e-wallet. We explain practical consequences of that contrast for deposit speed, verification steps and withdrawal reconciliation.

We adopt a mobile-first framing for account access: we support Android installation and point users on iOS to browser access, we note minimum network requirements for stable live-dealer streams, and we design login flows for use on a single phone. We also mention how payment choices affect verification when you follow deposits for football markets such as Liga 1 and tournaments like Piala Indonesiaor when you top up for slots and esports markets.

Details on graha spin data handling

What we collect

We collect contact details you provide to set up an account, including email and phone number. We collect basic identity information during verification, such as name and a government-issued ID number when local law requires verification for payments or withdrawals. We record transactional data for deposits and withdrawals, including timestamps, amounts, payment rails (DANA, e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, online payment, e-wallet) and virtual-account references.

How we use your data

We use contact details to communicate account status, verification requests and withdrawal notices. We use verification information to match deposits made via bank virtual accounts or mobile banking scans, and to reduce processing delays on withdrawals. We use aggregated usage data to monitor stream quality for live-dealer tables and to prioritise network capacity for mobile users watching blackjack, roulette and baccarat.

Key takeaways

  • We keep payment logs for reconciliation and fraud prevention.
  • We process identity documents only for verification and withdrawal clearance.
  • We store session and cookie data to maintain login and streaming quality.

Payments, verification and withdrawal flow

We accept e‑wallet top-ups and QR payments for faster crediting; we accept local payment, online payment, e-wallet, mobile banking, local payment and online payment for scan-and-pay top-ups. We accept bank virtual-account transfers through e-wallet, mobile banking, local payment and online payment for larger transfers or when a VA record is required. We match incoming payments to accounts using the reference or a verified receipt. We hold withdrawal requests while identity or payment method verification is pending; our review steps require a completed verification file only where local law or payment partner rules demand it.

Cookies, tracking and device data

We set cookies to keep you logged in on mobile and to remember language and payment preferences. We collect device identifiers and basic telemetry to improve app installation guidance on Android, to suggest browser settings for iOS users, and to stabilise streams during MotoGP or badminton coverage. We use analytics providers to aggregate playback errors and page load metrics; we do not use third-party tracking to profile betting behaviour for advertising outside our service.

Third-party processors and storage

We use payment processors, identity verification vendors and cloud hosting providers to carry out transactions and to store encrypted records. We transmit only required fields to payment partners and retention follows contractual and regulatory rules. We note that our servers may sit outside your jurisdiction; we take contractual and technical steps to maintain encryption and access controls.

Transaction logs
We retain for reconciliation and fraud review; retention periods reflect partner rules.
Verification files
We hold securely while an account is active or until regulatory retention ends.
Session cookies
We use to maintain login and streaming sessions on mobile browsers and apps.
Account guide

Steps to verify and link your payment methods

Guide
mobile banking

E‑wallet top-up and reconciliation notes

Payment
local payment

Scan-and-pay guidance for mobile top-ups

Quick

Policy for graha spin privacy and retention

We commit to minimising data collection to the information necessary for account operation, payments and regulatory compliance. We limit internal access to verification files and transactional logs; we grant access only to staff with a defined business need. We log administrative access for audit purposes.

We provide options to update contact details and payment preferences inside your account. We respond to requests about data correction and export via our support channel; we ask that you start the process from the support page and provide the verification details we need to process the request. We route requests through our compliance team and aim to respond within a reasonable timeframe consistent with legal requirements.

We operate support and payment services while access is available only where local law permits. We note common local events and timing that affect processing: holiday queues during Idul Fitri and Idul Adha, and local bank closures around Imlek and Nyepi can delay settlement times in cities such as JakartaSurabaya and BandungWe recommend confirming payment references when submitting deposits, especially around major match days and tournament fixtures like Liga 1 and Piala Indonesia.

We at graha spin review this policy periodically and publish updates as needed. We encourage account holders to check the policy before using payment services and to contact our support team for any clarification about data handling related to sports, live-dealer sessions or slot and esports activity.