PlayingAFK

Privacy policy

PlayingAFK runs on your computer, so most of your data never reaches us. This page says what does, why, and how to get it back or get rid of it. It is written to be read in five minutes.

The short version

  • Your game login, account names, screenshots and chat stay on your computer. The app sends us counts of what it did, never what it saw.
  • We keep what an account and a licence need: your email, your licence key, and an id for each computer you activate.
  • We do not sell data, run ads, or put analytics trackers on the site or in the app.
  • You can download a copy of your data or delete your account yourself, from Settings in the portal.

What stays on your computer

The app does its work locally. It reads the screen of your emulator and taps it; nothing about that is uploaded. We never receive your game password, the names of your game accounts, your screenshots, or anything you or other players say in the game. Your run history stays on your computer too: what we receive about it is the counts described under usage statistics below, and the details of a run only if you send us a failure report (also described below). There is no crash reporting.

The app does talk to us for four things: checking your licence, downloading the game pack, sending usage statistics once an hour, and sending a failure report when you ask it to. That is the full list.

What we keep about you

Your account

Your email address and a hash of your password (we never store the password itself). If you sign in with Google, we also keep the id Google gives us, the email it confirms, and the name on your Google profile. We record when you signed up, the IP address you signed up from, and when you ticked the box acknowledging the ban risk.

Each time you sign in, we note the IP address and browser of that session. This is so you can see your active sessions in Settings and sign out one you do not recognise.

Your licence and your computers

Your licence key, and for each computer you activate: an id for that machine, the label you gave it, when it activated and last checked in, the app version, the operating system family (Windows, macOS or Linux), and which game pack and version it has installed. We keep a record of seats you have released so the limit on your plan can be enforced fairly.

The machine id is a salted hash of an identifier your operating system assigns to the computer. The identifier itself never leaves your machine, and the hash cannot be turned back into it. If no identifier can be read, the app makes a random one instead and tells us it did. The machine id is personal data, and we keep it because that is how a per-device licence works.

The app checks in with the licence server a few times a day, asks the pack server for the pack it runs, and sends the pack server the usage statistics described below once an hour. Those requests carry your licence and the machine id, which also tells us which game you play.

Payments

PayPal handles your payment. We send PayPal your email address when you start a checkout, and we never see your card or bank details. We keep the ids PayPal gives your customer record and subscription, what you paid and when, and the notifications PayPal sends us about your payments, so we can answer a billing question later.

Support

Tickets you open: what you write, any screenshots you attach, and any diagnostics you paste in. A copy of each new ticket and reply is emailed to our support mailbox, and a short alert with your email and the first lines goes to our team chat, so someone sees it quickly.

We also keep a log of sensitive actions on your account, such as revealing your key, releasing a device or downloading a build, with the time and IP address. If you ever ask "did I do that?", this is how we answer.

Usage statistics the app sends

Once an hour, a licensed copy of the app sends us a short summary of what it has been doing. This is a condition of the licence and it cannot be switched off: it is how we see which automations work, which fail and on what, and which versions are in use, without asking you to send a report every time. It is a summary of the app's own work, counted, and it is built so that nothing in it can name you or your game accounts.

What is sent.

  • For each game account, a code the app made up for it (like acct-3f9a1c2e), never the name you gave it; and for each game day, how long the app was running and paused for that account, and which automations were enabled.
  • For each automation, each day: how many times it ran, succeeded, did nothing, failed or was interrupted, how long it spent, whether its daily work got done, and how often you pressed Run now.
  • Counts of events inside the app (a recovery, a reconnect, a pause) and of the in-game values the automations read while doing their job, such as the number of trucks sent or the diamonds the Lucky Discounter automation spent.
  • For each failed run, up to twenty a day per account: the automation, the kind of error, and the page it ended on.
  • About the machine: the app, pack, emulator and operating system versions, your plan, how many accounts are configured and running, and when the app last restarted.

What is never sent.

  • Your in-game names or your alliance, or anything about other players.
  • Screenshots, chat, or any text the app read off the screen.
  • Your game login, your licence key or token, or the labels you gave your accounts.

We use these statistics to run the service: to see which automations fail and on what, which versions are in use, and whether a machine has gone quiet. They are linked to your licence, so someone answering a support question about your account can read them. They are included in your data export and deleted with your account.

Failure reports you choose to send

When an automation fails, the app shows a Send button beside that run. Nothing leaves your computer until you press it. A report holds the failed runs' details (the task, when it ran, the error, the pages it went through), the events and log lines around them, the screenshots the app saved when it lost its place, the app, pack, emulator and adb versions, your plan, and the results of the device checks.

Before it is sent, the name you gave each account in the app is replaced by a code. Two honest caveats: the screenshots are sent as they are, so they can show your in-game name, other players' names or alliance chat if those were on screen; and a few events note text the app read off the screen, such as the name of a player you sent a gift to. Look at the run before you send it if that matters to you.

Reports are read only by PlayingAFK staff, only to work out what went wrong, and are deleted after 90 days, or sooner if you delete your account.

If an affiliate sent you

When you arrive through an affiliate's link, we count the visit without storing your IP address. What we keep are two one-way hashes made with a key only we hold, which let us count each person once a day and notice when one address pretends to be a crowd. They cannot be turned back into your address, and once the day is over they are never compared again. Bots and link previews are not counted.

If you then sign up, the affiliate sees a masked form of your email address (the first letter and the domain, like j***@gmail.com), when you signed up, and how far you got: on a trial, or subscribed and how many months you have paid for. They also see if their commission was reversed after a refund. Nothing else.

If you are an affiliate yourself, we also keep the PayPal email you want paid, and send it to PayPal when we pay you.

Keeping the free trial free

To stop one person taking many trials, we compare sign-up emails (ignoring dots and +tags) and sign-up IP addresses. The sign-up form also uses Cloudflare's bot check, which sees your IP address. Our servers keep ordinary request logs (IP address and URL) for a short while, as almost every web service does; they are small and roll over on their own.

Who helps us run this

We do not sell personal data and we do not share it with anyone beyond the services that run PlayingAFK:

  • Amazon Web Services, where the servers and storage live, in the United States.
  • Cloudflare, which sits in front of the site and portal and runs the sign-up bot check.
  • PayPal, for payments and affiliate payouts.
  • Resend and Amazon SES, which deliver our emails.
  • Google, for Google sign-in and for our own mailbox.
  • Slack or Discord, which carry the short support alerts to our team.

Your data is stored in the United States. We are based in Israel, and if you are in the UK or EU that counts as a transfer abroad, made to perform your contract with us.

Why we are allowed to

Because you asked us to (your account, licence and devices), because the law requires it (payment records), and because we have a fair reason to (keeping the trial honest, paying affiliates for the customers they bring, defending a payment dispute, and keeping the service working).

How long we keep things

Your account data for as long as you have an account. Usage statistics for 400 days, and the failure details inside them for 90 days. Failure reports for 90 days. Payment records for as long as tax law requires. Our logs of sensitive actions and sign-in sessions do not expire automatically yet; they are kept for security and dispute purposes. Backups are kept for 14 days, so something you delete can linger in a backup for up to two weeks before it is gone everywhere.

Seeing your data, and deleting it

Both are in Settings in the portal. Export gives you a file with your account, licences, devices, orders, tickets, reports and usage statistics. Delete cancels any live subscription, revokes your licences, removes your failure reports, your usage statistics and your Google link, and blanks your email and name from your account record.

Some things stay after deletion, and it is better to say so than to surprise you: payment records, because the law requires them; the ids of the computers you activated and the security logs, so a seat or a dispute can be accounted for; and your support tickets. None of them link back to a name once your account record is blanked.

You can also ask for a copy, a correction or a deletion by writing to [email protected]. If you are in the UK or EU you may also complain to your data protection authority.

Cookies

The marketing site sets none. The account portal sets one cookie to keep you signed in (30 days), two short-lived ones for the few minutes a Google sign-in takes, and, if you arrived through an affiliate link, two that last thirty days to record the referral. The sign-up bot check may set its own cookie. The portal also remembers a few preferences in your browser, like your theme and which notices you dismissed; those never leave your browser. There is no analytics or advertising cookie anywhere.

Who we are

The data controller is PlayingAFK, Yigal Alon St 94, Tel Aviv-Yafo, Israel. Questions go to [email protected], and a person reads them.

When this page changes

We update it when the software changes what it collects, and the date at the bottom moves. If a change matters, we will email you about it.

Last updated 19 October 2026.