Ashport · What we know about you
Privacy Policy
Version 1 · In effect from 2 August 2026
The short version
- We ask for an email address and a password. That is the whole signup. No real name, no phone number, no date of birth, no address.
- We never see your card. Payments go straight to Stripe.
- We do not sell your data, and we do not run advertising. There are no ad networks, no trackers, and no third-party analytics scripts in this game.
- We keep an IP address, a coarse network fingerprint and a device hash to stop one person running twenty accounts. It is deleted after 180 days.
- Two cookies. One keeps you signed in. One lives for ten minutes during a Google sign-in. Neither follows you anywhere.
The detail is below, written against what the code actually does rather than against a template.
01 What we collect
The complete list. Nothing on this page is collected that is not here.
What you give us
| Data | When | Note |
|---|---|---|
| Email address | Signup | Stored encrypted. We keep a one-way hash of it separately so we can tell whether an address is already registered without reading it. |
| Password | Signup |
Stored only as a salted scrypt hash. It cannot be reversed and
nobody here can read it back to you.
|
| Your name in the game | Signup | Public. It appears on boards, in chat, and on your Rap Sheet. |
| What you write | While playing | Family chat, family names and descriptions. |
| Google account identifier and email | Only if you use Sign in with Google |
We request the openid and email scopes and nothing
else. We do not receive your name, your profile photo, your contacts, or
anything in your Google account.
|
What we record because you connected
| Data | Why | Kept |
|---|---|---|
| IP address | Rate limiting, blocking signup floods, and refusing account creation from datacentre networks. | 180 days |
| Network operator and country | The AS number, the network's name and a two-letter country, from Cloudflare. Used to notice a session moving somewhere it should not. | 180 days |
| Browser user agent | Part of the device hash below, and for diagnosing bugs. | 180 days |
| Device hash | Linking accounts run by one person. See section 5. | 180 days |
| Gameplay events | What you did and when, so the economy can be balanced and so we can tell whether new players are getting stuck. Recorded against your player identifier, not your email. | Analytics retention, currently 90 days |
| Purchase records | What was bought, when, for how much, and the Stripe reference. Required to honour refunds and to keep accounts. | 7 years (tax records) |
02 Why, and on what legal basis
For readers in the UK and EEA, the GDPR Article 6 basis for each purpose.
| Purpose | Basis | Detail |
|---|---|---|
| Running your account and the game | Contract, Art. 6(1)(b) | We cannot give you an account without an address to attach it to. |
| Taking payment | Contract, Art. 6(1)(b) | And legal obligation, Art. 6(1)(c), for keeping the records. |
| Anti-cheat and abuse prevention | Legitimate interests, Art. 6(1)(f) | Keeping a competitive game fair, and keeping the service standing. We have written a Legitimate Interests Assessment for the device graph specifically, and we will send it to you if you ask. |
| Security and rate limiting | Legitimate interests, Art. 6(1)(f) | Refusing floods, credential stuffing and automated signups. |
| Balancing and improving the game | Legitimate interests, Art. 6(1)(f) | Aggregate and pseudonymous. Never sold, never shared for advertising. |
| Emails we send you | Contract, Art. 6(1)(b) | Address verification, password resets and purchase receipts only. We do not send marketing email. |
A note on honesty. Whether a device hash of this kind needs consent under the ePrivacy Directive rather than resting on legitimate interests is a genuinely contested question, and the EDPB's guidelines of October 2024 read on it both ways. Our own internal assessment says so in those words and says counsel must review it before we take significant EEA traffic. We would rather write that here than claim a certainty we do not have.
03 What we never collect
Stated so that the absence is on the record.
- Card numbers. Checkout happens on Stripe's own page. No card detail ever reaches our servers.
- Your real name, address, phone number or date of birth.
- Precise location. We never ask for the location permission. Country comes from the network, at country level only.
- Contacts, calendar, camera, microphone, or files. The game asks for no device permissions at all.
- Advertising or cross-site tracking identifiers. There are no ad networks, no pixels, no third-party analytics scripts and no session recorders on this site.
- Canvas, font, or WebGL fingerprints. See section 5.
05 The device hash, in detail
Because “we use a device fingerprint” is the kind of sentence that should be shown its working.
One person running many accounts is the main way a game like this is ruined. To notice it, we compute a hash from properties your browser transmits in order to open the connection at all:
- the TLS cipher chosen,
- the TLS version,
- the length of the ClientHello message,
- a digest of the TLS extensions offered,
- the user agent string.
Nothing is read from inside the page. No canvas is drawn, no font list is enumerated, no WebGL renderer is queried, no audio device is measured, and no JavaScript property is inspected to build this. The inputs are all network-layer facts that already had to be sent for the page to load.
The result is coarse. It tells us that two accounts probably arrived from the same browser on the same machine. It cannot identify you, it does not follow you to other websites, and it changes when your browser updates. Because it is coarse, it is evidence and not a verdict: it feeds a review, and above an in-fiction challenge, a person decides what happens to an account.
Device records are deleted after 180 days.
07 How long we keep it
Including exactly what an account deletion does and does not remove.
| Data | Kept for |
|---|---|
| Account, email, sign-in | Until you ask us to delete it |
| Era progress: money, rank, territory, inventory | One Era, roughly twelve weeks. It is then wiped as part of the game's design. |
| Legend score and Rap Sheet | For as long as the account exists. These deliberately survive the wipe. |
| IP, network, user agent, device hash | 180 days, then deleted by a scheduled sweep |
| Outbound email records | Until sent, then a short period for delivery troubleshooting |
| Purchase and tax records | 7 years. We cannot delete these on request, because we are required to keep them. |
What deletion does. When you ask us to delete your account, we remove your email address, your password hash, your Google link if you had one, your device records, and your writing in family chat. We keep purchase and tax records as above, and we may keep a one-way hash of your email for as long as necessary to stop a permanently banned account being remade, which is a legitimate interest you can object to.
08 Your rights
One address. There is no self-service button for this yet, and saying so is more useful than pretending otherwise.
Write to admin@ashport.city from the address on the account. We will answer within 30 days. We do not charge for this.
Depending on where you live, you can ask us to:
- Tell you what we hold about you, and why;
- Give you a copy of it in a portable format;
- Correct anything that is wrong;
- Delete your account and the data attached to it;
- Object to or restrict processing we do on the basis of legitimate interests, including the device graph;
- Withdraw consent where we relied on it.
UK and EEA. These are your rights under the UK GDPR and the EU GDPR. You also have the right to complain to your data protection authority: in the UK, the Information Commissioner's Office at ico.org.uk; in the EEA, your national supervisory authority.
California. Under the CCPA as amended, you have the right to know, delete, correct, and to opt out of sale or sharing. As set out in section 6, we do not sell or share personal information, so there is nothing to opt out of. We will not discriminate against you for exercising any right.
Verification. We will ask you to make the request from the email address on the account, because that is the only identifier we hold that can prove it is yours. We may ask you to confirm from a signed-in session as well.
09 Children
This game is for people aged 16 and over.
Ashport is not directed at children, and we do not knowingly collect personal information from anyone under 16. If you believe a child has given us information, write to admin@ashport.city and we will delete the account and the data attached to it.
10 Security
What actually protects the account.
- Everything is served over HTTPS. There is no unencrypted path into the game.
-
Passwords are stored as salted
scrypthashes with per-account salts. - Email addresses are encrypted at rest, with the key held outside the database.
-
Session cookies are
__Host-prefixed,HttpOnly,SecureandSameSite=Lax. - Signing in with Google links on Google's account identifier and never on an email address alone, and refuses an address Google has not itself confirmed. Linking a Google account destroys any existing password on that account and signs out every other session, which closes a known account pre-hijacking attack.
- A password reset signs out every session everywhere, so recovering an account also evicts whoever was in it.
No system is perfect. If you find a security problem, write to admin@ashport.city. We will not pursue anybody who reports a genuine vulnerability in good faith and does not exploit it or exfiltrate other people's data.
If a breach ever puts your data at risk, we will tell you and the relevant authority within the time the law requires, and we will say what actually happened.
11 Where it is held
On Cloudflare's network, which means close to you and also elsewhere.
Ashport runs on Cloudflare Workers, which execute in whichever of Cloudflare's data centres is nearest to you. Our permanent database is hosted in the United States. Stripe, Resend and Google also process data in the United States.
If you are in the UK or the EEA, this means your data is transferred outside your region. Those transfers rely on the European Commission's Standard Contractual Clauses and the UK Addendum, which our processors incorporate into their terms, and on the EU-US and UK-US Data Privacy Frameworks where the recipient is certified under them.
12 Changes to this policy
Versioned, like the terms.
This policy carries a version number at the top of the page. If we change it in a way that materially affects you, we will raise that version, tell you in the game, and where the law requires it, ask for your consent before the change applies to you.
13 Contact
The same address as everything else.
We are the data controller for the personal data described in this policy. If you want the Legitimate Interests Assessment mentioned in section 2, ask and we will send it.