Privacy Policy
Brand context
This Privacy Policy explains how personal data may be processed in connection with Crash Game Plinko as a game product and related communications. In many deployments, the hosting platform collects and processes end-user account, payment, and verification data. Where the hosting platform acts as controller for those activities, you should also review the hosting platform’s privacy documentation in its account area.
Brand entities and contacts
| Item | Value |
| Brand | краш игра plinko |
| Primary domain identifier | spribe.co |
| Operator | Spribe OÜ |
| Support channels | sales@spribe.co; hello@spribe.co |
| Data contact | Not provided |
Definitions
| Term | Definition |
| Personal data | Information relating to an identified or identifiable person. |
| Processing | Any operation on data, such as collection, storage, use, disclosure, or deletion. |
| Controller | The party that determines purposes and means of processing. Not provided; check official terms/policy in account area. |
| Processor | A service provider processing data on behalf of a controller. |
| Cookies | Files or similar technologies used for core functions, preferences, analytics, or advertising, depending on configuration. |
Categories of data
Data categories depend on integration and your interaction type.
Communications data
- Messages sent to support channels
- Contact details you provide in correspondence
- Request metadata (time, subject, attachments where supplied)
Technical and security data
- Network and device information that may be present in logs (for example IP address, timestamps)
- Security signals used to prevent abuse
Account, payments, and verification data
Not provided under this policy, because these are typically processed by the hosting platform that provides end-user accounts and payments. Check official terms/policy in the account area.
Purposes of processing
Service operations
- Handle enquiries and operational requests
- Maintain service integrity and investigate incidents
Security and fraud prevention
- Detect abuse and protect systems and communications channels
Compliance
- Meet legal obligations where applicable to the operator’s activities
- Preserve records for disputes or regulatory requests where required
Legal bases
Legal bases depend on jurisdiction and context. Common bases may include:
- Legitimate interests for security and service integrity
- Performance of a contract when providing requested services
- Legal obligation where recordkeeping or disclosures are required
- Consent where required for certain cookie categories or optional communications
Cookies
General approach
Cookies may be used on operator websites for core functionality and analytics, depending on configuration.
Cookie details
Not provided. Check official terms/policy in the account area.
Data retention
- Retention periods: Not provided
- General approach: data is retained only as long as necessary for the purposes described, then deleted or anonymized where feasible, subject to legal obligations.
Recipients and processors
Data may be shared with:
- Infrastructure providers (hosting, monitoring, email delivery)
- Security and anti-abuse providers
- Professional advisers (legal, audit) where necessary
- Authorities where required by law or valid request
Specific vendor lists: Not provided.
International transfers
If data is transferred across borders, appropriate safeguards may be applied depending on the relevant legal framework. Details: Not provided.
Security
Security measures may include access controls, encryption in transit, secure credential handling, monitoring, and incident response processes. Exact technical measures are not exhaustively listed for security reasons.
Your rights
Depending on your jurisdiction, you may have rights to:
- Access and obtain a copy of your data
- Correct inaccurate data
- Delete data in certain cases
- Restrict or object to processing in certain cases
- Portability in certain cases
- Withdraw consent where consent is used
How to submit a privacy request
| Step | Description |
| Step 1 | Describe your request clearly: access, correction, deletion, or objection. |
| Step 2 | Provide sufficient information to locate relevant records (avoid unnecessary sensitive data). |
| Step 3 | Send the request to the support channels: sales@spribe.co or hello@spribe.co. |
| Step 4 | If identity verification is needed to protect your information, follow the instructions provided. |
| Step 5 | If the requested topic concerns a hosting platform account, submit the request via the hosting platform’s account area. |
Document updates
Last updated
Not provided