File 0005 // Privacy record

BLACK STACK + Shardfall + Brass & Brine // Effective 16 November 2026

Privacy by architecture.

Blackglass Assembly does not collect or retain player personal data on developer-controlled systems. Its games store their own records on your device and use only the storefront, Steam, and multiplayer services described below.

IMG_0005 // Blackglass markNo trackers filed

A complete account of the data flow.

This policy expressly explains what BLACK STACK, Shardfall, and Brass & Brine capture, how it is used, who receives it, and how long Blackglass Assembly retains it across local records, storefront integrations, multiplayer, cloud saves, and this website.

Developer collection
Ordinary gameplay of BLACK STACK, Shardfall or Brass & Brine does not send personal data to Blackglass Assembly or any developer-controlled server.
Developer retention
Blackglass Assembly operates no player database, telemetry backend, account service, or multiplayer server, and retains no personal data from ordinary gameplay.
Sale or advertising
No sale of data, advertising, profiling, or marketing trackers.
Local game data
Each game writes saves and settings to the player's device. BLACK STACK also keeps recovery files and an optional local balance log; Shardfall keeps battle replays and, after a crash, a local crash report. None of these files is uploaded to a developer-controlled server.
Platform services
The games use storefront services for authentication, licensing, achievements, and cloud saves; Shardfall and Brass & Brine also use Steam friends, invites, and joinable games. Blackglass Assembly does not store platform-account data on a developer-controlled server.
Multiplayer
Shardfall and Brass & Brine connect players' computers to each other. Players in a game see each other's in-game names and actions and can receive each other's IP addresses. Shardfall has text chat; Brass & Brine sets up online co-op through third-party connection services.

01 // Scope and controller

Who this policy covers

Effective 16 November 2026. This policy applies to BLACK STACK, Shardfall, Brass & Brine, and the blackglassassembly.com website operated by Blackglass Assembly.

All three games are developed and published by Blackglass Assembly, an independent game studio based in Australia. This is the official privacy policy for those games, and the one linked from BLACK STACK's storefront and account-service applications.

Blackglass Assembly does not require or operate a Blackglass Assembly player account. BLACK STACK is a single-player product. Shardfall and Brass & Brine include multiplayer, which connects players' computers to each other directly or through the platform and connection services described below. Blackglass Assembly does not operate developer-controlled gameplay, analytics, advertising, matchmaking, multiplayer, social, or telemetry servers.

02 // BLACK STACK: data captured by the game

No personal data is sent to us

Playing BLACK STACK does not send personal data to Blackglass Assembly. We do not automatically receive, collect, or retain your name, email address, postal address, password, payment information, precise location, contacts, messages, voice data, advertising identifiers, device identifiers, IP address, or gameplay history on any developer-controlled system.

BLACK STACK creates local files so the game can function. These files are controlled by the player and are not automatically transmitted to Blackglass Assembly.

  • Save and recovery files containing profile progress, unlocks, settings, achievement-delivery state, and active-run state.
  • A local-only balance log, enabled by default and switchable off in SYSTEM CONFIG, containing run information such as timestamp, seed, identity, result, act, floor, difficulty, statistics, and protocol or relic identifiers.
  • Temporary runtime information held in computer memory while the game is open.

03 // BLACK STACK: Epic Account Services

How BLACK STACK uses the Epic integration

The Epic Games Store build connects to Epic Account Services and Epic Online Services only for launcher-session authentication and Epic achievement delivery.

For those functions, BLACK STACK processes a platform-generated Epic Account ID and Product User ID, a launcher exchange code or authentication token, session state, and achievement result data during the running session. BLACK STACK requests the Basic Profile authorization scope but does not read or use email addresses, friends lists, presence, display names, or external-account details.

BLACK STACK uses those values only to authenticate the current launcher session, connect to the achievement service, submit achievement unlock identifiers, and reconcile achievement status. It does not write them to the BLACK STACK profile save or local balance log, and it does not transmit them to a Blackglass Assembly server. Values held by BLACK STACK in memory are cleared when the game closes. Local diagnostic output created while the application runs is not automatically sent to Blackglass Assembly.

Blackglass Assembly does not operate Epic's services and makes no statement about provider-side collection, use, sharing, or retention. For that information, read Epic Games' privacy policy.

Read Epic Games' privacy policy

04 // BLACK STACK: Steam services

How BLACK STACK uses Steamworks

The Steam build connects to Steamworks only for launcher authentication and licensing, achievement delivery, and configured Steam Cloud integration.

BLACK STACK does not request Steam passwords or payment details, does not write Steam account data to the BLACK STACK profile save or local balance log, and does not transmit Steam account data to a Blackglass Assembly server.

Blackglass Assembly does not operate Steamworks and makes no statement about provider-side collection, use, sharing, or retention. For that information, read Valve's privacy policy.

Read Valve's privacy policy

05 // BLACK STACK: cloud saves

How BLACK STACK handles local saves

BLACK STACK writes its profile save locally. That file can contain settings, progression, inventory, decks, loadouts, achievement-delivery state, run history, and an active-run checkpoint. Blackglass Assembly does not upload or retain a developer-controlled copy of that save.

If the player enables a storefront cloud-save feature, BLACK STACK continues to use the configured local save location. Blackglass Assembly does not operate the synchronization service or receive a separate copy. Consult the relevant provider's privacy policy and account documentation for provider-side processing, retention, conflict handling, restoration, and deletion.

06 // Shardfall: data kept on your PC

What Shardfall writes, and where

Shardfall writes its files to %LOCALAPPDATA%\Shardfall\Saved on the player's PC. These files are controlled by the player and are not transmitted to Blackglass Assembly. The shipped game writes no gameplay, network, or chat logs.

  • A settings file containing settings, key bindings, campaign progress, the name you use in multiplayer, and the last address you joined by. Steam Cloud keeps a copy of this file and of your saved games.
  • Saved games and the autosave, which record the match setup, including player names. Online battles cannot be saved.
  • Replays of your 30 most recent battles of 30 seconds or longer, online battles included, with every player's in-game name and the result. Replays stay on your PC and are not synchronized to Steam Cloud.
  • Display settings such as window mode and resolution.
  • After a crash, a crash-report folder containing a snapshot of part of the game's memory at the moment of the crash, the install path, a random machine identifier, and, if the Epic Games launcher has stored one on that PC, an Epic account ID. The machine identifier is created by Unreal Engine, which Shardfall is built with, and kept in the Windows registry. Shardfall never uploads crash reports; one leaves your PC only if you choose to send it to support.

07 // Shardfall: Steam and multiplayer

How Shardfall uses Steam and connects players

Shardfall requires Steam. It uses Steamworks to confirm that the signed-in account owns the game, to deliver achievements, and for Steam Cloud. It reads your Steam display name, the starting name for multiplayer, and your Steam ID. While the MULTIPLAYER screen is open, it reads your Steam friends' display names, the game they are playing, and their rich presence, to list the games they are hosting.

When you host or join a multiplayer game, Shardfall sets your Steam rich presence, which your Steam friends can see: what you are doing and, while a game you host has an open seat, the map, the number of players, and a join link containing your Steam ID. INVITE FRIENDS opens Steam's own invite dialog.

Players in a multiplayer game receive each other's in-game name (your Steam display name unless you change it), faction, colour, team, orders, connection quality, and any chat messages typed. Chat is text only and is relayed by the host to the other players. Shardfall keeps recent chat lines only in memory while it runs and never writes them to disk.

Joining a Steam friend uses Steam's networking, which connects players directly or relays traffic through Valve's servers; whether your IP address is shared with the other player then follows your Steam client's settings. Joining by address connects players' computers directly, so the host and each player receive each other's IP addresses. While a game is hosted with its lobby open, Shardfall announces it on the local network, with the host's in-game name, the map, and the host's address, to every computer on that network.

Shardfall uses no analytics, telemetry, advertising, or crash-report uploads, and it does not contact any Blackglass Assembly server. Blackglass Assembly does not operate Steamworks; for Valve's processing, read Valve's privacy policy.

Read Valve's privacy policy

08 // Brass & Brine: data kept on your PC

What Brass & Brine writes, and where

Brass & Brine writes its files to %APPDATA%\Brass & Brine on the player's PC. These files are controlled by the player and are not transmitted to Blackglass Assembly. The game writes no logs and no crash reports.

  • A save file containing the captain's record, the voyage under way, and the best wave, including the names entered for split-screen crewmates and the type of controller each used. When Steam Cloud is on, Steam keeps the same file.
  • Settings, key bindings, your co-op name, a random player identifier the game creates, the last voyage code you used, and a backup of the previous save when a newer cloud copy replaces it, kept in the game's local storage on that PC only.
  • A tally of where damage came from during play, kept in the save to help balance the game. It is never uploaded.

09 // Brass & Brine: Steam and online co-op

How Brass & Brine uses Steam and connects players

On Steam, Brass & Brine uses Steamworks for achievements, Steam Cloud, and Steam friends. Hosting an online voyage opens a friends-only Steam lobby that holds the voyage code, and sets a join entry in your Steam rich presence so friends can join; Invite Steam Friends opens Steam's own invite dialog. The game reads your Steam display name as the starting name for co-op. It does not store or send your Steam ID.

Online co-op connects each guest's computer to the host's over WebRTC. To set up that connection, each player's game contacts the PeerJS project's public connection broker (0.peerjs.com), Google's public STUN server, and PeerJS's public TURN relay servers. These services, which Blackglass Assembly does not operate, can see each player's IP address and connection details, and the broker sees the voyage code. The broker does not carry the game itself; a TURN server relays the game's encrypted traffic only when a direct connection cannot be made.

Players in a voyage receive each other's captain name (your Steam display name unless you enter another), random player identifier, ship and crew setup, and in-game actions. The host and each guest receive each other's IP addresses, as any direct connection between computers requires. Brass & Brine has no text or voice chat; crews signal with preset flags.

Joining by voyage code also works without Steam. Brass & Brine uses no analytics, telemetry, advertising, or crash reporting, and it does not contact any Blackglass Assembly server. Blackglass Assembly does not operate Steamworks; for Valve's processing, read Valve's privacy policy.

Read Valve's privacy policy

10 // How data is used

Purpose limitation

Local game data is used only to save progress, restore interrupted runs and voyages, remember settings, show earned unlocks, replay battles, and support local balance review. Platform and multiplayer information is used only to authenticate the current session, deliver the platform features described above, connect players, and keep their games in step.

Blackglass Assembly does not use player data for advertising, behavioural profiling, cross-site tracking, automated eligibility decisions, sale, rental, data brokerage, or marketing.

11 // How data is shared

No developer sale or disclosure

Because Blackglass Assembly does not collect player personal data on developer-controlled systems, we do not sell, rent, license, trade, or share that data with advertisers, data brokers, analytics providers, or other game developers.

Each game sends only the requests its storefront integration needs for authentication, entitlement or licensing checks, achievements, cloud saves, and, in Shardfall and Brass & Brine, friends, invites, and joinable games. In multiplayer, Shardfall and Brass & Brine share with the other players in the game, and with the connection services described above, only what is needed to play together. No game forwards platform-account data to a Blackglass Assembly server. Blackglass Assembly makes no representation about provider-side processing; consult the relevant provider's privacy policy. If Blackglass Assembly were legally required to disclose information, we could disclose only information actually in our possession; ordinary gameplay creates no developer-held player record to disclose.

12 // Retention and deletion

What remains, where, and for how long

Blackglass Assembly retains no player personal data from ordinary gameplay because no such data is sent to or stored on a Blackglass Assembly server.

  • The games do not transmit local saves, settings, replays, recovery files, crash reports, or balance logs to a Blackglass Assembly server. Those files remain on the device until the player removes them or the local storage becomes unavailable. Shardfall keeps only its 30 most recent replays.
  • BLACK STACK does not write platform identifiers or authentication values to its profile save or local balance log. Shardfall and Brass & Brine store the in-game name you play under, which starts as your Steam display name, in their local settings, and Shardfall's settings file, which Steam Cloud copies, also keeps the last address you joined by. Values held in application memory, including Shardfall's chat lines, are cleared when the game closes.
  • Blackglass Assembly does not set or control retention for storefront services or third-party connection services. Consult the relevant provider's privacy policy and account documentation.
  • If you voluntarily email us, we receive the address and message you choose to send, and any file you choose to attach, such as a save or a crash report. We use it only to answer the request and retain it only as long as reasonably necessary to resolve the request or meet a legal obligation. It is not added to a marketing list or sold.

13 // Player controls

You control the local record

You can disable future local balance-log entries in BLACK STACK's SYSTEM CONFIG, delete the local analytics file, or delete the BLACK STACK save family to remove local progress and settings. In Shardfall and Brass & Brine you can change the name other players see before you host or join, and you can delete a game's folder, listed on the support page, to remove its local saves, settings, and replays; Shardfall's settings file also holds campaign progress. Make any backup you want before deleting local files. The games cannot delete data held outside their local files; with cloud saves on, the storefront may restore its copy, so consult its documentation before deleting.

The games provide no in-game controls for storefront account data or provider-hosted storage. Questions or requests about provider-held data should be directed through the relevant provider's privacy and support channels. Because Blackglass Assembly does not hold a player account or player database, it normally has no developer-held gameplay record to access, correct, export, or erase.

14 // Website

No cookies, pixels, or analytics

blackglassassembly.com contains no Blackglass Assembly-added advertising cookies, analytics cookies, tracking pixels, fingerprinting, account registration, or contact forms. Blackglass Assembly does not use website requests to build player profiles or serve advertising.

The hosting account can expose ordinary request and security logs containing information such as IP address, browser or user-agent information, requested URL, date and time, and error or security events. Blackglass Assembly uses any such access only for site operation, troubleshooting, and security; it does not export those logs into a player database or use them for advertising. For the hosting provider's separate practices, read its privacy policy.

Read the hosting provider's privacy policy

15 // Children

No direct collection from children

BLACK STACK and Brass & Brine contain no chat. Shardfall's multiplayer includes text chat between the players in a game; Blackglass Assembly does not receive, review, or store it. None of the games includes user-generated-content sharing, targeted advertising, or a Blackglass Assembly account system, and none sends children's personal data to Blackglass Assembly. Any data practices associated with a storefront account are outside the games and are described in the relevant provider's privacy policy.

16 // Changes and contact

Questions, requests, or policy updates

We may update this policy if the games' data practices or platform features change. Material changes will be published on this page with a new effective date before they apply where required.

For a privacy question or request, email privacy@blackglassassembly.com. Do not attach a save file unless support has specifically requested it and you choose to provide it.

Questions about this policy?

Contact Blackglass Assembly directly. Ordinary gameplay creates no developer-held personal-data record.

privacy@blackglassassembly.com