Privacy Policy for Splash Coins Casino
Policy Overview
This Privacy Policy explains how Splash Coins Casino may collect, use, store, protect, and review personal information within a digital entertainment and casino information environment. It is designed to help users understand data handling practices related to account activity, identity verification, payment review, fraud prevention, cookies, security monitoring, and privacy rights.
This page is provided for informational purposes and should not be treated as individualized legal advice. Privacy requirements may vary by state, jurisdiction, platform operation, payment provider, and applicable regulatory framework. Users should always review the official account notices, terms, and privacy controls available inside the relevant platform environment.
Information We May Collect
Different types of information may be collected depending on how a user interacts with the platform, whether an account is created, whether identity verification is required, and whether payment or withdrawal activity takes place.
- Account Information: name, username, email address, phone number, date of birth, and account login details.
- Identity Verification Data: government-issued identification, address confirmation, payment ownership evidence, or other KYC-related materials when required.
- Transaction Records: deposit history, withdrawal requests, payment references, dispute records, refund logs, and balance-related activity.
- Device and Technical Data: IP address, browser type, device identifiers, operating system, session logs, and security signals.
- Geolocation Data: location signals used to support jurisdiction checks, access controls, geofencing, and compliance review.
- Support Communications: messages, ticket history, screenshots, attachments, and service-related correspondence.
- Cookie and Usage Data: session behavior, preference settings, security cookies, analytics data, and fraud prevention signals.
Why Personal Data Is Processed
Personal data may be processed to support account security, payment validation, regulatory compliance, fraud prevention, responsible gaming safeguards, technical stability, and customer support. Data processing should be limited to legitimate operational needs and handled through controlled systems where applicable.
| Processing Purpose | Examples of Data Used | Reason for Use |
|---|---|---|
| Account creation and access | Email, username, password status, device logs | To create accounts, support login access, and protect user credentials |
| KYC and age verification | Date of birth, ID documents, address confirmation | To confirm eligibility, reduce fraud, and meet verification requirements |
| Payment and withdrawal review | Transaction ID, payment method, account ownership proof | To process payments, investigate disputes, and prevent unauthorized withdrawals |
| Fraud prevention | IP address, device signals, login behavior, geolocation data | To detect suspicious activity, account abuse, and unauthorized access |
| Responsible gaming controls | Limit settings, self-exclusion records, account restriction preferences | To maintain safety tools and enforce responsible gaming decisions |
| Customer support | Support tickets, screenshots, communication history | To respond to user requests, resolve issues, and keep service records |
KYC, SSN, and Identity Verification
Identity verification may be required when a user creates an account, requests a withdrawal, changes sensitive account information, or triggers a compliance or security review. Verification helps confirm account ownership, reduce fraud, support age eligibility checks, and protect payment activity.
Some operators may request sensitive identifiers, including partial or full tax-related information, depending on jurisdiction, payment processor requirements, reporting thresholds, or compliance obligations. Not every platform requests the same information, and users should only provide sensitive documents through a verified secure upload interface.
Users should never send identity documents, Social Security numbers, payment credentials, or one-time security codes through public comments, unsecured messages, social media replies, or unofficial third-party forms.
How We Protect User Information
Data protection relies on layered security controls intended to reduce unauthorized access, limit unnecessary exposure, and separate sensitive information from general analytics or support data. Security methods may vary by system, but the core objective is to protect account, payment, and identity-related records.
- Restricted access controls for sensitive account and KYC records.
- Encryption or protected storage for payment-related references where applicable.
- Segmentation between identity datasets, transaction logs, and behavioral analytics.
- Security monitoring for suspicious login patterns, device changes, and unusual account behavior.
- Document review workflows designed to limit unnecessary access to uploaded identity materials.
- Retention controls to avoid storing data longer than required for operational or legal purposes.
Real-World Privacy Scenarios
Player Changes Sensitive Account Information
When a user changes an email address, phone number, password, payment method, or login credential, additional verification may be required. These checks help prevent unauthorized account takeover and reduce the risk of funds being redirected to an unverified payment destination.
Player Requests KYC Document Deletion
A user may request deletion of identity documents, but deletion can be limited when records are needed for anti-fraud review, AML obligations, tax reporting, payment disputes, chargeback defense, responsible gaming enforcement, or regulatory audits. In such cases, records may be moved into a restricted retention state rather than deleted immediately.
Player Permanently Closes an Account
When an account is closed, active marketing preferences and unnecessary session data may be deactivated or removed. However, certain transaction records, verification logs, and responsible gaming records may remain stored for a defined retention period when required by law, dispute handling, or compliance review.
Data Retention
Retention periods vary depending on applicable state law, platform policy, payment provider obligations, gaming regulation, tax reporting requirements, and dispute resolution needs. The table below provides a general overview of typical retention logic rather than a fixed legal promise.
| Data Type | Typical Retention Approach | Primary Purpose |
|---|---|---|
| Identity and KYC documents | May be retained for several years after account closure where required | Compliance review, AML obligations, fraud prevention, and audit history |
| Transaction records | May be retained for multi-year financial and dispute review periods | Payment reconciliation, tax reporting, chargebacks, and withdrawal verification |
| Geolocation and access logs | Usually retained for operational or compliance review windows | Jurisdiction verification, geofencing, and access control enforcement |
| Support tickets | May be retained during the service lifecycle and dispute history period | Customer care, issue tracking, quality assurance, and complaint handling |
| Cookie and analytics data | May be retained according to consent settings and technical requirements | Session stability, preference management, security monitoring, and site improvement |
| Responsible gaming records | May be retained even after deletion requests where safety obligations apply | Self-exclusion enforcement, limit management, and player protection compliance |
User Privacy Rights
Depending on location and applicable law, users may have the right to access, correct, delete, restrict, or request a copy of certain personal information. These rights may be subject to identity verification, security review, legal retention duties, and compliance limitations.
California Privacy Rights
California residents may have rights under CCPA and CPRA, including the right to request access, correction, deletion, and information about certain data practices. Some requests may be limited when retention is required for fraud prevention, payment disputes, tax reporting, or legal compliance.
Colorado Privacy Rights
Colorado users may have rights under the Colorado Privacy Act, including access, correction, deletion, portability, and opt-out rights for certain types of processing where applicable.
Virginia Privacy Rights
Virginia users may have rights under the Virginia Consumer Data Protection Act, including access, correction, deletion, portability, and the ability to opt out of certain processing activities.
Connecticut Privacy Rights
Connecticut users may have rights under the Connecticut Data Privacy Act, including rights related to access, correction, deletion, portability, and opt-out controls where applicable.
How to Submit a Privacy Request
Users who want to access, correct, delete, restrict, or receive a copy of their personal data should submit a request through the designated secure support or privacy request channel. The request may require identity confirmation before any account-specific information is released or modified.
- Select the privacy, account, or data request category in the official support area.
- Provide the registered email address or account identifier connected to the request.
- Clearly state whether the request involves access, correction, deletion, restriction, portability, or marketing preferences.
- Complete any identity verification steps required to protect the account owner.
- Wait for confirmation, follow-up questions, or a response explaining whether legal limitations apply.
Cookies and Tracking Technologies
Cookies and similar technologies may be used to maintain login sessions, remember preferences, protect accounts, measure site performance, detect suspicious activity, and improve user experience. Some cookies are necessary for security or platform operation, while others may support analytics or preference management.
Users may manage browser cookie settings or platform consent preferences where available. However, disabling essential cookies may affect login sessions, security verification, payment flow stability, or access to certain account functions.
Third-Party Service Providers
Some data may be processed by trusted service providers that support payment processing, fraud detection, identity verification, analytics, hosting, security monitoring, customer support, or compliance review. These providers should only receive information necessary for their assigned function and should not use personal data for unrelated purposes.
Payment processors, identity verification vendors, and security providers may have their own privacy practices. Users should review relevant notices when interacting with third-party payment or verification systems.
Children and Age Restrictions
Splash Coins Casino content and related casino information are intended for adults who meet the legal age requirements in their jurisdiction. The platform is not designed for children or underage users. Age verification and identity checks may be used to help prevent unauthorized or underage access.
Internal Compliance Links
- Terms and Conditions → review platform rules, eligibility requirements, and user obligations
- Responsible Gambling → learn about player protection, account limits, and self-exclusion tools
- Payment Methods → understand payment processing, deposits, withdrawals, and verification checks
- Contact Support → submit privacy, account, KYC, or payment-related support requests
Privacy Policy Updates
This Privacy Policy may be updated when data practices, compliance requirements, payment methods, verification processes, cookie tools, or user rights procedures change. Users are encouraged to review this page periodically to understand how personal information may be handled.
If a factual error appears on this page, readers may report it through the contact process. Verified corrections are reviewed and implemented as quickly as possible, especially when the issue involves privacy rights, data retention, KYC verification, payment security, or responsible gaming records.
Privacy FAQ
Can I delete my Splash Coins Casino account and personal information?
Users may request deletion of account information, but some records may be retained when required for payment disputes, fraud prevention, AML checks, tax reporting, responsible gaming enforcement, or legal compliance.
Why does Splash Coins Casino require my date of birth?
Date of birth may be required to confirm age eligibility, prevent underage access, and support compliance with jurisdiction-specific gaming rules.
Why does an online casino ask for ID?
Identity documents may be requested to confirm account ownership, prevent fraud, verify age, review payment activity, and support withdrawal security checks.
Why would an online casino request an SSN?
An SSN or similar tax-related identifier may be requested only in certain situations, such as jurisdiction-specific reporting, identity verification, payment processor checks, or tax-related obligations. Users should confirm that the request appears inside a secure official verification flow before submitting sensitive information.
Does Splash Coins Casino sell personal gaming or financial data?
Personal data should be processed for operational purposes such as account management, payment processing, fraud prevention, compliance review, and support handling. Sensitive financial credentials should not be sold or exposed through unsecured channels.
Can I request a full copy of my personal data?
Users may be able to request a copy of personal data through the official privacy or support channel. Identity confirmation may be required before account-specific information is released.
Will my account be restricted if I refuse KYC verification?
Account features may be restricted when verification is required for withdrawals, payment changes, compliance review, security checks, or legal eligibility confirmation.
Can casinos keep my documents after account closure?
Some documents and records may be retained after closure when required for audits, tax reporting, payment disputes, AML obligations, responsible gaming enforcement, or legal compliance.
What happens to self-exclusion data if I request deletion?
Self-exclusion and responsible gaming records may remain stored when needed to enforce safety restrictions and prevent a closed or restricted account from being reopened improperly.
Do cookies collect my financial information?
Cookies generally support session activity, preferences, analytics, security checks, and fraud prevention. They should not collect full payment card numbers, private wallet keys, or complete financial credentials.
How are uploaded identity documents protected?
Uploaded identity documents should be handled through restricted access systems, secure storage, verification-only workflows, and retention controls designed to reduce unnecessary exposure.
Can I request data deletion while a withdrawal is pending?
A deletion request may be delayed when a withdrawal, dispute, verification review, or compliance investigation is still active. The request may continue after the financial or legal review is resolved.