Privacy Policy
In short:
- No ads, no tracking, no selling of data, and no analytics, advertising or crash-reporting SDKs in the app.
- We never ask for your e-mail address, phone number, location, contacts or photos.
- You can play as a guest. Signing in with Apple is optional.
- Voice chat is optional and is not recorded by us.
- The public chat, when it is on, keeps its messages only in our server’s memory: never in a file or a database.
- You can delete your account in the app at any time.
1. Who we are
Meryas is a Mauritanian card game. It is made and operated by the Meryas developer (“we”, “us”). For any question about this policy or your data, write to support@meryas.app.
2. What we collect and why
2.1 Playing online (everyone, guests included)
- Player identity. When the app first connects, our server creates a random player id and a random secret token for it. The app keeps the token on your device so it can bring you back to your seat after a disconnect. The server keeps both in its game save file.
- Install id. The first time the app runs after it is installed, it makes a random number (128 bits) and keeps it in your device’s Keychain; it sends it to our server each time it connects. It is not your advertising identifier and it is not made from your device, your name or your account. We use it for two things only: to keep one abusive guest from writing in table chat or using online rooms again after a ban (section 2.5), and to count a guest once a day in our daily totals (below). Our server turns it at once into a one-way hash (SHA-256) and keeps only that hash: in its memory while you are connected, and until the end of the day (UTC) for the daily totals, and, only if you play as a guest, in a report about you and in a ban of your device (section 2.5). It is never saved with your account and never shown to other players. The hash is not written to a log in full: only its first 12 characters are, as the short reference our team uses to name a device when it acts on it (see “Log of our actions” in section 2.5). Deleting the app deletes it; installing the app again makes a new one.
- Display name and avatar. The name you type in the app (up to 20 characters) and the number of the built-in avatar you pick. They are shown to the other players at your table and, in public matches whose players allow it, to the people watching (section 2.10).
- Game state. Room code, seats, cards, bids, scores and room options, so that a game survives a disconnect or a server restart.
- Table chat. Short text messages are delivered to the players at your table and are not saved on our server.
- Daily totals. Each day we count totals: how many players opened the game, sat at a table, started a match, finished a match and left a match under way, and how many new accounts were created. To count each player once a day, our server holds your account id (or, for a guest, the one-way hash of the install id above, or, if the app sent none, the random player id) in its memory until the end of that day (UTC); it is never saved or logged. The totals have no name, id or device and are used only to improve the game; on a day with very few players a total can be small. They are kept 400 days.
A room is removed when it closes, or when all its players have been away for 15 minutes. A player identity that is not in a room is removed from the server 6 hours after it was last seen.
2.2 Your account (Sign in with Apple, optional)
- Apple user identifier. The stable identifier that Apple gives Meryas for your Apple ID, so we can recognise your account when you sign in again.
- Nothing else from Apple. We do not ask Apple for your name or your e-mail address, and we store neither. (Earlier versions of the app asked Apple for your name; the server update that ended this deleted every name stored before.)
- Account record. A random account id and the times the account was created and last updated.
- Display name. The table name you type in the app (section 2.1), kept with your account so the table shows it on any device you sign in on.
- Avatar. The number of the built-in avatar you picked, from your latest connection, kept with your account so the leaderboard can show it (section 2.3).
- Username (optional). If you reserve one, your @username, a normalised form of it used to keep usernames unique, and when you last changed it. It is shown to you in the app. When you start a table that is waiting for players, every player who opens the list of open tables (Home, Sessions) sees your @username on it for as long as the table waits; nothing else about you is in that list (no table name, no guest name, no id). Once search and invitations arrive, other players will find and invite you with it. When you change it, the normalised form of the old username is kept for 30 days so nobody else can take it at once; only you can take it back in that time, without waiting for your next change. If moderation removes a username that breaks the rules, we store until when you cannot choose a new one.
- Sessions. After you sign in, the server gives the app a random session token, which the app keeps in your device’s Keychain. The server stores only a one-way hash (SHA-256) of that token, with the times it was created, last used and expires. A session expires 90 days after it was last used (each use extends it), and signing out deletes it.
2.3 Ranked play and levels (accounts only)
For ranked matches we store your rating values, level points and tier, wins, losses and matches left, with their dates, and one rating record per ranked match (match id, team, result, and your values before and after). They are used to compute your level, which other players can see at your table.
Leaderboard. The leaderboard (“Leaders” on the home screen) lists the top 100 players. Every player who opens it can see, for each player on it, the @username, the avatar, the level tier and the level points. It never shows your hidden rating, your account id, your table name or how many matches you played, and the players are ordered by their hidden rating. Only an account with a username that has finished its placement matches can appear: guests never do, and neither does an account without a username. To stay off it, turn on Hide me from the leaderboard in Settings, Account. We store that choice (yes or no) with your account, and it takes effect at once, and we no longer list you. The list is held in the server’s memory for up to a minute and is rebuilt from the live data, so it is never kept anywhere else. You alone are also shown your own place if it is outside the top 100.
2.4 Voice chat (optional)
- Your microphone is off until you turn it on, and the app asks for the device’s microphone permission the first time.
- Voice is relayed in real time by our voice provider, LiveKit, to the players in the same room and, in a public match whose players allow watching, to the spectators who listen (section 2.10). We do not record it, and we do not ask LiveKit to record it.
- To connect you, our server gives your app a short-lived voice token with a random voice identity, created for each room and kept only in the server’s memory. The token carries no name, account id or other personal details.
- The first time you use voice, the app turns on a setting on your device, Listen automatically in private rooms, so that in private rooms it joins the table’s voice by itself to listen. You can turn it off in Settings. Your microphone still starts off.
2.5 Reports, blocks, voice bans, chat bans and suspensions
- Reports. Any seated player can report another player at the table, and a spectator and a seated player can report each other (section 2.10). We store who reported and who was reported (as an account id; for a guest, the one-way hash of the guest’s install id (section 2.1) when the app sent one, else the guest’s random player id; the reporter’s own install id is not kept), the room code, the reason, whether the reported player was in voice, and the time. We use reports to review abuse and act on it.
- Report reviews. When we review a report, we store the outcome, when it was reviewed and who on our team reviewed it, and we may add a short note. The note is erased if the reporter’s or the reported player’s account is deleted.
- Automatic mute. When two different players at a quick-match table (three in a private room) report the same player during one match, that player’s microphone is turned off for the rest of the match (they can still listen). Reports by spectators never count toward it. This is kept only in the server’s memory.
- Blocks (between signed-in accounts). We store your account, the blocked account, the name shown at the table when you blocked it, and the time.
- Voice bans. If we ban an account from voice after reviewing reports, we store the end date of the ban with the account.
- Chat bans and suspensions. If, after reviewing reports, we ban an account from writing free text at the table (a chat ban; the preset phrases and emoji still work) or suspend it (it is signed out, cannot sign in with Apple until the suspension ends, and can still play as a guest), we store the account id, which of the two it is, the reason (abuse, hate, sexual content, cheating, spam or other), when it was set and when it ends or that it is permanent, the report it followed if there is one, who on our team set it, and sometimes a short note. A suspension also deletes the account’s sessions.
- Bans of a guest’s device. If, after reviewing reports, we ban a guest from writing free text at the table or from online rooms (games against bots still work), the ban is kept against the one-way hash of the install id of the device the guest used (section 2.1), not against a name or an account: its kind, the reason (abuse, hate, sexual content, cheating, spam or other), when it was set, when it ends or that it is permanent, the report it followed if there is one, who on our team set it, and sometimes a short note. It applies only while you play as a guest. If you sign in with Apple on that device, you are treated according to your account, which we do not link to the device. A guest who is in a room when the ban is set is taken out of it.
- Log of our actions. Each action our team takes on an account or a report (a ban or its lifting, resolving a report, deleting an account) is written to a log with the time, the kind of action, the account id and which team member did it, and sometimes a short note. When the action is on a guest’s device (a ban of the device, including one that follows a report, or its lifting), the log holds the short reference of the device instead of an account id: the first 12 characters of the hash of its install id (section 2.1). It is not linked to an account, but anyone who has the install id can work it out, so these entries can be matched to that device. The same line, without the note, is also written to the game server’s own log (rotated by size, at most five files of 10 MB).
2.6 Network (IP) addresses
- The game server uses your connection’s IP address only in its memory, to limit how many connections one address can open at once. The game server does not save or log it.
- The web server in front of the game (Caddy, on
play.meryas.app) writes an access log line for each request: IP address, time, requested path, request headers such as the app or browser identifier (User-Agent), and the response status. We use it to diagnose faults and abuse. The log is rotated automatically by size (at most five files of 10 MB), so the oldest lines are deleted as new ones arrive. - This website (
meryas.app) keeps no access log.
2.7 Kept only on your device
Your settings (language, theme, sound and similar), your device statistics and practice points, and a saved offline match against bots stay on your device and are not sent to us.
2.8 E-mail to support
If you write to us, we receive your e-mail address and your message, and use them only to answer you.
2.9 Public chat (accounts with a username)
- Who and when. The public chat is one channel for players signed in with Apple who have a username. Guests cannot enter it. We switch it on and off from the server, and it is off until we switch it on.
- Your messages. A message you write is shown to everyone reading the channel with your @username and the time. The server holds the last 100 messages of the channel in its memory only: not in a file, a database, a log or a backup. They are gone when the server restarts, when we switch the chat off, when you delete your account, when you change your username or moderation removes it, and when a chat ban or a suspension is put on your account.
- What else the server uses. For as long as a message of yours is among the last 100 of the channel, your account id is kept in the server’s memory next to it, whether or not you are still connected, together with the account ids of the players who reported it. The time of your last message is kept too, for the pause between two messages (5 seconds unless we change it) and until our server next tidies up, a minute at most. They are used to apply that pause, a chat ban, the blocks other players made, and reports. None of it is sent to other players, and the ids go with the message in the cases listed above.
- Word filter. Words on our abusive-word list are replaced with asterisks before anyone sees the message, as at the table.
- Reporting a message. Any signed-in player in the channel can report a message or block the player who wrote it. A report keeps what section 2.5 lists, with the room shown as “public”, and the text of that one message and the time it was sent as evidence. Nothing around it is kept. A block is kept as any block (section 2.5), under the @username the player had then.
- Chat bans. A chat ban (section 2.5) stops your account from writing in the public chat as at the table; you can still read.
2.10 Watching public matches (the Majlis)
- Who watches. Players signed in with an account can watch a public quick match that is under way from the Majlis tab, if every player seated at that table allows it. The choice is in Settings (“Let others watch and hear my public matches”); it is on unless you turn it off, and the app explains it to you once before your matches can be watched. Private rooms are never watched.
- What a spectator sees and hears. What every player at the table already sees: display names, avatars, levels, the cards played, the bids and the score; never anyone’s hand, and never the free text written at the table. A spectator also hears the table’s voice chat without being able to speak, and can send ready-made phrases and emoji only. Each phrase or emoji is shown, with the sender’s display name, to the players at the table and to the other people watching it.
- What the players see. The players at the table see who is watching (display name, username if there is one, avatar, level, and whether they are listening) and can remove or block any spectator. When you watch, the players at that table see your display name, username if you have one, avatar and level.
- What we keep. We do not keep a record of who watched which match: nothing about it is written to our database or to a log. Who is watching or listening is held only in our server’s memory while they watch. For as long as the table stays open, that memory also holds which accounts watched it, were removed from it or left its match under way, so that a spectator keeps the same code there and nobody a player removed or blocked can come back to it. We count the minutes spectators spend listening, as one total per day and per month with no names, to stay within our voice provider’s limits. A report by or about a spectator is stored like any other report (section 2.5).
- Voice. A spectator who listens gets a listen-only voice token with a random voice identity, as in section 2.4, and LiveKit relays the table’s audio to them.
2.11 Friends, likes and play invites (accounts only)
- Who and how: you can add a player as a friend from their card at the table or by typing their full username; they become your friend when they accept. Guests cannot add friends. We turn this feature on and off from the server, and it is off until we turn it on.
- What we keep: for each friend request: the two accounts, its state (waiting, accepted or declined), when it was sent and when it was accepted. A request that is not accepted is deleted 10 days after it was sent. A player whose request you decline is not told. The limit is 20 friends unless we change it.
- What your friends see: your username (or your display name if you have no username), avatar and like count, and whether you are online now, at a table or offline. We show no “last seen” and keep no history of when you were online for this: the state is read from the server’s memory when the list is opened. A player you send a friend request or an invite to sees the same about you, and an invite also carries the room code.
- Likes: you can like each other player who sat with you in the same match, once per match. We keep the match number, the two accounts and the time. The number of likes you received is shown to any player who opens your card or sees you in their friends list; who gave them is not shown. Likes do not affect your rating or who you play with.
- Play invites: an invite to a room is kept in the server’s memory only, for 5 minutes or until the match starts, and is never written to the database.
- Blocks: blocking a player ends your friendship, and no request or invite from them reaches you afterwards.
3. What we do not do
- No advertising, no advertising identifier, and no tracking across other apps or websites.
- No selling or renting of personal data, and no sharing of it for advertising.
- No analytics, advertising or crash-reporting SDKs in the app.
4. Where your data is processed
- Hetzner Online GmbH hosts our server in Nuremberg, Germany. The game server, its database, the logs and the backups are on that server. Hetzner’s backup service also keeps a daily image of the server’s whole disk, in storage separate from the server, for 7 days, so the game can be recovered if the server is lost (see section 5).
- LiveKit (LiveKit Cloud) relays voice chat. Our LiveKit project is set up in its EU region (Frankfurt), but LiveKit may carry the audio through its servers nearest to each player, which can be outside the EU. It handles the audio, the random voice identity, the voice room id and the network address your device connects from. When the app connects to voice, the LiveKit library in the app also sends LiveKit technical details about your device: the device model, the operating system and its version, the network type and the library version.
- Apple provides Sign in with Apple and distributes the app through the App Store and TestFlight, under Apple’s own privacy policy. If you test through TestFlight, Apple may share with us the crash reports and the feedback you send there.
- Cloudflare provides DNS for
meryas.app(it turns the name into our server’s address); game and website traffic does not pass through Cloudflare. E-mail sent tosupport@meryas.appis forwarded to our mailbox by Cloudflare Email Routing. - Let’s Encrypt issues the certificates that encrypt connections to our server; no player data is involved.
We do not share your data with anyone else unless the law requires it.
5. How long we keep it
- Guest player identity on the server: 6 hours after it was last seen, once it is not in a room.
- Rooms and games: until the room closes, or 15 minutes after all its players left.
- Account, display name, username, ratings and rating records: until you delete the account.
- A former username (its normalised form only): 30 days after a change, a deletion or a removal by moderation, or until a running voice ban ends if that is later; it is not linked to you after a deletion.
- Avatar number and the choice to hide from the leaderboard: until you delete the account. The leaderboard itself is not stored: it is rebuilt from the live data every minute.
- Sessions: 90 days after the last use, or earlier when you sign out or delete the account.
- Reports: 180 days after they were filed, then deleted automatically (a report about a guest with the hash of its install id goes with it).
- Public chat messages: in the server’s memory only, the last 100 of the channel, each with its author’s account id (and the ids of the players who reported it); gone at a restart, when the chat is switched off, when the author’s account is deleted, when the author’s username changes, or when the author is chat-banned or suspended. The text of a message that was reported: 180 days, with the report (section 2.9).
- Chat bans and suspensions: until they end, then they are deleted automatically; a permanent one until we lift it.
- Install id: on your device until you delete the app. On our server only its hash: in memory while you are connected (and, for the daily totals, until the end of that day UTC), with a report for 180 days, and in a ban of a guest’s device until the ban ends, then it is deleted automatically (a permanent one until we lift it). The first 12 characters of the hash also stay in the log of our actions for 365 days (section 2.5).
- Log of our actions on accounts and reports: 365 days. When an account is deleted, its id in the log is replaced with “deleted” and our notes on it are erased. Our actions on a guest’s device stay in it under the short reference of the device for the same 365 days, even after the ban has ended; they are not linked to any account.
- Deletion log: when an account is deleted, its account id (a random number that is linked to nothing once the account is gone) and the time of the deletion are kept for 21 days, and nothing else. We use it only to delete again the accounts deleted after a backup, if we ever have to restore the server from that backup (section 6). Each entry is deleted 21 days after the account was.
- Blocks: until you unblock, or until either account is deleted.
- A friendship: until either of you ends it or blocks the other, or either account is deleted. Likes: until either account is deleted. A friend request that is not accepted: 10 days from sending. Play invites: server memory only, 5 minutes at most.
- Voice identities, the automatic mute, the list of open tables (kept for two seconds), IP addresses used for connection limits, and the per-account count of friend requests and invites: server memory only.
- Who is watching or listening: server memory only, while they watch. Which accounts watched a table, were removed from it or left its match under way: server memory only, until the table closes. The daily and monthly totals of listening minutes (numbers only): replaced each day and each month.
- Daily totals (numbers only, section 2.1): 400 days, then deleted automatically.
- Web server access log for the game host: rotated by size as described in 2.6.
- Backups: one backup of the database and the game save file each day. On the server only the newest 14 are kept. Hetzner’s daily disk images (which include these backups) are deleted after 7 days. Every backup copy is deleted within 21 days. A safety copy taken on the server before a manual restore is deleted once the restore is confirmed, and within 21 days at most.
- E-mails to support: as long as needed to handle your request.
6. Deleting your account
In the app: Settings, Account, Delete account, then Delete permanently. This deletes at once, from the live server: your account, Apple user identifier, display name and username, your avatar number and your choice about the leaderboard, your sessions, your ratings and rating records, your blocks (yours and other players’ blocks of you), and your friends, friend requests and the likes you gave or received. You disappear from the leaderboard at once when you delete in the app, and within a minute when we delete the account for you by e-mail. You can keep playing as a guest.
- The normalised form of your username is kept for 30 days without any link to you, so nobody can take it at once and pretend to be you.
- Reports you filed or received stay until their 180 days end, but your identity in them is replaced with “deleted” and our review notes on them are erased.
- Your messages in the public chat are removed from the channel at once. If a report was made about one of them, the text of that message is erased from the report; the report itself stays, without your identity, until its 180 days end.
- If a voice ban, a chat ban or a suspension is running on the account, we keep only a one-way hash of your Apple user identifier with the ban’s end date (and, for a chat ban or a suspension, its kind, its reason and the date it was set), until the ban ends, or until we lift it if it is permanent, so the ban comes back if the same Apple ID signs up again. Our notes on it are erased, and so are the link to the report and the name of the team member who set it. Nothing else is kept.
- If you are in a ranked match that has not ended, the saved state of that room keeps your account id and your rating values from the start of the match until the room closes. The match result is not applied to the deleted account.
- Copies in backups are deleted as old backups rotate out, within 21 days (section 5). If we ever have to restore the server from a backup, an account deleted after that backup was made comes back with it, and we delete it again; the deletion log (section 5) is how we know which ones.
By e-mail: if you cannot use the app, write to support@meryas.app and give your @username if you have one. We will ask for details to confirm the account is yours before deleting it. We then delete it exactly as the app’s button does.
Guests have no account to delete: guest data on the server is removed automatically as described above, and deleting the app removes what is on your device, the install id included. A ban of the device you used stays until it ends, because we do not link it to you.
7. Your choices
You can ask us for a copy of the data we hold about you, or ask us to correct or delete it, by writing to support@meryas.app. We confirm the account is yours first, as for a deletion. The copy is a file (JSON) with your account details, your username history, your avatar number and your leaderboard choice, your ratings and rating records, the dates of your sessions, the blocks you made, your friends and friend requests (by the other player’s current username), the number of likes you gave and received (as counts only, because the details of a like name another player), the reports you filed and those about you (without naming the other player, and with the text of any message of yours in the public chat that was reported), your voice ban, chat bans and suspensions, and our log of actions on your account. It leaves out our short review notes on reports and bans, because they may name other players, and your install id, any ban of a device and our log entries about a device, because we do not link them to your account. You may also have the right to complain to a data protection authority.
8. Children
Meryas does not ask for your age and collects nothing more from anyone than what is described here. Voice chat, table chat and the public chat connect players with other players, including strangers. If you believe a child is using an account and want it deleted, write to us and we will delete it.
9. Security
Connections between the app and our server are encrypted (TLS). Session tokens are stored only as hashes. The database and the game save file are stored with owner-only file permissions, and the backups in a folder that only the server’s administrator can open.
10. Changes to this policy
When this policy changes, we will publish the new version on this page with a new effective date.