Privacy policy
Last updated: 18 November 2026. This policy describes the game from the November 2026 update, which adds ads and in-app purchases.
In short
- From age 13 the game creates a guest account for you on its own. No e-mail, phone number, password or social login.
- We store a random player ID, your age group, the village name you choose, a snapshot of your village and your Endless mode scores.
- On the Endless mode leaderboards other players see your village name, the waves you reached and your Town Hall level. They never see your player ID.
- On other players’ maps your village appears as a real village: its name, its look and your Town Hall level, but only while your account is active. You can block players and report a village name; blocking works in both directions. Other players never see your player ID, in chat as well.
- From age 16, once you have accepted the terms of use in the game, you can send text messages to other players, one to one. Messages are kept for 90 days. Links, e-mail addresses and banned words are masked before a message is stored.
- From age 13, if you turn notifications on, the game registers your phone’s notification token with our server so that we can tell you about attacks on your village and, from age 16, new messages. Google Firebase Cloud Messaging delivers them, and on iPhone Apple’s push service. A notification never contains the text of a message. See Notifications.
- From age 13 the game shows ads from Google AdMob: rewarded ads that you choose to watch, and from level 11 an occasional full-screen ad after a won battle. Google’s ad software collects device data, such as the advertising ID, for this. In the EEA, the UK and Switzerland Google’s consent form asks you first; on iPhone the game asks once whether it may track you. Players aged 13–15 get only non-personalised ads and are never asked about tracking.
- You can buy gems and items in the shop. Google Play or the App Store takes the payment; we never see your card or payment details. Our server checks every purchase with Google or Apple before the game gives you anything, and keeps a record of it.
- Under 13 there are no ads, no purchases, no notifications from our server and no gameplay statistics, and the ad, purchase, notification and statistics software is never started.
- From age 13 the game can send anonymous gameplay statistics (Google Analytics for Firebase): never your player ID, your village name, your messages or your advertising ID. In the EEA, the UK and Switzerland only from age 16 and only if you say yes; elsewhere on unless you turn it off in Settings → Anonymous gameplay stats. See Anonymous gameplay statistics.
- We have no crash-reporting service of our own, and the game’s own code does not read your device’s advertising ID or any other device identifier, except the notification token your phone gives the game when you turn notifications on.
- The data is stored with Amazon Web Services in Frankfurt, Germany.
- You can delete your account at any time, in the game or with our request form. Questions: hearthold.support@gmail.com.
Who is responsible
Hearthhold is made and published by o7games, an individual developer based in Turkey.
Data controller: o7games (the “data controller” under Turkey’s Personal Data Protection Law No. 6698, “KVKK”, and the “controller” under the EU General Data Protection Regulation, “GDPR”).
To contact us or to use your rights, write to hearthold.support@gmail.com or send us a message with the request form.
What we store
Your guest account
From age 13 the game opens an account on our server in the background. For it we store:
- Player ID
- A random code of 26 letters and digits that identifies your account. Other players never see it.
- Device secret, hashed
- Your phone keeps a random secret that proves requests really come from it. The server stores only a SHA-256 hash of that secret, never the secret itself.
- Age group
- “13–15” or “16 and over”. The game asks your birth year once and works out the group. The year stays only on your phone, inside the game’s save, so the game can move you to the next age group when you are old enough. It is never sent to our server: the server stores only the age group.
- Village name
- The name you choose, 3 to 16 characters. A filter blocks offensive names. Other players see it on the Endless mode leaderboards and on their map.
- Your village
- A snapshot of your village: buildings and their levels, decorations, banner colour, hero, garrison, resource stock and Town Hall level. We use the Town Hall level to place you in an Endless mode league. Other players see part of it on their map (see “Your village on other players’ maps” below) and your Town Hall level on the leaderboards.
- Times
- When the account was created and last seen, and when the name and the village last changed.
Your game progress (coins, levels, settings) is saved only on your phone; there is no cloud save. The server receives only the account data above and your Endless mode runs.
Endless mode runs and leaderboards
When you play Endless mode online, the server records each run: a run ID, the waves you reached and how long the run took. It checks that the score is real and keeps your best score of the week in your weekly league and on the leaderboards. A leaderboard row shows the village name, the waves, the Town Hall level, when the score was made and a crown if that player won their league the week before. Instead of a player ID, other players’ rows carry a code that changes every week. You need an account and a village name to take part; offline, Endless mode plays unranked.
Your village on other players’ maps
Other players’ maps can show your village as a real village. What they see is: your village name, your Town Hall level, your banner colour, your hero and its level, how many defenders are in your garrison, and one defence value worked out from your buildings, and whether you can receive messages. Nothing else from your village or account is shown. Your village is shown only if you have a village name, you are 13 or over (all accounts are) and your account was active in the last 14 days. Other players’ maps identify your village with a key that is different for every pair of players; it is never your player ID.
Messages (chat)
Chat is for players aged 16 and over who have a village name and have accepted the terms of use (version 2) in the game. It is one to one: you write to one player at a time. To deliver your messages we store:
- each message: the text (up to 300 characters), who sent it, who it is for and when;
- for each conversation, an entry for each of the two players, with a reference to the other player’s account (their current village name is looked up when you open your messages, and the reference is never shown to anyone), the text and time of the last message, and how many messages you have not read yet;
- that you accepted the terms of use, and which version.
The other player sees your village name and your village, never your player ID. Before a message is stored, an automatic filter masks links, e-mail addresses and banned words with ***, and makes any markup harmless. We keep a message for 90 days and then delete it; the conversation entries are deleted after 90 days too. “Delete this conversation” hides the conversation for you only: the other player still has it, and it stays on our server until the 90 days are over. To stop abuse there are limits: 8 messages per minute, 200 per day and 10 new conversations per day. We do not read your conversations on our own; we look only at the last 20 messages of a conversation when it is reported.
Messages are stored on AWS in Frankfurt together with the rest of your data. They never pass through Gmail or any other e-mail service.
Blocks and reports
Blocks. You can block a player from their village panel. Blocking works in both directions on the map: their village no longer appears on your map, and yours no longer appears on theirs. In chat, a blocked player’s messages are never shown to you (we still store them, hidden from you, for the 90 days) and you cannot write to a player you blocked. We keep a block for as long as the account exists, and you can undo it in Settings.
Reports. You can report a village name from the village panel, and a conversation from inside the conversation. A report on a village name sends us the name as it is at that moment. A report on a conversation sends us, as evidence, the last 20 messages of that conversation. We take them from our own server, not from your phone, and they include messages you have hidden for yourself. The player you report never learns who reported them. Every report sends an e-mail notice to us (the data controller) through Amazon SNS; the e-mail carries no names, no player IDs and no message text. If three reports come from three different accounts that are at least 3 days old within 24 hours, the reported player’s messaging is switched off automatically until we have looked at it. We may also switch a player’s messaging off by hand if they abuse it. Reports, with their evidence, are kept until we have handled them and then for one more year.
Notifications
The game can tell you with a notification on your phone when another player has attacked your village and, from age 16, when another player has sent you a message. These come from our server. Reminders about your own village (a building is ready, your shield ends soon) are made by your phone itself and send nothing to us.
Notifications use the game’s Settings → Notifications switch and your phone’s permission for notifications: nothing is registered before you have said yes to both. Under the switch you can turn Attacks on my village and Messages off one by one. When you turn notifications on (from age 13, with online features on), Google’s Firebase software in the game gets a notification token for your phone from Google (on iPhone through Apple’s push service), and the game sends it to our server. For each phone we store:
- Notification token
- The address Google gives your phone for notifications. We store the token itself, because it is needed to send you a notification, and a one-way hash (SHA-256) of it as the key of the record. Other players never see it, and it is never written to our logs.
- Phone and language
- Whether the phone is an Android phone or an iPhone, and the language the game was in, so that the notification is in your language.
- Time-zone offset
- How many minutes your phone’s clock is ahead of or behind UTC, so that no notification arrives at night. It is not your location.
- Your choices
- Whether “Attacks on my village” and “Messages” are on.
- Times
- When the phone was registered and when it last confirmed its token, and on your account when a phone last confirmed one.
An account can have up to 5 phones; a sixth replaces the one that confirmed its token longest ago.
What a notification says. An attack notification gives the attacking village’s name and what you lost (coins, timber and stone), or, if your guards held, how many soldiers the attackers lost. A message notification says only which village wrote to you. A notification never contains the text of a message, and never your player ID or anyone else’s. If the other player’s account is gone, or we have hidden their village name or switched off their messaging, the notification carries no name. Notifications are not shown while the game is open.
When none are sent. No notifications between 22:00 and 09:00 by your phone’s clock: a notification due at night is dropped, not delayed, and the news waits for you in the game. At most 2 attack notifications a minute and 6 a day, and 2 message notifications a minute and 10 a day; a message notification comes only for the first unread message of a conversation. Nothing is sent about a player you have blocked or who has blocked you. An attack notification that cannot be delivered within 12 hours, or a message notification within 6 hours, is dropped.
Who delivers them. Our server hands each notification (its title, its text and the token) to Google Firebase Cloud Messaging, which delivers it to your phone on our behalf as our data processor; for iPhones, Firebase passes it on through Apple Push Notification service. To deliver notifications, Google’s Firebase software on your phone also sends Google a Firebase installation ID (a random code for this installation of the game, not for you or your phone) and technical details such as the app version, the phone’s system version and the software versions. Notifications are not counted in the anonymous gameplay statistics. Google and Apple never receive your player ID from us. Notifications and tokens are never used for ads or to track you.
Ages. Under 13: never; there is no account, and the notification software is never started. 13 to 15: attack notifications only, because chat starts at 16. 16 and over: attacks and messages. Our server checks the age group again before every notification.
Turning them off. Turn off the Notifications switch, or both kinds, in Settings, or turn notifications off for Hearthhold in your phone’s settings. The next time the game is open and online, it asks our server to delete your phone’s token and deletes the token on the phone too. This works even while we have paused notifications on our side.
Anonymous gameplay statistics
From age 13 the game can send anonymous gameplay statistics with Google Analytics for Firebase, so that we can see how far players get, which levels are too hard and whether our own adverts for the game bring players in. You choose with the Settings → Anonymous gameplay stats switch, at any time.
- When it is on. The game looks at your phone’s country signals: its SIM, its mobile network, its region setting and its time zone. If any of them points to the EEA, the UK or Switzerland, or none of them can be read, the statistics are off until you say yes to the game’s question (from age 16); players aged 13–15 there are never asked and never measured. Elsewhere they are on unless you turn them off. Under 13, and before you have told the game your birth year, they are always off and Google’s Analytics software is never started for them.
- What it counts. That the game was installed and opened (Google’s “first open”) and how long you played (sessions); finishing the opening; each campaign battle’s world, level, win or loss and stars; your Town Hall level when it rises; which hero joined you; how many waves an Endless mode run reached; whether a raid was won or lost. Google’s software adds technical details such as the phone model, the system version, the app version and the country, which Google works out from your masked IP address.
- What it never sends. Your player ID, your village name, your messages or anything you type; your advertising ID (it is switched off for Analytics, and on iPhone the part of Google’s software that could read it is not in the game) or the iPhone’s vendor identifier. Analytics gives each installation of the game a random app-instance ID that is not tied to you, your account or your phone. The statistics are not used to personalise ads, and the game shows no tracking question for them.
- Google Ads. We link these statistics to our Google Ads account only to count how many installs our own adverts for Hearthhold bring (the “first open” of an installation that came from one of our adverts), so that Google can show those adverts to people more likely to enjoy the game. Ad personalisation is always denied for this data, and for players aged 13–15 no data is passed on for Google Ads at all.
- Turning it off. Turn off Settings → Anonymous gameplay stats. Collection stops at once on your phone. Notifications are never counted in the statistics.
Purchases
You can buy gems, the Starter Pack, Master Builder and No Ads in the shop. Buying needs your guest account (online features on), because our server checks every purchase. Google Play or the App Store handles the payment under its own terms and privacy policy. We never receive your card number, bank details, name or e-mail address from the store.
How a purchase is checked: when you buy, the game sends our server the store’s receipt for that order (a Google Play purchase token or an App Store transaction ID). Our server asks Google (Google Play Developer API) or Apple (App Store Server API) whether the order is real and paid, and only then tells the game what to give you. Each order is given once. If you are offline, the game keeps the order and sends it when you are back online. The game also tags each order in the store with a code worked out from your player ID (not the player ID itself), so that the store’s record of the order can be matched to your account.
For each purchase we store:
- a record of the order: a one-way hash (SHA-256) of the store’s order ID, never the ID or the receipt itself; the product; the store; when it was bought; what it gave (for example, how many gems); whether it was a test purchase; whether it was refunded; whether the store’s tag matched your account; how many other accounts its lasting items were restored to; and which account it belongs to (your player ID);
- on your account: one entry per purchase with the product, the time, whether it was a restore, and whether the game confirmed that it received it.
Items you bought once (Starter Pack speed-up, Master Builder, No Ads) can be restored on a new install from the same store account: on iPhone with Settings → Restore purchases, on Android automatically when the store reports them. Gems and coins are not restored; your progress is saved only on your phone.
Refunds
Refunds are made by the store where you paid (see the terms of use). When Google or Apple refunds or cancels an order, they tell our server: Google through a daily check of its list of cancelled purchases, Apple through a signed notification and its notification history. Our server marks the order as refunded and keeps a note on your account until the game has applied it. The game then takes back the gems that purchase gave you, but never below zero; coins and lasting items stay.
Ads (Google AdMob)
The game shows ads from Google AdMob, Google’s ad service:
- Rewarded ads play only when you tap a WATCH button, for example for free gems or a revive.
- Full-screen ads may play after a won campaign battle from level 11 on: at most one every 3 battles and every 4 minutes, never in your first session, never after a defeat and never in Endless mode.
- No Ads removes the full-screen ads and gives you rewards without watching. Players who have bought anything never get full-screen ads.
To choose, show and measure ads, and to prevent ad fraud, Google’s ad software in the game (the Google Mobile Ads SDK and Google’s consent tool, the User Messaging Platform) collects from your device and sends to Google:
- device identifiers: the advertising ID (on Android; you can reset or delete it in your phone’s settings), on iPhone the advertising identifier (IDFA) only if you allow tracking, and an app-specific identifier (Android’s app set ID, Apple’s identifier for vendors);
- your IP address, from which Google may estimate your approximate location (country or city, never your exact location);
- ad and app interactions: the ads you are shown, taps and video views, app launches;
- diagnostics: how the app and the ad software perform (for example launch time, hangs, energy use) and crash logs of the ad software.
Google uses this data under its own privacy policy (policies.google.com/privacy); how Google uses data from apps that show its ads is explained at policies.google.com/technologies/partner-sites. For personalised ads Google acts as a separate controller. Our server receives none of this data; AdMob gives us only totals, such as how many ads were shown in a country and what they earned.
Who gets ads:
- Under 13, or before you have answered the age question: no ads. The ad software is not started, so it collects nothing.
- 13 to 15: ads are requested as for a user under the age of consent, so Google shows only non-personalised ads, and the game never asks about tracking.
- 16 and over: ads, which may be personalised; see your choices below.
- Everyone: ads are limited to content suitable for teens.
Your choices:
- EEA, UK and Switzerland: before any ad is requested, Google’s consent form asks whether Google and its ad partners may use your data. If you do not agree, you get only non-personalised or limited ads. You can change your answer at any time in Settings → Privacy choices (shown where Google’s form applies).
- Android: you can reset or delete your advertising ID in your phone’s settings (Settings → Google → Ads on most phones, or Settings → Security & privacy → Privacy → Ads).
- iPhone: see “Tracking on iPhone” below.
Tracking on iPhone
On iPhone, Apple’s App Tracking Transparency question (“Allow ‘Hearthhold’ to track your activity across other companies’ apps and websites?”) appears once, for players aged 16 and over, from the second time you open the game, on the village screen and before any full-screen ad. If you tap Allow, Google may use your device’s advertising identifier (IDFA) to personalise and measure ads. If you tap Ask App Not to Track, the IDFA is not available and ads are still shown, less personalised. You can change this at any time in iPhone Settings → Privacy & Security → Tracking. Players aged 13–15 are never asked, and their IDFA is never used.
Requests and e-mails you send us
When you write to us with the request form, we store what you send: the type of request, your message and, if you give them, a way to reach you and your player ID. When you e-mail us, we keep your e-mail address and your message so that we can answer you.
Technical logs
Our server keeps technical logs, such as when a request ran and whether it failed, and sometimes your player ID, so that we can find and fix faults. They never contain your device secret or your notification token. As with any internet service, our servers see your device’s IP address while it is connected; we do not store it with your account.
Not in the game
Apart from the anonymous gameplay statistics (see above), the game has no analytics and no crash-reporting service. The game’s own code does not read your device’s advertising ID, Android ID or any other device identifier, except the notification token your phone gives the game when you turn notifications on (see “Notifications”); the advertising identifiers are read only by Google’s ad software, as described under “Ads”. If we add analytics or anything else that changes what is collected, we will update this policy before it goes live.
Why we use it, and on what legal basis
- To run your account and the online features. This is needed to provide the game you use (KVKK art. 5(2)(c); GDPR art. 6(1)(b)).
- To show you on the Endless mode leaderboards and to place you in a league by Town Hall level: your village name, the waves you reached and your Town Hall level, never your player ID. Same legal basis.
- To show your village on other players’ maps: your village name, the look of your village and your Town Hall level, never your player ID. Same legal basis.
- To deliver your messages to the player you write to, and to show you your conversations and unread counts. This is needed to provide the chat you use (KVKK art. 5(2)(c); GDPR art. 6(1)(b)).
- To send you the notifications you turned on: storing your phone’s notification token and choices, and handing each notification to Google Firebase Cloud Messaging. This is needed to provide the feature you turned on (KVKK art. 5(2)(c); GDPR art. 6(1)(b)).
- To count anonymous gameplay statistics and the installs our own adverts bring. In the EEA, the UK and Switzerland, with your consent, given in the game’s question or the Settings switch (GDPR art. 6(1)(a)). Elsewhere, our legitimate interest in improving the game and in knowing whether our adverts work (KVKK art. 5(2)(f); GDPR art. 6(1)(f)); you can object at any time with the Settings switch.
- To keep the game safe: a filter keeps offensive village names out and masks links, e-mail addresses and banned words in messages, the server checks that Endless mode scores are real, blocks and reports let players protect themselves and help us deal with misuse, and limits slow down misuse (for example, a name can be changed once a day, and messages are limited per minute and per day). Our legitimate interest in a safe and fair game (KVKK art. 5(2)(f); GDPR art. 6(1)(f)).
- To sell you items and give you what you paid for: checking each purchase with Google or Apple, giving it exactly once, restoring lasting items and taking back gems after a refund. This is needed to perform the purchase you make (KVKK art. 5(2)(c); GDPR art. 6(1)(b)).
- To keep purchases safe from fraud: keeping the record of each order so that a receipt can never pay twice and refunds can be applied. Our legitimate interest in preventing fraud (KVKK art. 5(2)(f); GDPR art. 6(1)(f)).
- To show ads that pay for the free game. In the EEA, the UK and Switzerland, Google uses your data for personalised ads only with your consent, given in Google’s consent form (GDPR art. 6(1)(a)). Elsewhere, our legitimate interest in funding the free game with ads (KVKK art. 5(2)(f); GDPR art. 6(1)(f)); ads for players aged 16 and over may then be personalised, which you can limit in your phone’s ad settings. On iPhone the advertising identifier is used only if you allow tracking, and for players aged 13–15 ads are never personalised.
- To answer and carry out your requests, sent with the form or by e-mail. For requests about your personal data, our legal obligation (KVKK art. 5(2)(ç); GDPR art. 6(1)(c)); for other questions, our legitimate interest in answering them (KVKK art. 5(2)(f); GDPR art. 6(1)(f)).
- Technical logs: our legitimate interest in a working and secure service (KVKK art. 5(2)(f); GDPR art. 6(1)(f)).
All of this data is collected electronically: automatically through the game, and through the request form or e-mail when you write to us.
Who sees your data
- Other players: on the public Endless mode leaderboards, your village name, the waves you reached and your Town Hall level. Never your player ID or anything else.
- Other players, on their map: your village name, the look of your village (building levels, decorations, hero and its level, garrison size) and your Town Hall level, while your account is active. Never your player ID; the map uses a key that differs for every pair of players.
- The player you write to: your messages, your village name and your village. Never your player ID.
- Amazon Web Services (AWS): stores and processes the data on our behalf as our service provider (data processor) and may not use it for anything else.
- Google Play or Apple: when you buy, the store takes your payment under its own terms and privacy policy. Our server sends the store the receipt of your order, and the code worked out from your player ID, to check it; the store tells our server about refunds.
- Google (AdMob): Google’s ad software in the game collects the data described under “Ads” straight from your device, for players aged 13 and over. Google may share it with its ad partners, as its consent form and privacy policy explain.
- Google (Firebase Cloud Messaging) and Apple (Apple Push Notification service): only if you turn notifications on. Google delivers each notification on our behalf as our data processor, under Google’s Firebase data processing terms, and for iPhones hands it to Apple’s push service. They receive the token and the notification’s title and text, plus what Google’s Firebase software on your phone sends (see “Notifications”). Never the text of your messages and never your player ID.
- Google (Analytics for Firebase, Google Ads): only while the anonymous gameplay statistics are on. Google processes the statistics on our behalf as our data processor, under Google’s data processing terms, and counts for our Google Ads account the installs our own adverts brought. Never your player ID, your village name, your messages or your advertising ID.
- Google (Gmail): only if you e-mail us. Our mailbox is a Gmail account, so Google holds the e-mails you send us.
- Nobody else. We do not sell your data. Apart from Google’s ad software and the install counts for our own adverts described above, we do not share your data with advertisers, and we build no advertising profiles ourselves. We give data to authorities only when the law requires it.
Where it is stored
The data is stored on AWS servers in Frankfurt, Germany (region eu-central-1), and managed by us from Turkey. For players in the EU and EEA, the data is stored inside the EU. For players in Turkey, storing the data there is a transfer of personal data abroad; we make this transfer only on a basis allowed by article 9 of KVKK. The data that Google’s ad software collects, and the payment data the stores hold, are processed by Google and Apple on their own servers, which may be outside Turkey and the EU. If you turn notifications on, Google Firebase Cloud Messaging and Apple’s push service process your phone’s token and each notification on their own servers, which may also be outside Turkey and the EU. For players in Turkey this is a transfer abroad, which we make only on a basis allowed by article 9 of KVKK; for players in the EU and EEA, Google processes this data for us under its Firebase data processing terms. The same holds for the anonymous gameplay statistics, which Google Analytics processes on its own servers.
How long we keep it
- Account data
- Until you delete your account, in the game or with the form. When you delete it, it is removed from our server straight away. An account that is not used online for 180 days is deleted automatically, together with its village.
- Endless mode records
- Weekly records and leaderboard rows are deleted 14 days after the week ends, or straight away when you delete your account.
- Your village on other players’ maps
- Only while your account is active (used online in the last 14 days). The village snapshot and your profile are removed after 180 days without use, together with the account.
- Messages and conversations
- 90 days, then deleted. The conversation entries are also deleted after 90 days. “Delete this conversation” only hides it for you. When you delete your account, your conversations and the messages in them are deleted on both sides, straight away.
- Notifications
- A phone’s token and choices are kept until you turn notifications off, until you delete your account, until Google tells our server that the token no longer works, or until 60 days after your phone last confirmed it, whichever comes first. The game confirms the token when something has changed and at least once every 7 days when you play online. The time on your account when a phone last confirmed its token is kept until you delete your account.
- Blocks
- As long as the account exists. When you delete your account, all blocks you made and all blocks against you are deleted.
- Reports
- Until we have handled them, then one more year; this includes the copy of the last 20 messages in a conversation report. Reports about you and reports by you are deleted when you delete your account.
- Purchases
- The entries on your account: until you delete your account. The record of each order: kept with no end date, because it is what stops one receipt from paying twice and lets a refund be applied. When you delete your account, the record’s link to your player ID is removed; what stays (the hashed order ID, the product, the time and the refund mark) no longer points to you or your account. A refund note on your account: until the game has applied it, or until you delete your account.
- Ads data
- We hold none. Google keeps the data its ad software collects under its own retention rules (policies.google.com/technologies/retention).
- Anonymous gameplay statistics
- We hold none on our server. Google Analytics keeps the event data for 2 months (its shortest setting), then only in totals that no longer point to an installation.
- Requests sent with the form
- 1 year.
- E-mails you send us
- As long as we need them to handle your request.
- Technical logs
- 14 days.
If you remove the game without deleting your account, the account stays on our server until you ask us to delete it, or until it is deleted automatically after 180 days without being used online. Write down your player ID first: it is how we find your account.
Age rules
Hearthhold is meant for players aged 13 and over. The game asks your birth year once, the first time you start it. The year stays only on your phone, so the game can move you to the next age group when you are old enough (13 or 16); our server stores only the age group.
- Under 13: the game plays fully offline. No account is created and nothing is sent to our server. No ads, no purchases, no notifications from our server and no gameplay statistics: the ad, purchase, notification and statistics software is never started.
- 13 to 15: a guest account, online features and purchases. Ads are non-personalised only, and the iPhone tracking question is never shown. Chat is not open to this age group. If you turn notifications on, you get notifications about attacks on your village only. Anonymous gameplay statistics only outside the EEA, the UK and Switzerland, and never for Google Ads.
- 16 and over: a guest account, online features, purchases, ads (which may be personalised; see “Your choices” under “Ads”) chat (once you have accepted the terms of use in the game) and, if you turn them on, notifications about attacks and messages.
Online features are optional. If you delete your account, they stay off on that phone until you turn them on again with Settings → Account → Turn online features on, which creates a new account. Without them you can still play the campaign; Endless mode leaderboards need an account.
If you think a child under 13 has an account, tell us at hearthold.support@gmail.com or with the request form and we will delete it.
Your rights
Under article 11 of KVKK you can ask us:
- whether we process your personal data and, if we do, for information about it;
- why we process it and whether we use it only for that;
- who we pass it to, in Turkey or abroad;
- to correct it if it is incomplete or wrong;
- to delete or destroy it, under the conditions of article 7 of KVKK;
- to tell those we passed it to about a correction or deletion;
- to object to a result against you that comes only from automated analysis of your data;
- for compensation if unlawful processing caused you harm.
Under the GDPR you have similar rights: access, rectification, erasure, restriction of processing, data portability, and objection to processing based on our legitimate interest. You can also complain to a data protection authority: in Turkey, to the Personal Data Protection Board after first applying to us; in the EU, to the authority in your country.
How to use them
- Delete your account: in the game, Settings → Account → Delete my account. It happens at once. Or send a deletion request with the request form. Deleting your account removes your village from other players’ maps, all blocks (those you made and those against you), which villages your map showed and your daily action counts, your conversations and all messages in them (on both sides, so the other player loses those messages too), your phones’ notification tokens, and the reports about you and by you (they contain your village name, and conversation reports contain messages). The records of your purchases are kept without the link to you (see “How long we keep it”). Deleting your account does not delete what Google holds from its ad software; for that, use your phone’s ad settings and Google’s tools (myadcenter.google.com).
- Change your ad choices: Settings → Privacy choices (EEA, UK and Switzerland), your phone’s advertising ID settings on Android, and iPhone Settings → Privacy & Security → Tracking.
- Stop notifications: Settings → Notifications, or your phone’s notification settings. Your phone’s token is then deleted from our server the next time the game is online.
- Restore items you bought once: on iPhone, Settings → Restore purchases; on Android they come back on their own.
- Unblock a player: Settings, in the list of blocked players.
- Correct your village name: Settings → Account → CHANGE.
- Anything else: write to us at hearthold.support@gmail.com or with the request form. Include your player ID (Settings → Account → Player ID; tap it to copy). The account has no e-mail or password, so the player ID is how we know which data is yours.
We answer as soon as we can, and within 30 days at the latest.
Security
All connections between the game and our server are encrypted with HTTPS. The server keeps only a hash of your device secret, and only a hash of each store order ID; purchase receipts are never stored. Google’s ad software and Google’s Firebase software also send their data encrypted. Access to the stored data is limited to the developer.
Changes
If we change this policy, we update this page and the date at the top. If we add something that changes what we collect, for example ads, purchases or analytics, we update this page before that feature goes live.
Contact
o7games, hearthold.support@gmail.com