Privacy Policy
This translation is provided for convenience. The English version is the binding one.
Last updated: 6 November 2026
This policy explains what Cordonfall collects when you play at cordonfall.com, why, who else is involved, and the choices you have. Cordonfall (“we”) is responsible for this data; you can reach us at hello@tegarama.com.
In short: you can play without an account. We collect what the game needs to run, keep scores honest and stop abuse. We don’t show ads, don’t use tracking cookies, and don’t sell or rent your data.
1. When you play as a guest
- In your browser. Your saves, settings (such as the skin and sound you chose) and a random browser id the game makes for itself are kept in your browser’s local storage, on your device.
- The heartbeat. While you play, the game tells our server what it is doing: when you start, every ten minutes while you play, at a run’s start and end, and when you leave the tab. It sends the random browser id, your call-sign, the screen you are on, the mode, map, night, kills, your HQ’s health, the skin, the minutes played, the game’s version, whether it runs as an installed app, and how far you have come through the game’s first steps (such as the first night’s guide). Our server adds your country, as our host’s network reports it, and a device class such as “iPhone · Safari”, worked out from your browser’s user agent, which we don’t keep. We use this to see how the game is played and to fix it. Nothing is sent before you press PLAY, and automated browsers and crawlers are not recorded.
- On itch.io and Game Jolt. Our pages there show the game from cordonfall.com inside theirs, so this policy covers it there too; each site’s own privacy policy covers the site itself. Your browser keeps the game’s saves there apart from those at cordonfall.com, and tells our analytics which site the visit came from.
2. When you have an account
- Your account: your email address (to sign in; we don’t send you marketing), your call-sign, your password (stored only as a salted PBKDF2 hash that can’t be turned back into it), when you joined and last signed in, and your career totals such as your best night, kills and scrap. When you pick a call-sign, it alone is sent to an AI model through OpenRouter (section 8), to check it is fit for the public boards.
- Each sign-in and sign-up: its time, country and device class.
- Shared Siege: the tickets you take, the recorded commands of the runs you send (so our server can replay and verify them), their results, any defence you publish (shown with your call-sign), the Levy you earn and spend, your cosmetics, and your commando’s progress.
- Street War: the fortress you publish (the map it stands on, its defence and your call-sign), the attacks you make and those made on your fortress (each one’s recorded commands, so our server can replay and check it, and its result and stars), and your two ratings, as an attacker and as a defender.
- While you are signed in, the heartbeat above also carries your account.
3. What other players see
When you submit a score we store the name you give (your call-sign), your result (nights survived, kills and scrap), the mode, the date, and the map you played: its name and centre point. The name and the map’s name are shown publicly on the leaderboards. If you play on a map of your own street or home, remember its name will appear next to your score.
What you leave on the street in Extraction. On the maps that come with the game (not a place you searched for), other players’ runs can meet what you leave there: when a run is lost, where on that map your scavenger fell, its last minute of steps, what it wore and a few things it carried, and what killed it; a note you leave (one of a few set phrases) and its place; and a thing you choose to leave for the next player. If you are signed in, each carries your call-sign; a guest’s carries no name. We also keep who laid your fallen scavenger to rest or took your gift, so we can tell you. Nothing about where you are is stored with any of it.
Street War. Other signed-in commanders can attack a fortress you publish and put on duty: they see your call-sign, your rating and the fortress, and after a night the attacker and the defender each see the other’s call-sign. The ranks show the best commanders’ call-signs and ratings, and the Fortress of the Week’s board the call-signs of those who attacked it. A night either side shares can be watched by anyone with its link, which carries no names. The map an attacker plays on has no street name and no place on Earth: it is centred on your HQ and turned, the buildings’ outlines are moved a little, and what each building is (a shop, a school) is left out. Someone who knows your street well could still recognise its shape, so publish a fortress only of a street you are happy to show. Taking it off duty stops new attacks.
4. Maps and place searches
To build a map, the game fetches OpenStreetMap data for the area you choose from public Overpass servers, through our server or directly from your browser. Searching for a place sends your search text to OpenStreetMap’s Nominatim service. The pin-drop map shows tiles from OpenStreetMap’s tile servers and loads the Leaflet map library from unpkg. These services see your IP address and what was requested, under their own privacy policies. We keep the map data for an area in a shared cache for up to 90 days; it contains no personal data.
Your Street. If you choose “Find my street”, your browser asks whether to share your location, and only then gives it to the game. The game sends it to OpenStreetMap’s Nominatim service to learn your street’s name, shows small map tiles around it from OpenStreetMap’s tile servers, and then fetches the map of the area around it as for any other map. We don’t store your location on our servers. The street you confirm (its name and a point on it) is kept in your browser’s local storage so you can play it again; clear the site’s data to remove it. If you post a score from your street, the street’s name goes on its leaderboard, as any map’s name does, with its place rounded to a few hundred metres (so neighbours share a board). If you share a run from your street, the link you share carries the street’s point rounded to about 100 metres, so whoever opens it can play the same street; nothing is sent until you share it.
5. Analytics
We use Rybbit, a privacy-friendly analytics service, to count visits: the pages viewed, where visitors came from, and their country, device and browser. Rybbit uses no cookies and no persistent identifiers, and its cloud keeps data in the European Union (Germany).
6. Security and abuse prevention
To stop floods and password guessing, our server counts requests in short time windows by IP address, and by account for some actions. These counters contain your IP address and are deleted within 24 hours. Our hosting provider’s own logs also record IP addresses for a limited time.
7. Cookies and local storage
We don’t use advertising or tracking cookies, so there is no cookie banner. The game keeps its saves, settings and your sign-in session in your browser’s local storage, which stays on your device; clearing this site’s data removes them and signs you out. One page meant only for the developer, the password-locked codebase page, sets a strictly necessary session cookie when unlocked.
8. Who processes data for us
- Vercel
- hosts the website and runs our server functions (United States).
- Neon
- hosts our database (United States).
- Steam (Valve)
- in the Steam edition only: your Steam ID and Steam name, used to open your account and sign you in; your saves and achievements are kept by Steam under Valve’s own privacy policy (United States).
- Rybbit
- visit analytics (European Union).
- OpenRouter
- passes a few of the game’s questions to an AI model and back (United States): whether a new call-sign is fit for the public boards, and, from a run’s numbers alone, a few of the game’s picks, such as a receipt’s headline, a hint or the advisor’s word before dark. Our server asks it, so it never sees your IP address or your account.
- OpenStreetMap services, Overpass servers, unpkg
- map data, place search, map tiles and the map library, when you use those features.
- IndieDB, itch.io
- the landing page shows IndieDB’s button and itch.io’s widget, loaded from their servers, which see your IP address and browser under their own privacy policies.
We don’t sell or rent your data, and we don’t share it with advertisers. Your data may be processed in the United States and elsewhere; where the law requires, we rely on our providers’ safeguards for such transfers, such as standard contractual clauses.
9. Why we use it
We use this data to provide the game and your account (to perform our terms with you), and to keep the game secure, fair and working and to understand how it is played (our legitimate interests). Where the law asks for your consent, we rely on it.
10. How long we keep it
- Your browser’s storage: until you clear it.
- Your account and its game records: while the account exists. When you ask us to delete it, we delete them, except anything the law requires us to keep.
- Heartbeat and run records: while they are useful for running and improving the game. You can ask us to delete those tied to your account or browser.
- Leaderboard entries: while the leaderboard exists.
- Street War: your fortress, the attacks on it and yours, and your ratings, while your account exists. To have a fortress taken down, email us.
- Rate-limit counters: up to 24 hours. The map cache: up to 90 days. What you leave on the street in Extraction: 14 days (a gift: 28, so we can tell you who took it).
11. Your rights
Depending on where you live, you can ask to see, correct, export or delete your data, or object to how we use it. Write to hello@tegarama.com from your account’s email address. If you play as a guest, clearing this site’s data removes what is on your device; to have the server’s records of your browser deleted, email us too. You also have the right to complain to your local data protection authority.
12. Children
Cordonfall isn’t meant for children under 13, and we don’t knowingly collect their personal data. If you believe a child has made an account, email us and we will delete it.
13. Changes to this policy
If what we collect or how we use it changes, we will update this page. The date at the top shows when it last changed.
14. Contact
Questions or requests about your data: hello@tegarama.com.