Hordelane: Zombie Survival ("Hordelane", "the game") is developed and published by Roy Greenberg (PlayRG), an independent developer in Israel. This policy
explains what information the game collects, why, and how to switch it off. It applies
to the Android application with the package name com.greenberg.hordelane,
and to the iPhone application with the bundle identifier
com.greenberg.hordelane on the App Store. The two are the same game, but the
iPhone version leaves some parts out: On iPhone below says exactly where they
differ. Everything else on this page applies to both. In short, the iPhone version has no
ads, no advertising ID and no sign-in, and it sends analytics only after you say yes.
The game collects gameplay statistics — which level you played, whether you won, and what you upgraded — so that the difficulty and pacing can be improved. None of it carries your name, email, contacts, photos, precise location, or anything else that identifies you personally. You choose, the first time you play and again at any time in Settings, whether those statistics may carry a random tag that lets us find and delete yours (statistics sent that way are pseudonymous: tied to random identifiers, never to your name or account), or whether they are sent as anonymous statistics only, with no identifier at all.
Rewarded videos are the one kind of advertising in the game (Android only), and they play only when you ask for one: WATCH AD to get back into a run you have just lost or to refill a heart, choosing a mission to refresh after CHANGE MISSION on the missions board, WATCH AD TO SPIN on the lobby's bonus wheel, or WATCH AD TO DOUBLE IT beside the loot of a stage you have just won. They are served by Google's ad service, AdMob, which reads your device's advertising ID and a few other things described under Rewarded videos below, and uses them for its own purposes under Google's own privacy policy. Nothing you do in the game is sold to anyone.
The global Survival boards are public. When a Survival run that cleared at least one wave ends, the game enters its result — the waves cleared and the time they took — on boards every player can see, under a random BOARD ID and a "Survivor #" name, or a name you choose yourself (except for a player the store reports as under 13 — see Players under 13). The boards are not statistics, so the statistics choice does not switch them off; Global Survival boards below says exactly what is sent, who can see it, and how to have it removed.
Invite friends (INVITE & GET in the lobby) gives you a six-character code to share. The code, and which players joined with it and later won stage 10, are kept on the same server as the boards under each player's BOARD ID, and anyone who knows a code can read that code's record. On Android, a player who installs the game from a friend's link has the code entered for them from Google Play's install referrer. The game sends no message itself; Invite friends below says exactly what is involved.
Backing your progress up to Google Play Games (Android) is a separate, optional sign-in, and the game is fully playable without it. It is the only part of the game that uses an account of yours — the boards and invites use an anonymous one the game creates itself — and the only part that sees the gamer name on your Play Games profile, which reaches the boards only if you choose to put it there.
The iPhone version differs from the Android one in these ways, and only these:
| Data | Example | Why |
|---|---|---|
| Gameplay events | Level 7 started; level 7 failed after 42 seconds with 60% of the horde cleared | To find levels that are too hard, too easy, or where players give up |
| Progression events | Fire rate upgraded to level 3 for 800 coins; 30 diamonds spent on a heart refill; a stage's loot doubled by a video | To check whether upgrade prices and rewards are balanced |
| Purchase record | The small coin pack was bought at level 12; a purchase of it was cancelled; the store did not offer a diamond pack that was pressed; on Android, a signed receipt named a different product from its order | To judge pricing and pacing, to find purchases that fail, and to notice receipts that do not match their orders. Which product, when, and whether it went through — never the payment itself, the receipt or the order number |
| Holiday event records | The Thanksgiving 2026 window was opened on its third day, by a tap
(event_window_opened: the event, the day, and whether it was tapped or
opened by itself); its free gift was claimed and paid 1,000 coins
(event_gift_claimed); the coins, diamonds and hearts an event's gifts,
track and shop hand out (coins_granted, diamonds_granted and
life_refilled, source event_gift); a won stage's coins paid
again on New Year's Day (coins_granted, source event_bonus);
chocolate left over after Valentine's turned into coins (source
event_leftovers); a holiday bundle's diamonds and coins (source
event_bundle; the purchase itself is recorded as any offer's) |
To see how many players an event reaches and what its gifts pay. The events' calendar is a table inside the game: apart from a bundle, which is bought through the store like any other purchase, the events send nothing anywhere but these statistics. What an event has given you and how far you got is kept in your saved game, and so in your Play Games backup if you use one. An event's progress is cleared the first time the game is opened after its claim days are over (a holiday currency that buys things is first turned into coins), while a holiday hat it gave you is kept for good |
| Start-up time | The game took 6.2 seconds to start | To find devices where the game is slow to load |
| App instance identifier | A random ID generated on install (on iPhone, also Apple's identifier for vendors) | To count players rather than events, and to measure whether people return |
| DATA ID | A random 12-character tag, shown to you in Settings | So that a request to delete your data can be carried out |
| Device and app information | Device model, Android or iOS version, app version, language | To reproduce bugs and to know which devices to test on |
| Approximate location | Country and city level, derived by Google Analytics from your IP address; the IP address itself is masked and not stored | To understand where players are, for language and release planning |
| Advertising data, when a video is fetched or played (Android only) | Your advertising ID and app set ID, your IP address, that a video was requested, played or tapped, and how the app performed while it played | Collected by Google's ad service, not by the developer, to serve, count and limit the rewarded videos and to detect fraud — see Rewarded videos |
| Board entry (global Survival boards) | Survivor #K7QX2M, 23 waves cleared in 4:12.6 on today's HORDE board; with it, a platform tag (Android or iPhone) and the time the server received it | To run the public boards and pay their prizes. Shown to every player — see Global Survival boards |
| BOARD ID | A random identifier for an anonymous account the game creates the first time it sends a board entry or a report, or the first time it has something to do for invites (for example when you open INVITE & GET); shown in PERSONAL RECORDS | So that each entry and each invite record belongs to one player and only that player can change it, and so that a request to remove them can be carried out |
| Invite record, only if you open INVITE & GET or a friend's code is entered | Your six-character code, the BOARD ID it belongs to and when it was made; the BOARD IDs of the players who joined with it, and of those who then won stage 10; for a player who joined, which code they joined with and when | To pay the inviter when a friend wins stage 10, and to stop a code being entered twice or by its own owner. A code's record can be read by anyone who knows the code — see Invite friends |
| Install referrer (Android, read on the phone) | The text Google Play keeps with the install about the link it came from, for example
invite=K7M2QX |
To enter a friend's code for a player who installed from their link. Read once, on the phone; only a friend's code found in it is sent, as the join above |
| Name on the boards, only if you choose one | A name you type with CHANGE NAME: 3 to 16 English letters, digits, spaces and
_ - . |
To show your entries under it, to every player |
| Report of a name, only if you send one | The board, the reported player's BOARD ID and name, your BOARD ID, the time, and its deletion date (about 90 days later) | So that the developer may review the name and take it down |
Survival mode has public boards, on Android and, from the iPhone version that adds them, on iPhone: HORDE and BOSS, each for today, this week, this month and all time, with the days, weeks and months counted in UTC. Each board shows its top 50 and your own place. The RULES window on the Survival page sets out how the boards work and what they pay.
What is sent. When a Survival run that cleared at least one wave ends, the game sends its result to each board still running that it would improve your entry on: the number of waves cleared, how long into the run the last of them was cleared, the name the entry is shown under, a one-letter platform tag (Android or iPhone), the version of the record's format and, on a daily, weekly or monthly board, the date the entry is due to be deleted (see below); the server adds the time it received it. A result set without a connection waits on the device and is sent the next time the game is online, to the boards still running then. The campaign sends nothing to the boards, and looking at the boards adds nothing to them.
The BOARD ID. The first time the game has a result or a report to send, or the first time it has something to do for invites — you open INVITE & GET, a friend's code is entered (by you, or from an invite link), or a saved game that already holds an invite code checks that code's record (see Invite friends) — it creates an anonymous account with Google's sign-in service, Firebase Authentication. The account has no email, password, phone number or name: it is a random identifier, your BOARD ID, which PERSONAL RECORDS shows. Your entries are stored under it. The BOARD ID and the sign-in that goes with it are kept on the device, outside your saved game, and are not part of the Play Games backup, so a reinstall, or clearing the game's data, starts a new one. A player who never sends a result or a report and has nothing to do with invites never gets a BOARD ID.
One thing travels with your saved game: for each HORDE daily, weekly or monthly board your result was entered on, the save notes the board, the BOARD ID and the score sent, until the game has checked that board for a prize after it closes, so that a restored save can still collect one. On Android that note is in your Play Games backup if you use one.
Who can see it. The boards are public: the game shows every player each entry's place, name, waves, time and prize. The boards' data can also be read straight from the server by anyone, and there each entry also carries its BOARD ID, its platform tag, the time it was received and its deletion date. Nothing else about you is in it.
Your name on the boards. Until you choose one, your entries are shown
as "Survivor #" followed by six characters worked out from your BOARD ID. With
CHANGE NAME on the Survival page you can type a name instead: 3 to 16
English letters, digits, spaces and _ - ., changeable once a day. A word
filter refuses some names, and the game checks every name it shows again. A name you
choose is shown to every player, is written onto your entries on the boards still
running, and is kept in your saved game, so on Android it is also in your Play Games
backup if you use one. It is better not to use your real name. On Android, if you are
signed in to Google Play Games and have not chosen a name yet, CHANGE NAME fills in your
Play Games gamer name as a suggestion, provided it would pass the same checks as a typed
name; it is used only if you press SAVE. Once the store's age check —
Google Play's age signals on Android, Apple's age range on an iPhone version with the
boards — reports a player as
13 to 17, the game sends their results under a "Survivor #" name, does not let them type
one, and offers them no suggestion. A player under 13 sends nothing (see Players
under 13).
Players under 13. Once the store's age check reports a player as under 13, the game sends nothing of theirs to the boards: no entry, no report, and no anonymous account is created for them. The phone keeps one note that it should stay off the boards (no age), which is never copied to the cloud save. On that phone the boards still show the player, as "YOU", at the place their best result would hold, and pay the prize that place earns when the board closes, worked out only by reading the boards; other players never see them. Anything the phone sent before the age check answered stays on the boards until it is deleted, automatically or on request, as described below.
Reporting a name. The ! on a line reports that name. A report holds the board, the reported player's BOARD ID and name, your BOARD ID, the time the server received it and its deletion date (about 90 days later), and only the developer can read it. The reported player is also hidden from the boards on your device; that list stays on the device. A report changes nothing for anyone else by itself: the developer is sent the reported names by email, at most once an hour, and decides. A name the developer hides is put on a public list of hidden names (the name and when it was hidden - nothing about who wrote it or who reported it), and every copy of the game then shows it as a "Survivor #" name. A hidden name stays on that list until the developer restores it. The emails, which list each reported name, how many times and on which boards it was reported, and when, stay in the developer's mailbox.
Prizes. The HORDE daily, weekly and monthly boards pay prizes in in-game coins, which have no cash value, from two hours after the board closes by the server's clock, the next time you open the game's lobby online. A prize is paid at most for the result your own device sent, and lapses if it is not collected before the board is deleted (30, 90 or 365 days after a daily, weekly or monthly close). BOSS boards pay no prizes. The amounts and rules are in the RULES window on the Survival page.
Separate from the statistics. The boards are not statistics, and the GAME DATA choice does not reach them: with ANONYMOUS ONLY on Android, or GAME DATA OFF on an iPhone version with the boards, a Survival result still goes to the boards. There is no setting that keeps a Survival result off them. The BOARD ID and the DATA ID are two different identifiers: neither is attached to the other's records, and each one is the key to its own records when you ask for deletion.
How long, and how to have it removed. Entries are deleted automatically: those on a daily board 30 days after the day closes, on a weekly board 90 days after the week closes, and on a monthly board 365 days after the month closes. Entries on the all-time boards are kept for as long as the boards run. Reports are deleted automatically about 90 days after they are made. The deletion is done by the database itself, usually within a day of the date on the record. Entries and reports made before 7 October 2026 carry no such date and are kept until deleted on request. The anonymous account is kept for as long as the boards run. To have it all removed sooner, email playrg.games@gmail.com with your BOARD ID: your entries on every board, the reports you sent, the reports about you and the anonymous account are deleted. Because BOARD IDs and codes can be seen by others, the developer may ask you to confirm the request from your phone, for example with a screenshot of PERSONAL RECORDS or INVITE & GET. Note the BOARD ID before you uninstall: the game keeps it on the device, and once the game is removed you have no way to see it again. Without it (or, for the invite records, the code described under Invite friends) the developer may not be able to tell which entries, reports and invite records are yours, and then they go only by the automatic deletion above, where they have a date. If you play Survival again afterwards, the game creates a new BOARD ID.
Where. The boards are stored by Google in Cloud Firestore, part of
Firebase, in Google Cloud's nam5 location in the United States, and the
anonymous accounts in Firebase Authentication — both on the developer's behalf (see
Who processes the data). As with any connection to a server, Google receives
your device's IP address with each request.
INVITE & GET in the lobby gives every player who may use it a six-character code, and can pay the inviter in-game rewards when friends who joined with it win stage 10; the INVITE & GET window shows what each friend pays. It is kept on the boards' server, in Cloud Firestore, under the same anonymous account and BOARD ID as the boards; it is not a statistic, and the GAME DATA choice does not reach it.
What is sent. When you first open INVITE & GET, the game makes your code and stores a record of it: the code, your BOARD ID as its owner, and the time the server made it. When a player enters a code, two things are written: their BOARD ID is added to that code's list of players who joined, and a record under their own BOARD ID notes which code they joined with and when. When that player then wins stage 10, their BOARD ID is added to the code's list of players who won. Nothing else is sent: no name, no contact, no message, no list of who you shared with. While you have a code and fewer than five friends have been paid for, the game reads its record when you open the window, and otherwise at most every five minutes while you are in the lobby, to see whether a friend has joined or won.
Who can see it. A code's record — the owner's BOARD ID, the BOARD IDs of the players who joined with it and of those who won stage 10, and when it was made — can be read by anyone who knows the code; codes cannot be listed or searched. So a friend you give your code to can read your BOARD ID, and with it find your entries on the global boards if you have any. The record of which code a player joined with can be read by that player alone, and by the developer.
SHARE. SHARE opens your phone's own share sheet with a message holding your
code and a link, …/hordelane-legal/invite.html?c= followed by the code. You pick
the app and send it yourself; the game does not send it and does not learn who it went to.
The link's page stores nothing, counts nothing and sends nothing of its own; it passes the
code on to Google Play (Android) or shows it to copy (other devices). Like these documents,
it is hosted on GitHub Pages, which, as any web host does, receives the address asked for,
code included, and the visitor's IP address.
The install referrer (Android). When a friend's link sends someone to Google
Play, Play keeps a short text with the install that names the code
(invite= and the code). On the first visits to the lobby the game asks the Play
Store app on the phone for that text, through Google Play's Install Referrer library: once,
and again on a later launch only if Play could not answer, five times at most. It reads the
install referrer text and nothing else the library offers. Only a friend's code found in it
leaves the phone, entered exactly as a typed code would be, and only for a player who may
still enter one. A referrer that names no friend's code, from an ordinary install or an ad,
is let go and sent nowhere. On iPhone, where invite friends is still to come, the App Store
keeps no such text, so there the code will be typed.
Kept in your saved game. Your own code, how many friends you have been paid for, the code you joined with and how far that has got, and the BOARD ID that recorded your join are kept in your saved game, so on Android they are also in your Play Games backup if you use one.
Players under 13. On a phone the store's age check reports as under 13, INVITE & GET does not exist: no code, no join, no request, and the install referrer is not read. Until the store has answered the age check, the same is true for everyone.
How long, and how to have it removed. Invite records have no automatic deletion date: they are kept for as long as invites run, or until deleted on request. Email playrg.games@gmail.com with your BOARD ID, as for the boards: the record of the code you joined with is deleted, and your BOARD ID is replaced with the word "deleted" in every code's record that holds it — as its owner, and in the lists of players who joined or won. The lists themselves are not shortened, because the game counts them to pay other players, and a code whose owner is "deleted" can no longer be joined. If PERSONAL RECORDS, where the BOARD ID is shown, is not open to you yet, send the six-character code INVITE & GET shows you instead: the developer reads from that code's record the BOARD ID it was made under. What your own saved game keeps, described above, is on your device and in your own backup, not on the server.
The game can back your progress up to Google Play Games so that a new phone, or a reinstall, does not cost you your campaign. This is optional. If you decline, the game plays exactly as before and your progress stays on the device and nowhere else.
If you do sign in, two things happen. Your saved progress — the stage you have reached, your coins, which survivors and weapons you own, a name you chose for the global boards, if you chose one, and the boards' notes for prizes not yet checked, each with the board, your BOARD ID and the score sent — is stored in your own Google account. And Google tells the game your gamer name and avatar from your Play Games profile, a name you chose for Play Games rather than your legal one. The game shows it in Settings, so you can see which account your progress is backed up to, and offers it as a suggestion in CHANGE NAME until you have chosen a name; it leaves the device only if you press SAVE there, and then appears on the global boards like any name you type.
This saved data lives in your Google account, not on any server belonging to the developer. The developer cannot read it, and cannot delete it for you. You remove it the same way you would for any other game: through the Play Games app, or through your Google account settings.
Signing in and the GAME DATA switch in Settings are two separate choices, and neither one turns the other on. Declining the statistics does not sign you out, and signing in does not start any collection you had switched off.
The identifier is generated randomly when you install the game. It is not your device's serial number, not your advertising ID, and is not linked to any account. On its own it cannot identify you, and it changes if you uninstall and reinstall the game or clear its data.
On iPhone, Google Analytics also records Apple's identifier for vendors (IDFV): a random ID that Apple gives to one developer's apps on one device. It is not the advertising identifier, it is not linked to any account, and it is reset when all of this developer's apps are removed from the device.
The first time you reach the safe house, the game asks how it may measure your play, and lists what that covers. Nothing that can be traced to you is sent before you answer (Survival mode, and with it the global boards, opens only later in the campaign). On Android, until the question is settled, Google Analytics is told that storage is denied, so the few events the Firebase component sends on its own when the app starts — that it was opened, and that a session began — carry no app instance identifier and no DATA ID, and cannot be linked to you or to one another. The gameplay statistics described above are held back entirely until you have answered. The question cannot be closed without answering it. There are two answers on Android (on iPhone, see On iPhone above):
Players who installed the game before this question existed were not shown it. Their play is measured in the first way, which is what the earlier version of this policy set out, and they were told so directly, in the channel the closed test uses. They can switch to anonymous statistics only in Settings at any time.
On Android, open Settings inside the game (on iPhone, see On iPhone above): it shows GAME DATA FULL or ANONYMOUS ONLY, and the CHANGE button under it switches to the other (in earlier versions of the game, tap the mode itself); each tap switches again. The change takes effect immediately: from anonymous only, nothing further carries an identifier; from full, the tag is attached again from that moment. The switch is always there, whichever way you answered the first question, and your choice is remembered. The game is identical in both modes — no feature, reward, or level is withheld.
On Android, payments are handled entirely by Google Play (on iPhone, by the App Store - see On iPhone above). The developer never receives, sees, or stores your card number, billing address, or any other payment detail. When a purchase succeeds, Google Play hands the game a signed receipt naming the product and an order number; the game checks the signature and then delivers the item.
The game records that a purchase happened — which product, and so its price tier, and when — and, when a purchase does not go through, which product it was, the level, and the reason it did not (for example: cancelled, no connection, payment declined, payment still pending, or the store not offering that product), as analytics events, so that pricing and pacing can be judged and failing purchases can be found. Diamond packs and the offers are recorded the same way, and what they gave (the coins and diamonds) as progression events. On Android, after checking the signature, the game also compares each receipt with the order it came with; if they differ, it records which product it was and one word for how they differ (the receipt's form, its product, or its purchase token), and nothing else from the receipt. The purchase goes on as it would have either way. These records carry the same random DATA ID as everything else and contain no payment information, no order number, no purchase token, and no name.
Refunds are handled by Google Play on Android and by Apple on iPhone. The Terms of Service explain what a purchase gives you.
The game shows one kind of advertisement: a rewarded video, which plays only when you ask for one: WATCH AD to get back into a run you have just lost or to refill a heart, choosing a mission to refresh after CHANGE MISSION on the missions board (the window says a video is needed), WATCH AD TO SPIN on the lobby's bonus wheel, or WATCH AD TO DOUBLE IT beside VICTORY LOOT on the summary of a stage you have just won, which pays that loot a second time (up to five a day). Nothing plays on its own, between levels or in the lobby, and a video you close before the end simply pays nothing. If you never tap the button, the ad service is still started when the game starts and fetches a video in advance, so that the button works when you do.
The bonus wheel gives one spin for each video watched, up to five a day and two minutes apart. It has six cells with equal chances, and every spin wins one of them: a free boost, a heart, 100 coins, a heart and a boost, 20 coins, or 200 coins. No money and no coins are spent on a spin.
The videos are served by Google AdMob, part of Google LLC. When the game asks Google for a video, and while it plays, Google's software collects — in Google's own words — your device's IP address, which it may use to estimate a general location; your interactions with the video, such as that it was requested, played or tapped; diagnostic information about how the app performed while it ran; and device identifiers, the Android advertising ID and the app set ID. Google uses that data for advertising, analytics and fraud prevention, and it may use the advertising ID to choose which video to show you.
Players 13 to 17. From Android version 1.3.2, where Google Play provides an age signal, the game honours it: when the signal reports a player as 13 to 17, the game asks Google's ad service for non-personalised ads only for that player, from the moment the answer arrives in a session. The first videos of a session may be fetched before Play has answered; for such a player they are then thrown away unseen and fetched again as non-personalised. The answer is asked for again every session, and nothing about the player's age is stored. No age or age band is ever sent to the ad network: the only thing sent is the request for non-personalised ads. The videos still come from the same service, which still receives the data described above. A player reported as under 13 is shown no videos at all (see Children).
This is the one place where data leaves the game for a company's own use rather than for processing on the developer's behalf, which is why the Data Safety section on Google Play lists it as shared. Google handles it under Google's privacy policy and explains its advertising in How Google uses information from sites or apps that use its services. The developer receives none of it: the game learns only whether the video finished, and records that as one of the gameplay events described above, without the advertising ID.
Your controls. Android lets you reset or delete the advertising ID and switch off ads personalisation — Settings → Google → Ads on most devices. With the ID deleted, Google receives a string of zeros in its place and the videos still play. You can also manage ad personalisation for your Google account at adssettings.google.com. The button decides whether a video is ever shown to you — none is shown unasked — but not whether one is fetched in advance, as described above; these settings are the control for that.
If you allow them, the game reminds you, at most once a day, when your hearts are full again, when the daily gift is waiting, when a holiday event starts or ends tomorrow, and when rain is about to start; none is scheduled between 10 pm and 9 am (Android may deliver one a few minutes late). These are local notifications: the game schedules them on your phone from its own state, and nothing about them is sent to the developer or to anyone else. Turn them off any time in your phone's settings. Players a store reports as under 13 get none.
Analytics are processed by Google Firebase Analytics on the developer's behalf. Google acts as a data processor and is bound by the Firebase Data Processing Terms, under which Google processes the data only on the developer's instructions and provides the same or equal protection of it as this policy describes. See also Firebase privacy information.
If you sign in to Google Play Games, that part is not processed on the developer’s behalf at all: the saved progress and your gamer profile sit inside your own Google account, under Google’s privacy policy and the terms you already have with Google. The developer receives only what the game needs to restore a save.
Purchases go through Unity's In-App Purchasing service, the component the game uses to talk to Google Play (on iPhone it is built without this report, and Unity receives nothing - see On iPhone above). When you start a purchase, Unity Technologies receives a record of each step — started, cancelled or failed (with the reason), paid and delivered — with the product and its price, the Google Play receipt and its signature, the order number, the time, the game's version and package name, the device platform, a session identifier for the game's Unity project and a random identifier Unity gives this installation of the game, and details of the phone it was made on: its model, Android version, language and region settings, storage size, the time the phone was last started and the time the game was installed. It does not include the phone's advertising ID. Unity uses it to report purchase statistics to the developer. From version 1.3.2, the game's Android version sends Unity nothing else: Unity's own analytics, performance reporting and crash reporting are switched off in it (earlier Android versions still had Unity's built-in analytics switched on). That processing is described in Unity's privacy policy for players of Unity-made games. Unity does not receive your card number or billing address either; those never leave Google Play.
The global Survival boards and the invite records are stored in Cloud
Firestore, and their anonymous accounts are kept by Firebase
Authentication: both are Google
services, part of Firebase, processing the data on the developer's behalf as a processor,
under Google's data processing terms for Firebase and for
Google Cloud, on
which Cloud Firestore runs. The boards' database is in Google Cloud's nam5
location, in the United States. Unlike the statistics, board entries are public by
design, as described under Global Survival boards, and an invite code's record can
be read by anyone who knows the code, as described under Invite friends.
On Android, the install referrer is read from the Google Play Store app on
the phone through Google's Install Referrer library, and whether a newer version of the game
is waiting is asked of the Play Store app the same way, through Google Play's In-App Updates
library, once each time the game is opened, when the lobby first shows; Google handles
that question under its own privacy policy. Neither sends the developer anything. On
iPhone, from the version that adds this check, the game asks the same question of the App
Store's public lookup service at
itunes.apple.com, with the game's bundle identifier and nothing about you; Apple
receives your IP address, as with any web request.
Rewarded videos are served by Google AdMob, which is not a processor acting on the developer's behalf: Google decides for itself what it does with the data its advertising software collects, as described under Rewarded videos, and is bound to you by Google's privacy policy.
Reports of names on the global boards reach the developer by email: a script running in the developer's own Google account (Google Apps Script) reads the new reports from Cloud Firestore and sends them to the developer's Gmail inbox, listing each reported name, how many times and on which boards it was reported, and when - nothing about the player who sent the report. Google processes them under the developer's Google account terms.
To study the gameplay statistics - for example, which stage players find too hard - the developer uses AI tools, including Anthropic's Claude, which read the exported records in BigQuery on the developer's instructions. These are the records described above, identified only by random identifiers: no name, contact details or advertising identifier. The game itself sends nothing to any AI service, and no decision about you is made by one. Some of the game's pictures and sounds were made with AI tools; making them used no player data.
The gameplay statistics are not sold, rented, or shared with advertisers, data brokers, or anyone else; apart from the services named in this section, which handle them for the developer, they are used only to improve this game. The only data that reaches an advertising company is what Google's own ad service collects when the game fetches and plays rewarded videos, described above. Board entries are shown to other players, which is what the boards are for, and are not sold either.
Your saved game — level reached, coins, diamonds, upgrades, what you have bought, settings, and reward and offer timers — is stored locally on your device. It is not readable by the developer, and uninstalling the game removes that local copy.
If you sign in to Google Play Games, a copy is also kept in your own Google account so that it survives a reinstall — see Backing up your progress above. Without that sign-in, your saved game does not leave the device. Your Survival results do: they go to the global boards, as described under Global Survival boards, and so do the invite records described under Invite friends.
In the Firebase Analytics reporting console, event data is retained for 14 months and is then deleted automatically. Summary reports built from it - counts and totals such as how many players finished a stage on a given day, with no identifier in them - are kept for as long as the reporting console keeps them.
A copy of the raw event records is also exported to Google BigQuery, where it is kept so that changes can be compared over time, and deleted automatically no later than 24 months after it was collected. These records contain only the gameplay information described above and the random identifiers described above — no name, account, contact details, or advertising identifier. Records are deleted sooner on request. What Google's ad service collects for the rewarded videos is held by Google under its own retention rules, not in these records.
Global board entries are deleted automatically 30 days after a daily board closes, 90 days after a weekly one and 365 days after a monthly one; all-time entries, and the anonymous account behind a BOARD ID, are kept for as long as the boards run. Reports of names are deleted automatically about 90 days after they are made. Entries and reports from before 7 October 2026 have no deletion date and are kept until deleted on request. Invite records have no deletion date either and are kept for as long as invites run. All of it is deleted sooner on request with the BOARD ID, as described under Invite friends for the invite records.
Depending on where you live you may have the right to access, correct, or delete data relating to you, and to object to its processing.
Data tied only to random identifiers creates a practical problem for those rights: without something to match on, no one can tell which records are yours. The game therefore shows you a DATA ID — a random 12-character tag created on your device when you first play. Open Settings and it is printed on the line under the title; tap that line to copy it.
To have your data deleted, email the address below and include your DATA ID. Records carrying that tag will be deleted. Please send the request before uninstalling: the tag is stored only on your device — it is deliberately left out of the Play Games backup — and once the game is removed it cannot be recovered by you or by the developer.
To stop being identified without deleting anything, switch to ANONYMOUS ONLY in Settings (GAME DATA OFF on iPhone, which stops the statistics altogether); from then on no statistic sent carries your DATA ID or any other identifier. Records sent before the switch keep the tag and can still be deleted by the request above, as long as you copy the DATA ID first. The switch does not reach the global boards.
The DATA ID covers the statistics, and only those. Your entries on the global Survival boards, the reports you sent or that name you, your invite records, and the anonymous account behind them are found by a different identifier, the BOARD ID shown in PERSONAL RECORDS on the Survival page. To have them deleted, or to ask what they hold, email the address below with your BOARD ID; one email may carry both IDs. If you signed in to Google Play Games, your backed-up progress sits in your own Google account rather than in the developer’s records, so it is removed through the Play Games app or your Google account settings — not by the email request above.
Under the California Consumer Privacy Act, the categories of personal information collected are identifiers (the random app instance identifier, the DATA ID, the BOARD ID, your invite code, a name you choose for the global boards and, on iPhone, Apple's identifier for vendors), internet or other electronic network activity (the gameplay events listed above, your Survival results on the global boards, and which code you joined with and whether you then won stage 10), and commercial information (which in-app products were bought, without any payment detail). They are collected directly from the app on your device, for the business purposes of analysing and improving the game, of running the global boards, where entries are shown to other players, and of paying invite rewards. When the game fetches or plays a rewarded video, Google's ad service also collects the advertising ID and IP address described under Rewarded videos, for its own purposes.
Your personal information is not sold. Since 17 September 2026 one thing may count as "sharing" under California's definition: when the game fetches a rewarded video, Google's ad service receives your advertising ID and IP address and may use them to choose ads, which is cross-context behavioural advertising in the statute's terms. It happens whenever the game fetches a video, which it does in advance from the moment it starts, not only when you tap WATCH AD. To opt out, delete the advertising ID and switch off ads personalisation in Android's settings and at adssettings.google.com, as described under Rewarded videos; Google then receives a string of zeros in place of the ID. The developer holds no copy of the identifier and does not sell or share anything else.
You have the right to know what is collected, to request deletion, to request correction, and not to be discriminated against for exercising those rights. The game is identical whether or not you opt out. To make a request, follow the DATA ID and BOARD ID instructions above.
A number of US states now have their own consumer privacy laws. The details differ, but the rights they give overlap heavily, and this game treats every US resident the same way rather than working out which state you are in.
You may ask what is collected about you, ask for it to be deleted, ask for it to be corrected, and object to its processing. The route is the one described above: send your DATA ID, your BOARD ID, or both, to the address at the bottom of this page.
Your personal information is not sold. The one case of sharing for targeted advertising is the rewarded video, described under Rewarded videos and in the California section above, and the way out of it is the same: delete the advertising ID and switch off ads personalisation in Android's settings. The game does not profile you for decisions that have legal or similarly significant effects, and it collects none of the categories those laws treat as sensitive: no precise location, no health data, no biometrics, and nothing about race, religion, or immigration status.
The game behaves identically whether or not you exercise any of these rights.
Under India's Digital Personal Data Protection Act, 2023, you may ask for a summary of the data relating to you and of the services, named under Who processes the data, that handle it, have it corrected, completed or erased, withdraw your consent (ANONYMOUS ONLY in Settings on Android, GAME DATA OFF on iPhone, as described above; this does not reach the global boards), and nominate another person to use these rights if you die or become unable to. Send the request, or any complaint about how your data is handled, to the address under Contact with your DATA ID, your BOARD ID, or both; the developer answers within 30 days. If you are not satisfied with the answer you may complain to the Data Protection Board of India.
The developer, Roy Greenberg, is the controller of the data under Israel's Protection of Privacy Law, 5741-1981. You may ask to see the data relating to you, and to have it corrected or deleted, by writing to the address under Contact with your DATA ID, your BOARD ID, or both. You are under no legal obligation to give any data. On iPhone, GAME DATA OFF sends no statistics; on Android, ANONYMOUS ONLY sends them with no identifier, as described above. A Survival result goes to the public boards either way. The data is used for the purposes this policy describes, and is processed for the developer by the services named under Who processes the data, some of them outside Israel.
The developer is the data controller. The legal basis for processing gameplay analytics that carry an identifier is consent, which you may withdraw at any time by switching to ANONYMOUS ONLY in Settings (GAME DATA OFF on iPhone); withdrawing does not affect processing that already took place. Anonymous statistics carry no identifier and are processed on the basis of the developer's legitimate interest in balancing and improving the game. Global board entries are processed to provide the boards themselves, which a Survival run takes part in. You may also lodge a complaint with your national supervisory authority. Data is processed by Google on servers that may be located outside the EEA, under Google's standard contractual clauses. The game, on Android and on iPhone, is not distributed in the EEA or the UK, and the rewarded videos are requested without a consent dialog for that reason; before any release there, a consent request meeting Google's requirements would be shown before the first video is fetched.
Hordelane is not directed at children under 13. It is not listed in Google Play's Families programme or in the App Store's Kids category. The game does not knowingly collect statistics, advertising data or board entries from children: on iPhone, where Apple's age-range feature reports a player under 13, the game stops sending statistics for that player as soon as that report arrives; on Android, from version 1.3.2, where Google Play's age signals report a player under 13, the game stops sending its statistics and stops showing and requesting rewarded videos, without telling the ad service anything about the player's age, and from then on, on that phone, sends no statistics and requests no videos until the game's data is cleared or it is reinstalled. To do that the phone keeps one note that it should stay quiet; it keeps no age, and the note is never copied to the cloud save. Statistics already sent with a DATA ID are deleted on request with that ID.
A purchase a parent approves for a player the store reports as under 13 is handled like any other purchase, only to deliver it: the store takes the payment (Google Play's or Apple's parental approval decides whether it happens at all), the game checks the receipt and delivers the item, and on Android Unity's In-App Purchasing service receives its purchase record, as described under Who processes the data. The game uses none of it for advertising, and, on Android from version 1.3.2, that player is shown no ads.
On Android, and on iPhone from the version that adds the boards, a player the store reports as under 13 sends nothing to the global Survival boards: no entry, no report, and no anonymous account is created for them. The phone keeps the same kind of note, with no age, and only that phone shows the player on the boards, as "YOU" at the place their best result would hold; it also pays the prize that place earns. Anything the phone sent to the boards before the store's answer stays there until it is deleted automatically or on request, and a parent can have it deleted sooner by emailing the BOARD ID shown in PERSONAL RECORDS. Where the boards are in the game, a player reported as 13 to 17 takes part only under a "Survivor #" name and cannot type a name of their own.
For a player the store reports as under 13, INVITE & GET does not exist: no invite code is made, no code can be entered, nothing is sent for invites, and on Android Google Play's install referrer is not read. The same holds for every player until the store has answered the age check. On that phone no offer opens by itself and the HELP PACK is never offered.
Rewarded videos were added on 17 September 2026, and this policy, the Data Safety declaration on Google Play, the store's ads and advertising-ID answers and the game's own manifest changed together for them. The iPhone version was added on 3 October 2026, and this policy now covers it too. On 6 October 2026 the passages that tied the advertising data to asking for a video or tapping WATCH AD were corrected: the game fetches a video in advance from the moment it starts, as the Rewarded videos section already said, so the advertising ID can reach Google's ad service without a tap. On 7 October 2026 CHANGE MISSION, which has offered a rewarded video since Android version 1.3.1, was added to the places a video is described as playing; earlier versions of this policy left it out. On 9 October 2026 the opening paragraph gained a one-line summary of the iPhone version, and the paragraph on who processes the data now says that Google protects the data as this policy does.
In version 1.3.2 this policy changed in four ways. The global Survival boards were added, on Android with this version and on iPhone with a later one: public boards with a BOARD ID, a name a player may choose, reports of names, in-game coin prizes and automatic deletion, and nothing sent to them by a player reported as under 13; the passages that said the game sees no name but the Play Games one, has no user-generated content, or sends nothing when the statistics are refused were corrected to match. Rewarded videos on Android can now also spin the lobby's bonus wheel. On Android, a player Google Play reports as under 13 gets no rewarded videos and sends no statistics, as the Children section describes. And Unity's own analytics, performance reporting and crash reporting were switched off in the Android version, whose purchase report to Unity is now described under Who processes the data.
Also in version 1.3.2: Invite friends was added — the invite code and its record on the boards' server, who can read it, SHARE, Google Play's install referrer on Android, and how the records are deleted — and the BOARD ID is now said to be created for invites too, not only for a board entry or a report. WATCH AD TO DOUBLE IT on a won stage's summary was added to the places a rewarded video plays. The purchase records now name two more things they may carry: that the store did not offer a product that was pressed, and, on Android, that a signed receipt differed from its order. The check for a newer version of the game is described under Who processes the data. The date at the top of this page shows when it was last revised.
Also in version 1.3.2, the holiday events' records were added to What the game collects.
In the same version, a player Google Play's age signals report as 13 to 17 is asked for non-personalised ads only, as Rewarded videos describes.
On 19 October 2026 the opening paragraph gained where the developer is; Who processes the data gained the email script that delivers reports of names and the AI tools used to study the statistics; the BigQuery copy of the statistics was given a deletion no later than 24 months after collection instead of "as long as it is useful"; How long it is kept now says that summary reports outlast the 14 months; sections for India and Israel were added; and Contact now says where the developer is and that complaints go to the same address. Nothing the game collects changed.
In version 1.3.3 the game gained local notifications, asked for only after the player says yes; the permission sentences and a Notifications section say so.
Hordelane is made by Roy Greenberg (PlayRG), an independent developer in Israel. Questions about this policy, requests to delete data, and complaints can be sent to playrg.games@gmail.com. Please include your DATA ID, your BOARD ID, or both, with a deletion request.