Privacy

Last updated: 15 October 2026

This policy explains what personal data jocuriclasice.ro collects, why, who receives it, how long it is kept, and what you can do about it. The short version comes first; each line names the section below that gives the detail. If anything is unclear, write to us and ask.

In short

• Who we are: discusdev srl, the operator of jocuriclasice.ro, is the controller of your personal data. Write to contact@jocuriclasice.ro about anything in this policy ("Who is responsible").
• What we collect: what you give us (a display name, and for an account an email address), what playing produces (matches, progression, rankings, messages), what keeps the service running and safe (sign-in sessions, server logs, error reports) and, only if you agree, product analytics and where you play from ("What we collect").
• Why: to run the game and your account (contract); to keep the service safe, fix errors and publish rankings (legitimate interests); analytics and personalised advertising (consent); records the law requires (legal obligation) ("Why we use it, and on what legal basis").
• Advertising: asked only in Google's own consent form, never on our card; personalised only if you agree there; if you refuse, you may still be shown limited ads, which you can object to ("Advertising").
• Who receives it: other players; anyone, for the public boards; our service providers, acting for us; Google, for advertising. Some are in the United States, under the safeguards described ("Who else sees it").
• How long: as the schedule says; private and club messages, for example, 90 days ("How long we keep it").
• Your rights: access, rectification, erasure, restriction, portability, objection and withdrawal of consent, some of them from the app and all of them by writing to us; no decision with legal or similarly significant effect is made about you by automated means alone ("Your rights").
• Complaints: to the Romanian supervisory authority, ANSPDCP, or to the authority where you live or work ("Your rights").
• Age: the app is for people aged 16 or older ("Children").

Who is responsible

jocuriclasice.ro is a free app for traditional card and board games, operated by discusdev srl, a limited liability company incorporated under the laws of Romania, tax identification code (CUI) RO43192872, registered with the Trade Register under no. J2020001015016, with a subscribed and paid-up share capital of 200 RON and its registered office at Str. Orhideelor no. 29, Alba Iulia, Alba County, Romania ("we", "us" or "the operator"). Under the EU General Data Protection Regulation (GDPR), discusdev srl is the data controller for the personal data described below.

Contact for any privacy question or request: by email at contact@jocuriclasice.ro, or by telephone on +40745814257. Requests to exercise your rights are best made in writing to that email address, so that there is a record of what was asked and when. We have not appointed a data protection officer, as the law does not require one for processing of this nature and scale.

What we collect

• Your profile. A display name of your choosing, shown to other players (so do not put personal information in it), and when you changed it (the timestamps only); a profile picture, if you upload one, stored re-encoded without the location or camera data the original may carry; for a guest, the hash of a random key our server creates and your device keeps, never the key itself.
• Your account, if you create one. Your email address and whether it has been verified; if you sign up with an email address, your password, stored only as a hash; which sign-in providers you linked (Google, Apple or Facebook), with the tokens each hands us to keep the link working (deleted when you unlink it) and the web address of the picture it prefills your profile with, which you can clear; and, if you enable two-factor authentication, its secret and hashed backup codes. To limit how often one address is sent a confirmation link, we keep a one-way hash of it in memory for at most a day.
• Match data. Game, variant and the table's settings, seats, the score and placing of each seat, a few counted facts about how each seat played that the achievements read, the result of each round and what it earned (points, seeds, experience and the rating before and after), and when the match started and finished. The moves themselves are held in the room's memory only while the match is being played and are not stored afterwards.
• Progression and social play. Your levels, experience and achievements, your seed balance and the ledger that explains it, daily-hand results, Arena seats, tournaments with your standings and pairings; the groups (mese) and club you belong to, your role and since when, a club's name, tag and crest; friend requests and friendships, the accounts you block and the players you mute; invitations to rooms, groups and clubs and what became of each; the games you starred, the notifications you dismissed, and when you were last seen active.
• The shop and gifts, with an account. The frames you bought in the app's shop, the seeds each cost and when, and which frame you chose to wear, if any; the gifts you sent and received: who sent each, who received it, the item, the seeds it cost its sender, when it was sent and when it was first shown to the player who received it.
• Messages. Direct messages you send, including the "Team" thread (what we write to you about your account and your answers), with sender and time. Club chat. The lines you write to your club, with sender and time, and the tables you share into it; every member of the club can read them. Table chat, which is kept only while the room lives: short messages to the other people at an online table, checked by our server against a word list that masks what it finds, and relayed, with no row in our database and nothing in a log; emoji reactions are relayed and not kept.
• Reports. If you report a player, the reason you picked, anything you wrote and a short quoted excerpt of what you report; if you are reported, the same record naming you, including how it was resolved. A notice of unlawful content also records your statement that it is made in good faith and, if you send it as a guest, the name and email address you give (not required for a notice about child sexual abuse material); that address is used to acknowledge the notice and to tell you the decision.
• Security and operation. For an account, the IP address and user agent of each signed-in session, with its start and expiry (a guest profile's session has neither, only its start and expiry). Server logs: a shortened address (the last part is dropped, so it points at a network and not at you), the page asked for, your user agent, the time and the server's answer; sign-in cookies, authorisation headers and one-time links are never written to them. Support requests: the email address you give us, your message, your user agent and a salted hash of your IP address, so the form cannot be used to send mail in bulk; the IP address itself is never stored. The form ordinarily also delivers your message to our support mailbox as an email. Mail you write straight to our contact address reaches the same mailbox, with your address and whatever you write.
• Error diagnostics. When something crashes, our error monitoring service (Sentry) receives the error (its type, its message with secrets removed, and where in the app's own code it happened), its level, a timestamp, the app's release and environment, technical identifiers of the report and of the app build, which name nobody, the address of the page you were on, without any secret it may contain and without anything after a question mark or a hash sign, and your browser identifier (user agent), from which the provider works out the browser and the operating system, plus the versions of the interface framework and of the reporting software. That is the whole report. No IP address is kept with a report: the address your device connects from is seen in transit, as any server sees it, and is not stored. It carries no account, no display name, no cookies, no other header, no message of yours, nothing you typed, and no trail of what you did before the crash (no screens visited, no controls pressed, no requests made, nothing written to the browser console). The reporter inside the app's screens stores nothing on your device. In the Android and iOS apps the same service can also report a crash outside the app's screens and count sessions that ended without one; that native part runs only if you tick the "Help improve the app with usage statistics" box, on the card the app shows the first time it runs or in Privacy options ("Analytics" below), from the next time the app starts, and writes a random installation identifier on the device (naming no account and no person, and listed in the cookie policy) and sends a short note when the app opens and when it goes to the background: app version, device and system type, and whether the session crashed.
• Product analytics, only if you consent. A small set of events (such as the app opening, analytics being switched on, a game starting or a match finishing, an invite shared or opened, a room joined, a rewarded ad watched), each carrying at most the game, its variant, the number of seats, the match's length, whether it was online and one word for how it went; never a room code, message content, display names, another player's identifier or the page you were on. If you are signed in, they are linked to your account identifier. The provider's own code adds your browser and operating system, a session identifier and an approximate location derived from your IP address. Decline, and none of this is collected or even requested.
• Where you play from, only if you choose. A Romanian county or a country, never an address or a coordinate, picked from a list or worked out by your own device from the map of Romania the app carries. It is saved, and shown next to your name on the rankings and the map, only once you tick a separate box agreeing to it; your device's location prompt is not that agreement. Only the county is sent to us: your coordinates are never sent to us or looked up by us anywhere (your operating system's location service may consult its maker's servers, under that maker's policy). We also note it against each month, so a closed month's ranking keeps the places people played from at the time. "Stop sharing" in your profile removes it.
• A record of your acceptance and of your consent choices. If you have an account, a record of your acceptance of the terms and of each choice about Analytics, advertising (your answer in Google's consent form, as the app reads it) and showing where you play from: the choice, your answer, when, and the version of these documents; for the terms, Analytics and advertising also where (the card the app shows the first time it runs, Privacy options or Google's form), the platform and the card's version. For a guest profile we keep only the entries about where you play from. Nothing reads this record to decide what the app does: it is our evidence of your choices.
• Settings stored only on your device. Theme, the other interface options you choose and your consent choices live in your browser's local storage and are not sent to us, except that switching Analytics on is itself one of the analytics events listed above, and that while you are signed in to an account your consent choices are also sent to us for the record above. Some entries are handed to us when used: your display name and the games you starred are kept with your account when you have one; the reconnect ticket for an online room is presented to our server to take your seat back; and the interface language you chose is sent with the requests the app makes to our sign-in service, and with a withdrawal, so that a mail we send you is written in it. The language is not stored with your account: it is kept only beside a withdrawal acknowledgement waiting to be sent, and no longer than the address that mail goes to. The cookie policy lists every entry.

We do not collect payment details, precise location, biometric data or identity documents, and we never read your device's address book: the friends, blocks and mutes described above are made inside the app. We do not sell personal data, we do not use it for profiling for advertising or marketing purposes, other than counting how much you play to decide how many ads you are shown ("Advertising"), and we make no decision based solely on automated processing that produces legal effects concerning you or similarly significantly affects you. Automated evaluation that is part of the game (a skill rating, a level, an automated opponent's standard, the server's check that each move is legal) is only that. No account is restricted, suspended or closed automatically for its conduct: that decision is taken by a person, and can be contested, as the terms explain.

You are not obliged to give us any of this: offline play stores nothing on our side but the count of practice-table rounds described under "Advertising". An online seat needs a display name and a device key, and an account needs an email address; without them that part of the service cannot work, and nothing else follows from declining.

Why we use it, and on what legal basis

• Running the game, your account, online matches, the shop and gifts: performance of a contract with you, Article 6(1)(b) GDPR.
• Keeping the service usable and safe (anti-cheat, rate limits, server logs, abuse reports, bans): our legitimate interests, Article 6(1)(f).
• Diagnosing crashes and fixing bugs: our legitimate interests, Article 6(1)(f); the native crash reporting in the Android and iOS apps, which stores an identifier on your device, only with your consent to Analytics, Article 6(1)(a).
• Publishing leaderboards, so that a standing is public, comparable and worth playing for: our legitimate interests, Article 6(1)(f).
• Answering your support requests: Article 6(1)(b) and 6(1)(f).
• Optional storage and product analytics: your consent, Article 6(1)(a), which you may withdraw at any time. Analytics is asked by an optional box on the card the app shows the first time it runs, unticked until you tick it, and can be changed at any time in Privacy options.
• Advertising: personalised advertising, and the storing and reading of information on your device to serve and choose ads, on your consent, Article 6(1)(a), asked only in Google's own consent form, never on our own card; limited ads after a refusal, and deciding how many ads you are shown, on our legitimate interests, Article 6(1)(f). All of it is explained under "Advertising" below.
• Showing where you play from on the rankings and the map: your consent, Article 6(1)(a), given by ticking the separate box in the form where you set it; "Stop sharing" in your profile withdraws it with immediate effect.
• Keeping the record of your acceptance of the terms and of your consent choices, so that we can demonstrate them: legal obligation, Article 6(1)(c), read with Article 7(1), which requires us to be able to demonstrate that you consented.
• Keeping records we are legally required to keep, handling notices of unlawful content, sending the acknowledgement of a withdrawal from the contract, establishing, exercising or defending legal claims, and answering lawful requests from authorities: legal obligation, Article 6(1)(c), and our legitimate interests, Article 6(1)(f).

Advertising

The app may show three advertising formats: banners, on the web and in the Android and iOS apps, in the break after a hand (between rounds and at the end of a match), in the waiting room before a game and on the end-of-game screen, and on the web also beside the table during a hand, on a wide screen; full-screen ads, in the Android and iOS apps only, at the end of some games (before the final score, or when you leave a table after finishing a round) and after every third round of a game, but never during a hand, never offline, never more than one every 3 minutes and never more than seven in an hour; and ads you choose to watch, on the web and in the apps: for an experience boost, to play today's game again, or for an extra daily seed reward. Each advertising format can be switched off at any given time, and Privacy options in the app shows which of them are active at the moment. The advertising provider is Google: AdMob in the apps, Google Ad Manager on the web.

How many ads. How many ads you are shown in a game, and in which formats, depends on how long you have had your account and on how many rounds of that game you played in the last 7 days, online and at practice tables: a new or occasional player of a game is shown no banner and no full-screen ad in it, and more formats are added as you play it more. Each day, the first match you play of each game is free of banners and full-screen ads. The ads you choose to watch stay available whatever you played. The rounds you finish at practice tables are sent to our server while you are connected, and are counted for this alone. We work this out each time the app opens, from data we hold (when your account was created, the rounds you finished online and the practice rounds your device sent), and keep a daily record of the result (your advertising level, for each game and overall) for 90 days, to measure our advertising, and the count of practice rounds for 30 days. This rests on our legitimate interest in funding the free service with advertising while showing fewer ads to new and occasional players, Article 6(1)(f), and you may object to it at any time, on grounds relating to your particular situation, by writing to us (Article 21).

Consent. Because Google stores and reads information on your device to serve and choose ads, advertising is asked only in Google's own consent form (on the web, its consent message), never on our own card. Consent is therefore asked in two layers, one after the other: first our own card, the first time the app runs, which accepts the terms and offers the Analytics box; then Google's own consent form, which the app may show at that same first open, before any ad is requested (on the web and in the Android app it does so already). An ad is shown only when both allow it, and refusing in Google's form is as easy as accepting there: its first screen offers both. Before you have accepted the terms on the card, no request is made to Google at all. After you accept the terms, wherever Google's form is shown, the app first contacts Google: in the Android and iOS apps, through its User Messaging Platform, to ask whether a consent form is needed where you are; on the web, to load Google's consent message. Either sends Google the device's IP address and basic information about the device or browser and the app before you have answered anything; nothing to do with advertising runs before your answer. Google shows its form where its EU User Consent Policy applies (the European Economic Area, the United Kingdom and Switzerland), judged from where your device is and not from where you live; on the web, its message is shown again whenever Google needs your answer renewed. Where the form is not shown, nothing is asked and no ad is requested at all: no silence is read as consent, and nothing else, in the app or in the device's settings, switches advertising on.

Personalisation. The same form asks separately whether ads may be personalised, and they are personalised only with the consent you give there, and only in the apps: on the web every ad is requested non-personalised, whatever you answer. You may accept advertising while refusing personalisation, from the form's options (its one-tap "Consent" button accepts everything it lists). On iOS, Apple's tracking prompt comes only after Google's form has been answered and must be authorised before an ad can be personalised; denying it keeps every ad non-personalised.

Limited ads. If you refuse there, you may still be shown limited ads: they are not personalised, and Google documents them as using no advertising identifier, profile or other local identifier to choose them, count them or limit how often they are shown, though Google may still write and read cookies or local storage on your device, solely to detect fraud and invalid traffic. Requesting and showing a limited ad (which sends Google your IP address and the information about your browser or device that the request carries) rests on our legitimate interest in funding a free service with advertising, Article 6(1)(f), and you may object to it at any time, on grounds relating to your particular situation, by writing to us (Article 21).

What Google receives. In the apps, Google's Mobile Ads SDK receives your device's IP address, its advertising identifier (on Android the advertising ID or app set ID; on iOS the IDFA, only if you allow tracking in Apple's prompt), information about the device and the app, your interactions with the ads, and diagnostics; on the web, Google's tag receives your IP address, information about your browser and device, Google's cookies or local storage, and your interactions with the ads. Google uses this to serve and measure ads, to prevent fraud and, where personalisation is allowed, to choose ads for your interests, as described at policies.google.com/technologies/partner-sites.

Our role and Google's. For the collection of data by Google's advertising code while it runs in our app or on our page, and for its transmission to Google, and for that step alone, we and Google are joint controllers within the meaning of Article 26 GDPR, because we both determine its purposes and means. In essence, we decide whether the code loads at all and owe you this information; Google decides what it collects and how it is transmitted. For everything Google does with the data afterwards (serving, measuring and choosing ads, and any profile it builds) Google is independently responsible, as a separate controller, under the Google Ads Controller-Controller Data Protection Terms (privacy.google.com/businesses/controllerterms) and its privacy policy (policies.google.com/privacy); we are never joint controllers with Google for that advertising, and we build or receive no advertising profile of you (your advertising level above is never sent to Google). You may exercise your rights against either of us for the collection and transmission, and against Google for what follows.

Changing your mind. "Privacy options" on the account page re-opens Google's form (on the web, its message) where it is available, so advertising consent is withdrawn where it was given. Personalisation alone can also be switched off in the device's settings: on iOS under Settings, Privacy & Security, Tracking; on Android under Settings, Google, Ads (on some devices Settings, Privacy, Ads), where you can also delete the advertising identifier. Those settings can only withdraw personalisation, never switch it on. A changed answer applies from the next ad the app requests. Whatever you choose, the game stays fully playable.

Who else sees it

Other players see your display name, your avatar, the moves you make in a shared match and any message you choose to send. The frame you wear is shown with your avatar wherever it appears. Anyone who opens your profile sees how many seed bags and golden seed bags you have received, as they see your seed balance; the player who receives a gift also sees the display name of the player who sent it, and nobody else is shown who sent a gift.

Public boards. Some things are readable by anyone on the internet, without an account. Leaderboards are public: a board carries your display name, your profile picture if you uploaded one, your club's tag and crest if you belong to a club, your position on it and your score or rating for that game. So are the seed board and the daily-hand board, open championships (each naming its creator), a championship's standings, the tables waiting for players (titled with the host's display name), profile pictures, and, if you agreed to show it, where you play from, on the map and on the rankings ("Stop sharing" in your profile takes it off at once, closed months included). A game's leaderboard and the seed board also show your player id: a random number, public by design, which another player can use to open your public profile page, to send you a friend request, to block you or to report you, and for nothing else; it is not your account identifier and signs nobody in. If you would rather not appear, a setting in the app, "Hide me from public boards", takes you off the public boards and the map, and takes your name off the list of tables waiting for players; in a championship's standings and pairings your row stays, because it is the other entrants' result too, but without your name, and a championship you created no longer names you. Friends still see you, and you still see your own place. You can also change your display name, play offline, or object to us and we will act on it. Public player pages are marked so that search engines do not index them.

Beyond that, personal data is disclosed only to these recipients, and only as far as the purposes in this policy need.

Processors, acting on our documented instructions under Article 28 GDPR data-processing agreements:

• Hosting: Hetzner Online GmbH, Germany, in the European Union.
• Error monitoring: Sentry, run by Functional Software, Inc., United States, in its European Union data region.
• Product analytics, only if you consent: PostHog, Inc., United States, in its European Union region.
• Delivery of the emails we send you: Resend, Inc., United States, sending from its European Union region.
• Our mailbox, which holds what you write to us and the copy of a support request: Zoho Corporation B.V., the Netherlands, in the European Union.
• Our private code repository and issue tracker: GitHub, Inc., a Microsoft company, United States, which receives an excerpt of an unresolved error report copied there to be fixed (the error and where it happened, the app version, the browser, system and device type, the page or request address without its secrets, and how often and when it was seen). No account is attached to the excerpt, and your browser identifier and your IP address are left out.

Independent controllers, under their own privacy policies, which we do not control:

• Google, for advertising: an independent controller for what it does with the data its advertising products collect once that data has reached it, and joint controller with us for the collection itself, as "Advertising" above sets out.
• Google, Apple or Facebook (Meta), if you sign in with one: each handles that step and is an independent controller for what it hands us (typically your name, email address and whether the provider has verified it).

Others: professional advisers, and public authorities, courts or other third parties where the law requires it or where it is reasonably necessary to establish, exercise or defend legal claims, to enforce our terms, or to protect anyone's rights, property or safety; and a successor if the service, or the business operating it, is transferred, under the same protections as this policy.

Transfers outside the European Economic Area. Sentry, PostHog, Resend and GitHub are United States companies. Sentry and PostHog keep our data in their European Union region, but either may process personal data in the United States for support, administration or through a sub-processor. Resend sends our emails from its European Union region, but its records of them (each address, content and delivery log) are stored in the United States. GitHub keeps what it holds for us in the United States. Zoho keeps our mailbox in its European Union data centres, and staff of its group company in India may access it for technical support. Every such transfer follows Chapter V GDPR and is covered by appropriate safeguards: the European Commission's adequacy decision for the EU-US Data Privacy Framework (Article 45), where the provider is certified under it (GitHub is certified in its own name), and the Commission's standard contractual clauses (Article 46(2)(c)), supplemented where necessary by additional measures. The clauses are in each provider's data processing agreement: Sentry's at sentry.io/legal/dpa, PostHog's at posthog.com/dpa, Resend's at resend.com/legal/dpa, GitHub's in its customer terms at github.com/customer-terms, and Zoho's in the addendum we have signed with it. The certified companies are listed at dataprivacyframework.gov. Google, Apple and Meta act through their European affiliates for players in the European Union, and their own transfers are governed by their own policies. You can ask us for a copy of the safeguards that cover a given transfer, and for further information about it, by writing to the address at the top of this policy.

How long we keep it

Where an entry states a period, an automated job removes the record once it has passed. Where an entry says "indefinitely", the record is kept for as long as reasonably necessary for the purpose it serves (keeping the game's records consistent, complying with our legal obligations, resolving disputes and enforcing our agreements) and is reviewed against that criterion.

• Table chat and emoji reactions: nothing reaches our database, so this job has nothing to delete. The room keeps the last 16 chat lines in its own memory while it lives, so a player who joins or reconnects can read them, and forgets them the moment it closes; reactions are relayed and not kept at all.
• Direct messages, including the "Team" thread: 90 days from when each message was sent. That window lets you read a recent conversation, lets us moderate and investigate abuse reported in it, and keeps the service secure.
• Club chat: 90 days from when each line was written, for the same three purposes.
• Support tickets: 12 months in our database; the mailbox copy is cleared by hand on the same schedule, as a practice rather than by that job.
• Mail written straight to our contact address: kept as long as needed to answer it and resolve what it raises, then as long as the record it belongs to (three years, for example, for a request about your data or a notice of unlawful content), and then deleted.
• Sign-in sessions: deleted once the session expires. A session lasts seven days, extended while you keep using it; signing out ends it.
• Guest profiles: a guest profile that has never played an online game is deleted once it has gone 30 days without being used, and any guest profile once it has gone 12 months without being used. "Used" means the app was open, and online, with that profile. A profile under a restriction still in force is kept while the restriction lasts, so it cannot be avoided, and in any case no longer than 24 months without being used. Deleting a guest profile removes its details as deleting an account does; its results stay, anonymised.
• Room, group (masă) and club invitations: 7 days after the invitation expires. A group or club is deleted outright, club chat included, when its last member leaves.
• Matches and results: kept indefinitely, and anonymised when the account that played them is deleted: its seat then points only at the empty shell of the deleted account. Three years after the match, even that link to the deleted account is removed, so what is left (the game, its settings, the dates, the scores and the placings) names no account at all.
• Championships, their standings and pairings: kept indefinitely, as they are the other entrants' results too; when an account is deleted, its entries and pairings stay, pointing only at the empty shell of the deleted account, and a championship it created no longer names its creator.
• The seed ledger, the round-by-round record behind it and daily-hand results: 400 days; an Arena entry: 90 days.
• Notifications you dismissed: 12 months.
• Your advertising level, one record a day for each game and overall ("Advertising"): 90 days.
• The count of rounds you finished at practice tables, per game and day ("Advertising"): 30 days.
• Rate-limit ledgers and internal queues: 30 days or less, most of them a day or two; they hold an account and a clock, never what was sent.
• Anything with an expiry of its own (a data-export download, a sign-in or verification token, a rewarded XP boost): deleted once it expires.
• Error reports in Sentry: for as long as the provider's plan retains them, currently 30 days from the report.
• Excerpts of error reports copied into our issue tracker: until the error they describe is fixed, and in any case no longer than 90 days after the excerpt was copied; the issue that records the fix may stay, without the excerpt.
• Analytics events in PostHog, if you consented to them: for as long as the provider's plan retains them (currently one year), and earlier where we instruct the provider to erase them, as "Delete my account" below explains.
• Server and application logs: ordinarily no more than a few weeks, bounded by size and rotation.
• Database backups: a copy of the whole database is taken every night and kept for 14 days, and one copy a week is kept for 28 days; a small fixed number (seven) of the most recent copies is also held off the server and replaced as newer copies arrive. Backups exist only to recover from a failure: erased data stays in earlier backups until they rotate out (about four weeks at the most) and is not read back from them for any other purpose.
• Where you play from, with its monthly record: kept while the account lives and deleted with it; "Stop sharing" deletes the current answer and every past month's entry immediately.
• The record of your acceptance and consent choices (including each time you agreed to show where you play from or stopped): kept while the account or guest profile lives and deleted with it, and included in the copy of your data you can ask for.
• The record of a moderation or account action we took: kept for three years from the action (the general limitation period under Romanian law), to evidence that we acted, to comply with our legal obligations, to resolve disputes and to enforce our terms, and then deleted. It names the account acted on and survives that account's deletion, as a report does.
• Reports: the report itself, the decision and the reasons for it, the quoted excerpt included, are kept for three years from the decision on the report, for the same purposes, and then deleted; a report not yet decided is kept until it is. The excerpt is not removed on the 90-day message schedule; it goes sooner only if the account that wrote it is deleted. What the person who reported wrote, and the name and address a guest gave with a notice of unlawful content, go sooner if that person's account or guest profile is deleted.
• The record of a request about your data (for a copy of it, or to delete your account): kept for three years from our answer, as evidence that we answered, and then deleted; an open request is kept until answered. It holds the kind of request, its dates and outcome, never your data.
• Frames you bought and gifts you received: kept while the account lives and deleted with it, and included in the copy of your data you can ask for, with the gifts you sent. A gift you sent belongs to the player who received it and stays with them; if your account is deleted, it no longer names you as its sender.
• Anything not listed above (such as your email address and its verification, linked sign-in tokens, a two-factor secret, your progression, achievements, seed balance and medals, your profile picture, friends, blocks and mutes, starred games, groups and clubs, and when you were last active) is kept while the account lives and deleted with it; there is no other criterion for it.

What is stored on your device stays there until you clear the app's storage or uninstall it.

Your rights

Under the GDPR you can ask us to give you a copy of your data, correct it, erase it, restrict or object to how we use it, and receive it in a portable, machine-readable form. Where processing is based on consent, you can withdraw that consent at any time; withdrawing it does not affect what was done before.

Right to object. You may object at any time, on grounds relating to your particular situation, to any processing we base on our legitimate interests (the anti-cheat and safety measures, the server logs, the crash diagnostics, how many ads you are shown, the public leaderboards and the limited ads described above) by writing to the address at the top of this policy. We then stop unless we can demonstrate compelling legitimate grounds which override your interests, rights and freedoms, or the processing is needed for legal claims.

Two of these are self-service, in your profile:

• "Request my data": an export is made available as a time-limited download link that works only while you are signed in to that account, which needs a confirmed email address for the link to be delivered (a guest profile, or an account without one, is asked to add one first). Otherwise write to us at the address above; we may first verify that the request comes from the holder of the profile. We never email raw data files. A message somebody else sent you is their words as much as yours, and reports that other players filed about you are not included in the automatic export, because they would identify who filed them. On request, by writing to us at the address above, we give you the personal data about you that those reports contain, with the identity of whoever filed them and other people's data removed where that is needed to protect them (Article 15(4) GDPR). And if a report leads to a decision against your account, the reasons for that decision are stated to you, as the terms describe.
• "Delete my account": your personal data, sessions, linked sign-in identities and message bodies are removed from our systems and your display name becomes "[DELETED]", so past matches and leaderboard rows stay consistent without naming you. If the account signed in with Apple, we also ask Apple to revoke the app's access to it. What outlives it names nobody: the empty shell of the account, the fact that a report or support ticket existed and how it was decided, and our record of any action we took. Analytics events and error reports held by our providers are erased under the retention above, or earlier on our instruction, as the law requires. After a withdrawal from the contract, the address the acknowledgement goes to is used only for that and kept only until the email is sent, never longer than seven days (with a one-way hash of it in memory for at most a day, to limit repeats); our email provider keeps its own delivery record for its standard period, as our processor.

We answer requests without undue delay and within the time limits the law sets (Article 12(3) GDPR). We may ask you to confirm your identity, or that a request concerns your own profile, before acting on it.

If you think we are handling your data unlawfully, you can complain to the Romanian supervisory authority, ANSPDCP (dataprotection.ro), or to the authority of the country where you live or work.

Children

The app is for people aged 16 or older and is not directed at children: people under 16 may not use it, as the terms say. 16 is the age of digital consent in Romania. The app does not ask for your age, and we do not verify it: accepting the terms on the card shown the first time the app runs, and again when an account is created, confirms that you are 16 or older. We store no age and no birthdate. We do not ask a parent or guardian to consent on a child's behalf and have no way to verify one. A parent or guardian who believes a child has given us personal data can write to us and we will delete it. Any player who would rather not appear on the public boards, a 16- or 17-year-old included, can hide themselves from them with the setting described under "Who else sees it" above.

How we protect it

Traffic is encrypted in transit. Passwords, guest device keys and backup codes are stored hashed, never in the clear. The game server sends each player only their own view of a match, so no opponent can read your hand. We apply technical and organisational measures appropriate to the risk, but no system is perfectly secure. Where a personal data breach is likely to result in a high risk to your rights and freedoms, we will inform you as the law requires.

Changes to this policy

When this policy changes, the date at the top changes with it. Material changes are announced before they take effect, by email to every account with a confirmed email address, and are shown in the app at your next visit, before you continue, whether you use an account or a guest profile. Where a change would need your consent, it is asked for again rather than assumed.