← SpaceCorps 2027

Privacy Policy

Last updated: November 20, 2026. This policy covers the game SpaceCorps 2027 (the downloads for Windows, macOS and Linux, the Steam version, the Android app, the iPhone app, the web version at web.spacecorps.xyz, and the game server they play on) and this download site. The Android and iPhone apps are in testing. SpaceCorps 2027 is operated by SpaceCorps Technology AB; in this policy, “we” and “our” mean that company. The Terms of Use apply to everyone who plays.

The short version: to run an online game we keep a small account and your game progress. We do not run ads, we do not sell data, and the game has no tracking and no third-party analytics. The game server keeps simple usage counts, described under “Usage statistics” below. Apart from the backup route described under “Connections and IP addresses”, the things that go to a company other than our host are the one-time ticket that checks a Steam link, and only if you link a Steam account (see “The Steam link”), your pilot’s number, which goes to Stripe if you pay for Premium (see “Premium and payments”), and the text of one chat line, which can go to Anthropic if you ask the game to translate it (see “Chat and reports”).

What we store

What we do not collect

Connections and IP addresses

Like any online service, the game server and the company hosting it (currently Sliplane) can see the IP address you connect from. We use it to run the service and keep it safe, not to profile you. The same is true for GitHub, which hosts this site and the game's downloads: when the game checks for updates or you visit the download page, GitHub sees your IP address.

The game talks to our own servers over encrypted connections (HTTPS and secure WebSockets). If you type in a server address of your own, the game connects as that address says, and a plain http:// address is not encrypted.

If your network cannot reach our server directly, the game can connect through a second address that runs behind Cloudflare. On that route Cloudflare passes your traffic (including your sign-in) to our server and sees your network address while doing so. We do not give Cloudflare anything else.

The server also keeps, in memory only, how many sign-ups and failed sign-in attempts came from one network address, to stop guessing of passwords and mass sign-ups. That count is not written to the database and ends with the time window (or when the server restarts).

Chat and reports

When you write in the game's chat (Global, Local, Group or Clan), the game server receives your message and sends it to the pilots who can read it in that channel. The server also writes each chat line to its operating log, with the channel, the map, your pilot name and the text. That log is kept by our hosting provider for up to 7 days and is read when we look into a problem or a report. The game's administrators can also read its latest lines (up to 5,000, kept in the server's memory only and gone when the server restarts) on the game's Admin page, and see which pilots are connected right now (pilot name, company, world and map, and, in the game's admin window, also position, hull and shield, clan tag and whether the pilot is muted) while they are connected. Apart from a line quoted in a report (below) and the Clan channel (see “Regional servers”), chat lines are not stored in our database and are not shown again after a server restart.

You can report a pilot from the chat: right-click one of their chat lines (on a phone, press and hold the line) and choose Report. A report stores your player number and the player number of the pilot you report, the chat channel, the reason you picked (spam, abuse or harassment, cheating, or something else), the last chat line of that pilot that you saw (at most 200 characters) and the time. The server's log also gets one line about the report, with both pilot names, the channel, the reason and the quoted line. The game's administrators read the reports. The pilot you report is not told who reported them, and nobody is punished automatically because of a report.

A report is deleted 30 days after an administrator has marked it reviewed, and in any case 180 days after it was sent. If you delete your account, the reports you sent are kept without your name (they are about someone else), and the reports about your pilot are deleted with it.

Chat translation. If you choose Translate on a chat line, or on a private message you received, the text of that one line (at most 200 characters) and the language you read are sent from the game to our game server (from a regional server, through it to our main server) and from there to our translation proxy, which we run at Sliplane in the EU (that connection runs inside our hosting provider’s private network and is not encrypted). The first choice is an AI language model (Gemma 4) that runs on a computer owned by the game’s developer; the text reaches it through Cloudflare’s tunnel, so Cloudflare carries it and can technically see it while it does. For Hungarian, and when that model is not available or gives no usable translation, our game server asks the proxy to send the text to Claude, an AI language model made by Anthropic, a company in the United States, through Anthropic’s API. Anthropic is a third-party service provider: its own terms and its own retention apply to what it receives. No name, no account or pilot number, no server and no time is sent with the text. Our translation proxy is set not to log the text or the translation. Our game server keeps the translation in its memory for 24 hours, so that the same line is not translated twice (it is never written to disk), counts in memory how many translations you ask each day, and writes a line to its operating log for each translation it makes, kept like the rest of that log, with your pilot number, whether your Premium is active, the service that answered, the two languages, the number of characters and how many of the day’s translations are left, but no text. The translation is shown only to you, is marked as a machine translation by an AI model and can be wrong. The line you translate may have been written by another pilot, who is not asked. You can use the game without ever using Translate. We can switch the feature off at any time.

Emoji, colours and emotes. Pilots with Premium can send emoji from a fixed list and one colour for the text of a chat line. Both are part of the line: they are kept and shown as the text is, and in the Clan channel the line is kept with its colour and with two flags (whether the sender had ever paid for Premium and whether the sender’s Premium was active), for the same 14 days as the line. The colour you pick, and your choice to show or hide other pilots’ colours, emoji and emotes, are game settings saved with your account like the others. An emote picked from the emote wheel is shown to the pilots on the same map for about three seconds; it is not stored, and a server counts in its memory how many emotes you use each day.

Clans

Clans hold text that you or your clan’s officers write and that other pilots can read. The clan’s name (up to 50 characters) and tag (up to 4) are shown to every pilot. A description of up to 200 characters and an optional Discord invite link of up to 100 characters are written by the Leader or a Co-Leader and shown on the clan page to every pilot. Clan posts of up to 200 characters are written by the Leader and the Co-Leaders for their members, who are the only ones who read them; at most 20 are kept for a clan, and they end at the season’s wipe. If you apply to a clan you may write a message of up to 500 characters; only the clan’s Elders and higher can read it, and it is deleted when the clan accepts or declines the application, when you delete your account, and when the clan ends. The clan log is a list of what happened in the clan (members who joined or left, gifts to the clan’s treasury, quests done and so on); the clan’s members read it, it can hold pilot names, and its newest 200 lines are kept for the current season.

The game does not filter these texts for offensive words. You can report a pilot from a chat line; there is no Report item for clan texts yet, so write to us (see “Contact”) about one. A clan and its texts end at the season’s wipe, or when its Leader leaves it while alone in it. If you delete your account, your posts and your application messages are deleted with it, but a line of the clan log that names you stays in the log until newer lines push it out or the clan ends.

Regional servers

Regional servers. Our main server in Finland holds your account. You can also fly from our regional servers, in Singapore and US East. When your game enters one, the main server sends it a copy of what the flight needs: your pilot name, number and company; your clan's name, tag, level and points, and your role in it; your game progress (wallet, statistics, position, quests, boosters, ships, items, drones, pets, skills, looks, titles and similar game state, including the numbers of pilots you recently destroyed); your game settings, including your ignored pilots; and, while it is active, your Premium and its end date.

What is not sent, and what is kept. Your email address, password hash, payment history (apart from one yes or no, since version 0.5.10: whether you have ever paid for Premium), an expired Premium, the price and grant reference of a look, the grant key of a title, and your clan's bank, tax, description and news are not sent. A regional server takes no database snapshot and, when it starts, removes database copies that older versions left on its volume. It deletes your copy when the main server has your final report. If the main server cannot take the report, or refuses the flight, the copy stays until the report can be sent or the copy is removed. The regional server's log names your player number when a flight starts and ends.

Connections. While the server list is on screen (the sign-in screen and the launch window), your game opens short test connections to every listed server, the regional ones too, to measure the delay. They send no data, but each server's host sees your IP address, as for any connection. If you fly from a regional server, the game then connects to that host for the flight.

Which server you flew from. The main server keeps a log of your flights from regional servers: your player number, the server, the time, the kind of event (such as launch, resume, recall or final report) and a short detail, such as the map you chose, a quest number with the credits and experience it paid, or an error message of up to 200 characters. The entries are written without your name. They are deleted after 30 days and with your account.

The main server also keeps one record per pilot of your latest flights (which server, when, the last numbers reported) for as long as your account exists. The copy of the values a flight could change, which it keeps to check the flight's report, is cleared 14 days after the flight ends.

Clan chat. The Clan channel is kept: our main server stores the clan's last 200 lines (each with the pilot's number, name, company, rank, time and text), each for 14 days (a sweep runs every 6 hours, so a quiet clan's last lines can stay a few hours longer), and sends them to members who connect, join or open the Clan tab. A pilot's lines go with their account, all lines go with the clan, and the lines of someone who left the clan stay until they expire.

Chat between servers. When you fly from a regional server, your clan lines and your chat reports pass through it to our main server in Finland, which stores them; the regional server keeps neither in a database. Global lines said on other servers (pilot number, name, company, clan tag, rank, text and, since version 0.5.10, two flags: whether the pilot has ever paid for Premium and whether the pilot’s Premium is active now), and the Clan lines of a clan with a member flying there, also reach a regional server from the main server, in memory only. A report is kept as described under “Chat and reports”. Every server writes its own pilots' chat lines to its operating log, and the main server also logs the lines said on regional servers, so such a line is in two logs.

Invite Friends

In Community, Invite Friends gives your pilot a personal invite code, made at random. When a friend redeems your code, the server saves who invited whom (both player numbers), the code, the time, what the starter pack gave, and the time the friend's pilot reaches level 5. That lets you see your friend's pilot name and whether they reached level 5, and collect your rewards.

When you redeem someone's code, the same record is made about you, and it also holds a keyed hash of your network address. The hash is made on our server from your address and a secret that only the server has, and cannot be turned back into your address; the address itself is not saved. It is used to limit how many codes can be redeemed from one network address in 24 hours, and the game's administrators can see its first characters next to each redemption to spot one address redeeming many codes. The hash is erased from our database 30 days after the redemption (leftover bytes in unused space of the database file can remain until that space is reused). The server's operating log gets a line when a code is redeemed or a reward collected, with player numbers and no address.

If you delete your account, your player number is removed from these records (the records stay, without it, so that limits and your friends' rewards still add up), and your invite code and the record of the invite rewards you collected are deleted.

Usage statistics

The game's administrators see usage statistics. They are counts: how many pilots played on a day, for how long, how many sessions, how many kills, how much in-game currency was created and spent, how many accounts were made, and how the game server was doing. Behind the daily and monthly counts the server keeps, for each account and each day, only whether the account connected, how many times, for how many seconds and which version of the game it used (for example 0.4.12 from Steam), and nothing else: no address, no name, no chat text, no position. These records are kept for 365 days and are deleted with your account. The counts themselves contain no account, name or address and are kept for 400 days. The game sends its version number and where it came from (Steam, Hangar or the website) with its requests, and no other information about your computer.

Your account also keeps the date and time of your first login and the total time your game has been connected to the game server, in flight or at the station. Both are shown on your pilot profile to every pilot who opens it, like your level, and to the game's administrators. They are deleted with your account. For pilots who played before version 0.4.12, the first login is the day of their first login after that update and the time played starts at zero then.

The Auction

The Auction is where pilots of level 5 and above sell and buy the items they earned, and where the game puts up an hourly lot for bids. To run it, the game server keeps in our database: for each listing, your player number as the seller, the item and how many, the price and its currency, the deposit you paid, when the listing was made, when it ends and how it ended (sold, cancelled, expired or returned); for each sale and each lot you win, a record with your player number and the other pilot's, the item, the amount, the price, the fee and the time; for each bid on a lot, your player number, the amount and the time; and, for each pilot, the last day they looked at the Auction (the game counts the pilots who looked in the last three days to size the hourly lots) and, if an administrator set one, a ban from the Auction with the administrator's reason.

Other pilots see your pilot name on your listings and in the result of a lot you lead or win; you see theirs in your sales, your purchases and your history. A sales record is deleted 90 days after the sale; a lot, with its bids, 30 days after it ended; a listing 30 days after it closed (an open listing stays while it is open). A ban stays until an administrator lifts it or the account is deleted. Leftover bytes of a deleted record can remain in unused space of the database file until that space is reused. The server's operating log names no pilot in a listing, a sale or a bid; it holds only the administrators' Auction actions (see the next section), with the administrator's name and the number of the pilot concerned. None of this is sent to a third party.

Changes administrators make to an account

Every change a game administrator makes to your account is saved as a record: credits, Thulium and Wipe Points added or set, honor, experience and level set, items added, changed or removed, a password reset, any other edit of your pilot's data, and a kick out of the game. A record holds the administrator's account number, your player number, the kind of change, the values before and after (such as a number of credits, or the name and quantity of an item) and the time. The server's operating log gets a line about it with the same facts and the two pilot names. A password is never recorded: not in the record, not in the log, and the server keeps only the scrambled form of any password. A record is deleted one year after it was made. If you delete your account, your player number is removed from the records about you. Actions on the Auction (cancelling or holding a listing, banning or unbanning a pilot from it, pausing it or voiding a lot) are recorded in the same way, with the administrator's account number, the pilot concerned and the time, and are deleted after a year too.

What administrators can do from the game. An administrator can, from a window in the game, see where pilots are, kick, heal, protect or message a pilot, message everyone, bring a pilot to them or go to a pilot, change aliens, and mute or suspend an account. Each change is saved just afterwards in the administrators' record of changes (if saving fails, only a line in the server log remains): the administrator's account number, your player number if it concerns you, the kind of action, a few numbers and the time. Records are kept one year. The log also names the administrator and the pilot.

The few numbers include a length of time, or the map and position of a move: for “bring”, yours and the administrator's; for “go to”, the administrator's and yours. A message's text is not saved; a reason given for a kick, mute or suspension is. Looking at the list of pilots, at a pilot's page or at the list of mutes is not recorded.

Mutes and suspensions

Mutes and suspensions. A game administrator can mute your chat or suspend your account. The main server keeps a record: your player and account numbers, whether it is a mute or a suspension, when it ends (or that it does not), the administrator's reason (up to 200 characters, or none), the administrator's account number and the time. Only administrators see it. You are told you are muted or suspended, not the reason or the end time. When an administrator mutes, kicks or suspends a pilot, every connected pilot also reads a system line with that pilot’s name; the reason, the administrator and the length are never in it.

The record is deleted when an administrator lifts it, when it has ended and the server next starts or an administrator next lists them, and with your account. The action and reason are also kept in the administrators' record of changes for one year; if you delete your account, that record stays for its year without your player number.

Seasons, wipes and rewards

At the end of each season, when the Universe Wipe runs, the game writes down what your pilot was: your rank, your place on your company's ladder, your points, your totals (level, experience, honor, credits, Thulium, kills, deaths, shots and the time you have played), how many ships the wipe kept and how many items it deleted, and what the season paid you (Wipe Points, Premium days, credits, Thulium, looks, containers and titles, including rewards that are still waiting to be paid). While a season runs, the game also keeps your totals from its start, so that it can show how you did in this season next to your whole career. It also keeps the best 50 of each ranking board as it stood at each wipe: the place, the pilot's player number, the points and the company, and no name (a board shows the pilot's current name). If the wipe fails for a pilot and has to be repeated, the game keeps a short note of it (the player number, the season, the error and the time) until it is done. Before a wipe starts, the server stores one report of what the wipe is going to do, with counts and, for the five pilots who would lose most to the caps on credits and Thulium, their player numbers and amounts. That report is replaced at the next wipe, and deleting an account does not remove those numbers from it before then.

All of it is kept for as long as your account exists and is deleted when you delete your account. The ranking boards of past seasons keep their places, points and companies, but without your player number: your place then shows as “Deleted pilot”. Other pilots see, on your profile, your rank, your places and your level at each past wipe and your kills in the current wipe, and the boards of past seasons show a pilot's name, company and points. The rest (your deaths, shots, distance and time played in a wipe, the honor you lost) is shown to you and to the game's administrators only.

Containers, special items, daily rewards, achievements and titles

Containers. When you open a container, the game server records which container it was, the prize, the random number it drew (with the seed it used and the version of the table of chances), your guarantee counter and the time. It also keeps how many containers you hold and how each one reached you (for example, given by an administrator, with the administrator's account number, or a reward). The record of each opening is kept for one year and then deleted; the rest is kept as long as your account. Everything is deleted when you delete your account. The chances are published on the wiki page “Containers”.

Special items. The game keeps the special items you hold (how many of each kind), a record of each time one was given to you, used or taken away (which kind, when, what it was used on and, for an item an administrator gave or took, the account number of the administrator and the note he wrote), and the special items that are working for you now (which one and when it ends). All of it is kept as long as your account and is deleted when you delete your account.

Daily rewards. The game keeps a record of the days on which you collected the daily reward: the season, which tile, chest or prize step it was, the day, whether you collected it late, whether you or an administrator collected it, the time and what it gave you. It is kept for as long as your account exists and is deleted when you delete your account.

Achievements and titles. The server keeps which achievements you have unlocked and when, the lifetime counters behind them (for example how many aliens and pilots you destroyed, how many hours you played, the most credits or Thulium you have held, the highest level you reached, how many wipes you have been through, and whether you have died or are in a clan), the rewards an achievement still owes you, a note of an achievement an administrator removed from you (so that it pays only once), the titles you own and the one you wear. Other pilots can see the title you wear (on your profile, in the rankings and next to your name in some windows) and, on your profile, how many achievements you have and your three rarest. All of it is deleted when you delete your account.

The Forge. Each piece of equipment carries its Forge state: tier, buffs, integrity and how many times its sockets were re-laid. Every action you take in the Forge is written to a journal: your player number, the piece, the time, the kind of action, the shards it cost, and the piece before and after. Offers waiting for your pick are stored until you pick or the server picks for you. Administrators use the journal to put a piece back and return shards. The journal has no end date: it is kept as long as your account and deleted with it. The regional servers' copy of your items includes the Forge state, but not the journal.

Puzzles. Some puzzles in the game use a personal code that the server works out from your player number when it is needed. The code is not stored, only which steps you completed and when. Administrators can look it up; each look is recorded, without the code, for one year.

The diary (Logbook)

The game keeps a diary of what your pilot did. An entry is a short line: when it happened and what it was (you reached a level or a rank, bought, crafted or sold something, destroyed aliens or another pilot or were destroyed, mined asteroids, joined or left a clan, finished a mission or a research, opened a container, collected a daily reward, used a special item, redeemed a bonus code or an invite, earned an achievement or a title, linked a Steam account, were wiped and what the wipe paid you). Alien kills and mining are folded into one line for each hour. Routine entries are kept for 21 days and milestones, such as a new level, a finished mission or a wipe, for a year; at most the newest 400 routine and 500 milestone entries are kept.

Only you see your diary, and the game's administrators, who can read it for support: each time an administrator reads it, that is recorded like the other things administrators do (see “Changes administrators make to an account”). The diary is kept by a small separate service that we run at the same hosting provider as the game's database, on a volume of its own. A line holds your player number, the time, the kind of entry and the game names it is about (an item, an alien, a sector, a clan's name), with amounts of in-game currency. It holds no chat, no account name, no email address and no network address. When another pilot is in a line (the pilot who destroyed you, or whom you destroyed), the line holds only that pilot's player number, and the page shows the name when you read it.

If you delete your account, your diary is deleted from the service: the game server tells the service right after the deletion and keeps trying until it answers.

The Steam link

If you link your Steam account (Settings › Account, in the Steam version of the game), the game server stores your Steam ID (a number Steam gives your account) and the time you linked it, and nothing else from Steam: not your Steam name, friends, games or password. To check the link, the game sends the server a one-time ticket from Steam, and the server sends that ticket to Valve, the company behind Steam, which tells the server whether the ticket is genuine and whose Steam ID it belongs to. Valve receives the ticket, the game's Steam app number and our server's key, and sees our server's address; we send it nothing else about you, not your pilot name or account number. The link tells the game which Steam account may receive this pilot's achievements, which the game on your own computer then reports to Steam (only when the Steam account you are signed in to is the one you linked). Unlinking in Settings, or deleting your account, deletes the stored Steam ID at once. For 24 hours after you unlink, the server also keeps the time you unlinked and a scrambled code made from that Steam ID with a secret that only the server holds, which it uses only to tell whether you link the same Steam account again; both are then deleted. Administrators can see that a pilot is linked and which Steam ID it is, and can remove or move the link. Other pilots never see your Steam ID. What Steam itself holds is covered by Valve's privacy policy.

Crash reports

If the game crashes, it saves a report on your computer (in ~/.spacecorps2027/crash-reports/). Sending it is off by default and happens only if you turn on Settings › General › Send crash reports. A sent report becomes a public issue on the SpaceCorps repository on GitHub, so it is visible to everyone. It describes the crash, the game version and your operating system, not your password. On a phone the saved report is in the app’s own private folder, and it is sent only as described above.

On your computer

The game keeps your settings, window layout and sign-in on your computer, in the ~/.spacecorps2027/ folder (in your user folder on Windows and macOS). It also keeps a log file there, of about 2 MB at most, with warnings, errors and connection details; the game removes your password and sign-in token before it writes a line, and never sends the file. Delete the folder to remove them.

On your phone

The Android and iPhone apps keep your settings, your sign-in (only if you chose Keep me signed in), the log file described above and any saved crash reports in the app’s own private folder on the phone. Uninstalling the app removes them. The Android app asks your phone for one permission, INTERNET. It has no permission for your location, contacts, photos, files, camera, microphone or phone number, and none to read your advertising ID. It contains no advertising and no analytics software of other companies, and it does not check for updates. Android’s backup is switched off for the app, so your sign-in does not go into a Google backup. On an iPhone, the app’s folder can be part of your iPhone’s own backup.

The web version

The web version at web.spacecorps.xyz runs in your browser. It keeps your settings, your language and, if you choose Keep me signed in, your sign-in token in your browser’s local storage on your device. It saves no crash report and no log file; its log goes to your browser’s console. Our web server (Caddy) writes an access log of the requests it receives, and passes your network address on to the game server, which uses it as described under “Connections and IP addresses”. The sign-in token is taken out of that log before a line is written.

Premium and payments

You can buy Premium on a web page of this site, one time or as a monthly subscription. Premium is not sold in the game itself, in the Steam version or in the Android and iPhone apps, and the apps contain no link to that page. Premium belongs to your account, whichever platform you play on. On that page you sign in with your game account; the page keeps the sign-in token in your browser tab only, and sets no cookie.

Purchases are processed by Stripe, the seller of record, on Stripe’s own page. Stripe asks for your card and your e-mail address, and for your name and billing address to work out the tax, and is responsible for them under its own privacy policy; we never see or keep your card number. Our game server gives Stripe your pilot’s number (not your name and not your e-mail address) so that the payment and the subscription belong to your account, and Stripe tells our server when a payment has gone through. We keep the ids of your Stripe checkout sessions and invoices, so that a payment is counted once, and the date your Premium ends. We also keep the customer number Stripe gives you (it looks like “cus_…”) next to your pilot number, so that a second payment, your subscription and its cancellation find the same customer; no card number, name or address is stored with it, only our main server has it, and it is deleted with your account.

Stripe keeps its own records of your payments, and sends your receipts. Deleting your account in the game also cancels a subscription that is running, but does not delete Stripe’s records; to ask about them, see Stripe’s privacy policy and the contact details on your receipt. To ask about what we keep, see “Contact”.

Gold name. The game stores, for each account, whether Premium has ever been paid for (a yes or no). It shows this as a gold name in the chat, so every pilot who can read the chat can see it, and there is no setting to hide it. Premium that you got as a reward does not make a name gold. Each chat line also shows whether the sender’s Premium is active at that moment, whether it was paid for or earned.

Chroma Archives with a payment. When a payment for 30 days of Premium gives you Chroma Archives, the game records on your account how many it gave, when, and which payment it was (Stripe’s checkout session or invoice number, never a card number or an amount), so that one payment cannot give them twice. This stays as long as your account exists and is deleted with it.

Steam and other stores

If you get the game through Steam or another store, that store handles your download, updates and purchases under its own privacy policy. To play, you still sign in with a SpaceCorps account, and this policy covers that account. In the Steam version you can also link your Steam account to your pilot; see “The Steam link”.

Who sees your data

Other pilots see your pilot name, ship, company, clan, rankings, chat messages, whether you have ever paid for Premium (your name is gold in chat) and whether your Premium is active when you write, the date of your first login and your total time played, and (if you use the Auction) your pilot name on your listings and in the result of an Auction lot you lead or win, and the title you wear, your number of achievements and your three rarest, your rank, places and level at past wipes and your kills in the current wipe. Your email address, your password hash and your Steam ID are never shown to other players. We do not sell your data, and we do not share it except with the hosting providers above, which run the service for us, with Valve if you link a Steam account (the one-time ticket described under “The Steam link”), with Stripe if you pay for Premium (your pilot’s number goes with the payment, as described under “Premium and payments”), with Cloudflare if your game uses the backup route described under “Connections and IP addresses”, with Cloudflare and Anthropic for a chat line you ask the game to translate (described under “Chat and reports”), or when the law requires it.

Copies of the database

The game server and the diary service each keep one copy of their database on their own volume, rewritten every six hours, and the game server also keeps one made before each Universe Wipe until the next wipe replaces it. A record you delete can remain in such a copy until it is replaced. Regional servers keep none.

Deleting your account

This section is the way to ask for deletion of a SpaceCorps 2027 account (operated by SpaceCorps Technology AB) and the data it owns. In the game: Settings › Account › Delete account, then your password. If you cannot sign in, or you no longer have the game installed, write to support@spacecorpstechnology.com from the e-mail address you registered with and tell us your pilot name; you can also ask us on our Discord. We delete the account and its data within 30 days and tell you when it is done. Because an e-mail address is not checked when an account is made, we may ask you to prove that the account is yours before we delete it. If you have a Premium subscription, deleting the account cancels it; Stripe keeps its own records (see “Premium and payments”). What stays after deletion is listed below.

Deleting removes the account and everything it owns (pilot, ships, items, and so on). If you lead a clan, it passes to its highest-ranking member, or is disbanded if nobody else is in it. Your Auction listings, your bids' link to you, the day you last looked at the Auction and any Auction ban are deleted; your player number is removed from the sales records, bids and lots, which stay without it until their 90 or 30 days are over so that the other pilot's history still adds up. Everything described above under “Seasons, wipes and rewards”, “Containers, special items, daily rewards, achievements and titles”, “The diary (Logbook)” and “The Steam link” is deleted with the account too (the ranking boards of past seasons keep their places and points without your player number). Chat lines other pilots already saw may remain on their screens, and the server's operating log keeps its lines for the 7 days described above. Your clan posts and application messages are deleted too; a clan log line that names you stays as described under “Clans”.

Children

SpaceCorps 2027 is for people aged 18 and over. The game does not ask for your date of birth and cannot check your age. If we learn that a person under 18 has an account, we will delete it. If you think this has happened, tell us (see “Contact”) and we will look into it.

Changes

If this policy changes, we update the date at the top and describe the change in the release notes.

Contact

Questions, requests to see or delete your data, or anything else about privacy: write to support@spacecorpstechnology.com, or ask on our Discord. Please do not post passwords or other private details in public.

SpaceCorps Technology AB, organisation number 559608-6172, Mandelgatan 6, 194 37 Upplands Väsby, Sweden.