Privacy Policy
Last updated 14 October 2026 (section 3: crash reports; section 4: where they are stored)
Contents · 18 sections
- 1. Who we are and what this policy covers
- 2. The short version
- 3. What we collect, why, and on what basis
- 4. Where your information is stored and who processes it
- 5. Online multiplayer (optional)
- 6. Community page (optional)
- 7. Ranking and leaderboards
- 8. Local storage on your device
- 9. Security
- 10. How long we keep information, and how to delete it
- 11. Your rights
- 12. Children and age rating
- 13. The virtual economy
- 14. Permissions requested
- 15. Changes to this policy
- 16. Contact
- 17. The App's own licences
- Sources and instruments referred to in this policy
1. Who we are and what this policy covers
This policy explains what personal information Orderli Group ("we", "us", "our") collects when you use Tavola Carte: Italian Card Games Lounge (the "App") on Android, Windows or the web, why we collect it, how long we keep it, who can see it, and the rights you have over it.
We are an Australian publisher. We handle personal information in accordance with the Privacy Act 1988 (Cth) and the thirteen Australian Privacy Principles ("APPs") in Schedule 1 of that Act. Where the small-business threshold in section 6D of the Act would otherwise exempt us, we nonetheless apply the APPs as our standard of practice. Because the App is offered to players in the European Economic Area and the United Kingdom, we also meet the obligations of Regulation (EU) 2016/679 (the "GDPR") and the UK GDPR for those players. The App is distributed through Google Play and the Microsoft Store and complies with the Google Play User Data policy, including its account-deletion requirements, and the U.S. Children's Online Privacy Protection Act ("COPPA").
This policy is written to satisfy APP 1 (open and transparent management of personal information), APP 5 (notification of collection) and Article 13 of the GDPR (information to be provided where personal data are collected from the data subject).
2. The short version
- You can play without telling us anything. Every game is fully playable offline. Choosing Play as a guest creates a random player identifier and nothing else; it does not identify you.
- Accounts are optional and minimal. If you choose Continue with Google, Continue with Microsoft or Continue with email, the only personal information we hold about you is the email address (and, for Google or Microsoft, that account's identifier, together with the name and, for Google, the profile picture the provider sends with every sign-in, which the App does not use) needed to recognise you on another device. We do not ask for your name, date of birth, phone number, address or payment details.
- We keep your game progress so it is there when you come back, and so that, in online play, we can match you with players of a similar rank.
- No advertising, no analytics, no sale of data. The App contains no advertising or analytics software, collects no advertising identifier and no location, and we never sell or rent personal information. If advertising were ever introduced for accounts created later (see section 4A of the Terms of Service), this policy would be updated before it took effect, and it would never apply to Founder accounts.
- You can delete your account and everything attached to it at any time, inside the App or from a web page, without reinstalling the App.
The rest of this policy is the detail behind those statements.
3. What we collect, why, and on what basis
We collect only the information listed below (APP 3: collection of solicited personal information; GDPR Article 5(1)(c): data minimisation). The "Legal basis" column applies where the GDPR governs the processing (Article 6: lawfulness of processing).
| Information | When it is collected | Why we collect it | Legal basis (GDPR) | Kept for |
|---|---|---|---|---|
| Player identifier: a random identifier created by our authentication provider when you first choose how to play | Guest, Google, Microsoft and email players alike | To recognise your profile and attach your progress to it. On its own it identifies nobody. | Article 6(1)(b): performance of the service you asked for | Life of the account, then deleted |
| Email address | Only if you choose Continue with email, Continue with Google (supplied by Google) or Continue with Microsoft (supplied by Microsoft) | To sign you in on any device, to send the one-time sign-in code, and to reach you about your account (a deletion confirmation, a security notice). Never for marketing (APP 7). | Article 6(1)(b) | Life of the account, then deleted |
| Google account identifier, and the name and profile picture on your Google account | Only if you choose Continue with Google (Google sends all three with the sign-in) | The identifier recognises the same Google account on another device. The name and picture are recorded with the identity by our authentication provider and used for nothing: your display name and avatar in the App are the ones you choose. We do not import your contacts. | Article 6(1)(b) | Life of the account, then deleted |
| Microsoft account identifier, and the name on your Microsoft account | Only if you choose Continue with Microsoft (Microsoft sends both with the sign-in) | The identifier recognises the same Microsoft account on another device. The name is recorded with the identity by our authentication provider and used for nothing: your display name in the App is the one you choose. We do not import your contacts. | Article 6(1)(b) | Life of the account, then deleted |
| One-time sign-in code | When signing in with email | To verify that the address is yours | Article 6(1)(b) | Expires within minutes; not retained |
| Display name and avatar | If you set them in your profile | Shown at the table, on the Community page and on leaderboards. Any name you like; it need not identify you. | Article 6(1)(b) | Life of the account, then deleted |
| Game progress: level, experience points, virtual chips, achievements, unlocked themes, settings | As you play, whether guest or account | So your progress is saved and restored, and, for account holders, follows you to a new device | Article 6(1)(b) | Life of the account, then deleted |
| Match results: which game, the score, win or loss, the date, and for online matches the opponent's player identifier | At the end of each hand and match | To keep your history and statistics, and to compute your rank | Article 6(1)(b) | Life of the account, then deleted |
| Record between friends: for an online match against a friend, the wins each way, each side's best score, sweeps and Settebellos, keyed by the friend's code | At the end of an online match against a friend | To show the head-to-head history on that friend's profile page. Kept with your own progress; each player holds their own copy. | Article 6(1)(b) | Life of the account, then deleted; gone from your side when you remove the friend's history |
| Rank | Derived from your progress and match results | To place you on leaderboards and, in online play, to match you with players of the same or a similar rank so that matches are fair | Article 6(1)(b), and Article 6(1)(f): our legitimate interest in fair matchmaking | Life of the account, then deleted |
| Application version, platform and last-seen date | Each time the App syncs your profile | To restore a save correctly across versions, to reproduce a problem you report, and to identify inactive accounts for deletion | Article 6(1)(f): our legitimate interest in running and maintaining the service | Life of the account, then deleted |
| Crash reports: if part of the App fails, the error message, a short technical trace of where in the App's code it happened, the App version and build, the platform (Android, Windows or web), the screen you were on, and the time | Automatically, when an error stops part of the App; at most five per session | To find and fix faults. A report carries no player identifier, display name, email address or game progress: file paths, web addresses, email addresses and codes in the error text are removed on your device before it is sent. | Article 6(1)(f): our legitimate interest in keeping the App working | 90 days, then deleted |
| Founder status: whether the account is a Founder and when it became one, and for the first hundred Founders a private founder number | When an account is linked while the Founder window is open | To give the account its Founder benefits (Terms of Service, section 4A). The founder number is not shown to other players. | Article 6(1)(b) | Life of the account, then deleted |
| Friends: the accounts you add by friend code or that add you, whether each request is pending or accepted, and the match challenges you send or receive (the game and its invite code) | Only if you use the Friends tab | To show your friends list and deliver challenges between the two of you. Each record is visible only to the two accounts involved. | Article 6(1)(b) | Until either of you removes it, or the account is deleted |
| Referrals: which account's invite link brought a new account to the App (the two account IDs), when it was claimed and when the inviter's reward was paid | When you sign in with an account after installing from a friend's invite link, or when a friend does so from yours | To give the invited player their welcome chips; to give the inviter their reward and Recruiter tiers once the invited player has played a match, which we check against the match count already kept with the invited player's progress, at most five in any 30 days; and to pay each invitation once. The inviter is shown the display name and avatar of a friend who counted; nothing else about the referral is shown to anyone. | Article 6(1)(b) | Life of either account, then deleted |
| Online presence: that your account is currently in the App | While you are signed in with an account | So your friends can see who is online to challenge. Held in memory by our realtime provider and not stored. | Article 6(1)(b) | Transient; gone when you close the App |
| Online match traffic: the moves of a match, the invite code, and the profile summary each player shares at the table (avatar, level, title, match record and, for a linked account, the friend code) | Only during an online match you chose to create or join | To relay the match between the two players, and to show each player the other's profile card, from which they can send a friend request | Article 6(1)(b) | Transient; not stored after the match ends |
| Community page: your vote, the text you write, your display name if set | Only if you vote or write on the Community page | To run the community vote and to answer suggestions and feedback (Section 6) | Article 6(1)(a): your consent, given by sending it | While the poll or topic is live; deleted with the account or on request |
What we do not collect. We do not collect your precise or approximate location, your contacts, your device's hardware identifiers, the advertising identifier (GAID/IDFA), your browsing activity, or any payment information. We do not use advertising or analytics SDKs, we do not track you across other apps or websites, and we do not make decisions about you by automated means that have legal or similarly significant effects on you (GDPR Article 22).
Anonymity and pseudonymity (APP 2). Playing as a guest, and choosing a display name that does not identify you, are the ways the App lets you deal with us anonymously or under a pseudonym. Online play requires an account only because a dropped connection must be able to find the same player again; it does not require your real name.
4. Where your information is stored and who processes it
Your profile, progress, Community contributions and crash reports are stored in a database operated for us by Supabase, Inc. ("Supabase"), hosted on Amazon Web Services in the Sydney, Australia region (ap-southeast-2). Data travels to and from the App over encrypted connections (TLS). Supabase acts as our data processor under its Data Processing Addendum (https://supabase.com/legal/dpa), which incorporates the European Commission's Standard Contractual Clauses (GDPR Articles 28 and 46) and binds Supabase's sub-processors to the same obligations. Supabase's privacy policy is at https://supabase.com/privacy.
If you sign in with Google, Google LLC processes the sign-in itself under Google's privacy policy (https://policies.google.com/privacy). We receive from Google your email address, your account identifier and, because Google's sign-in always includes its profile scope, the name and profile picture on your Google account; the App uses only the first two.
If you sign in with Microsoft, Microsoft Corporation processes the sign-in itself under Microsoft's privacy statement (https://privacy.microsoft.com/privacystatement). We receive from Microsoft your email address, your account identifier and the name on your Microsoft account; the App uses only the first two.
The typeface. The App's typeface (Outfit) is fetched from Google Fonts (fonts.googleapis.com and fonts.gstatic.com) when the device is online. Google receives the request and, as with any web request, the device's IP address; Google Fonts sets no cookies and Google states it does not use these requests to profile users (https://developers.google.com/fonts/faq/privacy). Offline, the device's own typeface stands in and nothing is sent.
Cross-border disclosure. Wherever you are, your information is stored in Australia. For players in the EEA and the UK, this is a transfer to a country that has not been the subject of an adequacy decision. We rely on the necessity of the transfer for the performance of the service you have asked us to provide (GDPR Article 49(1)(b)), and our processor's Standard Contractual Clauses provide the safeguards for its part of the processing. For the purposes of APP 8, we do not disclose your information to any overseas recipient other than these processors acting on our instructions.
We do not sell, rent or trade personal information, and we disclose it to no one else except where the law requires it (APP 6; GDPR Article 6(1)(c)).
5. Online multiplayer (optional)
Online play is optional; every game is fully playable offline against the computer. Online play requires an account (guest players are limited to single player) so that a match can be resumed if a connection drops and so that rank-based matchmaking, when offered, is fair. When you create or join an online match:
- What is transmitted: your display name, the invite code, the moves of the match, and the profile summary in Section 3. Match traffic is relayed in real time through Supabase over encrypted connections and is not stored after the match ends. The result of the match (Section 3) is stored against both players' profiles. The table's own dressing (your background, deck and face) is applied on your device only and is not sent.
- A dropped connection: if a player leaves or loses their connection, the seat is held for thirty seconds so they can return; a player who does not return forfeits the match, and the result is recorded like any other. The match runs inside the app of the player who created it; if that app closes, the match ends.
- Local network play (a same-network option once offered by the desktop build) has been removed from the App as of version 0.55; every online match is relayed as above.
- Matchmaking: when automatic matchmaking is offered, the only information used to pair players is rank. No other profile information is shared with the other player beyond your display name, avatar and rank.
6. Community page (optional)
The Game Centre has a Community page where you can vote on which table the games should add next, suggest a rule or a game mode, and send us feedback. When you do:
- What is stored: your vote; the text you write; your display name if set; the application version and platform; and your player identifier, so that one player gets one vote per poll (changeable) and a sensible number of messages an hour. Before version 0.32 this identifier was a random install identifier; from 0.32 it is the player identifier in Section 3.
- Who sees it: votes are shown only as totals. A message you send is read by us; we may answer it inside the App, and we may show it, with your display name and our answer, to other players on the Community page. We do not publish a message without reviewing it first.
- Retention and deletion: kept while the poll or the topic is live and for as long as it is useful to plan the games; deleted with your account, or earlier on request.
Never opening the Community page, or only reading it, means nothing in this section is ever sent.
7. Ranking and leaderboards
Your rank is a number derived from your level and match results. It exists so that a leaderboard can show where you stand and so that online matchmaking can pair you with someone of a similar standard.
- What other players can see: your display name, avatar, level, rank and, on the Community page, what you have chosen to post. Nothing else, and never your email address.
- Your controls: choose any display name; hide your profile from leaderboards with the switch in your profile's Account section (your rank is then used only for matchmaking); or play as a guest, in which case you appear on no leaderboard and are never matched.
8. Local storage on your device
Your progress and settings are also kept on your device (web localStorage / IndexedDB, or Android app storage) so that the App works offline and opens instantly. The device copy is the working copy; the copy in our database is the backup that follows an account to another device. Clearing the App's storage or uninstalling the App removes the device copy only; to remove the copy we hold, delete your account (Section 10).
9. Security
We protect personal information against misuse, interference, loss, unauthorised access, modification and disclosure (APP 11; GDPR Article 32) by:
- transmitting everything over TLS;
- storing profiles behind row-level security so that each player's row can be read and written only with that player's own credentials, and Community writes pass through validated database functions rather than direct table access;
- never storing a password in readable form: an email profile's password is kept only as a salted one-way hash by our authentication provider, sign-in with Google or Microsoft involves no password at all, and a one-time emailed code can always stand in for a forgotten password;
- restricting our own administrative access to the people who operate the service.
If a data breach is likely to result in serious harm, we will notify affected players and the Office of the Australian Information Commissioner as required by the Notifiable Data Breaches scheme in Part IIIC of the Privacy Act 1988, and, where the GDPR applies, the competent supervisory authority within 72 hours and affected players without undue delay (GDPR Articles 33 and 34).
10. How long we keep information, and how to delete it
We keep your information for as long as your account exists (APP 11.2; GDPR Article 5(1)(e)).
- Delete your account in the App: Settings โ Account โ Delete account. This deletes your profile, progress, match history, rank and Community contributions, and revokes the sign-in identity.
- Delete your account from the web, without reinstalling the App: https://orderligroup.com.au/arcade/tavola-carte/delete-account . This page lets you request deletion by email from the address on the account, or by quoting your display name and player identifier for a guest account.
- Timing: deletion is carried out within 30 days of the request. Copies in routine backups are overwritten within a further 30 days. There is no partial deletion: an account and its data are deleted together.
- Inactive accounts: an account not used for 24 months may be deleted. Where we hold an email address, we will write to you 30 days beforehand.
- What survives: nothing that identifies you. We may keep aggregate, non-identifying statistics (for example, how many hands of Scopa were played in a month).
You may also delete the device copy at any time by clearing the App's storage or uninstalling.
11. Your rights
You may at any time ask us for access to the personal information we hold about you and ask us to correct it (APP 12 and APP 13; GDPR Articles 15 and 16). Players covered by the GDPR also have the rights to erasure (Article 17), restriction of processing (Article 18), data portability (Article 20) and objection to processing based on our legitimate interests (Article 21), and, where processing is based on consent, to withdraw that consent at any time without affecting the lawfulness of processing before withdrawal.
To exercise any of these rights, write to privacy@orderligroup.com.au from the email address on your account, or, for a guest account, quote your display name and player identifier (shown on the profile page). We respond within 30 days and charge nothing. Because we hold so little, most requests are answered by the export or deletion functions already in the App.
If you are not satisfied with our response you may complain to the Office of the Australian Information Commissioner (https://www.oaic.gov.au) or, where the GDPR applies, to the supervisory authority of your EU member state (GDPR Article 77), for example the Garante per la protezione dei dati personali in Italy (https://www.garanteprivacy.it).
12. Children and age rating
The App is rated through the IARC questionnaire in each store. Its games, Scopa and Briscola, involve no betting of any kind (Section 13), so the expected rating is suitable for all ages (for example PEGI 3, ESRB Everyone, G in Australia); some regions add an advisory because optional online play lets you share a table with another person. The App is not directed at children under 13, and we do not knowingly collect personal information from anyone under 13 (COPPA). Where the law of your country sets a higher age below which a child may not consent to online services on their own (GDPR Article 8; for example 14 in Italy under Article 2-quinquies of the Italian Privacy Code, and up to 16 elsewhere in the EEA), a person under that age may play as a guest but must not create an account. If you believe a child has created an account, write to privacy@orderligroup.com.au and we will delete it.
13. The virtual economy
- No gambling of any kind: no game in the App stakes chips or anything else on the outcome of a hand, and there is no real-money play.
- Virtual chips ("fiches"): chips are earned by playing Scopa and Briscola and are used solely for in-game levelling and unlocking cosmetic items: card decks, card backs, table wallpapers, loading screens, avatars, Buzz Words, desktop cursor packs and sound packs. Every one of them is decoration; none changes how a game plays or is scored. A few are earned only, by inviting friends or by reaching a level, and are never sold. Your choice of card back and wallpaper dresses your own screen and is not sent to other players.
- No cash value: in-game chips have no monetary value and cannot be exchanged, transferred, redeemed or cashed out for real currency, goods or services in any circumstances, and are never sold for money.
14. Permissions requested
Android:
android.permission.VIBRATE: optional haptic feedback during card interactions (can be turned off in Settings).android.permission.INTERNET: used for the App's web framework and, only when you choose them, accounts, online play and the Community page.
Windows (Microsoft Store):
- The package declares only the standard desktop application capability. It requests no camera, microphone, location, contacts or other device access, and every such request from web content is refused by the App itself.
15. Changes to this policy
We may update this policy from time to time. Changes are posted on this page with a new "Last updated" date; a change that materially affects how we use your personal information is also announced in the App before it takes effect. The version history is public in the App's repository.
16. Contact
- Privacy matters and rights requests: privacy@orderligroup.com.au
- General support: support@orderligroup.com.au
- Website: https://orderligroup.com.au
17. The App's own licences
None of this concerns your personal information; it is here because players ask.
- Software: the App's source code is published under the MIT License (copyright 2026 Orderli Arcade / Tavola Carte Project). That licence covers the code alone, not the Tavola Carte name, the artwork or the audio. The App is built with open-source components (among them React, Vite, Electron, Capacitor and the Supabase client), each under its own licence, listed in the repository.
- Card artwork: the Napoletane and Piacentine faces are scans of public-domain traditional designs from Wikimedia Commons, retouched by us; the Siciliane and Trevisane faces are original Tavola Carte artwork, generated and composited after the traditional patterns, copyright 2026 Orderli Group, all rights reserved. Decks are named for their traditional regional pattern, never for a printer; the App is not affiliated with any card manufacturer.
- Everything else you see and hear: the card backs, the table wallpapers, the icons, crests and loading screens are drawn by us and belong to Orderli Group. The sounds are synthesised in the App; the spoken calls use the device's own speech voice or our recordings.
- Typeface: Outfit, by Rodrigo Fuenzalida, under the SIL Open Font License 1.1.
The Terms of Service (section 6) say what you may and may not do with these.
Sources and instruments referred to in this policy
- Privacy Act 1988 (Cth), including Schedule 1 (Australian Privacy Principles), section 6D (small business operators) and Part IIIC (Notifiable Data Breaches): https://www.legislation.gov.au/C2004A03712/latest/text
- Office of the Australian Information Commissioner, Australian Privacy Principles quick reference: https://www.oaic.gov.au/privacy/australian-privacy-principles/australian-privacy-principles-quick-reference
- Regulation (EU) 2016/679 (General Data Protection Regulation), in particular Articles 5, 6, 8, 13, 15 to 22, 28, 32 to 34, 46, 49 and 77: https://eur-lex.europa.eu/eli/reg/2016/679/oj
- Italian Personal Data Protection Code (Legislative Decree 196/2003, as amended by Legislative Decree 101/2018), Article 2-quinquies (age of consent for information society services)
- Children's Online Privacy Protection Rule, 16 C.F.R. Part 312 (U.S. Federal Trade Commission)
- Google Play Developer Policy Center, User Data policy and Understanding Google Play's app account deletion requirements: https://support.google.com/googleplay/android-developer/answer/13327111
- Supabase Data Processing Addendum: https://supabase.com/legal/dpa ; Supabase Privacy Policy: https://supabase.com/privacy
- Google Privacy Policy (Sign in with Google): https://policies.google.com/privacy
- Microsoft Privacy Statement (Sign in with Microsoft): https://privacy.microsoft.com/privacystatement