How Spinathlon handles account data, purpose by purpose
At Spinathlon we collect what an account needs to run, and the purpose drives the type: registration fields identify the player, transaction records power the cashier, and verification files serve the payout check alone. Our terms carry the security figures — the encrypted environment and the firewall-protected database — and this policy uses the same words for the rest.
How the data is used, purpose by purpose
- Registration fields identify the player and fix which published figures apply.
- The currency choice at registration determines the limits the cashier uses.
- Transaction history keeps the payout clock, the floors and the turnover rule working.
- Bonus records follow the claimed stages and their wagering progress through the Spinathlon lobby.
- Support messages are read by the team that answers in English and French.
What the account may collect
- Registration fields: the form data and the chosen account currency.
- Transaction records: deposits and withdrawals with dates, amounts and routes.
- Bonus records: the claimed welcome stages and their wagering progress.
- Verification documents: photo ID, address proof and payment ownership, requested at payout inside the 14-day window.
- Support messages: chat and email correspondence with the team.
How changes to this policy are announced
- Changes appear in the policy with the date line at the end updated.
- The terms pages carry the same wording so a change never splits between texts.
- Material changes reach registered players through an account message before they take effect.
The rights a reader keeps over the data
- A written request through support opens what the account stores.
- Registration fields can be corrected before verification runs.
- An exact name keeps the payout inside its window instead of delaying it.
- Closure goes through support; an account left alone meets the dormancy rule instead.
Third parties and how data is shared
| Recipient | Reason | What is shared |
|---|---|---|
| Payment routes | processing the transaction | the deposit or payout details the route needs |
| Verification provider | confirming identity and payment ownership | the documents the player submits |
| Support team | answering account questions | the messages the reader sends |
| No marketing sharing | our terms name no advertising schedule | no data leaves for marketing |
How the data is protected
The encrypted connection protecting data in transit
Our connection uses encryption in transit, covering the sign-up form, the cashier and the mobile session on iOS and Android the same way.
The firewall-protected database behind the account
The player database sits behind a firewall, and submitted verification documents rest inside the same environment our terms describe.
Cookies and analytics, briefly
- Essential session cookies carry the login state and the cashier session.
- Preference cookies keep the language and interface choices between visits.
- No cookie holds balances, bonus states or payout requests; those live in the account behind the login.
- Our terms name no advertising network on the lobby pages; the cookie policy has the full detail.
Last updated: 2026-11-09