Reference

Privacy Policy – How We Handle Your Account Information

We collect only what's needed to run your account, verify withdrawals to DANA, OVO, GoPay, and keep the platform secure. You control your data — request a copy, ask for corrections, or delete your account from the support panel.

Account verificationWithdrawal securityCookie settingsData request portalContact privacy team
pelangi33 Privacy Policy – How We Handle Your Account Information
PRIVACY CONTACT

How to Reach Our Privacy Team

Questions about what we collect, requests to download your data, or instructions to close your account — send them through the channels below. Response time is usually one business day for data requests, instant for general questions via live chat.

Live chat privacy queue Tap the chat bubble on any page, select Privacy & Data, and an agent will walk you through download or deletion steps. Open every day.
Privacy request form Log in, go to Account → Privacy, submit your request — download my data, correct a detail, or delete my account — and we'll process it within 48 hours.
Email privacy team Write to privacy@pelangi33 from the email on your account. Include your phone number so we can confirm it's you. We reply within one business day.
HOW WE PROTECT IT

Data Handling Practices

We encrypt everything in transit with TLS and at rest with AES-256. Payment details never touch our servers — DANA, OVO, GoPay connections run through their own secure gateways and we see only a masked reference. Passwords are hashed with bcrypt; even our own admins can't reverse them. You set a six-digit PIN for withdrawals, stored separately from login credentials. Two-factor via SMS OTP is optional but cuts account takeover risk by over ninety percent. Staff access is role-limited — support sees tickets and account status, finance approves withdrawals, no one gets both. Every data query is logged and audited quarterly.

Encryption everywhere

TLS 1.3 in transit, AES-256 at rest. DANA, OVO, GoPay credentials never stored — we hand off to their gateway and get back a token we can't decode.

Hashed passwords & PINs

Bcrypt with per-user salt for passwords, separate six-digit PIN for withdrawals. We can reset them but never see the plaintext. SMS OTP adds a second factor on request.

Role-limited staff access

Support reads tickets and account status, finance team approves cashouts, no overlap. Every lookup is logged. Quarterly audit reviews who accessed what and why.

Data export & deletion

Download your full history as JSON from Account → Privacy. Request deletion and personal profile vanishes in 30 days; transactional archive stays for legal retention only.

Common Privacy Questions

We ask for phone number, email, and your DANA, OVO, or GoPay account number. That's enough to send login OTPs, credit deposits, and route withdrawals. No scanned documents unless local law requires extra verification.

Yes. Log in, go to Account → Privacy → Download My Data, and you'll get a JSON file with registration date, transaction history, bet records, support tickets, login timestamps, and device logs. Usually ready in under a minute.

No. Providers see only an anonymous session token. Your DANA, OVO, GoPay account numbers stay with us and the payment gateway — never passed to studios or analytics scripts. Support staff see masked references when reviewing tickets.

Go to Account → Settings, enter the new phone or email, confirm via OTP sent to both old and new, done. Takes about two minutes. If you lost access to the old one, contact live chat with your account details.

Personal profile — name, phone, email — is deleted within 30 days. Transaction history stays in cold archive for three years to meet regulatory requirements, but it's anonymized and can't be tied back to you after deletion completes.

Email privacy@pelangi33 from your registered address or use the Privacy & Data queue in live chat. We aim to reply within one business day and resolve most requests in 48 hours. Serious concerns escalate to our compliance lead.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.