GRINDVALE by Demonfork

GRINDVALE

Privacy Policy

Last updated: October 18, 2026

Who we are. GRINDVALE: Dark Kingdom (the "Application" or "Game") is published by Demonfork (Leon Klostermann) ("Company", "we", "us", or "our"). This Privacy Policy applies to the GRINDVALE mobile application for Android and iOS, to its online game service (our game server, together with the Application the "Service"), and to the pages we host for it on grindvale.demonfork.io (the "Website").

By using the Service, you agree to the collection and use of information in accordance with this Privacy Policy.

At a glance

Interpretation and Definitions

Words with initial capital letters have meanings defined below. The following definitions shall have the same meaning whether they appear in singular or plural.

Collecting and Using Your Personal Data

Types of Data Collected

Personal Data. The Application does not ask for or collect your real name, email address, phone number, contacts, photos or location. GRINDVALE is played online: the game server decides the state of every village, so the data below is processed on our server. We only receive your email address if you email us.

Sign-in with Google Play Games (Android). When you sign in, Google Play Games gives the Application a one-time code. Our server exchanges this code with Google for your Play Games player ID and gamer name. We store the player ID and gamer name with your Account, so the same Google Play Games account always opens the same village, also on a new phone.

Sign-in with Apple Game Center (iOS). When you sign in, Game Center gives the Application your Game Center player ID, your alias and a signature. Our server checks the signature with Apple's public key and stores the player ID and alias with your Account.

The gamer name or alias from Google or Apple is not shown to other players. Each Account gets a random Player ID. For every sign-in our server issues a sign-in token that stays on your Device; our server stores only a one-way hash of it.

Your village. Our server stores the state of your village: buildings, their levels and timers, resources, your army, research, heroes, your Abyss Shards (bought and earned), tutorial progress, Trophies, Shield times, the Commander name you choose and how often you renamed it, and when your Account was created and was last active. Every action you take (build, upgrade, train, collect and so on) is sent to the server as a command and checked there against the server's clock and the game rules. While you play, the server notes for a few minutes that you are online, so that, as a rule, your village is not raided while you play.

Activity statistics. While you use the Application, our server notes in which 5-minute periods your Account sent it a request (this rides on the online note described above and stays in the server's short-lived memory for up to 30 hours; when you delete your Account, it is taken out of these notes at once). Each night it turns these notes into one line per day with the number of such periods and sessions, keeps these daily lines for 35 days, and keeps a short summary (first and last day active, number of days active) until you delete your Account. From these lines and from the records the Service keeps anyway (Accounts, raids, clans, purchases and the Abyss Shard record) our server counts players, how long and how often they play, how many come back, and how they progress, raid and buy. These counts are totals per day without any Player ID and are kept. Computer-controlled villages and our own test Accounts are left out. Our server does this itself, whatever your play data answer is; no third party receives the data. You can object to it (see Your Privacy Rights): we then delete your activity statistics and record your objection, so our server leaves your Account out of these counts from then on (your purchases still count in our sales totals, which we keep for accounting).

Moderation and support records. Changes our team makes to an Account, a village, a clan or a chat line (for example a ban, a mute, a rename, Abyss Shards we grant, a refund, a deletion or a changed game setting) are recorded with the time, what was changed and the reason we noted. Only our team sees them. They are kept for 400 days; after you delete your Account they carry no link to your Player ID.

Commander name. The Commander name you choose passes an automatic word filter on our server. Names that break our Terms of Use are refused.

Raids. When you search for a raid, our server picks an opponent and stores the raid: a copy of the defending village, the army you bring, the log of where and when you place your troops, the result, the loot and the Trophies won or lost. Your own village can be picked as an opponent for other players in the same way, and for computer-controlled villages (see Computer-Controlled Villages and Clans). Both sides see the raid in their battle log and can watch its replay. To keep raids fair, our server replays a share of the raids and every suspicious raid with the same battle rules; if a raid claimed more than it did, the extra loot and Trophies can be taken back, the attacker can for a while be matched only against computer-controlled villages, and a record of the failed check is kept (see Retention).

Abyss Shards. Every change of your Abyss Shards is recorded with its reason (for example a purchase, a speed-up, a reward or a rename, with the new name), so we can answer support requests, handle refunds and keep our accounts.

Purchases. In-app purchases are processed by Google Play or the Apple App Store under their terms. We never receive your payment card or bank details. After a purchase, the Application sends the store's purchase token or transaction ID and the product to our server. Our server verifies the purchase with Google (Google Play Developer API) or Apple (App Store Server API) and stores the purchase token or transaction ID, the product, the store's order number, whether it was a test purchase, the price and currency where the store reports them, and the time. Each purchase is credited exactly once. On Android, the purchase carries a one-way hash of your Player ID, so a purchase can only be credited to the Account that made it. If a purchase is refunded or cancelled, our server learns it from Apple (it asks the App Store Server API about a purchase again a few times during the 90 days after it), from Google (once an hour our server reads Google Play's list of refunded, cancelled or charged-back purchases of this app, which holds purchase tokens and order numbers, not payment details), from Google or Apple when our team asks the store about a purchase again, or from our team (for example when a store console shows the refund). It then takes back the Abyss Shards of that purchase as far as your Account still has them (bought Abyss Shards first) and records the refund with the purchase; if your village is being raided at that moment, it does so as soon as the raid is over. If they were already spent, or the purchase also gave resources, the missing amount is recorded and our team reviews the case; no Account is banned automatically for a refund. Resources and anything already built stay.

Play data and crash notes. See Play Data and Crash Notes.

Your consent answer. Your answer to the play data question (allow or do not allow) is stored on our server with the time you gave it, so we can show that we respect it.

Notifications. Reminders (a finished building, research or hero, your Shield ending) are scheduled on your Device as local notifications, only if you allow notifications. Nothing about them is sent to our server.

Push notifications. Some messages come from our server while the game is closed: your village was raided (the attacker's Commander name, the result, how much of your village was destroyed and the loot you lost), your Shield ends soon, and clan troops arrived in your Clan Hall (the sender's Commander name). For this, and only after you said yes to notifications (in the game's question, by turning on Notifications in the game's Settings, or when your Device asked you) and while your Device allows them, the Application gets a push token for your Device from Google Firebase Cloud Messaging (Android) or the Apple Push Notification service (iOS). To create the token on Android, Firebase also uses an installation ID it creates for the Application on your Device; the Application asks for neither before you said yes. On Android 11 and 12, where your Device allows notifications without asking, the game asks you first. The Application sends the push token to our server with the platform, your push settings (Raids, Shield and Clan troops on or off, the quiet hours 22:00 to 08:00 and your Device's time zone offset) and your language. Our server stores them with your Account and uses them only to send these messages; the text of each message passes through Google or Apple to reach your Device. No raid or troop message is sent while you are in the game, and none during the quiet hours. On Android the Application uses only the Cloud Messaging part of Firebase; Firebase Analytics is not included. You can turn each kind off in Settings, or all of them with Notifications. Turning notifications off in the game removes the token from our server and deletes it on your Device; turning them off in your Device settings does the same the next time you open the game. See Retention.

Data stored on your Device. The Application stores on your Device a copy of your village, actions not yet sent to the server, your sign-in token, a random install ID created on the first start (it leaves your Device only with play data and crash notes), your settings (sound, vibration, graphics, notifications, your play data answer, whether the global chat is shown in your village), whether you said yes to push notifications, the push token and the push settings last sent to our server, the year of birth you entered for the clan rules or the global chat, the versions of the clan rules and the global chat rules you accepted, and a small note used for crash notes. The year of birth is never sent to us. Uninstalling the Application removes all of it.

Store review prompt. At most once, after a good moment in the game, the Application may ask Google Play or the App Store to show their own rating dialog. Your rating goes to Google or Apple under their terms.

Server and Website requests. When the Application talks to our server or you open these pages, our servers process technically necessary connection data (IP address, date and time, requested address, status code, amount of data transferred, and the app, browser and operating system information that is sent) to deliver the answer and to keep the Service secure. The IP address is used in memory and in short-lived counters (deleted after 60 seconds) to limit repeated requests, for example sign-in attempts. It is written to our server log only when a sign-in fails. Neither our web server nor our game server keeps an access log of normal requests. These pages load no external fonts, scripts, trackers or cookies.

Contacting us. If you email us, we process your email address and the content of your message to answer your request.

What Other Players See

Your Google Play Games or Game Center name, your purchases and your play data are never shown to other players. What clan members see is described in Clans and Clan Chat, what every player sees of your global chat lines in Global Chat.

Computer-Controlled Villages and Clans

Computer-controlled villages and clans fill the game while it grows. They are run by our server, are not marked in the game and act like players: they build, raid, found and join clans, accept join requests, give and ask for troops, and write short lines from a fixed set we wrote. They are not people, and no person reads your data through them.

To act like players, they use the same data a player in their place would see, on our server only: for a raid, the copy of your village that any attacker gets; in a clan, your Commander name, rank, Castle level, Trophies, the troops you gave and your troop requests (they may greet you by your Commander name in the clan chat). In a clan they write chat lines only while a player of the clan is online, so our server checks the online note of the clan's players (see Your village); their other clan actions (troop requests with a short note from the same fixed set, accepting join requests, rank changes) can happen at any time. A computer-controlled village raids your village only while you are offline and your village has no Shield; the raid is played by our server with the same battle rules and shows in your battle log with its replay. A report about a computer-controlled village is not stored, because it writes only lines we wrote. Computer-controlled villages have no Google or Apple account, make no purchases and send no play data.

Clans, Clan Chat and Global Chat

Clan membership. When you found or join a clan, our server stores which clan you are in, your rank in it, when you joined, and how many troops you gave to and got from its members. The clan's name, badge, description and settings are stored with the clan; the name passes the same word filter as Commander names, the description the filter described below. Anyone in the Game can see a clan's name, badge, description and member list with each member's Commander name, rank, Castle level, Trophies, the troops given and got and when they joined. The games of other players also receive your Player ID with the member list and with your lines (it is not shown).

Clan rules and age. Before you use clans for the first time, the Application asks for your year of birth and shows the clan rules (the rules for clans in our Terms of Use). Your year of birth stays on your Device and is never sent to us; if it is under 16, clans stay locked on that Device. When you accept the clan rules, our server stores that you accepted them, with the version of the clan rules and the time. It takes no chat line, join request message or troop request note from you until you have accepted the current version; when we change the clan rules, the Application asks you again.

Clan chat. Every line you write is stored with your Player ID, your Commander name at that time, the clan and the time, and every member of the clan can read it, also members who join later. The clan chat also shows lines the Game writes: who joined, left or was removed, rank changes, troop requests and donations (who gave which troops to whom). Our server also notes up to which line you have read the chat, so the Application can show new lines. The clan chat is not private: besides the members of the clan, our moderation can read clan chat lines on our server to review reports and to enforce our Terms of Use.

Join requests. If you ask to join a clan, our server stores the request, your Commander name, Castle level and Trophies and the message you add. Members whose rank may accept requests see it.

Troop requests and donations (Reinforcements). A troop request (with the note you add) is a line in the clan chat. Our server keeps a record of each request: who asked, and who gave how many troops.

Word filter. Clan names, descriptions, chat lines, join messages and request notes pass an automatic filter on our server: links are refused, offensive clan names are refused, offensive words in other texts are masked, and extremist text is refused. Refused extremist text in a description, chat line, join message or note is reported to our moderation automatically, together with the refused text (at most one such report per player per hour).

Reports, blocks and mutes. You can report a player, a Commander name, a clan or a line in the clan chat or the global chat. A report stores who reported whom, the kind and reason, and a copy of the reported content, so we can review it even after the line is gone; we note how we handled it. We check every report about a player within 24 hours; a person, not a program, decides. The same report again within a day (the same player and content) is not stored a second time. You can block players: our server stores your block list, you no longer see their lines, and the blocked player is not told. Players who send the same line again and again are muted automatically for a few minutes (this is noted only in the server's short-lived memory). Our moderation can delete lines, rename clans or clear their descriptions, delete clans, remove members, mute players and ban Accounts; a mute is stored with its end and reason, a ban with its period and reason. A line our moderation deleted is hidden from everyone at once and stays on our server as evidence until it is deleted with the other lines after 7 days.

Clan statistics. When you found, join or leave a clan, our server notes this event with your Player ID and the time, and with the type of the clan, how you found it (for example the clan list or a search) or why you left (left, removed, clan disbanded or by our moderation). We use these notes to see how clans are used and to improve them. Our server writes them itself, whatever your play data answer is; they are kept like play data (13 months) and deleted with your Account.

While the chat is open. The Application keeps one request open to our server while you look at the clan chat, so new lines arrive at once. Like playing, this notes for a few minutes that you are online.

Global Chat

Global chat. The global chat is one chat for all players of the Game. Every line you write there is stored with your Player ID, your Commander name and your Castle level at that time, and the time. Every player of the Game can read it for 7 days; then it is deleted automatically. The games of other players also receive your Player ID with your lines (it is not shown). The global chat is not private: our moderation can read its lines on our server to review reports and to enforce our Terms of Use. Computer-controlled villages never write in the global chat.

Who can write. To write in the global chat you finish the tutorial, reach the Castle level the Application shows, wait until your Account is old enough (our server uses the time your Account was created, which it stores anyway; a new Account waits a short time) and accept the global chat rules (the rules for the global chat in our Terms of Use). The Application uses the year of birth you entered for clans, or asks for it before you write in the global chat for the first time; it stays on your Device and is never sent to us, and if it is under 16, the global chat stays locked on that Device. When you accept the global chat rules, our server stores that you accepted them, with the version of the rules and the time. It takes no line from you until you have accepted the current version; when we change the rules, the Application asks you again.

Filter, limits, reports and blocks. Your lines pass the same word filter as clan chat lines. To keep the chat readable, our server notes in its short-lived memory, for at most an hour, when you last wrote, how many lines you wrote and a fingerprint (a hash, not the text) of your recent lines, and for a few minutes which Player ID last sent a line with a given fingerprint, so it can refuse lines sent too fast, the same line again or a line another player has just sent. So that it does not look them up for every line, it also notes there, for up to 7 days, that you may write (your tutorial is over, your Castle level and when your Account was created), and for half a minute why a line of yours was refused. Reports, blocks and mutes work as in the clan chat (see above): a block hides the player's lines in both chats, and a mute covers both chats.

In your village. The newest global chat lines are shown in your village. For this, the Application sends the number of the newest line it already has with the requests it makes anyway, and our server answers with the newer lines; nothing else is sent for it. You can hide them under Settings. While you look at the global chat, the Application keeps one request open to our server, so new lines arrive at once; like playing, this notes for a few minutes that you are online.

Play Data and Crash Notes

Play data (only with your consent). On the first start the Application asks: "Can we collect play data to fix bugs and balance the game?" Until you answer, it sends no play data; if you choose Don't allow, it sends none. You can change your answer at any time under Settings > Privacy > Share play data. If you allow it, the Application sends events such as: tutorial steps started and finished, the time and number of taps per step, skipped or stuck steps, the result of the tutorial raid, whether you used a suggested Commander name, which hints were shown or tapped, your answer to the notification question, whether the review prompt was shown, and your answer to the play data question. Each event carries the time, the game version, the platform (Android or iOS), a random install ID created by the Application and, through the sign-in, your Player ID. Our server keeps only event types and fields from a fixed list and drops everything else. We use play data in our own server only; no third-party analytics service receives it. Separate from play data, our server notes when you found, join or leave a clan (see Clan statistics).

Crash notes. If the Application closed unexpectedly, on the next start it sends which screen and step it was in, the game version and the platform, with the install ID and your Player ID. Crash notes are sent whatever your play data answer is, because we need them to find and fix crashes. They contain nothing else.

Use of Your Data

We do not use your data for advertising and we do not build advertising profiles. There is no automated decision-making with legal or similarly significant effects; the word filter, the automatic mutes of a few minutes and the raid checks only decide about game content, and every report about a player is decided by a person.

Third-Party Services We Use

These providers process data under their own privacy policies:

Sharing Your Personal Information

We do not sell your personal data.

Retention

Google and Apple retain the data they process under their own policies.

International Transfers

Our game server and these pages are hosted in Germany. Google and Apple may process data in countries outside your jurisdiction, including the United States, where data-protection laws may differ. These providers use safeguards recognized under EU law, such as the EU-U.S. Data Privacy Framework or Standard Contractual Clauses. Proton AG is based in Switzerland, a country with an EU adequacy decision.

Delete Your Personal Data

We may retain certain information where we have a legal obligation or lawful basis to do so (for example, purchase records for tax law).

Disclosure

Business Transactions

If the Company is involved in a merger, acquisition, or asset sale, your Personal Data may be transferred. We will provide notice before your data becomes subject to a different policy.

Law Enforcement

Under certain circumstances, we may be required to disclose your Personal Data if required by law or in response to valid requests by public authorities.

Other Legal Requirements

Security

Connections between the Application and our server are encrypted (HTTPS). Sign-in tokens are stored on our server only as one-way hashes, our database is reachable only on a private network, and access to the servers is limited to us. No method of transmission over the Internet or electronic storage is 100% secure, so we cannot guarantee absolute security.

Children's Privacy

GRINDVALE is intended for players aged 16 and older. Before they use clans or write in the global chat for the first time, players enter their year of birth (it stays on the Device); if it is under 16, clans and the global chat stay locked on that Device. It is not directed at children, and we do not knowingly collect personal data from children under 16. If you believe a child under 16 uses the Service or has sent us personal data, contact us and we will delete the Account or the data.

Changes to This Policy

We may update this Privacy Policy from time to time. We will post the new policy on this page and update the "Last updated" date above. Where required, we will provide additional notice (for example, within the Application) or ask for your consent again.

Your Privacy Rights

EEA/UK residents: you may have rights under data-protection laws, including the right to request access, rectification, erasure, restriction, objection, and data portability, and to withdraw consent at any time with effect for the future. You also have the right to lodge a complaint with a supervisory authority; ours is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW).

Where we process data based on our legitimate interests, you can object to it for reasons arising from your particular situation. You are not obliged by law or contract to provide personal data, but without the sign-in data we cannot provide the online game.

Contact Us

If you have any questions about this Privacy Policy or our data practices, you can contact us:

Controller: Demonfork, owner Leon Klostermann, Robensstrasse 36, 52070 Aachen, Germany. Email: support@demonfork.io. More in our Impressum.

The rules for playing GRINDVALE are in our Terms of Use. How to delete your Account: Delete your account.

This Privacy Policy applies to the GRINDVALE: Dark Kingdom application (package com.demonfork.grindvale) published by Leon Klostermann (Demonfork).