Flak Jacket Chaos
Privacy Policy
Updated November 1, 2026
The SpiderTaz Network Privacy Policy covers shared identity and network services. This page explains the current Flak Jacket Chaos features.
Accounts and saved entries
Public dossiers and search are available without signing in. SpiderTaz handles sign-in and returns a signed account confirmation. Flak Jacket Chaos uses your network user identifier for its local session and private fieldbook; it does not maintain another password database. Your fieldbook is not public.
Community and player profiles
Publishing a post or reply makes its text and your Flak Jacket Chaos screen name public. Your profile bio and faction are private by default and become public only when you choose that option. Making your profile private does not hide previously published posts or replies. You can edit or remove your own visible contributions; earlier versions and removed content are retained privately for safety and moderation. Reports, reporting details and moderator notes are visible only to authorized reviewers. Content hidden by moderation cannot be republished through an author edit.
Creator pages and shared work
Publishing a creator page makes your chosen FJC screen name, headline, creator bio, website/channel links and published showcase work public. Creator drafts and private rights notes stay private to you and authorized reviewers. Your separate player profile is not made public by creating a creator page. Unpublishing or moderation removes the relevant page or work from discovery while retaining saved versions and private review history. External work is linked rather than embedded; opening a link takes you to that site and its own data practices. Channel links and rights declarations are supplied by the creator and are not automatic ownership verification. Contact SpiderTaz for a review or privacy request.
Event participation
Tournament entry names, captain screen names and confirmed roster screen names are public. Invited players confirm their own place before their name appears on the event roster. Pending invitations are private to the invited player, their captain and authorized event managers. Organizers retain registration, confirmation, check-in, withdrawal and exclusion records with private reasons and audit history. Locking records the agreed FJC roster independently of later crew changes. You may withdraw before rosters are locked; retained records support event integrity and safety review. Registration does not copy shared account names or email addresses and does not charge money or grant game rewards.
Tournament results and evidence
Bracket entry names, verified scores, winners and final standings are public. Match evidence links, captain reports, disputes and review reasons are private to the current match captains and authorized event managers or reviewers. A reviewer must not be a player in that tournament. We retain reports and invalidated results in private audit records. Corrections can reset later matches and replace published standings; the earlier records remain for integrity and recovery. Evidence URLs are supplied by users and are not automatically fetched by this site.
Developer webhook receivers
Application owners may select sandbox record-change notifications and register a public HTTPS receiver. Messages contain the application identifier, event and delivery identifiers, test slot name, revision and removal state; they do not include test documents or player data. Receiver addresses, operational signing keys, settings history, queued messages and delivery attempts are retained privately to operate and audit delivery. Signing keys are shown once and can be rotated; the sender retains private signing material. Pausing a receiver or changing its settings cancels older queued work; an already in-flight request may complete. Failed deliveries retry automatically with bounded attempts. Receiver operators control their own received copies and must protect signing keys.
Developer sandbox
Application owners can create scoped, expiring sandbox keys. The complete secret is shown once; we retain its verification hash, permissions, expiry, revocation state and private key-change history. Keys access only their application’s game test metadata and test records. Synthetic test documents are private to that application’s authorized keys, separate from real player progress. Removing a test document clears its contents but keeps the slot name and revision. Write retry receipts and call counters support safe retries and service limits. Key revocation does not erase test data. Do not submit personal information or secrets in test documents. Contact SpiderTaz for access or deletion requests.
Developer submissions
Developers submit game listings under their FJC screen names. Submitted versions and decisions are retained separately from later private drafts. Approved descriptions, game links and credits are public. Rights notes, drafts and review history are private to the submitting developer and network administrators. Archiving removes a listing while retaining its records. External games have their own data practices; links open only when you choose them.
Player images
Players can upload JPEG, PNG and WebP images for their profiles and community posts. We retain processed images, thumbnails, ownership declarations, captions and change history; original files and embedded metadata are not retained. Library images stay private until deliberately placed. A profile placement follows your public-profile setting; a post placement follows that post’s visibility. An image reused elsewhere can remain public after one placement is removed. Alt text, captions, credits and source links accompany public images. Retiring withdraws all public uses while retaining bytes and history for recovery. Reports and reviewer notes stay private to reviewers; reviewers can inspect reported images, not unrelated private libraries. Contact SpiderTaz about retained data or rights requests.
Editorial images
Authorized editors can upload image artwork and record its rights. Processed images and thumbnails are retained in the service; original upload files and embedded metadata are not retained. Uploaded images remain private until used in a published entry. Image alt text, captions, credit and source URLs are public on published uses. Rights notes, asset history and unused or retired image previews are private to authorized editors. Retiring an image removes its public delivery while retaining its record and bytes for recovery.
Private crew conversations and notifications
Current active members can read their crew’s chat under FJC screen names. Leaving, removal, account suspension or crew hiding ends access; an archived crew keeps read-only history for its members. Members can edit visible messages, remove their own messages, report concerns and mute unread-chat alerts. Crew owners/officers can hide or restore moderation visibility. Reports, message versions and private reasons are retained for community reviewers; reviewers see reported messages and their evidence rather than unrestricted access to private chat. Removing a message hides its text from members while retaining private safety records. Read positions and muting choices belong to you. Membership decisions produce private in-site notifications. These features do not send email or browser push notifications. Contact SpiderTaz for retained-content or privacy requests.
Crews and membership
Crew names, descriptions, notices and active rosters are public under FJC screen names. Requests awaiting approval and staff reasons remain private. Crew staff can review requests and manage ordinary members; owners appoint officers and transfer ownership. Owners and authorized community reviewers can read retained crew history. You can leave a crew or withdraw a request; owners must transfer ownership before leaving. Membership changes and earlier page versions are retained privately for safety and recovery. Archiving closes joining without deleting records.
Game progress and standings
Chaos Command stores your faction, preparation choices, mission history, game XP, supplies and achievements against your network user identifier. These records are private. If you explicitly opt into public standings, your Flak Jacket Chaos screen name, current faction and game XP appear there. You can turn this off in campaign preferences. Monthly season records retain your best victorious mission results by UTC month. The same public-standings preference controls sharing of your FJC screen name, faction and season route points; opting out also hides historical season listings. Season points do not change lifetime XP or have cash value. Game records are retained to preserve progression, prevent duplicate rewards and investigate faults; contact SpiderTaz for access or deletion requests.
Cookies and browser storage
A secure session cookie maintains local sign-in and protects account actions. Your appearance preference, briefing draft and the date you dismiss the cookie notice are stored in this browser. Briefing drafts are not uploaded to your fieldbook. The notice dismissal lasts 28 days; clearing browser storage removes these preferences and drafts.
Shared services and operational records
The network menu loads from SpiderTaz and can display network account controls. The shared top and bottom page inserts are managed by the network operator and may change. Hosting and security systems may retain request and error records to operate the service and investigate abuse. Search terms are sent to this site; the separate footer search sends your query to SpiderTaz.
Your choices
Remove saved entries from your fieldbook, reset your local briefing or clear this site's browser storage. Local sign-out clears this property's session; network sign-out clears sessions through the network chain. For account access, deletion, privacy questions or retention details, contact SpiderTaz.