EIMYRJA APP AND WEBSITE · UPDATED NOVEMBER 7, 2026
PRIVACY POLICY
This policy covers the EIMYRJA: The Last Fleet app for iPhone, iPad and Android, and the EIMYRJA website, dev blog, Android waitlist, comms, and contact forms, operated by EIMYRJA development team. It does not describe Apple’s or Google’s own services, such as the App Store, TestFlight and Google Play, which have their own privacy policies.
The EIMYRJA app
The app needs no account or sign-in, and it contains no advertising. We have not added analytics or tracking tools to it, and we do not receive your saves, contacts, location, or device identifiers. The only server of ours the app connects to is the co-op relay, which carries online co-op and is described below.
Your save game and settings are stored only on your device. Deleting the app deletes them, although your device backups may keep a copy.
Co-op multiplayer is optional and lets two to four players fly together; single-player needs no connection. On the Multiplayer screen you choose the network. ONLINE, the default, connects through the EIMYRJA relay, a server we run on Railway that passes game traffic between players over the internet. LOCAL connects your device directly to other players’ devices nearby and needs no internet connection: iPhones and iPads use your local network or Apple’s peer-to-peer connections, and Android devices use your Wi‑Fi network. iOS asks your permission before the app can use the local network. Online rooms can mix iPhone, iPad and Android players. LOCAL games are between iPhones and iPads, or between Android devices.
In either mode, during a session the other players’ devices receive your in-game pilot name and portrait, your ship and loadout, and what your ship does in the session. In a public online room, the other players see a call sign made from your ship’s name instead of your pilot name. Nothing is kept after the session except the scrap each player earns, which is saved in their own game.
Online, that session traffic passes through the relay, together with the room’s six-letter code, your game’s version, and the room’s listing: the host’s pilot name (a call sign in a public room), the game settings, and the number of players. The relay forwards the game traffic without decoding it, holds the rest in memory only while the room is open, and writes none of it to disk. If a player’s connection drops, for example while the app is in the background, the relay holds their room or seat for about two minutes so they can return, then discards it. To limit abuse, such as guessing room codes, the relay keeps your IP address in memory while you are connected and for up to a few minutes afterwards. The relay’s logs record only room counts, whether a room was public or private, how long it lasted, its peak traffic, and why connections closed; they contain no IP addresses, room codes, names, or game versions. Railway, which hosts the relay, processes technical connection information such as IP addresses to deliver and protect the service, under its own retention settings. While the Multiplayer screen is set to ONLINE, the app also checks that the relay can be reached; that check carries no game or player information.
If you choose to share analytics with app developers in your device’s settings, Apple may share crash reports and usage statistics with us. Apple controls that setting and its data under Apple’s privacy policy. On Android, if your device shares usage and diagnostics data, Google may share crash and performance reports with us through Google Play, under Google’s privacy policy. The app is built with the Unity engine, which may send Unity basic technical information about your device, such as its model and operating system; Unity’s handling of technical information from apps made with Unity is described in the Unity privacy policy.
The website
What we collect and why
If you join the Android waitlist, we store your email address, signup date, and the version of the consent wording you accepted. We use this information to email you about what you signed up for: when EIMYRJA is available on Android, or, if you joined the earlier playtest list, about EIMYRJA playtests. Joining is optional; it does not subscribe you to unrelated marketing.
If you contact us, we store your email address, request type, message, and submission date so we can respond and handle your request. Please do not send passwords, payment information, or other sensitive details.
Comms is a chat for people on the waitlist. To sign you in, we email a one-time code to your waitlist address when you ask for one; the code is stored only in scrambled (hashed) form and expires after 10 minutes. We store the display name you choose, the messages you post and when you posted them, and your sign-in session. Your display name and messages are visible to everyone signed in to comms; your email address is not. You can delete your own messages at any time. Leaving the waitlist removes your comms membership and your messages.
Our hosting provider, Railway, processes technical request information such as IP addresses, request times, URLs, and browser information to deliver and protect the site. The application also uses IP addresses temporarily to limit abusive submissions. We do not attach those addresses to the waitlist.
Cookies and tracking
We do not use advertising cookies, analytics trackers, or behavioral advertising. Public browsing and signup do not set application cookies. Signing in to comms sets an essential, secure session cookie that lasts up to 30 days or until you sign out. The private editor uses an essential, secure login cookie that expires after 12 hours or when the administrator signs out. These cookies are used only for authentication.
Who receives the information
Authorized people working on EIMYRJA can access signups and contact requests. Railway hosts the site and its PostgreSQL database. Comms sign-in codes are delivered by Resend, an email delivery service acting for us. We do not sell personal information or share it for targeted advertising. We may disclose information when required by law or necessary to protect the service and its users. Hosting may involve processing outside your country, including in the United States.
How long we keep it
We keep signup information while it is needed for the waitlist, unless you ask us to remove it sooner. We keep contact requests while handling them and for reasonable follow-up, then remove them when no longer needed. Hosting logs and backups follow the provider’s retention settings; deletion from the active database may not immediately remove copies from retained backups. Login sessions expire automatically.
Your choices and requests
You can withdraw signup consent or ask to access, correct, or delete your information through our contact form. Select “Leave the waitlist” for an opt-out request. We may need to confirm that a request comes from the person concerned before disclosing or changing information. Withdrawing consent does not affect earlier lawful processing.
Where applicable law provides them, you may also have rights to restrict or object to processing, obtain a portable copy of your information, and complain to your local data protection authority. We rely on your consent for waitlist emails and our interest in answering requests and keeping the site secure for the limited operational processing described here.
Children
The website and signup list are not directed to children under 13. If you believe a child has supplied personal information, contact us so we can investigate and remove it as appropriate.
Changes and contact
We will update the date on this page when this policy changes. For privacy questions, contact EIMYRJA development team through our contact form.