VOLLEYBALL BOSS

Privacy policy

Volleyball Boss (the Android app and this website) · version 2026-11-20

In short. You sign in with your Google account or an e-mail address and password, so we know your e-mail address and, with Google sign-in, your Google profile name. Other players only see your manager name, your club's name and crest, and your results in the game. The game has optional rewarded ads from Google AdMob: their SDK collects technical data and an advertising identifier on Google's terms, and we ask for your consent to personalised ads in a Google message — in Europe you can say no there (details). We do not sell your account data or track you outside the game. You can delete your account in the app or by e-mail (how to do it).

If you buy something in the game's shop, Google Play handles the payment and RevenueCat passes us the purchase confirmation — details in section 13.

If you agree, we send you push notifications when your club's match is over — without the result — through Google Firebase Cloud Messaging. You can turn them off at any time in Profile or in your phone's settings (section 14).

If you agree to it in Google's message, the app sends events from the game (for example screens opened, the steps of creating an account and a club, rewarded-ad offers, the course of purchases) and the data the Firebase SDK collects by itself to Google Analytics for Firebase — without your e-mail, names or account identifier — so that we can develop the game and measure how well our ads work in Google Ads. With the same consent we also store on our server, with your account, where you got the game from (for example a search in Google Play, our ad or a post). Without consent it sends nothing (section 15).

If you create an account with an e-mail address and password, we store the address and a hash of the password, never the password itself. Resend, from the USA, sends the codes in our e-mails, and we check passwords against the Have I Been Pwned breach database without revealing them. Two-step verification is optional — details in section 16.

The Polish version of this policy is the binding one; this is a translation.

1. Controller

The controller of your personal data is Piotr Świst AI Solutions (NIP 8252216904, REGON 545373182), address: Ks. Kard. Stefana Wyszyńskiego 42/18, 21-400 Łuków, “we” below. For anything about your personal data, write to piotr@swistai.com.

2. What data we process

Account

  • When you sign in with Google, Google gives us your e-mail address, profile name (first and last name), profile picture address and Google account ID. We never learn your Google password.
  • With an e-mail account you give an e-mail address and a password. We store the address and a hash of the password, never the password itself. We also store the account language, which we use for e-mails, and the time the address was confirmed.
  • If you turn on two-step verification, we store a TOTP secret assigned to your account (section 16).
  • We give you an internal account ID.

Game data

  • Manager name, club name and crest, the country you chose.
  • Your decisions in the game: lineups, tactics, training, transfers, ticket prices and other club settings.
  • When you were last active in the app — the game releases the club of a manager who has not opened it for two whole seasons (longer if they watched rewarded ads or bought something — see the terms, section 6).
  • Tutorial progress and in-game messages.

Rewarded ads

  • When you start a rewarded ad, our server stores a one-time token and, once Google confirms the ad was watched, the ad transaction ID, the type of reward (euro for your club or credits), the amount, the ad unit, the time and your internal account ID.
  • The data the ads SDK sends to Google is collected by Google, not by us — see section 5.

Consents

  • Your acceptance of the terms of service and this privacy policy (document version and time) and your confirmation that you are at least 16 years old.
  • Your choice in Google's ads message (consent or no consent), the time, and the technical record of the choice from that message. You can change it at any time (section 5).
  • Your choice about push notifications (consent or no consent) and the time (section 14).
  • Your choice in Google's message about ads also turns app analytics on or off (section 15).

Technical data

  • Game server logs: IP address, time and type of request, response code and app identifier. We use them for security (rate limits, abuse detection) and to fix bugs.
  • On your device the app stores your sign-in session, settings (theme, language) and a copy of recently loaded data so it works offline. This data does not leave your device.
  • When you write to us: your e-mail address and the message — we keep them until the matter is settled.
  • This website uses no cookies or analytics. The website host logs visitors' IP addresses.
  • With your consent to analytics: where you got the app from (the install source from Google Play, section 15).

We ourselves do not collect your location, contacts, photos or files (Google's ads SDK processes the IP address, from which an approximate location can be estimated — section 5). We never see your card number or other payment details — Google handles the payment (section 13). We send push notifications only with your consent — we then also keep your device's notification token (section 14). App analytics also runs only with your consent (section 15).

3. Purposes and legal bases

PurposeDataLegal basis (GDPR)
Creating and running your account, playing the gameaccount, game dataArt. 6(1)(b) — performance of a contract (terms of service)
Showing your club and results to other playersmanager name, club name and crest, resultsArt. 6(1)(b)
Granting ad rewards, the daily limit, protection against abuse and invalid ad trafficaccount ID, token, transaction ID, type and amount of the reward, ad unit, timeArt. 6(1)(b) (the in-game reward) and (f) (abuse protection)
Showing rewarded ads from Google: displaying and measuring ads, frequency capping, fraud prevention and, with consent, personalisationdata collected by the ads SDK (section 5)Consent (Art. 6(1)(a)) given in Google's message where the law requires it; Google processes the data as a separate controller (section 5)
Push notifications when your club's match is overdevice notification token, account and club ID, account language, opponent's name, match IDArt. 6(1)(a) — consent (section 14)
Developing the game (which screens and features players use, where they give up) and measuring how well our ads for the game work in Google Adsevents from the app and data added by Google Analytics for Firebase (section 15)Art. 6(1)(a) — consent given in Google's message (section 15)
Assessing which channels (our campaigns, posts, the game's website, Google Play) bring players who really playinstall source from Google Play (section 15)Art. 6(1)(a) — consent given in Google's message (section 15)
Signing in with e-mail and password, confirming the address and resetting the password with an e-mailed codee-mail address, password hash, account language, content of the e-mail with the codeArt. 6(1)(b) — performance of a contract (terms of service)
Protecting accounts: rejecting breached passwords, a limit of attempts per address, two-step verificationfirst 5 characters of the password hash, hash of the e-mail address, TOTP secretArt. 6(1)(f) — legitimate interest
Security, abuse prevention, backups, fixing bugstechnical data, accountArt. 6(1)(f) — legitimate interest
Proving that you gave your consents (including for ads) and confirmed your ageconsent historyArt. 6(1)(c) and (f)
Answering messages and data requestse-mail, message contentArt. 6(1)(c) and (f)

Providing data is voluntary, but you cannot play without an account (Google, or e-mail and password) and your acceptance of the terms of service and this policy. Consent to ads is voluntary and not a condition of playing, and you start rewarded ads yourself. Consent to push notifications is voluntary too — without it you play just the same. The same goes for consent to app analytics.

4. Who has access to the data

  • Other players — see your manager name, club name and crest, lineup, results and statistics. They never see your e-mail or Google profile data.
  • Server provider — the game server (database and backups) is hosted by the VPS provider Mikrus (mikr.us) in a data centre in the European Union.
  • Cloudflare, Inc. — relays connections to the game server (encryption, protection against attacks).
  • Netlify, Inc. — hosts this website.
  • OVHcloud — handles our e-mail when you write to us (servers in the European Union).
  • Plus Five Five, Inc. (Resend, USA) — sends the e-mails with codes for confirming the address and resetting the password, as a processor acting on our behalf (section 16).
  • Have I Been Pwned — lets us check whether a password appeared in known breaches. It receives from our server only the first 5 characters of the password hash; it does not receive the password, the e-mail address or your IP address (section 16).
  • Google (sign-in and Google Play) — provides Google sign-in and distributes the app on Google Play as a separate controller, under the Google Privacy Policy.
  • Google (AdMob) — shows rewarded ads and confirms to us that they were watched. It processes the data collected by the ads SDK as a separate controller (section 5).
  • Google (Firebase Cloud Messaging) — delivers push notifications to your device, as a processor acting on our behalf (section 14).
  • Google (Google Analytics for Firebase, Google Ads) — with your consent measures events in the app and shows us how well our ad campaigns work, as a processor acting on our behalf (section 15).
  • Public authorities — only where the law requires it.

Our other service providers process data on our behalf and only as far as the game needs. We do not sell your account data or pass it to advertisers; the only data that reaches Google in connection with ads is described in section 5.

5. Ads (Google AdMob)

In the game you can choose to watch a rewarded ad: in return you get euro for your club or credits in the game. These are the only ads in the game today and you start them yourself. Ads are served by Google AdMob through the Google Mobile Ads SDK. The game is for people aged 16 or over, and in the SDK we limit ad content to what is suitable for teenagers. If we add other ad formats, we will update this policy first.

What data the SDK collects

According to Google (data disclosure for the Google Mobile Ads SDK), the SDK automatically collects and shares with Google:

  • the device's IP address — Google can use it to estimate the approximate location;
  • product interactions: app launches, taps and video views of ads;
  • diagnostic information about the app and the SDK (for example launch time, hangs, energy use);
  • identifiers: the Android advertising ID (ad ID), the app set ID and, where applicable, other identifiers tied to accounts signed in on the device.

Data from the SDK is encrypted in transit. From us, Google additionally receives only a one-time random reward token (no e-mail, profile name or account ID) and sends it back to us in the confirmation that the ad was watched; only our server knows whose token it is.

Why, and who is responsible

Google uses this data to show and measure ads, to limit how often they are shown, to prevent fraud and abuse, and for analytics. Matching ads to your interests (personalisation) requires consent.

Google is a separate controller of the data it collects through the SDK and processes it under its own Privacy Policy, the rules described in “How Google uses information from sites or apps that use our services” and the controller-to-controller data protection terms for Google's ad products. We are responsible for the decision to show ads in the game, for asking you for consent (through Google's message) and for the reward data in section 2.

Consent

In the European Economic Area, the United Kingdom and Switzerland the app shows a Google message (Google User Messaging Platform) with the choice: consent, manage options or no consent. In some US states it shows a message about opting out of the sale or sharing of personal information instead. Elsewhere there is no message. We start the ads SDK only when, according to that message and the law, ads may be requested.

  • Consent — ads may be personalised, and Google may use the advertising identifier and the device's storage. Basis: Art. 6(1)(a) GDPR and the rules on the confidentiality of electronic communications, in line with Google's EU user consent policy.
  • No consent — does not block the game and changes nothing except the ads: Google then does not personalise ads. Depending on your choice, ads may be shown in a limited mode or may be unavailable. According to Google's documentation, the limited mode disables personalisation and features that need a local identifier, and covers technical and security purposes (delivering the ad, detecting fraud) and, optionally, measuring ad performance. The basis is then legitimate interest (Art. 6(1)(f) GDPR). Non-personalised ads may still use identifiers for frequency capping and aggregated reporting.
  • Outside the areas with a message, personalisation is governed by the Google ad settings on your account and device (below).

How to change or withdraw consent

  • In the app: Profile → “Privacy options” reopens Google's message so you can change your choice at any time. The item is visible where the law requires such a choice. Withdrawing consent does not affect the lawfulness of earlier processing.
  • On your device: in Android settings (usually Settings → Privacy → Ads; names depend on the Android version and manufacturer) you can reset or delete the advertising ID. After deletion apps receive a string of zeros; ads may still appear, but they are less relevant.
  • At Google: you can turn off ad personalisation in Google's ad settings.

Ad rewards

Only our server grants a reward, after Google confirms the ad was watched (server-side verification signed with Google's keys); the app never grants it by itself. We then store the data listed in section 2 so that the reward is granted exactly once, the daily limit is enforced and abuse can be detected.

If you buy “No ads” (section 13), you get the reward at once, without an ad video: no ad is shown, and our server stores the kind and amount of the reward, the time and your internal account ID. The daily reward limit stays.

6. Transfers outside the EEA

Cloudflare, Netlify and Google may process data in the United States — Google also the data from the ads SDK and from app analytics, on servers around the world. Transfers rely on the European Commission's adequacy decision for the EU–US Data Privacy Framework (Google LLC is DPF-certified) and, where it does not apply, on standard contractual clauses approved by the Commission. Resend stores data in the United States; section 16 describes the basis for that transfer.

7. How long we keep data

  • Account and game data — as long as you have an account.
  • After you delete your account — you can change your mind for 7 days. Then your club returns to the pool of bot-run clubs and we delete your e-mail, password hash, two-step verification secret, Google profile data, manager name, sessions, devices, account messages and unused reward tokens. An anonymous account ID that cannot be linked to you remains.
  • Ad reward records (transaction ID, type and amount of the reward, time) — stay with the anonymous account ID, like the game's ledgers, so that rewards cannot be granted twice.
  • Purchase records from the game's shop stay for as long as the law requires — see section 13.
  • Game world history (match results, tables, transfers) remains, but it belongs to the club, not to you.
  • Consent history (including ad choices) — stays with the anonymous ID so that we can show consents were collected properly.
  • Database backups — are encrypted and rotated; the oldest is up to 6 months old. Deleted data disappears from backups after that time at the latest.
  • Server logs — are overwritten in cycles and are not used for profiling.
  • Data collected by the ads SDK — kept by Google under its own rules (Google Privacy Policy).
  • App analytics data — kept by Google for the period set in Google Analytics, no longer than 14 months (section 15).
  • Install source — as long as you have an account and your consent to analytics applies; after the account is deleted, only the name of the channel and campaign remains with the anonymous identifier.
  • Push notification token — as long as notifications are on. We delete it when you turn them off, when you sign out, when Google reports it as invalid (for example after you uninstall the app) or when you delete your account.
  • Codes from e-mails — are single-use and stop working after 15 minutes.
  • E-mails at Resend — according to Resend, e-mail content, delivery data and logs are kept there for 30 days, and backups for 7 days (section 16).

8. Your rights

You have the right to access your data and get a copy, to rectification (you can also change your manager name in the game), erasure, restriction of processing, data portability, and to object to processing based on legitimate interest. Where we process data based on consent, you can withdraw it at any time — this does not affect the lawfulness of earlier processing. You can withdraw consent to ads and to app analytics in Profile → “Privacy options” (section 5, section 15), and consent to push notifications in Profile → Account → “Notifications” or in your phone's settings (section 14).

Send requests to piotr@swistai.com from your account's e-mail address. We will reply within one month. Google processes the data collected by the ads SDK as a separate controller, so you can also exercise your rights over that data directly with Google (Google Privacy Policy). You can also lodge a complaint with the Polish supervisory authority, the President of the Personal Data Protection Office (ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl), or with the authority in your country.

9. Age

The game, including its ads, is for people aged 16 or over. We do not knowingly collect data from younger people — if we learn that an account belongs to someone under 16, we will delete it.

10. Security

Connections of the app and this website are encrypted (HTTPS). Each player can only access their own private data, and only the people who maintain the game can access the server and the database. Backups are encrypted. We store passwords only as hashes (bcrypt). You can also turn on two-step verification (section 16).

11. Automated decisions

Match results, bot decisions and game events are drawn and calculated automatically under the rules of the game. We do not make automated decisions about you that have legal effects, and we do not profile you for marketing. If you consent to personalised ads, Google matches the ads (section 5).

12. Changes to this policy

We will announce a new version of this policy in the app — the next time you open it, the game will ask you to accept it. Each version is dated at the top of this page.

13. In-app purchases (Google Play and RevenueCat)

This section covers purchases in the game's shop: credit packs and the one-time “No ads” purchase. It adds to the other sections of this policy; where one of them says something different about purchases, this section prevails.

Who does what

  • Google (Google Play) takes and settles the payment. You give your card or other payment details to Google, not to us. Google processes them as a separate controller, under the Google Privacy Policy and the Google Play terms. We only receive confirmation of the purchase, without a card number.
  • RevenueCat, Inc. (USA) provides us with the in-app purchase service. It receives information about a purchase from the app and from Google Play and passes us the confirmation on which we add the purchase to your account. It processes data on our behalf, as a processor, under RevenueCat's data processing addendum (DPA).

What data we process for purchases

  • Your game account ID — a random identifier we give you when you create the account. The app passes it to RevenueCat as the user ID. We do not pass RevenueCat your e-mail address, manager name or club name.
  • Purchase data: the product (a credit pack or “No ads”), the Google Play transaction number and purchase token, the time of purchase, price and currency, the country of purchase (RevenueCat works it out itself from its data about where the customer last used the app), whether the purchase is a test one, and its status: delivered, on hold or refunded.
  • Technical data that the software development kit (SDK) in the app sends to RevenueCat: device type, operating system and the time the app was last used. Like any server, RevenueCat also sees the IP address of the connection. The app does not pass RevenueCat your device's advertising ID.
  • On our side: the order saved just before payment (the pack, the time), the purchase, the credits ledger on your account, the entry in the club ledger, and the full content of the purchase and refund notifications we receive from RevenueCat.
  • Your consent to immediate delivery of the purchase and your acknowledgement that you lose the right to withdraw from the contract; you tick it in the app before paying (version and time).

Purposes and legal bases

PurposeDataLegal basis (GDPR)
Delivering the purchase, keeping the credits wallet and the club ledger, handling complaintsaccount ID, purchase dataArt. 6(1)(b) — performance of a contract (terms of service)
Tax and accounting, keeping documentspurchase dataArt. 6(1)(c) — legal obligations (tax and accounting law)
Refunds and their effect in the game, abuse prevention, establishing and defending legal claimspurchase data, ledgers, notifications from RevenueCatArt. 6(1)(f) — legitimate interest
Proving your consent to immediate delivery, and confirming the purchaserecord of the consentArt. 6(1)(c) and (f)

You never have to buy anything. Without this data, however, a purchase cannot be made.

Who receives the data and transfers outside the EEA

  • RevenueCat, Inc. (Brandon, Florida, USA) — a processor. It stores data on Amazon Web Services servers in the United States and uses further sub-processors listed in its data processing addendum (revenuecat.com/dpa).
  • Transfers to the USA rely on the standard contractual clauses approved by the European Commission (Implementing Decision (EU) 2021/914), which RevenueCat incorporates into its data processing addendum (the controller-to-processor module). The addendum is publicly available at the same address.
  • Google — as in sections 4 and 6; for payments they act as separate controllers.

How long we keep purchase data

  • With us. We record purchases, orders and the notifications from RevenueCat, and we keep the credits and club ledgers by adding entries only, so entries do not disappear while you use the game. We keep this data for the period that tax and accounting law require: as a rule 5 years, counted from the end of the year they relate to. If a dispute or proceeding in which the data is needed is under way, we keep it until it ends. After that we delete it.
  • After you delete your account. The purchase records stay under the anonymous account ID — we remove the e-mail address, Google profile data and manager name from it (section 7). These records still contain the Google Play transaction number and purchase data that Google can link to you, so we keep them only as long as described above. Unused credits are lost and the balance is no longer accessible.
  • At RevenueCat. RevenueCat keeps data until we ask it to delete it. After you delete your game account we ask RevenueCat to delete the customer data for your ID. RevenueCat may keep what it needs to meet legal obligations and resolve disputes, under its own privacy policy.

Your rights

The rights described in section 8 apply. Send requests about data held by RevenueCat to us at piotr@swistai.com — we will pass them to RevenueCat, which processes that data on our behalf.

14. Push notifications (Google Firebase Cloud Messaging)

What we send

When your club's match is over, we send a “Full time” notification with the opponent's name, inviting you to watch the match. The notification does not give away the result. We send it only if you agree — the game asks for your consent, and on Android 13 and later the system also asks for permission to show notifications. Without consent you play just the same.

What data, and who processes it

  • Notification token — a random identifier that Firebase Cloud Messaging assigns to the app on your device. We store it on our server with your account. The app contacts Firebase for this only after you have given your consent.
  • Notification content — the title and text in your account's language (with the opponent's name), the match, club and message IDs the app needs to open the match, and the address of a picture with the game's logo. We send them to Google together with the token.
  • Google delivers the notification to your device as part of the Firebase Cloud Messaging service, as a processor acting on our behalf (Firebase data processing terms). The data may be processed outside the EEA under the rules in section 6.

Legal basis and how to withdraw consent

The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time in Profile → Account → “Notifications” — we then delete the token from our server and from your device — or by turning off Volleyball Boss notifications in your phone's settings. Signing out also deletes the token. Withdrawing consent does not affect the lawfulness of notifications sent before.

How long

We keep the token as long as notifications are on (section 7); the record of your choice is kept like your other consents.

15. App analytics (Google Analytics for Firebase)

Why

We use analytics for two things. First, to develop the game: we want to know which screens and features players use most and for how long, at which step of creating an account and a club they give up, which rewarded-ad offers and shop products they choose, and which app versions they play on. Second, to assess our campaigns in Google Ads: we want to know where new players come from and what a player who really starts playing costs us, not just one who installs the app.

What data

  • Our events and properties — we record what happens in the app: screens opened and time spent on them, the steps of creating an account and a club and of the tutorial, watching matches (viewing time, skipping to the end), rewarded-ad offers shown and chosen (which offer, whether the ad was displayed), opening the shop and the course of a purchase (the product and whether the purchase succeeded, was cancelled or ended with an error), and credits spent and earned in the game (how many and on what). On top of that, a few general properties: the chosen play mode (simple or expert), the app version number, whether you have a club, the league level and whether you have ever bought anything in the shop. We do not send your e-mail, manager, club or player names, account identifier or anything you type in the game, and the app does not give you a user ID in Analytics.
  • Data the Firebase SDK collects by itself (Google's description): the app instance ID and, with consent to ads, the Android advertising ID; device model and OS version, language, approximate location (country, region, estimated from the masked IP address — Google Analytics does not store the IP address itself), app version; automatic events such as sessions and engagement time, screen views, app and OS updates, push notification opens and purchases in the game's shop (product ID, name and price — no payment details).

Install source

With the same consent the app reads once from Google Play where you got it from (the so-called Install Referrer — for example a search in Google Play, our campaign in Google Ads, a link in our post or on the game's website) and stores this on our server with your account: the campaign tags (source, channel type, campaign name and variant), the time you clicked the link and when the installation started, and whether the link contained an ad click identifier — we do not store the identifier itself. This tells us which channels bring players who really play and what that costs us. We do not pass this information to anyone. Without consent the app does not read it; if you withdraw your consent, we delete it from the server the next time you start the app.

Consent and how to withdraw it

Analytics follows the choice you make in Google's message about ads (section 5). Until you make it, the app collects and sends no analytics data. In the EEA, the United Kingdom and Switzerland it collects it only if you consent in the message to storing information on your device; Google Ads may use it to measure campaigns only if you also consent to ad performance measurement, and for ad personalisation only if you consent to personalisation (Google consent mode). Elsewhere analytics runs when, according to Google's message, ads may be shown; there you can delete the advertising ID in Android's settings (section 5).

The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it in Profile → “Privacy options” — the app stops collecting analytics data at once. Without consent you play just the same. Withdrawing consent does not affect the lawfulness of earlier processing.

Who processes the data

Google processes Analytics for Firebase data as a processor acting on our behalf (Firebase data processing terms, privacy in Firebase). We link the Analytics project to our Google Ads account so that campaigns see these events as conversions; for this Google processes the data under the Google Ads data processing terms. The Analytics project is also linked to our AdMob account (revenue from ads shown) and to Google Play (purchases in the game's shop). The data may be processed outside the EEA under the rules in section 6.

How long

Google keeps event-level and user-level data for the period set in Google Analytics (no longer than 14 months); after that only aggregated reports remain. This data does not include your account identifier, so it cannot be linked to your account.

16. E-mail account, password and two-step verification

Instead of a Google account you can sign in with an e-mail address and password. This section describes the data related to such an account and two-step verification, which is available for every account.

E-mail address and password

We store your e-mail address and a hash (bcrypt) of your password. We never store or know the password itself: it reaches the server over an encrypted connection, and the server uses it only to create or check the hash and for the check described below. You confirm the address with a code from an e-mail. Legal basis: Art. 6(1)(b) — performance of a contract (terms of service).

E-mails with codes (Resend)

  • Who sends them. We send the code for confirming the address and the password reset code through the Resend service, run by Plus Five Five, Inc. (2261 Market Street #5039, San Francisco, USA). Resend processes this data on our behalf, as a processor, under its data processing addendum (DPA), and uses sub-processors.
  • What data. The recipient's address, the subject and content of the e-mail with the code (in your account language) and delivery data. The code is single-use and valid for 15 minutes. Resend does not receive the password.
  • Transfer to the USA. Resend stores data in the United States. The transfer relies on the standard contractual clauses approved by the European Commission (Implementing Decision (EU) 2021/914), which Resend incorporates into its data processing addendum (the controller-to-processor module). Resend also states that it participates in the EU–US Data Privacy Framework.
  • How long. According to Resend, e-mail content, delivery data and logs are kept for 30 days, and backups for 7 days. Deleting your game account does not shorten these periods.

Checking passwords against a breach database (Have I Been Pwned)

We reject passwords that have appeared in known breaches. When you enter a password, our server computes its hash and sends to the Pwned Passwords service of Have I Been Pwned only the first 5 characters of that hash (the k-anonymity method). The service returns a list of hashes with the same beginning, and the server itself checks whether the full hash is on it. The password, the full hash and your e-mail address do not leave our server, and the service sees a connection from our server, not from your device. Legal basis: Art. 6(1)(f) — legitimate interest.

Limit of attempts

To make guessing passwords and codes harder, we count attempts to sign in, sign up, reset the password and enter a code separately for each e-mail address. The counter keeps a hash of the address in the server's memory for about a minute; it does not reach the disk or backups. Legal basis: Art. 6(1)(f) — legitimate interest.

Two-step verification (TOTP)

Two-step verification is optional and also works with a Google account. You turn it on and off in Profile → Account. Once it is on, you also enter a code from an authenticator app of your choice when signing in. To check these codes, we store on the server a TOTP secret assigned to your account. We delete it when you turn verification off or delete your account; it disappears from backups like other data (section 7). If you lose access to the app, write to piotr@swistai.com from your account's address: after checking that the message came from that address, we will turn verification off. Legal basis: Art. 6(1)(f) — legitimate interest.

17. Reward for joining Discord

Linking a Discord account to your game account is optional: in the app you can join the game's Discord server and get a one-off credit reward for it. Once you link, we store your Discord user ID and username with your account. We use them to grant the reward once and to prevent abuse: one Discord account can be linked to only one game account. The legal basis is your consent, which you give by linking the accounts (Art. 6(1)(a) GDPR). We keep the data for as long as you have an account and anonymise it together with the account: when the account is deleted, we delete the Discord username, and the Discord ID stays only with the anonymous account ID so that the same Discord account cannot get the reward a second time (Art. 6(1)(f) GDPR — preventing abuse). Discord sign-in and the Discord server are run by Discord Inc. (USA) as a separate controller, under the Discord Privacy Policy.