Your Personal Information

Account data, Lisbon server processing and privacy requests revised on 2026-11-16.

Riviera Spin Privacy Policy for Australian Accounts

Account Data Responsibility and Closed Accounts

Account data is handled under the responsibility of Riviera Spin LTD at Barge straat 1, Willemstad, Curaçao. Its wholly owned subsidiary, also Riviera Spin LTD, is at Hollandia 24. Contact [email protected] to identify the processing activity involved in your request and the records you want reviewed.

Closing your account does not necessarily erase records needed to handle a pending withdrawal, identity check or dispute. Our site does not publish a fixed retention period, so request the applicable period and reason for the record concerned. We should distinguish data still required for an identified purpose from information that can be deleted or anonymised. An exclusion record may need separate handling so that closure does not remove the restriction you requested.

Processing Outside Australia

Our published account information places servers in Lisbon, so account data may be processed outside Australia. That location concerns infrastructure and does not identify every organisation able to receive a particular record. Ask which entity handles the transfer and what protection applies before relying on an assumed Australian storage location.

When a request concerns a cross-border record, identify the activity and method involved, such as a Skrill withdrawal or an Evolution round. We can then distinguish the account record from information maintained by the named service.

Reasons for Handling Account Information

We use registration and identity information to administer accounts, check eligibility and review withdrawal requests. Payment records connect a deposit or payout to the correct account, while session and game records help investigate reported faults. We should identify the applicable processing basis for each purpose rather than treating registration as consent to every possible use.

Account administration, a required verification check and optional marketing serve different purposes. Ask us to identify whether a disputed use depends on contractual necessity, a legal requirement, consent or another applicable basis. Withdrawing an optional preference should be handled separately from evidence needed to complete an existing transaction.

Complaints About Personal Information

You may complain about how personal information has been handled, and can ask which supervisory authority is competent for the responsible controller and processing activity. Start by describing the record, the action you dispute and the remedy you want.

ACMA is not our data controller. We should identify the appropriate route after the relevant entity and jurisdiction are established, rather than promising that a gaming complaint channel can decide all data protection matters.

Information Recorded During Use

We collect the registration details you submit, including your email, password credentials, name, date of birth, address and mobile number. Cashier records identify the method, amount, status and transaction reference. KYC records can include a passport or Australian driver’s licence, proof of address and an e-wallet profile image when relevant to a payout.

Technical records include session events, device or browser information and the logs needed to investigate access problems. Cookies can store a preference or session state. We should explain the collection when requesting an additional item and avoid asking for a complete unrelated document where a relevant extract is sufficient. Never send a current authentication code or password in a support message.

Session cookies support sign-in, and preference storage can remember interface choices. Optional analytics and promotional storage must be distinguished from those account functions. Our published index does not name an analytics supplier, so this policy does not identify an unconfirmed service as a recipient of your browsing history.

You can change browser cookie settings and clear stored site data, although doing so may end a session or reset a saved preference. Ask support how to change a particular optional choice where no setting is visible. Blocking a session cookie is different from declining optional analytics. We should explain which category a requested setting affects instead of presenting all storage as equally necessary.

Recipients Connected to Specific Services

A payment or game service receives information needed for the selected activity, rather than every provider receiving the whole account file. Our cashier names PayID, Visa, Mastercard, Apple Pay, Google Pay, Skrill, Neteller, MiFinity, Jeton, Paysafecard and bank transfer, alongside Bitcoin, Ethereum, Tether (USDT) and Litecoin. Naming a cryptocurrency does not identify a separate corporate processor.

Game records can concern Pragmatic Play, Hacksaw Gaming, Nolimit City, Play’n GO, Relax Gaming, ELK Studios, Quickspin, Microgaming, Blueprint Gaming or Evolution, depending on the title played. This does not mean every studio receives your KYC images. The index names no KYC service company, so ask us to identify an actual recipient before uploading a document for a third-party check.

How to Request Access or Correct a Record

You can request access to your personal information, correction of inaccurate details and consideration of deletion, restriction, objection or portability where the applicable rules provide those rights. Tell us which record and action you mean.

We may need to confirm that you control the account before disclosing personal information. Use the least additional evidence needed for that check and ask for a secure route if documents are requested. Where a restriction prevents the requested action, we should explain the relevant record, purpose and reason rather than issuing a blanket refusal.

Written Data Enquiries

Send personal information requests to [email protected] from your registered email where possible. State that the message concerns privacy, describe the account record and specify the action requested. Include an existing case reference if we have already discussed the same record, but omit passwords, authentication codes and complete card details.

General support email is answered within 24 hours; that acknowledgement window is not a promise that a complex data request will be completed within the same period. Ask for the responsible entity, applicable timetable and next step when additional verification is needed. Keep the written reply and tell us promptly if the result contains an error or fails to address the particular record you identified.