Who we are
Hearthsea is an online board game, played on the website at hearthsea.com and in the Hearthsea app for Android. Both use the same accounts and the same server, and this policy covers both. Hearthsea is run by a small independent team based in Amman, Jordan. In this policy, “Hearthsea”, “we” and “us” mean that team, and we are responsible for the personal data described here.
For any privacy question or request, email hello@hearthsea.com.
What we collect
Your account
- Your email address and username.
- Your password, stored only as a scrypt hash. We can’t read it, and nobody at Hearthsea ever sees it.
- The character, colours and other looks you pick for your profile.
- When the account was created and when you were last active, plus the dates (not times) you played, which we use to count daily players.
- The country you signed up from and the country you last played from, and your browser or app and device type in broad terms (for example “Chrome on Android”). We work the country out from your IP address when you connect and keep only the country, never the address. Other signed-in players see that country’s flag and name beside your username when they look for friends.
- Your friends list and friend requests, and the players you block, if you use them.
If you sign in with Google
Google Identity Services sends us a signed token, on the website and in the Android app alike. From it we keep your Google account ID and email address. Google also includes your name, which we use only to suggest a username the first time you sign in; we don’t store it. We never receive your Google password.
Your games
- Game stats, levels and achievements tied to your account.
- For online games: who sat at the table, the map and mode, start and end times, the number of turns, final scores and the winner. While a game is running, we also keep its moves so it can be resumed if the server restarts. When it ends, we keep a replay of it: its moves, and each seat’s name and colour, but not account IDs.
- For games against bots and pass-and-play games: when one ends, its settings and moves are sent so the server can check the result and credit your progress. We keep the result (the island, how it ended, the rounds and the time played), not the moves.
The emotes are a fixed set, and we don’t store them.
Chat and messages
There are three kinds of chat. Table talk is for the players at an online game; team chat in team games only reaches your team. Clan chat is for the members of a clan. Direct messages are between two friends. Each message holds your username, the text and the time it was sent.
Chat is stored in Firebase Realtime Database, a Google service that runs it for us, not in our own database. Only the people in that chat can read it: our server gives each player a pass for the chats they belong to, and Firebase refuses everyone else. We can read chat when we look into a report.
- Table talk is deleted a day or two after the game ends.
- A direct conversation is deleted when the two of you stop being friends (either of you removes the other or blocks them), and when either account is purged.
- Clan chat stays in the clan’s chat, including after you leave the clan or delete your account. Email us and we’ll remove your messages.
The worst words are masked in clan chat, and in every chat in the Android app. Blocking a player hides the two of you from each other in chat, emotes, friend requests and room invites. When you report a player, we keep the reason, your note if you write one, and the game; a report from a game or a direct conversation also keeps a copy of its last 20 messages so we can see what happened.
Support messages
When you write to us from the game’s support form, we keep what it’s about, your message, your email address (your account’s, or the one you give us if you’re not signed in), a short note of where in the game you were, your country and your device type. Our replies are kept with it, sent to your email and shown in the game, and you can write back from there.
Things you make and share
If you use them: a clan’s name, motto and flag; the boards you make or publish and the likes you give; and your votes in polls, with any answer you type in.
Purchases
On the website, Stripe takes the payment. We keep a record of what you bought, the price, the currency, its status, the Stripe references for the payment and your Stripe customer ID. Stripe handles the card itself, so we never see or store your full card number.
In the Android app, Google Play takes the payment. The app sends us Google Play’s purchase token, our server asks Google what it stands for, and we keep the token, Google’s order ID, the product, and when it was bought and when it ends or was refunded. Google tells us when a subscription renews, ends or is refunded. We never see your payment details. So a purchase can be tied to your Hearthsea account, our server gives Google Play a code made from your account number, which means nothing outside Hearthsea.
Either way, we also keep what your account is entitled to and until when.
Technical data
Every request to our server comes with your IP address. The game uses it in memory to limit how fast one address can send requests (for example, failed sign-ins and password-reset emails), and forgets it within an hour. The country comes from Cloudflare, which sits in front of our server, or from a copy of a country database on our own server, and we keep only the country. We don’t write IP addresses to our database. Our web server keeps no access logs for Hearthsea. Its error log can record an IP address when a request fails, and we use it only to find faults and stop abuse.
- Crash reports. When a game ended because the page or the app was closed by your device (usually for lack of memory), the next time you open it sends a short report: when the game started and stopped, the mode, map and turn, the graphics quality, the screen size, memory use, and the browser’s or app’s user-agent text. We add your account if you’re signed in, your country and your device type.
- Error reports. When something in the game breaks, it sends the error message and where it happened, a few a session at most (the Android app removes email addresses from them first). We keep it as one line in our error log, with your device type and your account number if you’re signed in.
- Store visits. When you’re signed in, we note when you open the store, look at an item or an offer, and tap Buy, with the item and where in the game it was.
We also count page views per day as a single total, with nothing that identifies who viewed.
How we use it
- To run your account: sign you in, keep you signed in, and show your username, avatar and stats to the people you play with.
- To run online games, chat and messages, and keep your progress, achievements and friends in sync across devices, on the website and in the app.
- To take payments, unlock what you paid for, and handle refunds, and the renewals and cancellations of monthly subscriptions.
- To send account emails you need, such as password reset links, a notice when your password changes, and our answers to your support messages. We don’t send marketing email.
- To keep the game fair and safe: rate limiting, spotting abuse, masking the worst words in chat, and acting on cheating or harassment reports.
- To understand, in aggregate, how many people play and which modes and maps they use, so we know what to fix and build next.
- To find and fix what breaks, from crash and error reports.
- To see how the store works for players: how many open it, look at an item and tap Buy, so we can make it clearer.
We don’t show ads and we don’t sell or rent your data. On the public pages (the home page, pricing, rules, the blog, sign-in and these policies) we use Google Analytics to count visits from people who aren’t signed in. It doesn’t run inside the game or in the Android app, and it doesn’t run for you once you’re signed in. The Android app has no ads, no analytics and no crash-reporting tools from other companies.
Legal bases
If you’re in the European Economic Area or the United Kingdom, the GDPR asks us to name the legal basis for each use.
- Contract: running your account, your games, chat and messages, and your purchases is the service you signed up for.
- Legitimate interests: security logs, rate limiting, preventing cheating, fraud and abuse (blocks, reports and the word filter), crash and error reports, store visits, and aggregate counts of how the game is used. We keep these to the minimum that does the job.
- Legal obligation: keeping payment records that tax and accounting law require.
Who else handles it
A few companies process data for us so the game can work. Each gets only what its part needs.
- Stripe processes payments. It receives your card details directly from you, and your email so it can send receipts. Stripe’s own privacy policy covers what it does with them.
- Google Play takes payments in the Android app. Google receives your payment details from you, and tells our server what you bought and when a subscription renews, ends or is refunded. Google’s privacy policy covers what it does with them.
- Google provides “Sign in with Google”, if you choose it. When you use the Google button, Google’s script loads from Google’s servers and Google’s privacy policy applies to that sign-in.
- Google’s Firebase Realtime Database stores chat and direct messages for us, with each player’s account number and username.
- Brevo sends our account emails, so it receives your email address, your username and the message itself.
- Google Analytics measures visits to our public pages from signed-out visitors: pages viewed, how you arrived, your rough location, and your device and browser type. Google signals and ad personalisation are turned off. Google’s explanation of how it uses this data applies.
- DigitalOcean hosts our server and database, and Laravel Forge is the tool we use to manage that server.
- Cloudflare sits in front of our server: every request passes through it, and it tells us which country a request comes from. It also stores our nightly database backups.
We may also share data when the law requires it, such as a valid court order, or to protect players or the service from fraud or abuse. If Hearthsea were ever sold or merged, your data would move with the game and this policy would continue to apply until you’re told otherwise.
Where it’s stored
Our server and its MySQL database are hosted by DigitalOcean in New York, in the United States. If you play from elsewhere, your data travels to and is stored in the US. Chat and direct messages are stored by Firebase in Belgium, in the European Union. Database backups are stored by Cloudflare. Where the GDPR applies, we rely on our providers’ standard contractual clauses or equivalent safeguards for those transfers.
How long we keep it
- Account data, stats, achievements, friends, blocks, purchase records, store visits, clans, boards and poll votes: while your account exists.
- Sign-in sessions: up to 30 days, or until you sign out.
- Password reset links: they expire after one hour.
- IP addresses used for rate limiting: up to one hour, in memory only.
- Table talk: deleted a day or two after the game ends.
- Direct messages: until the two of you stop being friends, or either account is purged.
- Clan chat: while the clan’s chat exists, unless you ask us to remove your messages.
- Reports: until the account that made the report, or the one reported, is purged.
- Support messages and our replies: kept so we can follow up. When your account is purged, the text, your email address, the context, your country and your device type are removed from them.
- Replays of online games: 180 days.
- Crash reports: kept while they help us find faults. When your account is purged, they’re no longer linked to it.
- Server error logs, which hold the error reports: our web server’s are rotated daily and deleted after 52 days; the game’s own is capped in size, so older lines are dropped as new ones come in. We keep no access logs.
- Backups: the database is backed up nightly and each backup is deleted after 30 days, and the server is backed up weekly with older copies replaced by new ones, so deleted data disappears from backups as older copies go.
When an account is deleted, we purge it 30 days later, as explained in Deleting your account. A few things stay after that. Summaries of finished online games, and their replays until they expire, keep the usernames that played in them, so the other players’ histories stay correct. Clan chat messages stay unless you ask us to remove them. And our internal admin log keeps a short record of actions taken on accounts (for example, that an account was deleted), which can include the username and email at the time. Stripe and Google keep their own payment records for as long as financial law requires.
Your rights
Wherever you live, you can ask us to:
- tell you what personal data we hold about you and send you a copy;
- correct anything that’s wrong;
- delete your account and its data;
- export your data in a machine-readable format (JSON);
- stop or limit a particular use, or object to it.
Email hello@hearthsea.com from the address on your account, or tell us your username. We may ask you to confirm the request from that address before acting on it. We reply within 30 days, and requests are free.
In the EEA and UK you can also complain to your local data protection authority. California residents have the rights the CCPA gives them, including to know, delete and correct. We don’t sell or share personal information for cross-context advertising, and we won’t treat you differently for using any of these rights.
Deleting your account
This is how to delete your Hearthsea account, whether you play on the website or in the Hearthsea app for Android. You can do it in two ways:
- In the Android app: open Me, then Settings, tap Delete account and type your username to confirm.
- From anywhere: email hello@hearthsea.com from the address on your account, or tell us your username, and ask us to delete it.
We mark the account deleted straight away: you’re signed out everywhere and it can no longer sign in. Thirty days later it’s purged for good. That deletes its email address, username, password and profile, sessions, friends and friend requests, blocks, private conversations, purchase records (Stripe and Google Play) and entitlements, stats, levels, achievements, game seats, progress, trial record, activity dates, clan membership, the boards it made and the likes it gave, poll votes, store visits, and reports made by it or about it. Its support messages keep only their topic and date. The 30-day gap is there so a mistaken or malicious request can be undone; write to us within that time if you change your mind.
Some things are kept after the purge: summaries of finished online games, and their replays for up to 180 days, keep your username so the other players’ histories stay correct; clan chat messages stay unless you ask us to remove them; crash reports stay without a link to you; our admin log keeps a short record that the account was deleted; and backups hold a copy for up to 30 days until they’re replaced. See How long we keep it.
Subscriptions
The expansions are sold as monthly subscriptions, on the website through Stripe and in the Android app through Google Play.
- A subscription you pay for in Google Play is billed by Google, and deleting your Hearthsea account doesn’t cancel it. Cancel it first in the Play Store: tap your profile picture, then Payments & subscriptions, then Subscriptions.
- A subscription you pay for on the website can be cancelled on your account page on the website. Deleting your account in the Android app stops it at once. A deletion by email doesn’t cancel it by itself: cancel it first, or tell us in the same email and we’ll cancel it for you.
Children
Hearthsea isn’t directed at children under 13, and you must be at least 13 to create an account. If you’re under the age of digital consent where you live, a parent or guardian needs to agree to you using it. If you think a child under 13 has given us personal data, email us and we’ll delete the account.
Security
The site is served only over HTTPS, and the Android app talks to our server only over HTTPS. Passwords are hashed with scrypt, session tokens and password reset tokens are stored as hashes, and the session cookie is HttpOnly. Access to the server and database is limited to the people who run Hearthsea. No system is perfectly secure, but if a breach affects your data we’ll tell you and the relevant authorities as the law requires.
Changes to this policy
If we change this policy, we’ll update the effective date at the top. If a change affects how we use data you’ve already given us, we’ll tell you by email or in the game before it takes effect.
Contact
Questions, requests and complaints go to hello@hearthsea.com. The terms you agree to when you play are in our terms of service.