MilsimStack
PrivacyCookiesTerms
Legal · Privacy

Privacy Policy

This policy explains what MilsimStack collects, why it is needed, who can see it, and the choices available to players and unit operators.

Effective August 31, 2026 · Last updated August 31, 2026

1. Who operates the service

MilsimStack is operated under the Shadow Haven Studios name. For platform account, trial, security, and service-operation data, MilsimStack is the service operator. Each milsim unit controls the roster, personnel, operations, documents, and game records its administrators choose to place in the service. Questions can be sent to support@milsimstack.com.

2. Information we collect

Discord account and unit membership

  • Discord user ID and basic profile information returned by Discord sign-in, such as display name and avatar.
  • Discord server, role, channel, RSVP, and membership information needed for a unit's configured roster and bot features.
  • MilsimStack access roles, permissions, sign-in session data, and security records.

Unit records and content

  • Names, callsigns, ranks, billets, teams, join and departure dates, status, qualifications, attendance, and applications.
  • Operations, RSVPs, surveys, tickets and comments, discipline records, audit history, SOP acknowledgements, and unit documents.
  • Communications plans, server settings, integration tokens, and files or links submitted by authorized unit administrators.

Arma Reforger integration

  • Reforger player UID and display name, server and session identifiers, connection and attendance events.
  • In-game combat, casualty, injury, treatment, vehicle, and operation events sent by a unit's configured game server.
  • Medical events describe a game character's state and actions. They are not intended to record a player's real-world health information.

Contact and technical information

  • Discord handle or email, unit name, game, approximate unit size, and notes submitted with a trial request.
  • IP address used for abuse prevention and rate limiting on protected links, plus ordinary server security and error logs.
  • Public or shared Google Docs and Sheets content when an authorized administrator asks MilsimStack to import it.

MilsimStack does not currently use advertising pixels or third-party website analytics, and does not collect payment-card details through this application.

3. How information is used

  • Authenticate users, determine unit access, and protect accounts and tenant boundaries.
  • Provide roster, ORBAT, scheduling, operations, attendance, SOP, document, communications, and administration tools.
  • Link a Reforger identity to the correct roster member and produce the unit reports requested by administrators.
  • Operate Discord bot features, synchronize configured roles, and mirror authorized workflow activity.
  • Respond to support and trial requests, maintain the service, investigate misuse, and meet legal obligations.

Depending on location and context, processing is based on providing the requested service, legitimate interests in operating and securing it, consent where required, and compliance with law. MilsimStack does not sell personal information or use unit data for behavioral advertising.

4. When information is shared

  • Within a unit: unit owners and authorized members can see information according to the permissions configured by that unit.
  • Discord: sign-in and configured bot workflows exchange necessary identifiers, roles, channels, RSVPs, and workflow content with Discord.
  • Google: MilsimStack requests a document or spreadsheet only when an administrator supplies an import link.
  • Infrastructure providers: hosting, storage, networking, and security providers process information to run the service.
  • Legal and safety: information may be disclosed when reasonably necessary to comply with law, protect rights and safety, or investigate abuse.
  • Business change: information may transfer as part of a merger, financing, acquisition, or sale, subject to this policy and applicable law.

5. Retention and security

Unit records are generally kept while the unit account is active and for a reasonable period afterward so service can be restored, exported, secured, or closed. Short-lived sign-in and linking codes expire automatically. Security, audit, backup, and legal records may remain longer where reasonably necessary. Unit administrators can correct and remove many records directly and may request a database export or account deletion.

MilsimStack uses access controls, tenant isolation, signed sessions, transport security, and restricted administration. No online service can guarantee absolute security, so suspected account or data exposure should be reported promptly.

6. Your choices and rights

You may ask to access, correct, export, or delete personal information, object to or restrict certain processing, or withdraw consent where consent is the basis. Start with your unit administrator for unit-controlled records, or contact MilsimStack for platform records. Identity verification may be required, and some information may be retained when law or legitimate security needs require it.

You can disconnect Discord access through Discord, sign out to end the active MilsimStack session, and manage browser storage as described in the Cookie Policy.

7. International use, children, and changes

MilsimStack and its providers may process information in countries other than yours. Safeguards required by applicable law will be used for covered transfers. The service is not directed to children under 13 and should not be used below the minimum age required for Discord or local law.

This policy may change as the service changes. Material changes will be posted with a new update date and, when appropriate, additional notice. Continued use after the effective date is subject to the updated policy, except where law requires another form of agreement.

MilsimStack
Privacy policyCookie policyTerms and conditionsContact
© 2026 Shadow Haven Studios