cozmetica - Privacy Policy for your account
cozmetica keeps your account, casino, sportsbook and payout data under one clear Privacy Policy, so you can see what we collect before you open an account. This page...
How we treat personal data
This Privacy Policy applies when you use cozmetica.app in supported regions, open an account, contact us, verify a withdrawal, or move between casino, live casino, slots and sportsbook areas. We collect only the data needed to run your account flow, protect access, meet platform checks and process requests tied to local payment rails. That can include your name, contact details, login activity,
device data, transaction references, support messages and verification files. We do not sell your personal data. We share limited details with service partners only when they are needed for hosting, fraud controls, payment checks, customer care or legal requests where local law permits. By continuing, you can read exactly how each data category is used before you share more.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions and contact paths
If you need help with this Privacy Policy, contact us before sharing extra documents or account details. We route privacy requests separately from general lobby questions, so your message reaches the team that can check data access, correction, deletion or retention matters.
Privacy email
Send privacy requests to [email protected] with your account email and a short reason. We may ask for limited verification before discussing account records, because privacy requests can expose sensitive profile data.
Live chat handoff
Use chat to ask where to send a privacy request, not to post full documents. Our chat team can direct you to the privacy email and mark the account so follow-up is easier.
Account message
If you are already signed in, you can send a brief message from your account area. Keep the request focused on privacy, such as access, correction, deletion, retention or payment reference handling.
Policy care signals we maintain
We keep this Privacy Policy practical rather than vague. Each data point connects to an account process you can recognise, such as sign-in security, live table access, sportsbook settlement, withdrawal checks, or...
Plain data mapping
We describe account, device, transaction and support data in separate groups. That makes it easier for you to see why each category exists and which account process depends on it.
Access controls
Internal account tools are role based, so staff see only the records needed for their task. Privacy requests are not handled through open lobby chat histories unless your request starts there.
Local payment context
JazzCash, Easypaisa, SadaPay and Raast references are treated as transaction data. We use them for matching, verification and support checks, not for unrelated messaging outside your account relationship.
Retention checks
We keep records for as long as account operation, dispute handling, security checks or legal duties require. When a record is no longer needed, we aim to remove or anonymise it safely.
Security monitoring
Login attempts, device signals and session changes help us detect suspicious access. These records support privacy by reducing the chance that another person can reach your account without approval.
Human response
Privacy messages are read by people who can check account context. Automated filters may help sort requests, but access or deletion matters still receive human handling before action is taken.
How this policy aligns
Our legal pages are meant to fit together without mixed wording. The Privacy Policy explains data handling, while other legal pages cover account rules, cookie settings and promotion...
| Account terms | Account rules may explain what you can do on the platform, but this Privacy Policy explains how data linked to those actions is collected, used, stored and shared with limited partners. |
|---|---|
| Cookie page | Cookie wording covers browser storage and similar tools. This Privacy Policy connects those signals to wider account data, such as sessions, device checks, fraud controls and preference handling. |
| Promotion terms | Promotion rules may require eligibility checks. When those checks use personal data, this Privacy Policy explains the privacy side, including why we may store records tied to account activity. |
| Payment terms | Payment wording explains transaction handling. This page focuses on the personal data around those transactions, including JazzCash, Easypaisa, SadaPay and Raast references used for matching and support. |
| Support rules | Support pages explain how to reach us. This policy explains what happens to chat logs, email messages, account screenshots and follow-up records after you contact us about your account. |
| Security wording | Security text describes account protection steps. The Privacy Policy explains the data behind those steps, such as login records, device signals, verification checks and access-control logs. |
| Regional wording | Market pages may mention access in Pakistan where local law permits. This policy explains how privacy handling works when your account, device or payment references are connected to that region. |
Layout cues on this policy page
This page is built so privacy terms are easy to scan before you create or use an account. We use section labels, short badges, contact cards and direct...