PliCount

PliCount privacy policy

Last updated: 2026-10-20

PliCount is a score sheet for card games made by Tekartik. This page says what the app stores, where, and why. PliCount needs no account, and has no advertising and no analytics.

Without an account

Nobody has to sign up. A game played on one phone needs no sign in at all. The first time you create, share, join or open a shared game, the app signs in anonymously with Firebase Authentication (a Google service): a random identifier, with no name, email or phone number attached. It lets a shared game know who created it, so that only its creator (its admins) can lock or delete it. The identifier stays in the app's storage on your device.

With an account (optional)

You can create an account with your email address, or sign in with Google, in Compte (the menu of the app). Firebase Authentication then keeps your email address, the dates you signed up and last signed in, and for Google the name and picture of your Google account. An account only keeps you an admin of the shared games you create, on every device where you sign in: the list of your games stays on each device. Signing in to an account on a device that used shared games without one makes the account an admin of the games created there too.

On your device

  • Your games: a game played on one phone lives only in a database of the app on that phone (the browser's storage on the web): its name, the game played, the names you typed for the players and the teams (all optional), the places, the settings and every deal (the bid, the points, the result).
  • The list of your games, local and shared, for the history and to resume them. It is never sent anywhere.
  • Your settings: the theme, and whether a deal is entered on one page or in two steps.

Shared games

When you share a game (Partager en ligne), its content is copied to Cloud Firestore (Google Cloud, European Union multi-region) so the other phones at the table can follow it:

  • the game itself: the same content as above (name, players' names as typed, settings, deals);
  • a game record: its name at creation, the identifiers of its creator and of its admins (anonymous, or of an account), its current join code and when it was given, whether it is locked, and its dates;
  • its join code: 6 digits pointing to the game, working for 2 days. The code record stays until the code goes to another game or the game is deleted.

Whoever has the link of a shared game, or a valid join code, can read and change it, signed in anonymously like you: share it with the people at your table only. Its admins can lock it (read only for the others).

The app talks to a server function of PliCount (Google Cloud, Belgium) to create a shared game, give or renew its join code, lock it and delete it, and to delete an account. Google Cloud keeps the technical logs of these requests for 30 days.

Deleting your data

  • Deleting a local game deletes it from your device. Removing a shared game from your games takes it out of your list (its copy stays in the app's storage until you clear it, below).
  • Supprimer pour tout le monde (delete for everyone), for an admin of a shared game, deletes it from the server: its content, its record and its join code.
  • Supprimer mon compte (delete my account, in Compte) removes your account from the admins of your shared games (a locked game left without admin is unlocked), then deletes it from Firebase Authentication. The games themselves stay, for the other players, and so does the list of your games on your device.
  • Clearing the app's data (the site data of plicount.web.app in your browser) deletes everything the app keeps on your device, the anonymous identifier included.

A shared game is not deleted by itself: to have a shared game deleted when its creator cannot do it any more, contact Tekartik through tekartik.com.

Changes

This policy may change as the app evolves; the date above says when.