rubic Privacy Policy
This page describes what we collect when you use rubic and how we keep that data protected. We at rubic take your privacy seriously and comply with data protection regulations in the jurisdictions where we operate. When you register an account, deposit funds, or place bets on our platform, we collect personal information necessary to verify your identity, process your transactions, and provide customer support.
Our rubic platform processes data across multiple systems: account registration, payment processing (DANA, e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, online payment, e-wallet), live-dealer game streaming, sportsbook operations, and customer support. Each system is protected by encryption, access controls, and regular security audits. We do not sell your data to third parties, and we limit sharing to only what is necessary to operate our service and comply with law.
This policy explains what data we collect, how we use it, who we share it with, how long we keep it, and what rights you have. If you have questions about your data or how we handle it, contact our support team.
What Data We Collect on rubic
We collect different types of data depending on how you use rubic. When you register an account, we collect your legal name, email address, date of birth, phone number, and residential address. We use this information to verify your identity and comply with anti-money-laundering regulations.
When you deposit or withdraw funds, we collect payment information: your chosen payment method (DANA, e-wallet, mobile banking, local payment, online payment, e-wallet, or bank account details), transaction amounts, and timestamps. We do not store full payment card numbers or wallet credentials; instead, we use tokenization to store a secure reference that our payment processors can use to execute transactions.
When you use rubic's live-dealer tables, sportsbook, or slot games, we collect information about your gameplay: which games you play, bet amounts, outcomes, and session duration. We use this data to settle bets, detect fraud, and improve our platform. We also collect technical data: your IP address, device type, browser version, and operating system. This helps us troubleshoot technical issues and detect unauthorized access.
How We Use Your Data on rubic
We use your data for several purposes. First, we verify your identity and comply with Know Your Customer (KYC) and anti-money-laundering (AML) regulations. This is a legal requirement in the jurisdictions where rubic operates. Second, we process your deposits and withdrawals, which requires sharing your payment information with our payment processors.
Third, we operate our games and settle bets. When you place a bet on a rubic live-dealer table or sportsbook market, we record your bet, the outcome, and your winnings or losses. This data is used to credit or debit your account and to detect fraud or collusion.
Fourth, we provide customer support. If you contact our support team, we review your account history, transaction records, and gameplay data to assist you. Fifth, we improve our platform. We analyze aggregate data (not linked to individual players) to understand which games are popular, which payment methods are preferred, and where technical issues occur. This helps us make rubic better.
Finally, we comply with legal obligations. If a court orders us to disclose your data, or if we detect illegal activity, we may share your information with law enforcement or regulatory authorities.
Our commitment on rubic is that your data is used only for the purposes you expect: account management, payment processing, game operation, and legal compliance. We do not use your data for marketing, profiling, or sale to third parties.
Third-Party Processors and Data Sharing
We share your data with third parties only when necessary to operate rubic. Our payment processors (the companies that handle mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, and bank transfers) receive your payment information to execute deposits and withdrawals. These processors are contractually bound to protect your data and use it only for payment processing.
Our live-dealer studios may be located outside your jurisdiction. When you watch a live-dealer stream from rubic, your session data (which table you joined, how long you played, your bets) may be processed on servers in Southeast Asia or other regions. We ensure that all data transfers comply with data protection standards and are encrypted in transit.
We may share aggregate, anonymized data with analytics providers to understand platform usage trends. This data cannot identify you personally. We do not share your personal data with marketing companies, data brokers, or advertisers.
Data Retention and Deletion on rubic
We retain your account data for as long as your rubic account is active. If you close your account, we retain your data for seven years to comply with anti-money-laundering regulations and to resolve any disputes. After seven years, we delete your personal data unless we are required by law to retain it longer.
You have the right to request deletion of your data before the seven-year retention period ends, subject to legal and regulatory constraints. Contact our support team to request data deletion. We will delete your data within 30 days unless we have a legal obligation to retain it.
Your Rights on rubic
You have the right to access your personal data. You can view your account information, transaction history, and gameplay records by logging into your rubic account. You also have the right to correct inaccurate data. If your name, address, or other information is wrong, contact our support team and we will update it.
You have the right to request a copy of all data we hold about you in a portable format. You have the right to object to certain uses of your data, such as profiling or automated decision-making. You have the right to lodge a complaint with your local data protection authority if you believe we have violated your privacy rights.
-
Access Your Data
Log into your rubic account to view your personal information and transaction history.
-
Request Corrections
Contact our support team if your account data is inaccurate and we will update it.
-
Request Data Export
Ask our support team for a portable copy of all data we hold about you.
-
Request Deletion
Request deletion of your data, subject to legal retention requirements.
Cookies and Tracking on rubic
We use cookies on rubic to remember your login session, store your language preference, and track your gameplay for fraud detection. Cookies are small text files stored on your device. Most are session cookies that expire when you close your browser. Some are persistent cookies that remain on your device for up to one year.
We use analytics cookies to understand how players use rubic. These cookies track which pages you visit, how long you stay, and which games you play. This data helps us improve our platform. You can disable cookies in your browser settings, but this may affect your ability to use rubic.
Security and Encryption on rubic
We protect your data using industry-standard encryption and security practices. All connections to rubic use TLS 1.3 encryption, which scrambles your data in transit so that third parties cannot intercept it. Your password is hashed using bcrypt, a one-way encryption algorithm that makes it impossible for us to recover your plaintext password even if our database is compromised.
We store payment credentials using tokenization: instead of storing your full card number or wallet ID, we store a secure token that our payment processors can use to execute transactions. We conduct regular security audits and penetration testing to identify and fix vulnerabilities. We maintain a security incident response plan so that if a breach occurs, we can respond quickly and notify affected users.
International Data Transfers
Our rubic servers and payment processors may be located outside your jurisdiction. When you use rubic from Jakarta, Surabaya, Bandung, Medan, or Semarang, your data may be transferred to and processed in other countries. We ensure that all international data transfers comply with data protection standards and are protected by encryption and contractual safeguards.
Contact and Complaints
If you have questions about this privacy policy or how we handle your data, contact our support team. We respond to privacy inquiries within 14 days. If you believe we have violated your privacy rights, you can lodge a complaint with our support team or with your local data protection authority.
Changes to This Privacy Policy
We may update this privacy policy at any time. We will notify you of material changes via email or by posting a notice on rubic. Your continued use of rubic after changes take effect constitutes acceptance of the updated policy. If you do not agree with changes, you may close your account and request a withdrawal of your balance.
Understanding rubic Security, Fairness & Verification
Platform security layers
We at rubic employ multiple layers of encryption and security monitoring to protect your account and payment information. Every connection between your device and our servers uses TLS 1.3 encryption, the current industry standard for secure data transmission. Your account password is hashed using bcrypt with a random salt—even if our database were compromised, an attacker could not reverse-engineer your plaintext password. We store payment credentials separately from your account data using tokenization, ensuring that card numbers and wallet IDs never reside on our main servers.
Beyond encryption, we employ real-time fraud detection algorithms that learn your typical transaction patterns. If a deposit or withdrawal deviates significantly from your norm—for example, a sudden large withdrawal to a new payment method—we flag the transaction for additional verification before processing. This proactive approach catches many frauds before they occur. We also implement device fingerprinting, which tracks the devices you typically use to access rubic. If someone attempts to log in from an unfamiliar device, we send you a verification email or SMS.
Every rubic account requires password protection and optional two-factor authentication (2FA). 2FA adds a second verification layer—even if your password is compromised, an attacker cannot access your account without the second factor (typically an OTP sent to your phone or generated by an authenticator app). We strongly recommend enabling 2FA, especially before making deposits or withdrawals. Our support team is available around the clock to assist with account security issues.
Game fairness and RTP
Our rubic live-dealer games are conducted by real human dealers using physical gaming equipment. There is no RNG (random-number generator) in live dealer games; fairness is guaranteed by the laws of probability and the physical nature of the game. Every card shuffle, every roulette spin, and every dice roll is conducted in person and recorded on multiple camera angles. Players at the table can observe the action in real time, and the full session is archived so you can review your play later if desired.
Return to Player (RTP) is not applicable to live-dealer games in the traditional sense, because outcomes depend entirely on chance and player decisions, not pre-programmed payback percentages. However, some rubic games incorporate multiple betting options with different payouts (for example, Baccarat's Banker, Player, and Tie bets have different odds). These odds are mathematically fair—the non-specific info commission on Banker wins, for instance, compensates the house for a slight statistical advantage but does not constitute an unfair game. Our terms of service and each game's info screen explain payouts and commissions transparently.
For slot games on rubic, we use only RNGs certified by independent gaming authorities. These RNGs have passed rigorous statistical tests to confirm they are truly random and not biased toward the house. Each slot game displays its RTP (return to player percentage) in the game info screen. RTPs are audited annually by third parties. We publish certification documents from independent gaming auditors confirming that our dealers follow proper protocols, that our equipment is unbiased, and that our game operations comply with industry standards. These certifications are available upon request through our support team.
KYC verification process
Know Your Customer (KYC) verification is a compliance requirement designed to prevent money laundering and fraud. We collect your legal name, date of birth, ID number, and proof of residence. Most new rubic accounts can deposit and play with basic limits without full KYC verification, but to unlock higher deposit and withdrawal limits or to process your first withdrawal, you'll complete verification.
We accept Indonesian KTPs (national ID cards), passports, and driver's licenses as primary identification. Proof of residence can be a utility bill, bank statement, or government letter showing your current address—any document dated within the last three months. You'll also provide a selfie holding your ID next to your face, which we compare against your uploaded ID photo using automated facial-recognition software and manual review by our compliance team.
Verification on rubic typically completes within 1-2 business days. You'll receive an email confirming approval or, if we need clarification, a request for additional documents. Once verified, your wallet limits increase significantly, and you're flagged as a trusted account in our system. Verification is good indefinitely; you only re-verify if we detect major changes to your account (address change, new ID, etc.) or if you've been inactive for over a year. Our KYC process complies with international anti-money-laundering standards and local regulations in supported jurisdictions.
User feedback and review channels
We actively solicit player feedback through in-app surveys, email follow-ups after withdrawals, and community forums. This feedback informs product updates—if dozens of players report that a particular rubic Live Draw table is consistently slow, we investigate the technical infrastructure or add additional tables. We publish aggregate statistics monthly: number of support tickets, average resolution time, table availability during peak hours, and popular payment methods. These metrics let players gauge platform health and responsiveness.
Individual player reviews of rubic appear on independent gaming forums, app stores, and community sites. We encourage honest reviews, both positive and critical. When players report bugs, balance errors, or feature gaps, our support team triages these into our development backlog. Serious issues—security flaws, payment failures, or dealer misconduct—are escalated immediately to senior staff and investigated thoroughly.
We do not publish fabricated aggregate ratings or cherry-picked testimonials. If you encounter a rubic review claiming "non-specific info player satisfaction" or "highest-rated live casino," treat it with skepticism—no platform achieves universal approval. Instead, read several individual reviews to form your own picture. Look for patterns: do multiple users praise the speed of deposits via DANA or OVO? Do players complain about dealer language barriers? Do users mention consistent withdrawal delays during holidays like Imlek or Nyepi? These details are far more informative than a single star rating and help you make an informed decision about whether rubic suits your needs.