◇ Command ForgeOpen workshop

Your decks. Your sharing choices.

Privacy information for the friends beta · Updated October 10, 2026

Command Forge helps you build, save and discuss Commander decks. This page explains the data used by those features, where it goes, and the controls available to you.

Who operates the workshop

The operator is Brad Boagenson. For privacy questions, corrections or help with deletion, contact bradlaytonfleming@gmail.com.

What you save

Guest decks, collection, preferences and Game Night sessions are saved in this browser. Signing in adds your email address, account identifier and session information, plus the decks, versions, collection, profile, playtests and other workspace records you choose to save to your account. Device drafts also remain available for offline work and conflict recovery. Searches and online features still make network requests when you use guest mode.

This information supports saving and syncing, account recovery, collaboration and the features you request. Feedback includes the text you submit and the context shown in its form. A note from Estimated Bracket includes the feeling you choose, any optional note, the estimated bracket number, and the deck id. It does not include the card list, deck notes, journals, or chats. Moderation reports and actions support community safety. Avoid including sensitive personal information or someone else's private details in notes, questions, screenshots or reports.

Who can see it

New cloud decks are private. You can invite collaborators with separate viewing or editing roles. Publishing makes the selected deck information discoverable; an unlisted link can be opened by anyone who receives it. Public deck views exclude private notes, journals, playtests, collection and AI conversations. A public profile or public comment is visible according to the choice you make. Review the sharing preview before publishing.

Link previews follow that choice. A public deck link can show the deck name, commanders, color identity, Estimated Bracket, and commander art when the link is pasted into another app. An unlisted link does not, unless you turn rich link previews on for that deck. Private decks are not previewed. Preview images use Scryfall card art and name the artist.

The Rule 0 page uses that same public or unlisted link. It adds the bracket you saved for your table, any win conditions you named, and, when a recorded game has a duration, how many of those games there are and their typical length. Playtest notes, results, player names, journals, and your collection stay off that page. Private decks are not on it.

A signed-in host can share a live Game Night table. That table stores the player names, commander names, life totals, poison, commander damage, and commander tax for up to 18 hours, plus the accounts that joined. It does not include the deck list, deck notes, tokens, or playtest. Anyone signed in with the private link can view and change those totals. Ending the table, or waiting until it expires, removes it.

A signed-in visitor of a public or unlisted deck can suggest card adds and cuts, with a short reason. That suggestion stores your account id, the reason, each card’s public details (the same fields already shown on a shared deck), and whether the owner accepted or rejected each card. The owner sees the name on your profile while reviewing it. Other visitors cannot see the suggestion. It is included in the account export of the author and the deck owner. Deleting the deck removes its suggestions. Deleting the author’s account removes the packages they wrote. An accepted change can remain in the deck’s change summary. Private decks do not accept suggestions. The same hourly social rate limit and moderation reports used for other community actions apply, including a report the owner can file on a suggestion.

Returning a deck to private or revoking a share stops future access through that share. It cannot retrieve copies someone already saved. Private account permissions limit access by other users; the operator and hosting providers retain administrative access needed to run and support the service.

Services involved

These providers can process connection and security information such as IP addresses and request times. Processing can occur outside your country. Their linked policies explain their own services; they do not replace this description of Command Forge.

Optional AI requests

When an AI provider is configured and you ask for AI help, the server sends your question, recent conversation and relevant deck evidence to that provider. Depending on the request, evidence can include cards, budgets, preferences, goals, collection counts, prior recommendations, playtest summaries, playgroup preferences and matchup notes. Private journal entries are excluded. Ordinary deck analysis does not require AI. Provider retention is separate from your Workshop account, so do not include secrets or sensitive personal details in AI requests.

Cookies and diagnostics

Sign-in cookies maintain your session. Browser storage holds drafts, offline data and preferences. Essential application diagnostics use an error reference, feature area, time, app version and outcome instead of deck bodies, chat text or credentials. That reference is kept for 90 days so support can match a report after hosting logs expire. The stored record is only the reference, feature area, app version, time, and outcome or status. It does not include the error message, the page address, an account identifier, or the contents of a deck. Usage records can associate an account with request counts, timing, outcomes and AI token totals. Rate limits use hashed identifiers. Infrastructure providers can also keep their own request and authentication logs.

Optional product event counts are off by default. You can turn them on or off in Settings; they record actions such as importing or saving a deck, without its contents. When they are on, the server adds one to a daily total for that action and app version. The total is not tied to an account or browser. Counts older than 90 days are removed. They describe how often an action happened, not who did it. This application does not include advertising trackers or an advertising data-sale feature.

Retention and deletion

Saved account content and immutable versions have no automatic expiry. Archiving or moving a deck to Trash does not erase its stored history. Account deletion revokes sessions and removes the live account and its owned records, including publications. Moderation reports and audit entries can remain after reporter and actor references to the deleted account are removed. Their target identifiers can still identify a deleted account. Change summaries on another person's deck can remain with the actor reference removed. Retained text is not automatically scrubbed of names or other details.

Scheduled housekeeping removes rate-limit records older than 2 days, save-retry receipts older than 30 days, and usage, maintenance, error-reference, and product-count records older than 90 days. Cleanup runs periodically, so those ages are cleanup thresholds. Provider logs, database backups and isolated recovery copies have separate retention and can contain earlier data after it is removed from the live account. Contact the operator about retained reports or recovery copies.

Your controls

Export cloud records or delete your account from Account. Settings provides browser backup tools and analytics preferences. Review both your account export and device backups before clearing any data, especially unsynced drafts. Browser copies, downloaded exports and copies held by recipients require separate removal. For access, correction or deletion help beyond these controls, use the privacy contact above; account ownership may need to be verified.

Storage and recovery help · Contact and reporting