Bearo Casino privacy notice: what we collect and what stays in your hands
An account at Bearo Casino generates two kinds of data: the details a player enters, and the records play itself produces. We collect the first to open and protect the account, and we produce the second so deposits, bonuses and withdrawals can be tracked and audited. Both stay bound to the account holder, and read, correction or removal requests all run through our support routes.
The collection follows the account’s life: sign-up takes the identity fields, play adds transaction and technical records, and the first withdrawal adds the verification file. Each category has its own purpose and its own retention window, which the table sets out; the rights list explains what a player can ask us to do with any of it.
What the account collects from its holder
- Account data from registration: name, date of birth, gender, phone number, address and the chosen country and currency.
- Contact data: the e-mail address that doubles as the login and the address support replies to.
- Transaction records: deposits, bonuses, wagers and withdrawals, kept so every balance movement can be traced.
- Verification records: the identity document, address proof and payment-method proof gathered before the first withdrawal.
- Technical records: security logs such as login sessions, held to protect the account rather than to profile the player.
How changes to the notice get announced
When the notice moves
Material changes are announced through the account before they take effect, so a player reading the notice sees the current version and the date it started.
Which purposes stay constant
The collection purposes stay tied to running the account: identity for the legal minimum age, transaction records for balance integrity, verification for payout safety. New purposes arrive only with a new announcement.
How long each record type stays
| Record type | Typical retention | Why it stays |
|---|---|---|
| Registration details | Life of the account | They define the account and the legal age |
| Transaction history | After closure, per financial record-keeping needs | Deposits and withdrawals must stay traceable |
| Verification documents | While the account is active, then per the retention schedule | Payout safety and audit duties outlive single payouts |
| Security logs | A bounded technical window | Session protection needs recent events, not history |
The rights a player can exercise
- Access: a request through support returns what the account holds about its holder.
- Correction: wrong registration details are fixed at the source, which keeps the KYC file consistent.
- Erasure: closure removes the active profile; financial and verification records keep to their retention schedule rather than vanish.
- Restriction and objection: processing that has no operational role can be paused on request.
- Complaint: if an answer disappoints, the data route can be escalated through the same support desk.
How we use the data, purpose by purpose
Registration data opens the account and confirms the 18-plus minimum age; contact data carries security notices and support replies; transaction data keeps bonuses, balances and payouts consistent with the terms; verification data gates the first withdrawal and later AML checks; technical data protects sessions through login security. Nothing in the flow exists to sell on, and requests about any of it travel through our 24/7 support, which hands them to the team that owns the records.
Last updated: 9 November 2026