Privacy policy
Mineral Line works without an account. There are no ads and no tracking, and we don’t sell or share your personal information. The app sends anonymous usage data and crash reports, which you can turn off. This policy explains what the app keeps on your device, what it sends and why.
The short version
- Your lists, games and settings are saved on your device. If you turn on sync, a copy goes to your own iCloud or Google Drive, which we can’t see.
- An account is optional. If you sign in, your lists, games and settings are kept on our server so they reach your other devices, until you delete the account.
- Linked games, table displays, events, army codes, rules questions and lists imported from the official army builder send what those features need to our server. Games are deleted from it automatically, at most 7 days after their last change, and army codes 60 days after they were last used.
- Feedback and bug reports you send from Settings go to our private issue list on GitHub, with your device details if you leave them on.
- Your ZIP or postcode never leaves your device, except in your own backups.
- Anonymous usage data and crash reports go to PostHog, under a random ID made on your device, with no names. Turn it off in Settings → Usage data.
- The web app (app.mineralline.app) uses cookies only to sign you in, and sends no usage data.
- Anyone with a game code, watch link or recap link can see that game, including the players’ names.
Who we are
Mineral Line is published by Dakotah Cote (“we”, “us”), who is responsible for the personal information described here. Contact: privacy@mineralline.app.
On your device
The app saves these on your device:
- The name you enter, your faction, your ZIP or postcode, and your other settings.
- Your army lists, and your game history: dates, missions, scores, your opponents’ names and factions as entered, and each game’s log.
- A game in progress, including a code that proves you’re a player in it.
- A random ID the rules assistant and feedback use for fair-use limits (see below). It isn’t connected to your name or any account.
- A second random ID for usage data (see below), made on this device and never synced.
- A third random ID for this installation of the app, so a reinstall doesn’t pick up an earlier sign-in. It isn’t sent anywhere.
Your device’s own backups (iCloud Backup, Android backup) can include these files. You can delete lists and games one at a time, or everything in Settings → Backup & sync → Erase all data on this device.
iCloud and Google Drive sync
If sync is on, your lists, game history and settings are copied to a hidden app folder in your iCloud account (iPhone and iPad) or your Google Drive (Android), so they reach your other devices. Apple or Google keeps that copy under their terms, and we can’t access it.
On Android, connecting Google Drive shows your Google account’s email address in Settings. It stays on your device.
You can turn sync off, disconnect, or delete the cloud copy in Settings → Backup & sync.
Accounts
An account is optional. Without one, nothing described in this section applies: your data stays on your device and in your own iCloud or Google Drive.
If you create an account, with Apple, Google or an email address and password, our server (on Cloudflare) keeps:
- your email address, and your name if Apple or Google share it. Sign in with Apple lets you hide your email; then we only get an address Apple forwards to you;
- which ways you sign in, and the ID Apple or Google gives us for you;
- for an email account, a scrambled (hashed) form of your password, never the password itself;
- Apple’s sign-in token, encrypted, so we can cancel it with Apple when you delete the account;
- your signed-in sessions: when each started, and the device’s IP address and app or browser version at sign-in;
- what you save to the account: your army lists, game history, rosters, events you run and settings, so they reach your other devices.
On your device, the app keeps your sign-in in the system’s secure storage (the Keychain on iPhone and iPad, the Keystore on Android). If you turn on Face ID, Touch ID or fingerprint unlock for the account, your device checks your face or finger itself: the app never sees it, and nothing about it is sent anywhere. In a browser the sign-in is a cookie instead (see “The web app”).
While you’re signed in, the app syncs with your account instead of iCloud or Google Drive, and leaves your iCloud or Drive copy as it was. Signing in on a device adds what’s on it to the account. Signing out keeps everything on the device, and sync goes back to iCloud or Google Drive.
We email you only about the account: a code to confirm your address, a code to reset your password, and a link if you ask to delete the account from the web. The emails go through Cloudflare’s email service. No newsletters or marketing.
When you choose a new password, the server checks it against passwords known from data breaches using Have I Been Pwned. Only the first 5 characters of a scrambled form of the password are sent, so the service never learns it.
- The account and what’s saved to it are kept until you delete it. A session ends after 60 days without use, or when you sign out.
- Codes expire after 10 minutes, and a deletion link after 60 minutes.
- To slow down password guessing, the server counts sign-in attempts per IP address for a few minutes.
Delete your account at any time in Settings → Account → Delete account, or without the app at https://live.mineralline.app/account/delete. Deleting removes the account and everything saved to it from our server straight away, and cancels Apple’s sign-in token. What’s on your devices stays. Settings → Account → Export my data gives you a copy of your data first.
Your account isn’t linked to usage data: the account ID and email address are never sent to PostHog.
Linked games, table displays and watching
When you start or join a linked game, the app sends our server your player name, faction, the army list you chose (its name, units and cards) and each change to the game. A table display you add can have a name too.
Anyone with the game code or the watch link can follow the game in the app or a web browser: both players’ names, lists, score and game log. Share codes with the people you want to watch, and use a name you’re happy for them to see.
- A finished game is deleted from the server 4 hours after its last change. Any other game is deleted 7 days after its last change.
- A table display’s pairing code is deleted within 10 minutes.
- The server keeps only a scrambled (hashed) form of the codes that prove who the players and displays are.
Events
When you run an event and you’re online, the app sends our server the event so it gets its event code: its name and settings, the players’ names and factions, each player’s army list when the organizer registers one (its name, faction, Mineral limit, units, upgrades and cards), the pairings, results and the army list names entered with them. Anyone with the event code or link can see it, in the app or a web browser, and the page asks search engines not to list it. The event’s web page doesn’t show the army lists, but anyone with the code can read them in the app. Enter players by a name they’re happy to have shown.
When a player links a game to an event, their device sends the event a summary of that game every few seconds while it’s played, and once when it ends: both players’ names and factions, both army lists (their names, units, upgrades and cards) when they fit, Victory Points, faction resource, round and phase, Mission Markers, the clock and the game log. When the game ends, it also sends how long it took, each player’s time used and left on the chess clock and how many of each army’s units are left, and each player’s tap on Send to the event sends the score they confirmed. Anyone with the event code can see it, and the organizer sees it on their dashboard.
When a player picks themselves in an event, their phone sends a random key it made for that event, so no other phone can pick the same player. The server keeps only a scrambled (hashed) form of it, and which player it picked; anyone with the event code can see that a player has been picked, but not on which phone. It’s deleted when the player lets go (Not you?), when the organizer frees them, or with the event.
An event, with its games’ summaries, is deleted from the server 3 days after its last change, or straight away when the organizer takes it offline. A game’s summary is deleted two rounds later, except the summary of how a finished game ended (the final score, how it ended, the clock, VP by round, units left and the players’ confirmations), which is kept for the life of the event. The organizer’s devices keep that summary with the event.
When a player calls a judge, their phone sends the event their table and the note they typed, if any. When a player’s chess clock runs out, the event records which player it was and in which game round. Only the organizer sees these alerts. When the organizer clears one, the ruling they type, if any, is kept with it, and the player who called the judge sees it on their phone. The alerts, notes and rulings are deleted with the event; the organizer’s devices keep them with the event.
If the organizer turns on Alerts on this phone, their phone sends the event its push token, an address our server uses to send it notifications through Expo’s push service, and from there Apple’s or Google’s. Each notification carries the event’s name and the alert, with the player’s note. The token is deleted when the organizer turns alerts off, when Apple or Google say it no longer works, or with the event.
Recap links
A recap link carries a finished game’s summary in the link itself: both players’ names and factions, list names, units, the score round by round, and the mission. We don’t store recaps, so we can’t delete one: anyone with the link can open it, and apps that preview links may keep a copy. Recap and watch pages ask search engines not to list them.
Rules questions (Ask)
When you ask a question, the app sends our server the question, the rules version, whether you’re on iOS, Android or the web, and the app’s random ID. The server finds the relevant rules and sends them with your question to an AI model that writes the answer: Cloudflare Workers AI, or Groq when Workers AI can’t answer. They don’t receive the ID or your IP address from us.
Answers are saved so that the same question is answered faster next time, and a saved answer can repeat what the question said. Please don’t put personal information in questions.
To keep the service fair, the server counts questions per app ID and per IP address. Per-minute counts are held briefly by Cloudflare; daily counts are stored as hashed values and deleted after 2 days.
On iPhones and iPads with Apple Intelligence, the app can also answer on the device, and then nothing is sent to us. Voice questions use Apple’s speech recognition, which works on the device when it can and otherwise sends the audio to Apple under Apple’s privacy policy.
Lists from the official army builder
When you import a list by its official army builder code, the app sends the code to our server, which reads that saved list from the official builder (Archon Studio’s, hosted on Google Firebase) and sends it back. Nothing else about you goes with it.
When you import the builder’s PDF or a picture of it, the app sends the file and the app’s random ID to our server, which sends the picture to an AI model (Cloudflare Workers AI) to read the list’s code off it. Neither we nor the model keep the file, and the model doesn’t receive the ID. Lists you import as text are read on your device and aren’t sent anywhere.
To keep the service fair, the server counts these requests per IP address, and files per app ID, the same way as rules questions: per-minute counts are held briefly by Cloudflare; daily counts are stored as hashed values and deleted after 2 days.
Army codes
When you open a list’s share sheet or show its army QR code, the app sends the list to our server to get its army code: the list’s name, faction, Mineral limit, units, upgrades and cards, without its record. The server keeps the list under that code, and anyone with the code can import a copy of the list.
A code and the list kept under it are deleted 60 days after the code was last used, by someone looking it up or by its share sheet. Editing a list gives it a new code; the old code keeps the old version until it’s deleted.
To keep the service fair, the server counts these requests per IP address. The counts are held briefly by Cloudflare.
Feedback and bug reports
When you send feedback from Settings → Feedback & bugs, the app sends our server your message, whether it’s a bug, a feature request or feedback, the email address if you give one, whether you’re on iOS, Android or the web, and the app’s random ID.
If “Include device info” is on (it is unless you turn it off), the app also sends the app’s version and build number, its update channel and update ID, your device’s operating system and version, its model, and whether it’s a phone or a tablet. The screen shows exactly what will be sent.
Our server files the message, the email address and the device info as an issue in our private project on GitHub (GitHub, Inc., in the United States), where only we can see it. It doesn’t send GitHub the random ID or your IP address. We keep a report while we need it to fix the problem or answer you; write to us to have one deleted. Please don’t put other personal information in it.
To keep the service fair, the server counts reports per app ID and per IP address, the same way as rules questions.
If you choose to send it by email instead, your mail app sends it, and we get your email address with it.
Events near you
Your ZIP or postcode is matched to an area using tables built into the app, so it isn’t sent to us or anyone else. To tell apart codes that exist in two countries, the app reads your device’s region setting, not its location. The app never uses location services.
News, images and links
The app downloads lists of news, events and videos from our web host, and shows pictures hosted by others, such as the official StarCraft: Tabletop Miniatures Game site, Google’s Firebase Storage and YouTube. Like any web request, these reveal your IP address to the host. Event pages, videos and maps open in other services under their own policies.
The web app
Mineral Line also runs in a browser at app.mineralline.app, for building lists, browsing units, reading the rules and seeing your stats. This policy covers it too, with these differences:
- Cookies: only for signing in. One keeps you signed in, for up to 60 days without use or until you sign out. If you sign in with Apple, a second one lasts a few minutes and checks that Apple’s answer came back to the same browser. Until you sign in there are none, and none is used for ads or tracking.
- No usage data or crash reports are sent from the web app, and it loads no analytics.
- Your lists, games and settings are kept in your browser’s storage only while you’re signed in, and sync with your account, never with iCloud or Google Drive. Signing out or deleting the account clears them from that browser. Signed out, the web app saves nothing of yours.
- The browser keeps a few things either way: whether the sidebar is folded, which update notes you’ve seen, the random ID that rules questions and feedback use, and a saved copy of the news, events, videos and downloads lists.
- If Google sign-in is offered, the sign-in dialog loads Google’s sign-in script from Google, which can set Google’s own cookies under Google’s privacy policy. It loads only where the Continue with Google button shows.
- Reading a list’s QR code from a picture happens in your browser, and the picture isn’t sent anywhere. In Safari and Firefox the first time downloads the code reader from jsDelivr, a public file host, which sees your IP address like any web request.
Our website
Our website (mineralline.app) and the watch, recap and policy pages set no cookies and use no analytics, and everything on them is served by us. The landing page stores one note in your browser for the length of your visit (“intro-seen”), so its intro plays only once.
Usage data and crash reports
Unless you turn it off in Settings → Usage data, the app sends usage data and crash reports to PostHog, the service we use to count and read them, so we can see how the app is used and fix what breaks.
What’s sent:
- Game data: the factions, Faction and Tactical Cards, units and upgrades you choose while building armies and in the armies you play; game results, scores by round, units destroyed, missions and deployments.
- Which screens you open and which units, cards, keywords and rules you look up, and when the app is installed, opened and updated.
- Crash and error reports: what went wrong and where in the app’s code.
- The app version, device model and operating system, your language and time zone.
- A random ID made on your device the first time the app runs, so we can tell one install from another. It isn’t your device’s advertising ID or any other identifier, and it isn’t linked to your name.
What isn’t: your name or your opponents’ names, list and event names, anything you type (including rules questions, feedback and your postcode), your location, or your contacts. PostHog is set not to store IP addresses or look up where you are.
PostHog processes the data for us in the United States and keeps it for up to a year. Turning the switch off stops it straight away; to have past data deleted, write to us.
Server logs
Our server runs on Cloudflare. Cloudflare keeps short-lived request logs (such as the IP address, time and address requested) for security and troubleshooting, for up to 7 days.
Camera, photos and microphone
- Camera: only to scan QR codes. The picture isn’t saved or sent.
- Photos: only a picture you choose, to read a QR code in it.
- Microphone and speech recognition (iPhone and iPad): only while you ask a question by voice.
What we don’t do
- No ads, tracking or advertising IDs. Usage data isn’t combined with data from other companies or used for advertising.
- No selling or sharing of personal information, as those words are used in US state privacy laws, and no profiling.
Legal bases (EU and UK)
We use personal information to provide the features you ask for (a contract with you), and to keep the service secure and fair (our legitimate interests). Usage data and crash reports rely on our legitimate interest in improving the app; you can object at any time by turning them off.
Where data is processed
Our server, its AI providers, Expo’s push service, GitHub and PostHog can process data outside your country, including in the United States. Where the law requires it, these transfers rely on safeguards such as the EU Standard Contractual Clauses.
Your rights
Depending on where you live, including the EU, the UK, Canada and several US states, you can ask to access, correct, delete or get a copy of your personal information, object to or restrict how it’s used, and complain to your data protection authority.
Most of your information is only on your device, where you control it. For a game on our server, write to us with the game code; games are deleted automatically within 7 days in any case. For an army code, write to us with the code. For a feedback report, tell us roughly when you sent it and what it was about. We answer within 30 days and won’t treat you differently for asking.
Children
Mineral Line isn’t directed at children under 13, or under 16 in the EU and UK, and we don’t knowingly collect their personal information. If you think a child has put their real name into a linked game, contact us and we’ll delete it.
Changes
If this policy changes, we’ll update the date above, and for significant changes we’ll say so in the app before they apply.