1. Who we are
Carbon Ashes is operated by SolidRusT Networks
(“SolidRusT”, “we”, “us”). The public site is
carbonashes.com.
Related services include the Windows launcher download on
dist.carbonashes.com, the launcher itself, and the
game client and servers.
Questions: suparious@solidrust.net.
2. What this covers
This policy applies to:
- The teaser site at carbonashes.com (static HTML, CSS, JS).
- Installer and update files served from dist.carbonashes.com.
- The Carbon Ashes launcher (local identity + ticket mint).
- The game client and the authoritative game servers.
It does not cover third-party sites we link to, including solidrust.net.
3. What we process
This teaser has no first-party analytics, no accounts, and no cookies we set. The ash canvas is decoration only. Hosts and fonts still see ordinary web traffic.
Website
- GitHub Pages (Microsoft) hosts the site and may log IP address, user-agent, referrer, and request path.
- Google Fonts loads Teko, Barlow, and IBM Plex Mono. Google may see your IP and user-agent when the font CSS is fetched.
Downloads and updates
- The Windows installer is a versioned object on Amazon CloudFront at dist.carbonashes.com. AWS may log IP, user-agent, and the object path.
- The launcher checks a signed manifest on that same host so it can fetch updates.
Launcher (on your machine, then the mint)
- If you play, the launcher stores a game key and a display name in a local player file (unix mode 0600). The key is a credential. Do not share it.
- The key is sent only as an
X-API-Keyheader to the mint atapi.solidrust.ai, with body{"display_name":"…"}, to exchange a one-shot join ticket. The launcher does not upload the key anywhere else. - Display names are 3–20 characters, ASCII alphanumeric, and are public in the yard.
Game session
- Player ID (from the key/mint), display name, connection metadata (IP, port, timestamps), and gameplay state the server must own: position, combat, vehicles, scrap, world edits, deaths, joins/leaves.
- The sim is server-authoritative. The client sends intent. The server keeps the scar.
- We do not currently run a separate crash-reporter or marketing telemetry pipeline. If that changes, this policy will change first.
4. Why we process it
- Run the site, CDN, launcher, and game.
- Authenticate a session (game key → ticket → server).
- Keep a shared world consistent and fair (anti-cheat, abuse, capacity).
- Deliver and verify updates.
- Debug outages and security incidents.
- Meet legal duties if we are compelled.
We do not use this information to advertise to you. We do not sell it. We do not build a marketing profile from play.
6. Retention
- Host and CDN logs: whatever those providers keep, typically weeks to months, plus anything we copy for an incident.
- Game world state: until a wipe, ban, or we shut the shard down. The public site already says seasons wipe on a weekly cadence while we are in development.
- Launcher player file: on your disk until you delete it or uninstall.
- Game keys and mint records: as long as the key is valid plus a short audit window after revoke.
7. International transfers
SolidRusT operates from Canada. GitHub, Google, and AWS may process traffic in the United States and other regions. If you download or play, that routing is part of using the service.
8. Children
Carbon Ashes is not directed at children under 13. Do not create a game key, set a display name, or play if you are under 13. The game is a violent PvP sandbox; it is intended for mature players. We do not knowingly collect information from children under 13. If you believe we have, email us and we will delete it.
9. Your rights
Depending on where you live (including Canada under PIPEDA), you may ask us to confirm what we hold, correct it, or delete what we can. Some records we cannot unwind (already-wiped shards, other players’ world state, provider logs we do not control).
To exercise a right, email suparious@solidrust.net from a mailbox we can match to the game key or display name. We may ask you to prove control of the key.
10. Security
Game keys are secrets. TLS covers mint and HTTPS downloads. The yard is still a hostile multiplayer service in development. Do not reuse the game key as a password anywhere else. Report suspected compromise to the contact below.
11. Changes
Pre-release software changes. When this policy changes in a material way, we will update the effective date on this page. Keep using the site, launcher, or game after that date and the new policy applies. For a shutdown or a sale, we will say so here if we still control the domain.
12. Contact
SolidRusT Networks
Email: suparious@solidrust.net
Related: Terms of Service ·
Acceptable Use Policy