Privacy policy
How the current invitation-only pilot handles your information.
Updated 15 November 2026 · Current pilot notice
Contact and scope
This notice covers the hosted Bastion Master pilot and its companions. The existing pilot privacy contact is jeremiah.joseph.costello@gmail.com. Contact this address about personal information, access, correction or deletion.
It describes the service currently available. Public registration, payments, portrait uploads are not enabled.
Information the service stores
- Account access: the Google account identifier and email used to verify invited membership, your campaign role, invitations and access records.
- Collaboration: invite-link hashes, roles and selected rights, expiry and acceptance records, comment display names, party-visible comments and manager replies. Raw invite tokens are shown when created, not stored in the invite-link table.
- Beta applications: your submitted name, Google account email, party size, campaign stage, optional note and feedback preference, plus application status. These are private to the development team; applying does not grant campaign membership or create a paid account.
- Development feedback: your account email, feedback type and text, app section, campaign reference and review status. This is visible to the development team and its author, rather than other party members. Campaign saves and notes are not attached automatically.
- Sessions: expiring sign-in sessions and temporary sign-in/approval records. Session credentials are stored hashed on the host.
- Campaign content: character names and levels, buildings, personnel, finances, inventory, Household profiles and descriptive boons, expeditions, banner choices, notes and recorded changes.
- Support: information you choose to send when requesting help.
Google handles your Google password. Bastion Master does not ask you to send that password or your sign-in codes.
Why it is used
Account and session data are used to provide invited access and enforce permissions. Campaign records provide shared play, saved decisions, revision history and recovery. Access records help protect the pilot and investigate errors. Support messages are used to respond to your request. Beta applications are used to select and contact testers; development feedback is used to improve the app. Hashed, short-lived rate-limit keys help prevent application spam.
The current application does not include advertising or a third-party analytics SDK.
Who can see campaign information?
The DM and authorized Bastion Manager can manage the campaign within their permissions. Player members receive a limited shared view. Floor plans, personal room proposals, homecoming decisions, inventory notes, Household descriptions, approved boon descriptions, party comments and manager replies are shared content; do not use them for confidential information.
Administrative records and private campaign history are not included in the ordinary player view. The operator may access stored records to operate the pilot, handle support or review privacy requests.
Hosting and service providers
The hosted pilot runs on Cloudflare Workers and D1. Google provides account authentication. These providers may process technical connection information, including network and device information, under their own arrangements and policies.
See Google’s privacy policy and Cloudflare’s privacy policy. This notice does not promise that all processing occurs in one country.
Cookies and information on your device
Necessary sign-in cookies maintain the session and protect the sign-in process. Hosted sessions expire after seven days; temporary sign-in flows have shorter expiries. You can sign out to end your current session.
The app also stores interface preferences, guide progress and unfinished setup drafts on your device. These can include names entered during setup. Private Practice uses temporary tab memory and resets when the page reloads. No advertising cookies are added by the application.
Retention and recovery
Sessions expire or are revoked. Campaign content and revision history remain while the pilot’s campaign is retained, so the group can review decisions and recover earlier states. History can include the account identifier responsible for an action. Signing out does not delete those records.
The pilot has no automatic account-deletion portal or fixed automatic campaign-deletion schedule. The operator reviews deletion requests, including shared-history and security implications, and can explain any information that must be retained. Save exports and revision history should not be treated as a guarantee against every form of data loss.
Your choices and requests
You can sign out, ask the DM to revoke access, request access to or correction of your personal information, and ask for deletion. Where applicable, you can also ask about portability, restriction or objection and contact your data-protection authority.
To make a request, use the privacy contact above. We may need to verify that the request relates to your account. Do not send a password or sign-in code.
Authorized hosts can export campaign saves. Exports may contain information about other party members, so share and store them with care.
Changes to this notice
This page will be updated when the pilot’s data handling changes. New services such as uploads, paid accounts or forums will need their own applicable information before they are enabled.
Member community forums
Forums are visible to signed-in beta members across Bastion groups. Your chosen forum name and the text you publish appear to those members; your Google email is not displayed. Forum profiles, discussions, replies, timestamps and moderation records are stored separately from campaign saves. Reports and their reasons are visible only to the community moderator. Private campaign saves, party comments and invitation links are not copied into the forums. Do not post personal information or private campaign details. Contact support for forum-name or content-removal requests.
Optional forum profiles and Gravatar
You may share an About introduction and select games you play. These appear to signed-in beta members across groups, alongside your forum name; they never grant access to your Bastion. You can edit or clear these optional fields. Profile revisions are used to prevent one save overwriting another.
Avatars use local initials by default. If you choose Use my Gravatar and save, we store a SHA-256 hash of your normalised sign-in email and request its avatar from Gravatar, operated by Automattic. The email and hash are not published in your forum profile. Avatar images are served through Bastion Master, so visitors’ browsers do not load Gravatar directly. Gravatar processes the email-derived identifier and server request information under its own privacy policy. Images may be cached in a visitor’s browser for up to five minutes. Uncheck Gravatar and save to stop new avatar requests and remove the stored hash. No Gravatar profile biography or other account details are imported. Automattic’s privacy policy.
Voluntary development questionnaire
The optional questionnaire stores your selected answers and written feedback linked to your signed-in account, with creation and update times. This lets you review, change or withdraw your response. It is not anonymous. Only the development team can review responses; the review screen shows no email addresses. No campaign saves, party comments or forum posts are attached. Taking part does not affect access or features. Nothing is submitted until you choose Submit; you may skip any question. Withdrawal removes the response from active questionnaire results.
Forum trust and moderation
Forum participation levels appear beside posts. Trust changes, first-contribution decisions, timestamps and moderator reasons are stored for moderation. Reasons are shown privately to the affected member and moderator; Google emails and private Bastion information are not included in public forum badges. New members’ pending contributions are visible only to their author and the moderator until approved. Reports do not automatically lower trust, and we do not track reading time or visits to award rank. The forum stores your last explicitly marked-read discussion version, up to 500 markers per account, to share unread indicators across devices. It does not record reading duration or use read markers for trust. Edited posts retain prior text for moderator review. Personal forum bookmarks store your account reference, discussion reference and save time, up to 200 per account, and are not shown to other members. Pinned announcements and selected answers are community-visible discussion status; changing them does not grant Bastion access. Posting drafts are held only in the current page’s memory and disappear when it closes or reloads. Eligible unsaved inventory, personal-room and new-comment fields may also be kept in bounded tab memory through a shared refresh or conflicting save. Hidden fields, passwords and files are excluded; removed rights, a different signed-in account and replacement campaigns prevent restoration. A private account marker helps associate unsent input with the current account. Refreshing does not submit these inputs. Forum restrictions do not change private Bastion membership.
Security and temporary practice
Practice now runs in a separate temporary server session so the rules engine is not delivered to browsers. Practice data expires after one hour and is removed when expired-session cleanup runs; reload starts a new example. It is never attached to your real Bastion. Internet access is required.
To limit abuse, the app keeps short-lived request counters using keyed hashes of account identifiers and network addresses. Routine security diagnostics contain event categories, keyed actor hashes and timestamps, not raw IPs, emails, session tokens, messages or campaign names. These routine diagnostics expire after14days; they are not a forensic incident archive. When activated, Cloudflare Turnstile processes a security challenge for new-member posting, beta applications and practice starts; the app validates hostname, action, account/network binding and token reuse on the server. You can inspect active session counts and sign out all devices in Account security. Backups may retain earlier data separately.