← BACK TO OPSCOM

PRIVACY POLICY

Effective Date: 21/10/2026 · Last Updated: 21/10/2026

1. Who we are

OPSCOM ("OPSCOM", "we", "us") is an online platform for managing military simulation (milsim) communities, available at https://opscom.one. OPSCOM is run by OPSCOM, registered with the Netherlands Chamber of Commerce (KvK) under number 42049425.

Contact for privacy matters: opscom.contact@gmail.com

This policy explains what personal data we process, why, who we share it with, how long we keep it, and what rights you have. It should be read together with our Terms of Service.

2. Our role: controller and processor

  • Accounts, sign-in, billing and platform security: OPSCOM decides how this data is used. We are the controller.
  • Community content: Each community on OPSCOM is run by its owner and staff, who decide what is recorded about their members. This includes personnel files, ranks, notes, attendance, awards and disciplinary records. For this content the community owner is the controller, and OPSCOM stores and processes it on their behalf as a processor. Questions or requests about what a community records about you should go to that community's staff first. If you can't reach them, contact us and we will help.

3. What we collect

3.1 When you sign in with Discord

Signing in requires a Discord account. With your permission, Discord shares the following with us (OAuth scopes identify, email and guilds):

  • your Discord user ID, username, display name and avatar
  • your email address
  • the list of Discord servers you are in

We use the server list only at sign-in, to match you to OPSCOM communities linked to those servers. We do not store the list.

We also store the Discord access token and refresh token from your sign-in. We need them to keep your community memberships up to date without asking you to sign in again. We use them only to read your Discord server list.

3.2 Community owners

If you create a community, we also process:

  • Google account: Owners must link a Google account before creating a community. Google shares your Google account ID, name, email address and profile picture with us, and we store them with your account. We use the linked account only to verify that the owner of a paid community holds an established Google account in addition to their Discord account. This helps prevent abuse of free trials and paid communities. We don't use your Google account to sign you in or to email you, and we don't access any other Google data.
  • Subscription and billing: your Stripe customer ID, subscription ID, subscription status, trial end date and billing period. Payments are handled by Stripe, and we never see or store your full card or bank details.
  • Discord server details: the Discord server ID you link, and the settings you configure for it.

3.3 Members of a community's Discord server, including people without an OPSCOM account

When an owner connects their Discord server, our Discord bot syncs that server's member list into the community. This creates a personnel record even for members who have never signed in to OPSCOM. For each member we store:

  • Discord user ID
  • account username, display name and server nickname
  • avatar
  • membership status

If you later sign in, that record is linked to your account. Owners can exclude specific users and roles from the sync.

3.4 Personnel and activity records created by community staff

Depending on which features a community uses, its staff may record:

  • Profile details: a display name, timezone, custom avatar and free-text notes
  • Structure: rank, unit, position, and rank and assignment history
  • Activity: awards, certifications, training results, operation and training sign-ups, attendance, and promotion points
  • Disciplinary records: warnings, strikes, suspensions and other entries, including the reasons given, who issued them and when

3.5 Content you upload or create

This covers images (community logos, rank insignia, unit insignia, award and device images, operation and training covers, member avatars), attachments, documents, tactical maps (TacMaps) and their share links, Google Drive links you paste in, and messages scheduled to be sent by Discord direct message.

Some uploaded files are public by link. Images, member avatars and training attachments are stored so that anyone with the direct link can open them. Operation attachments are private. Don't upload anything to OPSCOM that you wouldn't want to be viewable by someone holding its link.

3.6 Logs and security

  • Audit log: each community has a log of actions taken by its staff (who did what, to whom, and when). It includes names and before/after values.
  • Platform bans: if an account is banned from the platform, we keep its Discord user ID so the ban can be enforced.
  • Server logs: our hosting provider automatically records technical request data, such as IP address, browser type and the time of each request, to run and secure the service.

3.7 What we don't do

  • We don't use analytics, advertising or tracking tools.
  • We don't sell your personal data.
  • We don't use your data for automated decisions that have legal or similarly significant effects on you.

4. Why we use your data, and our legal basis (GDPR Article 6)

PurposeLegal basis
Creating your account, signing you in, linking you to your communitiesPerformance of a contract (Art. 6(1)(b))
Providing community features to owners and their membersPerformance of a contract with the owner (Art. 6(1)(b)). For members without an account: the owner’s legitimate interest in managing their community (Art. 6(1)(f))
Billing, subscriptions and trialsPerformance of a contract (Art. 6(1)(b))
Service emails, such as your trial ending soonPerformance of a contract (Art. 6(1)(b))
Verifying community owners with a linked Google accountLegitimate interest in preventing abuse of trials and paid communities (Art. 6(1)(f))
Security, preventing abuse, enforcing bans, audit logsLegitimate interest in keeping the platform safe (Art. 6(1)(f))
Keeping accounting recordsLegal obligation (Art. 6(1)(c))

5. Who we share data with

We use the following service providers, each only for the purpose shown:

ProviderPurposeLocation
SupabaseDatabase, sign-in and file storageEU (Frankfurt, Germany)
VercelWebsite hosting and server logsProcessed in the EU (Frankfurt, Germany). Vercel Inc. is a US company
DiscordSign-in, server member sync, bot messages and webhooksUSA
GoogleAccount linking for community ownersUSA
StripePayment processing and subscriptionsUSA / EU
ResendSending service emailsUSA

Within your community: other members of the same community can see your personnel record, as allowed by that community's permission settings. If a community sets up Discord webhooks or scheduled direct messages, information such as names and event details is posted to Discord.

Authorities: we may disclose data when the law requires it. As our Terms state, we report child sexual abuse material to the relevant authorities.

6. International transfers

Our database, file storage and server-side processing are located in the EU (Frankfurt, Germany). Some providers, namely Discord, Google, Stripe and Resend, and Vercel as a US company, may process data in, or give access to it from, the United States. Where personal data is transferred outside the European Economic Area, it is protected by the EU-US Data Privacy Framework where the provider is certified under it, or by the European Commission's Standard Contractual Clauses.

7. How long we keep data

DataHow long
Account data (Discord profile, email, sign-in tokens)Until your account is deleted
Community data, personnel records, audit logsUntil the community deletes it, or the community itself is deleted
Members who have left a community’s Discord serverMarked inactive, then deleted automatically after the community’s grace period (30 days by default; each community can change it)
Subscription recordsFor as long as the subscription exists. Invoices and payment records are kept by Stripe, and we keep the records Dutch tax law requires us to keep (up to 7 years)
Platform ban recordsFor as long as the ban is in force
BackupsWe don’t keep separate backups of our database. Deleted data is removed from our live database straight away
Server logsKept by our hosting provider for a short period (no more than 30 days)

8. Cookies and browser storage

We use only what the service needs to work:

  • Sign-in cookies (set by Supabase) to keep you logged in. These are strictly necessary and don't require consent.
  • Local storage in your browser to remember your theme choice (opscom-theme) and whether you've collapsed the sidebar (sidebar-…). This never leaves your device.

We don't use tracking, analytics or advertising cookies.

9. Your rights

Under the GDPR you have the right to:

  • access the personal data we hold about you
  • correct inaccurate data
  • delete your data ("right to be forgotten")
  • restrict how we process your data
  • object to processing based on legitimate interest
  • data portability: receive your data in a common, machine-readable format
  • withdraw consent, where processing is based on consent

To use any of these rights, email opscom.contact@gmail.com from the address linked to your account, or contact us on our Discord. We will respond within one month.

Deleting your account: there is currently no self-service delete option. Email us and we will delete your account and the personal data linked to it. Records that a community keeps about you are that community's records (see section 2). We will forward your request to the community, or delete those records ourselves where the law requires it.

You can also stop Discord sharing data with OPSCOM at any time: in Discord, go to User Settings → Authorized Apps and remove OPSCOM.

Complaints: you have the right to complain to a data protection authority. In the Netherlands that is the Autoriteit Persoonsgegevens. You can also complain in the EU country where you live.

10. Children

You must be at least 13 to use OPSCOM, as set out in our Terms. Community owners must be old enough to enter into a binding contract. If you believe a child under 13 has given us personal data, contact us and we will delete it.

11. Security

  • Data is encrypted in transit (HTTPS).
  • Database access is restricted by row-level security, so users can only reach data they are allowed to see.
  • Sensitive tables, such as bans and community secrets, can only be accessed from our servers.
  • Payment details are handled entirely by Stripe.

No system is perfectly secure. If a data breach is likely to put your rights at risk, we will notify the Autoriteit Persoonsgegevens and you as the GDPR requires.

12. Changes to this policy

We may update this policy. When we make a material change, we will tell you on the platform or by email, and we will update the date at the top.

13. Contact

OPSCOM · KvK 42049425 · Email: opscom.contact@gmail.com · Discord: https://discord.gg/dXKDeEcBxS