Who holds your data
View Clash decides what is collected here and why, and can be reached through the contact form at viewclash.com/contact. Our postal address is in the Legal Notice.
View Clash runs on servers we rent from Hostinger International Limited and administer ourselves in the European Union. The database is ours, on that machine; its nightly backups are the one copy that leaves the European Union (see Who else sees it).
What we collect when you play as a guest
- An anonymous account, created the first time you press Play, create or join a room, follow a room link or open the channel search, with a display name and avatar we pick for you. Your browser holds the key to it in the sign-in cookie.
- The games you play: mode, settings, answers, times, scores, and the resulting statistics and leaderboard positions.
- While a page is open, a note every twenty seconds that you are here and whether you are in a lobby (with its room code) or a game. It is one record, overwritten each time. Friends see from it whether you are online, a public room you host stays listed on Join only while you are here, and we count how many players are online.
- A one-way, salted hash of your internet address, used only to count free games per connection so that one person cannot take an unlimited number by making new guest identities, and to limit how many contact messages one connection can send.
That last one is worth being plain about. For this count we do not store your IP address. We combine it with a secret held on the server and store only the result, which cannot be turned back into an address without that secret. The free-game count is kept for seven days and then deleted; a contact message keeps its hash for as long as the message is kept.
What we collect when you have an account
- Your email address, and a password we store only as a hash.
- Your display name, username, avatar, chosen languages and interests.
- Everything listed above for guests, kept against your account instead.
- If you sign in with Google, the account identifier Google gives us and your email address. We do not receive your Google password.
Your sign-in sessions
Each time a device signs in, as a guest too, our sign-in service records the IP address and the browser it signed in from, alongside the session. That is how a stolen session can be spotted and how every device can be signed out at once. It is kept until you log out on that device or the account is deleted.
Why we are allowed to use it
- To give you the game you asked to play — your guest or account identity, games, scores, statistics, leaderboards, rooms, chat, friends and blocks, and Premium once you pay — because it is needed to provide the service to you (contract, GDPR Art. 6(1)(b)).
- To stop free games being taken without limit, keep the service and its sign-in secure, deal with reports and keep backups, because we have a legitimate interest in it, which we weigh with extra care for players under 18 (Art. 6(1)(f)).
- The sign-in cookie needs no consent, because the game cannot work without it.
Nothing we do today relies on your consent. If we ever add something that does, such as optional emails, we will ask for it separately, and you can withdraw it at any time.
Messages you send us
When you use the contact form we store your name, the email address you give, the topic, your message and the interface language you wrote from, together with your account if you were signed in and the salted connection hash described above, so that one connection cannot flood the inbox. We use them only to answer you and to deal with what you raised. We delete a message a year after it was answered or closed, or 90 days after it was marked as spam.
Chat, friends and reports
Messages you send in a match are stored so the other players can read them, and are deleted after thirty days. Moderators can read a player's recent match chat, and do so only to deal with a report.
Friend requests, blocks and reports are stored, including who made them. A block is enforced in both directions.
Paying
Payments are handled by Paddle, who are the seller of record. Your card details go to Paddle and never reach us. We receive from them a customer identifier, what you bought, and whether the subscription is active, so we know to unlock Premium. Paddle's own privacy policy governs what they do with what you give them.
YouTube
View Clash uses the YouTube API Services to fetch public information about videos — titles, thumbnails, channel names, view counts, likes and upload dates. This is information about videos, not about you. The video and channel pictures you see are fetched by our own server and passed on to you, so we send YouTube nothing that identifies you.
Google's Privacy Policy is at https://policies.google.com/privacy. You can review and revoke the access third-party applications have to your Google data at https://myaccount.google.com/permissions.
Cookies
We store five kinds of thing on your device, all set by View Clash itself: the cookie that keeps you signed in, as a guest or with an account; a cookie that remembers you unticked 'Remember me', so that your sign-in ends when the browser closes; cookies that make the sign-in links we email you safe to use; a cookie that remembers the interface language you picked; and your sound setting, kept in your browser's local storage. Each is either strictly necessary for the game or remembers a choice you made, so none needs your consent and there is no cookie banner. If you only read the site, nothing is stored at all. The Cookie Policy, linked at the foot of every page, lists each one and how long it lasts.
The sign-in cookie lasts 400 days and is renewed while you use the site, so it lasts until you log out or stay away that long. It carries your account's identifier, the interface language you picked and, for an account, your email address. View Clash's own pages can read it; other websites cannot. Logging out removes it from that device. A guest has no log-out: clearing this site's cookies loses the guest from that browser.
We do not use advertising cookies, and we do not embed third-party analytics. What we measure, we measure ourselves, in our own database.
Who else sees it
- Hostinger International Limited, our hosting provider, a company registered in Cyprus, on whose machine the servers run. It keeps its own weekly backups of the whole server, two at a time, so for up to fourteen days.
- GitHub, Inc., in the United States, which holds our nightly database backups for five days. A backup contains everything in the database, including your account and game records. GitHub is certified under the EU-U.S. Data Privacy Framework and its UK Extension, and otherwise relies on the European Commission's standard contractual clauses for data it receives from the European Union and the United Kingdom.
- Paddle, for payments, as described above. When you open the Premium page signed in with an account, your browser loads Paddle's script, which gives Paddle's servers your IP address before you press Subscribe.
We do not sell your data, and we do not share it for advertising.
How long we keep it
- Account and game records: while your account exists.
- Guest accounts: deleted, with their games, after 180 days in which nobody used them — no sign-in, no page open, no game started. A guest whose browser has lost its cookie goes the same way.
- Sign-in sessions, with the IP address and browser they signed in from: until you log out on that device or the account is deleted.
- Match chat: thirty days.
- Messages sent through the contact form: a year after they were answered or closed; 90 days if marked as spam.
- Connection hashes used for free-play limits: seven days.
- Event log (games started and finished, answers, free games used, limits reached): 180 days.
- Error reports (which page or request failed and how, with nothing that identifies you): 30 days after the error last happened.
- Player reports: a year after they were resolved. Reports about a question: a year after they were made. Moderation records otherwise stay while the accounts involved exist.
- Video statistics: refreshed or deleted within thirty days, as YouTube requires.
- Backups: five days for our nightly copies of the database; up to fourteen days for our host's weekly copies of the whole server.
Your rights
If you are in the European Union or the United Kingdom you have the right to see the data we hold about you, to correct it, to have it deleted, to object to how we use it, and to take it elsewhere. Write to us through the contact form at viewclash.com/contact and we will answer within a month.
Deleting your account deletes your profile, your games, your chat and your sign-in sessions. Event-log entries stay for their 180 days without anything that names you. Data already written to a backup disappears when that backup expires, within fourteen days.
You can also complain to the data protection authority where you live.
Children
View Clash is not meant for anyone under 16, as a guest or with an account; the Age Policy explains how we ask and what we do. If we learn that a player is under 16, we suspend the account at once and delete its data within seven days. Players under 18 get what every player gets here: no advertising, no marketing profiles, and nothing sold or shared for marketing. A parent or guardian can ask us to close a child's account by writing to us through the contact form at viewclash.com/contact.
Changes
The date at the top says when this policy last changed. If a change matters, we will say so in the app rather than only here.