Riverline1. Who is responsible for your data
1.1 The controller of your personal data is the operator whose name appears on the site where you registered. That operator's legal name is in the footer of every page and its registered details are on the About page. Reach it about anything in this policy through the form on the Help page, choosing Privacy or data request, or at the address the room publishes in its footer.
1.2 Riverline operates the platform on the operator's behalf and processes your data under its agreement with the operator. Where you play at a table shared across the network, Riverline also acts as controller of the game record for the purpose of running and settling the hand between players from different operators.
1.3 Your operator has not appointed a data protection officer. If its licence or the law where it is established requires one, the appointment and how to reach that person are published in this section.
2. What we collect, and where it comes from
We collect only what the service needs. Each category below exists as a table or a record in our systems.
2.1 Account data. Your username, your email address if you give one, the hash of your password (we never hold the password), whether and when you enrolled an authenticator, your age and legal-age declarations, the country you declared, your account status and the dates you first deposited and first withdrew. Source: you, at registration and in Account.
2.2 Device and session data. For each device you sign in from: a fingerprint your browser supplies, the browser's user-agent string, the last network (IP) address it used, a label if you set one, and when it was first and last seen. For each sign-in: when it happened, from which device and address, when it was last used, and if and why it was ended. Source: your browser and our servers.
2.3 Location data. The country our edge determines from your connection, and, where a location provider is configured, that provider's assessment of your connection (country, whether it appears to be a VPN, proxy or hosting range, and whether the device was verified). Source: your connection and, where configured, a location-evidence provider; see section 5.
2.4 Integrity signals. For each decision you make at a table, the client sends a handful of summary numbers that tell a person apart from a script: how much your pointer path curved and how much its speed varied, how long you held the button down, how much the touch pressure varied where the device reports it, how many pointer samples the decision produced, how many times the window lost focus while the decision was open and for how long, how long the decision took, and whether the browser reported an automation flag. The pointer positions themselves are reduced to those numbers in your browser and never leave it: no coordinate, no per-event timestamp and no keystroke is sent, and nothing outside the table window is read. Source: the table client.
2.5 Play data. Every hand you are dealt into: the cards, every action, its timing, the result, the rake taken and the seed and commitment that produced the deck; the tables and tournaments you sat at and when; your seat changes, sit-outs and time-outs; and your responses to reality checks. Source: the game servers.
2.6 Chat and moderation data. Every message you send at a table, every moderation event concerning you, and any mute or chat restriction applied to your account with its reason and duration. Source: you, and our moderation.
2.7 Money data. Your balance and every entry in the ledger that changes it: deposits, the chain transaction and rate at which each was credited, buy-ins and cash-outs, rake, promotional grants and locks, withdrawals, the addresses you have verified and used, and every hold applied and released. Source: the ledger, the cashier and the chain.
2.8 Identity and verification data. Documents you upload for identity review (passport, identity card, driving licence, proof of address, selfie), the reviewer's decision and note, and your verification tier. Source: you, and our reviewers.
2.9 Screening data. The result of checking a deposit address or a withdrawal address against sanctions lists and known mixing services, and any risk score attached to a withdrawal. Source: screening providers and our risk rules; see section 5.
2.10 Limits and exclusion data. Every limit you set, every change to it and when it took effect, every time-out and every self-exclusion. Source: you.
2.11 Support and complaint data. What you write to support and what we reply, and the record of any complaint. Source: you and our staff.
2.12 Staff access records. Every action a member of staff takes concerning your account is written to an audit log with the staff member's identity, the action and the reason given. Source: our systems.
3. Why we use it, and the legal basis
| Purpose | What we use | Basis |
|---|---|---|
| Running the games and settling hands correctly | Account, play, money data | Performance of the contract |
| Crediting deposits and paying withdrawals | Money, identity, screening data | Contract; legal obligation (AML) |
| Keeping your account secure and binding sessions to devices | Account, device and session data | Contract; our legitimate interest in preventing account takeover |
| Detecting collusion, bots, chip dumping and other prohibited practices | Play, chat, integrity, device, session, location data | Legitimate interest in the integrity of the games; contract (fair-play terms) |
| Verifying age, identity and source of funds; sanctions screening; reporting where required | Identity, screening, money data | Legal obligation |
| Enforcing limits, cooling-off periods and self-exclusions across the network | Limits data, account data | Legal obligation; contract |
| Enforcing where real-money play is permitted | Location data | Legal obligation (licence conditions) |
| Paying promotions and affiliate commissions correctly | Play and money data | Contract; legitimate interest in preventing promotion abuse |
| Answering your support requests and handling complaints | Support data and whatever the request concerns | Contract |
| Keeping the records the law on gambling and money laundering requires | All of the above | Legal obligation |
We do not use your data for automated decisions that produce legal effects on you without human review: every sanction beyond a warning, every identity decision and every withdrawal refusal is made by a person, who may be assisted by the signals above.
4. Who can see your data
4.1 The operator's staff, under permissions granted to them individually and revocable individually. A member of staff sees only what their permission covers, and every action they take on your account is logged with their name and a reason. Support staff cannot see your cards in a live hand; the permission that reveals hole cards is withheld from support, money review and customer-facing roles by design.
4.2 Riverline's platform staff, under the same permission model, for running the games, settling money across the network, integrity investigation and the security of the platform. Platform-only actions, such as changing a sanctions provider or an operator's commercial terms, require a second authorised person.
4.3 Other players see your username, your country flag where shown, your stack, your actions, your chat, and your cards only when the rules of the game show them (a showdown, or a hand you chose to show). Cards you folded or mucked are not shown to other players, at the table or afterwards.
4.4 Identity reviewers see the documents you upload. The documents are not returned to you or to anyone else through the service; only a reviewer reads them, and your view shows only the status and the reviewer's note, never the reviewer's name.
4.5 Service providers listed in section 5, each under contract to process your data only on our instruction.
4.6 Authorities and regulators where the law requires or permits, including the gaming regulator, financial-intelligence and tax authorities, and courts. Where we are required to report suspicious activity, we may be prohibited from telling you that we have.
4.7 A purchaser of the operator's business, as part of a sale, under confidentiality and this policy.
We do not sell personal data, and we do not share it with advertisers.
5. Service providers and international transfers
5.1 Hosting. The platform runs on rented servers, and your data is stored and processed on them. The countries those servers are in are set by the hosting contracts your operator holds; ask through the Help page and we will tell you where your data is held today.
5.2 Blockchain. Deposits and withdrawals are transactions on the Polygon public network, read and broadcast through two independent node providers. A transaction on a public chain is permanent, public, and outside our control; the address you deposit from and withdraw to is visible on that chain to anyone.
5.3 Sanctions and exposure screening. Deposit and withdrawal addresses are checked against an on-chain sanctions oracle and, where the operator has configured one, an exposure-scoring provider. Only the blockchain address is shared with either; your name, your email and your play are not.
5.4 Location evidence. Where the operator has configured one, a location-evidence provider supplies a signed assessment of your connection and device (section 2.3). Where one is in use for your room it is named under Where you can play.
5.5 Email. Transactional email (verification, password reset, security notices, withdrawal confirmations) is sent through one email delivery provider, which receives your address and the message. Links in those emails are constructed so that the secret part never reaches analytics or your browser history.
5.6 Analytics. On public pages only, Google Analytics 4 counts page views with advertising features and personalisation off and without storing IP addresses; it is not loaded on any signed-in page or on the pages reached from an email link. Vercel Analytics counts page views and sets no cookie. Neither receives your account identity. See the Cookie policy.
5.7 A provider may be outside the country you live in. Where the law where you live requires a transfer safeguard, the operator's contract with that provider carries one, and we will tell you which on request through the Help page.
6. How long we keep it
| Data | Kept for | Why |
|---|---|---|
| Account, identity and money data | At least as long as anti-money-laundering and gambling law requires after the account closes | Anti-money-laundering and gambling law |
| Hand records, including the seed and commitment | As long as they may be needed as evidence of a hand | A dispute or an integrity case months later can only be decided from the record |
| Chat and moderation records | With the hand they belong to, and for the duration of any restriction they support | Evidence in collusion and conduct cases |
| Device and session records | The life of the session, and afterwards while they are needed to detect abuse | Detecting account takeover and multi-accounting |
| Limits, time-outs and self-exclusions | The duration of the control, and afterwards so that it can be proved; a self-exclusion is kept for as long as it can be enforced | The control cannot be enforced across the network without the record |
| Screening results | With the money record they concern | Legal obligation |
| Staff audit records | With the account record they concern | Regulatory evidence of who did what |
| Support correspondence | While the complaint is open, and afterwards as evidence of how it was handled | Complaints handling |
We do not publish a number of years in this table, because the numbers are set by the licence your operator holds and it does not hold one yet. When it does, each period is written here as a figure. Until then nothing is deleted on a schedule, and this section says so rather than promising an erasure that no job performs.
When you close your account, personal fields that the law does not require us to keep are anonymised on request; the records the law requires us to keep are kept and then deleted.
7. Your rights
Depending on where you live, you have some or all of the following rights. You can exercise most of them yourself in Account; the rest through the form on the Help page under Privacy or data request, from the email registered to your account.
- Access. See the personal data we hold about you. Your profile, devices and limits are in Account, your settled hands in Hand history and your deposits and withdrawals in Cashier; a full copy is available on request.
- Rectification. Correct your profile in Account. Some fields (the age declaration, verified identity details) cannot be changed without re-verification.
- Portability. Ask for a copy of the data you gave us, in a machine-readable form, through the Help page.
- Erasure. Ask for your account to be closed and your personal data anonymised. We must keep the records in section 6 for their periods; the rest is anonymised.
- Objection and restriction. Object to processing based on legitimate interest, or ask us to restrict processing while a question is resolved. We will explain where an overriding interest, such as the integrity of the games or a legal obligation, means we must continue.
- Sign out any device. From Account → Sessions, at any time.
- Withdraw consent where processing is based on it, without affecting what was done before.
- Complain to the data protection authority of the country you live in. Where your operator's own supervisory authority is named by its licence, it is published in this section as well.
We answer a request within the period the law where you live gives us, and we may ask you to verify your identity before we act on one.
8. Security
8.1 Passwords are stored only as Argon2id hashes, and an authenticator code that has been used once cannot be replayed. Sessions are bound to a device fingerprint and rotated on every refresh; an access token lives ten minutes. Every withdrawal requires a second factor.
8.2 Staff access is by individually granted permission, and every staff action on your account is logged. An action that moves money manually is proposed by one member of staff and decided by another, and the database refuses the record when the same person does both. The platform's own owner is the single exception to that rule, and their decision is recorded in their name.
8.3 Identity documents are limited in size and type, hashed so a re-upload is not a second copy, and readable only by a reviewer.
8.4 The wallet that holds player funds is isolated on its own network segment, reachable only from the gateway, and its signing keys are never present in the service that serves the website. Funds above the amount needed for immediate withdrawals are held in custody that requires hardware signing by staff.
8.5 If we become aware of a breach affecting your data we will notify you and the authority within the period the law requires.
9. Children
The service is for adults. We do not knowingly hold data about anyone under 18 (or the age of majority where they live). An account found to belong to a minor is closed and its data deleted except where the law requires it to be kept; any funds are returned to the source where the law allows.
10. Changes to this policy
The date of the current version is at the top of this page. A material change is announced in your account before it takes effect.
11. Questions
Anything in this policy, and any request under section 7, goes through the form on the Help page under Privacy or data request. It reaches the room's support inbox whether or not you are signed in.