The fine print, kept short

Privacy

Dad Ops is a hobby gaming community run by volunteers. We collect as little as we can.

When you sign in with Discord

Discord shares your username, profile picture and email address with us. Your email is used only for signing in. We never show it on the site, sell it or send you marketing.
We store the callsign you choose, your Dad Ops rank, the date you joined, and that you confirmed you're 21 or older.
Your callsign also makes your page's address and recruiting link (dadops.gg/member/YourCallsign and dadops.gg/r/YourCallsign). Callsigns are one per member. When you change yours, the old one is kept so old links still find you, and nobody else can use it until you delete your account. These names are public, like your service record.
Things you do here are stored so the site works: seats you save for ops and ops you're on the bench for (on the site or with the Discord buttons), the nights you attended, your rank and any awards or pins.
When you finish joining you get a service number (DAD-0001, DAD-0002 and so on, in the order people joined). It's printed on your dog tags.
The bot hands out some ribbons by itself, like First Round and Hat Trick. It works them out from the nights you attended and your time in voice, so no extra information is collected for them.
A few classified ribbons aren't listed anywhere until someone earns one. For those, the same 5-minute voice check notes a little more: how many checks you were in voice in the morning, at lunch on weekdays and on weekend afternoons (one count per day, deleted after 3 days), whether you were in voice after 1 AM, and, during an op, whether you were in the muster channel before muster, whether you stepped into Kids Woke Up and came back, and which members shared a fireteam channel with you and for how many checks. It never hears what was said. These notes aren't shown anywhere (only the ribbons are), and they're deleted with your account.
If you volunteer as a battle buddy (Corporal and up) or to lead a fireteam (Sergeant and up) or lead ops (Sergeant First Class and up), we store that you volunteered. When a new recruit joins, we store who they were paired with and when they made Private. A new recruit's callsign, time zone, usual drink, short bio and who brought them go up on a card in #buddy-board, which only battle buddies, the S3 and the Owner can see. Each pair gets a private Discord thread that only the two of them and the S3 can see. We store the thread's ID, never what's said in it. The bot looks at who has posted there, only to check whether the battle buddy has said hello yet, and the thread is locked (not deleted) once the recruit makes Private. Your list of recruits on your service record is shown only to you.
After a recruit's second op night and first week, their card goes up on #buddy-board again so battle buddies can vouch for them; three vouches makes Private. The card shows their op nights, time in voice, battle buddy, who brought them and who has vouched. We store each vouch (who, for whom, when) and keep it once they're in. A battle buddy can tap I've got a concern: we store who raised it, when, and what they wrote, which only the S3 see. The recruit is never told who vouched or that a concern was raised; their service record shows only how many vouches they have. Every vouch, take-back, concern and promotion is noted in the S3 log. Deleting your account removes your vouches and any card about you.
If you pick who brought you to Dad Ops, we store that, and it shows on both of your service records.
Your profile can also hold a usual drink, favorite loadout, one-line bio and time zone. They're all optional and show on your service record.
You can also add linked accounts on dadops.gg/links: your wardogs.tools player page, your Twitch username and your YouTube channel. We store only the player id, username, or @handle or channel id, never a password. We don't pull anything from Twitch or YouTube. (wardogs.tools: see WARDOGS stats below.) They show on your service record, the Members page and /record, and the links only ever lead to wardogs.tools, twitch.tv or youtube.com. What those sites collect when someone opens a link is up to them. Each one has a Show switch there; a link you hide is kept privately (so switching it back on brings it back) and is off your record, the Members page and /record. The S3 can take links down if one breaks the house rules, and that goes in the S3 log.
My Limited Availability on your profile holds the days and rough times you say you're usually around (daytime, early evening, after bedtime, late night) and when you last updated them. It's what you tell us, not anything the bot measured, and nothing judges you by it: not ranks, ribbons, the MIA list or Squad Leaders. Only signed-in members see it, on your service record, in "Usually on tonight" on the Members page and in /whosup in the Discord (a reply only the person asking can see). Tick Count me, but keep my name off it and you're only a number there: nobody sees your name or your hours, the S3 and the Owner included. Untick every box and it's deleted. If your hours haven't changed in four months, the bot sends you one direct message asking if they're still right (at most once every four months, never while you're on leave), and we store when it was sent and whether it got through.
If you go on leave (you can set it on your profile, or the S3 can), we store when it started, the "back around" date if you gave one, and when it ended. Past leaves are kept so your streak stays paused for those weeks (one you switch off within an hour is simply deleted). While you're away you're taken off as Squad Leader for those nights. Coming back after 3 days or more gets a welcome-back shout-out in the Discord.
If you lead op nights, we store which ops you led. It shows on the op posts, in the muster call, on your service record and in the Hall of Fame.
If you're a Squad Leader and a Hot Zone Friday or Long Push still has no lead the day before, the bot may send you a direct message asking if you'll lead it. We store who was asked for which night, when, and whether they said yes, passed or didn't answer (or couldn't be messaged). Only the S3 and the Owner see that, on the S3 page.
When a Squad Leader sets the night's server with /server, we store the server ID, faction and who set it. It's deleted along with the op.
When a Squad Leader runs /fireteams, the job you pick on the card in #briefing-room (your main job and backup) is stored with your Discord ID for that night, so Horton can put you on a team. The bot makes a voice channel for each team and deletes it at /rally or 6 AM Eastern. Picks are deleted after 30 days and aren't in the backups.
Your fireteam comms style (🎯 Tactical, 🍺 Cold Ones or Either) is saved on your profile if you set one, and anyone can see it, like your usual drink. One you pick on the card is kept with that night's job picks and deleted with them.
Every Monday the bot posts the Bar tab in the Discord: last week's crew totals (op nights in each game, hours in voice and in WARDOGS, XP and levels gained, Gray Zone first-timers and tasks ticked off, the gold price). It's crew totals only: nobody is named.
Each Monday the bot picks a Regular of the Week from members who've made an op night or been in Dad Ops voice in the last 30 days (not anyone on leave). We store who was picked each week, and the bot posts it in the Discord.
On op nights the bot checks which members are in Dad Ops voice channels, to record attendance. From 2 hours before go time to 4 hours after, it adds up how many minutes you spend in voice (every channel except The Back Booth and Kids Woke Up), and 30 minutes gets you the night. We keep one total per op, not when you joined or left, and never anything that was said.
The bot also adds up your time in voice. Every 5 minutes, around the clock, it checks whether you're in any Dad Ops voice channel except Kids Woke Up (the AFK channel) and adds 5 minutes to that day's total. The same check also keeps a voice log: which Dad Ops voice channel you were in (Kids Woke Up included) and when you were first and last seen there, to the 5-minute check. Only the S3 can see the log, in case staff ever need to look something up. It's deleted after 90 days, and with your account. It never hears or keeps anything that was said.
Time in WARDOGS (Field stats): every 10 minutes the bot looks at who in the Dad Ops Discord is showing Playing WARDOGS and adds 10 minutes to that day's total. We keep one total per day and when you were last seen playing (for "Playing now"), nothing else about what you do. To stop it, turn off Discord → User Settings → Activity Privacy → Share your detected activities for this server.
Steam (dadops.gg/links, only if you choose Link with Steam): you sign in on Steam's own page and Steam tells us your public Steam ID. We never see your Steam password. Every hour the bot reads your WARDOGS hours and achievements from Steam's official Web API, and posts a shout-out in the Discord when you unlock a new one. Linking Steam also switches on your server stats, the DAD tag next to your in-game name on the server pages, and your Steam hours and achievements for other members; each has a Show switch on dadops.gg/links, all on to start. Your Steam ID is never shown on the site unless you turn on Let members add me on Steam (off to start): then signed-in members get a button that opens your Steam profile and shows your Steam friend code, which is worked out from your Steam ID. With Steam linked, the bot also reads your Steam friends list each hour if it's public, and keeps only which other members you're already Steam friends with (for the Already friends ticks on Members → Crew on Steam); nothing else from your list is kept, and it goes when you unlink. The switches never hide anything from the S3: once you link Steam, Range Control always shows that player is you. Unlink Steam on dadops.gg/links removes it and your achievements.
WARDOGS stats (Field stats, from wardogs.tools, with its owner's permission): about once a day, or once an hour on days you play, the bot asks wardogs.tools for your in-game stats (season rank, Wardog level, cash, gold, worth and role levels). It asks using the wardogs.tools player on your profile, or if you haven't added one, your Discord account ID. That's the only thing we send them. If wardogs.tools doesn't know you, nothing is stored except that it didn't. We keep one snapshot of those stats per day so Field stats can chart them over time. wardogs.tools is a separate site run by a WARDOGS player, not by Dad Ops or the game's makers.
Server list (#server-list): every few minutes the bot asks Wardog Servers (wardogservers.com) how the public WARDOGS servers the Owner picked are doing: online or not, player count, map and mode. Nothing about you or any member is sent to them or kept. Wardog Servers is a separate community site, not run by Dad Ops or the game's makers.
Callout maps: when you suggest a callout, we keep its name, note, outline and that you drew it. Once an S3 approves it, anyone can see it with your callsign. While it waits, only you and the S3s can. While it waits, the bot also posts it (name, note, map square and your callsign) in the S3s' private channel in the Discord so they can decide, and sends you a direct message once they have. If you delete your account, approved callouts stay on the map without your name.

The war room

The war room (dadops.gg/warroom, or the DAD Ops Activity in a Discord voice call) is a map the squad draws on together. Each drawing, marker and request is saved with the name of whoever made it (your callsign, or your Discord server name if you haven't joined on the site) and when, so everyone in the room can see who put it there. Rooms are seen only by people who have the room's link or code, or open it from the lobby, and you have to be signed in as a member or be in the Dad Ops Discord to open one. Quick rooms are deleted after 30 days nobody uses them; op plans stay for looking back on. Pings, "bring everyone here" and who's in the room right now go straight between screens and are never saved.

To know who you are, the site keeps a war room key for 12 hours (only a fingerprint of it, never the key) with your name, your Discord picture and your Discord account ID. In the Discord Activity, Discord tells us your account ID, name and picture when you tap Authorize the first time, and the bot checks that you're in the Dad Ops server. Nothing else from your Discord account is read or kept, and the Activity can't see your voice or messages. If you delete your account, your drawings stay on the map as "Former member".

Reminders in Discord

Anyone in the Dad Ops Discord can tap 🔔 Remind me on an op post, with or without a site account. We store your Discord account ID and which op, and the bot sends you one direct message an hour before go time (or a heads-up if the op is called off). Reminders are deleted two days after the op. Tap the bell again any time to cancel.

If you set standing orders on your profile, we store which nights you picked and the bot DMs you before each of them. The site doesn't show them, but they're kept with the rest of your profile, which isn't private. Skipping one night with the bell is stored until two days after that op.

Horton's DMs and quiet hours

Under Horton's DMs on your profile you pick which kinds of direct message the bot sends you, and your quiet hours. We store which kinds you switched off, your quiet hours (on from 11 PM to 7 AM in your time zone until you change them) and when you last changed them. Nobody else sees them. (If an S3 note or a Squad Leader ask doesn't reach you, the S3 Desk only says it didn't go through, not why.) A DM that lands in your quiet hours is kept until they end and then sent (or dropped if you switch that kind off first, or after a day and a half). It's deleted two weeks after. An op reminder in your quiet hours is skipped instead. For the line on the S3's Health check, we count how many DMs each day were switched off, held or skipped, with no names. Tickets, appeals and the welcome DM always go out.

Service milestones

At 1 month and 6 months after the day you joined the website, the bot raises a glass for you in #the-bar (and at 6 months sends you a DM, if you keep News for you on). A year and up is the Service Ribbon, as before. We note which milestones were posted, and when. Your service log shows them too, worked out from your join date, which is already public.

The heat map and the recruit pipeline

When's the crew around? on the Members page shows who's usually on tonight (from My Limited Availability, as before) and, for the whole week, the average number of members in Dad Ops voice each hour over the last 8 weeks. That comes from the 5-minute voice checks that already count voice time, which only ever stored how many members were in voice, not who. It shows numbers only, never names, and only to signed-in members.

The S3's Pipeline tab (only S3 – Personnel, Core and the Owner see it) lists newcomers and the joining step each one is on: in the Discord but not on the site, signed in but not joined, games and pings picked, battle buddy, first saved seat, first op night and Private. It's worked out from records the site already keeps (and, for people who haven't signed in, the Discord member list the welcome DM already uses). When an S3 taps Nudge, we store who nudged whom, for which step, when, and whether the DM went through. Not interested stores who marked it and when. The nudge DM counts as a note From the S3, so you can switch it off.

The Morale desk

When the S3's Morale desk opens a pick-a-date poll, we store which nights you tapped and when. Your callsign shows under the nights you picked, on the poll post and to the Morale desk. When the poll closes, members who picked the winning night get a DM (if they keep Morale events on under Horton's DMs). For a pop-up night, the bot works out whose usual hours (My Limited Availability) cover go time and DMs them; the Morale desk only sees how many. An idea you drop in with /event-idea is stored with your name for the Morale desk, and a line with it goes in the staff channel. Some special nights have a seat cap: once one's full, a new seat goes on the bench as a waitlist, and we note that you're waiting so the first one in line gets the next open seat (with a DM). A ribbon picked for a night goes to everyone on that night's roll call, like any ribbon.

Wrapped cards

On the 1st of each month, if you made an op night or spent an hour in Dad Ops voice the month before, we save a Wrapped card for you: your op nights (and for which games), time in voice, where that puts you among the crew, your favorite night, nights you led, your top squadmates and the ribbons, pins and promotions you earned that month. It's made from records the site already keeps, and saved so it doesn't change later (except that squadmates who delete their account are left off). Signed-in members can see it on your service record (it includes your time in voice, which is members only). The bot DMs you a link if you keep News for you on, and posts the crew's month in #the-bar with totals only, no names.

On December 15, if you made an op night that year, we save a yearly card the same way, with a few more numbers from records the site already keeps: op nights by month, your best streak, ranks climbed, recruits you were battle buddy to, your first op night, and Gray Zone tasks done and builds posted that year. Before then, the Owner can preview anyone's year on their service record. That preview is worked out on the spot and isn't saved or sent.

Discord roles from your profile

The pings you pick on your profile (each game's main nights, and its special ops) are stored with it, and the bot gives you the matching roles in the Discord, so you're pinged when one of those ops goes up. The bot also notes which of these roles it last set for you. Like standing orders, the site doesn't show your pings, but they aren't private.

The first time the bot sets your roles, it copies the ping roles you already had in the Discord into your profile, so you don't lose any. If Dad Ops later moves a night to a Discord role you already have, that night is checked on your profile the same way. Every morning it checks that your roles in the Discord still match your profile and fixes any that don't. The bot only does this for members who have joined on the site.

Games I play

The games you tick under Games I play on your profile are stored with it, and the bot gives you each game's role in the Discord. Your games show on your member card and service record, and anyone can filter the Members page by game. The first time the bot sets your game roles, it ticks any // roles you already had in the Discord, so you don't lose one; the same goes for a new game role you already had when it first shows up. Every morning it checks that your game roles in the Discord still match your profile and fixes any that don't. The bot's notes on which game roles it last set for you aren't shown to anyone. It only does this for members who have joined on the site.

Gray Zone tasks and keys

On My tasks you can tick off the Gray Zone Warfare tasks you've done, and on the Key finder you can mark the keys you carry. Each tick is stored with your profile and the time you made it. Other signed-in members can see them (which tasks you've done, which keys you carry, and the totals on your service record), so the crew knows who can help. Visitors who aren't signed in can't. The Bar tab only counts how many tasks the crew ticked off that week, without names. "Start over" and "Clear my key ring" delete your ticks. The task and key lists themselves come from the Gray Zone Warfare wiki; nothing about you is sent there.

Gray Zone blueprints

On Blueprints you can tick off the Gray Zone Warfare gun magazines you've found and whether you've done their task. Each tick is stored with your profile and the time you made it. Other signed-in members can see who has found which magazine, whether they've done its task, and when; visitors who aren't signed in can't. "Start over" deletes your ticks. The magazine list itself is kept on the site by the crew's Scouts.

Gray Zone hideout

On Hideout you can mark the hideout modules you've built, tick off the materials you have, and list spares you'd hand to the crew. Each one is stored with your profile and the time. Other signed-in members can see them on the crew board (what you've built, your power and your spares); visitors who aren't signed in can't. "Start over" deletes them. Any member can Report intel: what you send (the room, the module, what you saw), your callsign, the time and an optional screenshot are stored, and only you, the Scouts and the S3s can see them. If a Scout or an S3 approves it, the room, module and what you saw show on the Hideout page for everyone, with your callsign shown only to signed-in members. Screenshots are kept in a private store, never shown on the page, and deleted when the report is rejected or added to the hideout list. If your account is deleted, your builds, materials and reports go with it; a screenshot still waiting on a Scout stays in the private store until an S3 removes it, so ask one if you want it gone sooner.

The Field PDA

The Field PDA (dadops.gg/pda) has a notepad and a few settings: the frame finish, the accent light and which game it opens on. If you've joined Dad Ops and are signed in, they're stored with your profile and the time so they follow you to any computer or phone; nobody else can see your notes, not even the S3. Otherwise they stay in your own browser's local storage and never reach us. The PDA doesn't connect to the games and reads nothing from your computer. Deleting your account deletes your notes and settings.

The Gray Zone Scouts

The Scout desk is where S3s and members with the Scout badge keep two Gray Zone lists: who to sell loot to, and where the blueprint magazines are. Each change is stored with their callsign and the time, and kept in a change log that Scouts and S3s can read (so an S3 can undo a mistake). If a Scout's account is deleted, their changes stay, under the callsign they had. Any member can send a Seen it somewhere else? note from the Blueprints page or the Item lookup; it's stored with your callsign and the time, and only you, the Scouts and the S3s can read it. If your account is deleted, your notes go with it. Scouts and S3s can also correct an item on the Item lookup (its price, size, weight, category or a note); the item then shows the date, whether a Scout or an S3 changed it, and, to signed-in members only, their callsign. If your account is deleted, your corrections stay, under the callsign you had. The same goes for tasks on My tasks: Scouts and S3s can add tips, correct a task, add a task the wiki doesn't have or hide one, and the task shows the date, whether a Scout or an S3 changed it, and, to signed-in members only, their callsign. Any member can send a Tell the Scouts note about a task, stored and shown the same way as the other notes. If you're a Scout, Horton also gives you a Scout role in our Discord, and takes it off if the badge is taken away.

The Gray Zone Armory

The Armory is the parts list behind the Gray Zone weapon builder. S3s and members with the Armorer badge can fix it. Each fix is stored with their callsign and the time, and kept in a change log that Armorers and S3s can read (so an S3 can undo a mistake). If an Armorer's account is deleted, their fixes stay, under the callsign they had. Any member can send a Wrong number? note; it's stored with your callsign and only you, the Armorers and the S3s can read it. The guns and parts themselves come from the Gray Zone Warfare wiki; nothing about you is sent there.

The weapon builder

Anyone can use the weapon builder without signing in. Builds you save are stored with your profile and the time, and anyone with the link can see them along with your callsign, so you can share them with the crew. When you save a new build, Maj. Horton posts it in the #gzw-weapons channel on our Discord with its name, your notes and a mention of your Discord account; deleting the build takes that post down. Upvotes are stored with your profile so nobody votes twice; the page only shows how many votes a build has. Your vendor ranks (Gunny 3, Banshee 2...) are kept on this device, and on your profile if you're a member so they follow you to another device; only you can see them. Deleting a build deletes it and its votes. Deleting your account deletes your builds, votes and ranks.

If you're an Armorer, Horton also gives you an Armorer role in our Discord, and takes it off if the badge is taken away.

If you're on the S3, the Owner can give you a staff seat (Core, Operations, Personnel, Trust, Safety & Standards, or Morale). Who holds each seat is public: it's on the About page and your service record, with your callsign and Discord picture. Horton gives you that seat's role in our Discord, @mentions it in the S3's own channel when there's something for that seat, and takes the role off when the seat or your staff badge is taken away. When you hold a seat, the database also keeps who gave it to you and when, which only the S3 can see.

Founder, Squad Leader and Battle Buddy

The bot also gives out three Dad Ops roles in the Discord. Founder is handed out by the Owner and shows as a badge next to your name on the site. Squad Leader and Battle Buddy come from the "I'll lead ops" and "I'll be a battle buddy" boxes on your profile once you have the rank, and every S3 and the Owner has them. Whether you checked those boxes isn't shown on the site, but it isn't private. The S3 can switch Squad Leader or Battle Buddy on or off for a member. We store that switch, who set it and when. The switch itself is private: only you (on your profile), the S3 and the Owner can see it, and it's noted in the S3 log. The bot's notes on which of these roles it last set for you aren't shown to anyone. The roles themselves show in the Discord like any other role. Unchecking a box steps you down from a role the S3 switched on. If you already had one of these roles in the Discord when the site took them over, the bot keeps it for you (checking the box on your profile if it needs to) and notes that in the S3 log.

Running late and Can't make it after all on the muster call post a note in that Discord channel for the squad. We store how late you said you'd be until two days after the op. Can't make it also gives up your saved seat.

Staff applications. When applications are open, members can apply for staff from the About page. We store what you send (the seats you'd like, why, your experience, when you're around and anything else you add), your callsign and when you sent it. Only you and the S3 can read it, and Horton posts it in the S3's own Discord channel for them to review. You can send one every 30 days. If your account is deleted, your applications go with it.

Award recommendations. When you put a member in for a pin or ribbon with /recommend (or right-click → Apps → Recommend for an award), we store who you recommended, for what, your reason, when, and what the S3 decided (and who decided). Only the S3 and the Owner can see recommendations, on the S3 page and in the staff-only #s3-notifications channel. The member you recommended isn't told unless it's approved. Then the award's citation ends with “(Recommended by” and your callsign, like any other public award. If the S3 passes on it, the bot sends you one DM to say so. Recommendations stay on file after they're decided, and anything the S3 doesn't answer within 30 days is marked expired. An award that was approved keeps its citation, so it still names who recommended it, even if that member later deletes their account.

🪑 On the bench means you might make an op. It's shown with the op (under the seats) on the site, the #ops-board post and the muster call, which names you without pinging you. If you went to the bench more than an hour before go time and you're still there an hour out, the bot sends you one DM with the seat buttons. We note when that DM went out so it's only sent once.

The muster call also carries a muster board: who's saved a seat and whether they're in a Dad Ops voice channel (which one), in Kids Woke Up, somewhere else in voice, running late or not in voice yet, plus members in voice without a seat and members on the bench who aren't in voice yet. The bot redraws it from the same 5-minute voice check until 15 minutes after go time, then leaves the final count up. It only names voice channels everyone in the Discord can see: someone in a private channel just shows as being in a private channel. Who was in voice isn't stored: we only keep where the muster call is, so the bot can update it, and delete that after a month.

Tickets and appeals

Anyone in our Discord can open a ticket with the buttons in #open-a-ticket (or /ticket open), and the S3's Trust, Safety & Standards seat and Core can open one with a member. Each ticket gets its own private Discord channel that only the people on it, S3 – Trust, Safety & Standards and Core can see (plus anyone they add, and the server's admins, as with any Discord channel). We store what you send in the form, your Discord account ID and name, when it was opened, who took it on, who was added, and who closed it and their note. When it's closed, the bot saves the whole conversation (who said what and when, and the names of any files, not the files) and deletes the channel, and sends the member it was about one DM saying it's closed.

If you're banned from the Discord, you can appeal at dadops.gg/appeal. You sign in with Discord so we know which account it's for (that's all signing in does: it doesn't join you up). We store your appeal, your Discord account ID, whether you're banned in our Discord and the reason given (the bot looks that up), the S3's answer and who gave it, and whether the bot lifted the ban. You see your own appeals and the answers on that page.

Only S3 – Trust, Safety & Standards, Core and the Owner can read tickets and appeals, in S3 → Tickets. They're kept for a year after they close, then deleted. Because they're conduct records, they stay for that year even if an account they mention is deleted.

The DAD Ops game server

DAD Ops runs its own public WARDOGS server. Its page, dadops.gg/wardogs/server, shows the server's name, region, status and rules, and nothing about any player. The S3 change those on the S3 Desk, and each change goes in the S3 log with who made it.

What the website keeps about players on the server. Once a minute the website asks the server who's on. For everyone who plays there, member or not, it keeps: your Steam ID (the number Steam gives your account, which anyone can see on Steam), the in-game names you've used there, when you played (each time you joined and left), and what the server showed while you were on (faction, kills, deaths, ping). If you've linked Steam on dadops.gg, the S3 can see that the player is you. If you haven't, and your in-game name there is your callsign, Range Control shows the S3 a Probably guess that it's you; it's only a hint, nothing is linked or counted from it. If an admin acts on you, it keeps that too: warnings, kicks, bans (the rule, how long, who issued it) and any staff notes, plus a log of every admin action and what the server said back.

Seeding and reserved stools. While the server is nearly empty, the website also counts the minutes each player is on (seeding), per day, and the reserved-slot time that earns, so the server can give you a reserved slot. If you're given or buy a reserved slot, it keeps your Steam ID, the kind (paid, granted or earned), how long it lasts, a short staff note and who gave it. Your Steam ID goes on the server's own reserved list while your slot lasts. Members who've linked Steam and signed up for a WARDOGS op night also get a reserved slot around that night, if the S3 have op night seats switched on. If you've linked Steam, you can see your own seeding and slot on your Field stats.

Today's Specials. The website also works out from the same server data which daily and weekly challenges each player finished, the points and streaks that earns, and adds a day of reserved slot for clearing the week. dadops.gg/wardogs/specials shows how many finished each one, never who; the points show on the public leaderboards like the other boards.

Public leaderboards. dadops.gg/wardogs/leaderboards shows the top players on the DAD Ops server by seeding time, time played, days played, kills, K/D and longest shot, with their in-game name (and a link to the service record of DAD Ops members). Never a Steam ID, and nothing about bans or warnings. Members can hide themselves with Show my server stats on dadops.gg/links (or their Field stats), and take off the DAD tag with Show I'm DAD Ops on server pages; anyone else can sign in with Steam on dadops.gg/wardogs/server and hide themselves there, or ask an S3.

Server stats and the player lookup. dadops.gg/wardogs/server-stats shows weapon totals for the whole server, and the longest kills and top players by in-game name. dadops.gg/wardogs/server shows recent rounds and their standouts the same way. Signed-in DAD Ops members and players signed in with Steam can also look up one player on dadops.gg/wardogs/server-stats/player: their kills, deaths, headshots, longest shot, playtime, seeding, rounds won, recent rounds, favorite weapons and roughly what they've earned in game. Members see the same on each other's Field stats. Never a Steam ID, and nothing about bans, warnings or reports. Hiding yourself from the leaderboards (above) hides you from all of these too; you can still see your own.

Sign in with Steam (no Discord needed). On dadops.gg/report, dadops.gg/appeal, dadops.gg/wardogs/vote and dadops.gg/server, players who aren't in our Discord can sign in with Steam. You sign in on Steam's own page and Steam tells us your public Steam ID, nothing else; we never see your Steam password, and it doesn't create an account. The website keeps that Steam ID in a cookie (dadops_sid, signed so it can't be changed, sent only to the website's own sign-in code, for 30 days or until you choose Sign out). It shows you your own reserved slot, seeding, specials and leaderboard setting, and lets you report a player, appeal a server ban, or vote for the next map. A next-map vote keeps which map you picked, with your Steam ID, so each player votes once; it goes if your server data is removed.

Reports and server ban appeals from the website. A report keeps your Steam ID, the name you typed (and the player's Steam ID if it matched one), the rule, when, what you wrote and any clip link, plus how the S3 closed it. The player never sees who reported them, and you only see whether it's open or looked into. An appeal keeps your Steam ID, the ban, what you wrote, and the S3's answer and note (which you see on dadops.gg/appeal). Only S3 – Core, Core | WARDOGS and Trust, Safety & Standards can read them, on the S3 Desk. Nothing is posted to Discord.

Who can see it. Only the S3 seats that run the server: who's on right now for any S3; player records and bans for S3 – Core, Core | WARDOGS, Operations | WARDOGS and Trust, Safety & Standards; staff notes and the admin log only for Core and Trust, Safety & Standards; reserved slots for Core and Personnel. None of it is shown on the public site.

How long. We keep it to run and moderate the server, including spotting someone who comes back under a new name, so it's kept until you ask us to remove it. The one exception is each kill: after a year (S3 – Core can set it shorter) single kills are folded into a monthly total per player, so the leaderboards still add up. Ask an S3 in the Discord (or open a ticket) to have your server records removed; the Owner removes them, including your seeding, slots, specials, notes and website reports and appeals, and your name comes off kills and reports about you. A ban that's still in force stays on the ban list (with no name or note) until it runs out or is lifted.

Conduct records and the mod log

To keep the bar a good place, the S3 keep a conduct record for each Discord account in our server, whether or not it's on dadops.gg. Every 10 minutes the bot reads our Discord server's Audit Log (the list Discord itself keeps of what the staff and server tools did) and saves what matters for moderation: bans and unbans, kicks, timeouts, messages a staff member deleted (how many and where, never what they said), role and nickname changes, AutoMod hits, and changes to the server's security (bots, webhooks, invites and permissions). It saves who it was about, who did it, when, and the reason they gave. It also notes when an account joins or leaves the Discord.

Trust, Safety & Standards and Core can add a warning or a note to a record. A warning is sent to you by DM with its reason, and counts for 90 days. A note is only for the S3 and is never sent. If the same patterns keep showing up (3 active warnings, 2 timeouts in 30 days, 3 AutoMod hits in a day, or leaving and rejoining the Discord twice in 30 days), the bot points it out to Trust, Safety & Standards. That's a flag for a person to look at: nothing is ever decided or done automatically. We don't save anyone's chat messages.

Only S3 – Trust, Safety & Standards, Core and the Owner can read conduct records, on S3 → Conduct and in a staff-only Discord channel (#mod-log). Everything in them is deleted after a year, except a ban that's still in place, which stays on the record until it's lifted. Like tickets, conduct records aren't part of your dadops.gg account, so deleting your account doesn't remove them.

Joining needs our Discord. When you join on dadops.gg, the bot checks your Discord account is in our server, and notes the answer and when. If you leave the Discord, you're taken off the roster (the Roster, the Hall of Fame and the member count) and can't save seats until you're back. Your rank and record are kept, and rejoining puts you back. An account banned from our Discord is locked here too, and can still appeal.

The right Discord account. When you join, the site shows which Discord account you signed in with and asks you to confirm it's the one you use. To help catch anyone who signed up with an old or second account by mistake, the S3 see a short list of members whose account looks like it might not be the one they use: another account in our Discord with the same name and no site profile, or an account that joined our Discord when they signed up and has never been in voice. Horton posts new ones in a staff-only channel. For that, the 5-minute voice check also adds up time in voice for Discord accounts that aren't on dadops.gg (one total per day per account, deleted after 60 days). If you did sign up with the wrong account, the Owner can move your profile to the right one: you keep everything, the S3 log notes who moved it and when, Horton DMs the new account, and that account's voice time from the last 60 days can be added to your record.

Suggestions the S3 picks up

Members the Owner makes S6 can flag pages on dadops.gg that are out of date, wrong or missing something. A flag stores what they wrote, which page and part of the page it's about, their screen size and browser (so the fix lands in the right spot), who sent it and when, and any notes and status changes after that. Only the S6 and the Owner can see flags, on the S6 Desk and in a private #s6-desk channel in the Discord. Flags stay until the Owner deletes them in Supabase; deleting your account keeps the flag but takes your account off it (your name as it was stays on it). A flag sent from Discord (right-click a message → Flag for S6) also stores that message's text (up to 1,000 characters), who posted it (their Discord name), the channel and a link back to it. If the Owner moves a flag to the S3 Punch List, what the flag says is copied there, where every S3 can see it. When the S6 marks a page checked, we store which page, who and when. Ask the Owner if you'd like a flag removed.

The S3 keep a private to-do list, the Punch List. If an S3 copies one of your Discord messages onto it (a #suggestion-box post, say), we store the message's text, the names of any files in it (not the files), your Discord name and account ID, the channel it was in and a link back to it, plus who copied it and when. Only the S3 and the Owner can see the Punch List, along with their own notes on it and any screenshots they add to it (kept in private storage that only they can open). The bot replies in your post once to thank you, and once more if it gets built. If it's built and you're on dadops.gg, we also store that it counted toward your Field Improvement Ribbon, which goes on your service record like any other ribbon. An item stays until an S3 deletes it, and it isn't part of your dadops.gg account, so deleting your account doesn't remove it. Ask the S3 if you'd like your name taken off one.

Promotion certificates and recruiting links

Every promotion comes with a certificate: your callsign, service number, the rank you made and the date. The website draws it from your rank history whenever someone opens it, and the bot posts it with your promotion shout-out in the Discord. It shows nothing that isn't already on your service record.

Your own service record shows you your recruiting link (dadops.gg/r/ plus your callsign). When someone opens it, their browser remembers who sent them for 30 days, in its own local storage and not on our servers, so "Who brought you" is filled in when they join. It's only used when joining: they can change it before saving, it's forgotten once they've saved, and it's forgotten when someone who's already a member signs in.

The Discord member list

Every 10 minutes the bot reads the Dad Ops Discord's member list: Discord account ID, username, server nickname and when you joined the server. We keep it so the bot welcomes each new person once with a direct message, so a site member who joins (or comes back to) the Discord gets their rank, ping and game roles, and so the S3 can see who hasn't joined on the site yet. Only the S3 can see this list. Once you've been out of the Discord for 30 days, you're taken off it.

From that same look at the member list, the bot also keeps your Discord display name, your Discord roles, whether you're boosting the server (and since when), whether you're timed out (and until when), whether you've left and come back and whether you've finished the server's onboarding. When someone new joins, it also notes which invite link they most likely used and who made it (Discord doesn't say, so the bot works it out from how many times each invite has been used). Every 5 minutes it notes which Dad Ops voice channel you're in, if any, and every 10 minutes what you're playing or streaming (from your Discord activity), if anything. Only the latest is kept: when you leave voice or go offline, it's gone. To stop the "playing" part, turn off Discord → User Settings → Activity Privacy → Share your detected activities for this server.

The bot also counts messages: every 10 minutes it adds up how many messages each person sent in each channel it can see, per day, and when the last one was. It never reads, saves or shows what anyone wrote, only the numbers. Counts are deleted after 90 days.

All of this, with the rest of your record above, shows in your personnel file on the S3 Desk (S3 Desk → Members → your name). Only S3 who can open the Members tab see it. The part listing S3 log lines that mention you is only for S3 - Core, and the conduct part only for Trust, Safety & Standards and Core. None of it is shown to members or on your public record.

If you haven't been around for a while, the S3 can have the bot send you one friendly direct message (at most once every two weeks). We store when it was sent and whether it got through.

The bot keeps a log of what it did, like "posted the muster call", so problems are easy to spot. Only the S3 sees it, and it's deleted after two weeks.

When the S3 changes something on the website (roll call, awards, pins, recommendations, ops, Squad Leaders, news, staff badges and other roles, campaigns, nudges, someone's leave, taking down someone's linked accounts or removing someone from the site), the S3 log notes who did it, what and when. It names the members involved by callsign. Only the S3 and the Owner can see it. Entries are deleted after a year, and they stay for that year even if an account they mention is deleted.

What's public

Your callsign, Discord picture, rank, staff and Founder badges, service number, service record (nights attended), ribbons, pins (and which ones you picked to wear), streaks, campaign standings, battle buddy pairings, who brought you to Dad Ops, your profile extras (drink, loadout, bio, time zone), the games you play, your linked accounts (wardogs.tools, Twitch, YouTube), whether you're on leave (and your "back around" date), the op nights you led, your top squadmates (the members you've made the most op nights with, worked out from roll call), the weeks you were Regular of the Week, the last op night you made, your promotion certificates and the ops you've signed up for or are on the bench for can be seen by anyone who visits the site. The Hall of Fame and campaign pages rank members by these same numbers. Anyone in the Discord can bring up your service record with /record. The SITREP channels at the top of the Discord only show counts, never names. Dog tags and Tour of Duty cards are drawn by your own browser, so nothing is uploaded when you make them. Only you can make your Tour of Duty card, because it includes your time in voice. Your usual hours (My Limited Availability) are shown only to signed-in members, and only as a number if you keep your name off them. Your time in voice, and the last day you were in Dad Ops voice (the day, never the time), is shown only to signed-in members, and so are your Field stats (time in WARDOGS, whether you're playing now, your Steam hours and achievements, and your in-game WARDOGS stats from wardogs.tools) (including the voice records in the Hall of Fame and on campaign pages), and big milestones (like 100 hours) get a shout-out in the Discord. Your Discord account ID is used behind the scenes for the seat buttons, pings and roles, and is never shown.

Where it lives

The site is hosted on Vercel and the member data is stored with Supabase. Fonts load from Google Fonts (inside the Discord Activity, from this site). Your browser's local storage keeps you signed in (and, if you opened a recruiting link, who sent you). No ads, no analytics and no tracking cookies.

Every morning the bot makes a backup copy of the member data, so nobody's stripes get lost if something goes wrong, and posts it as a file in a private Discord channel that only the Owner can see. Each copy is deleted after 30 days. The Owner can also download a copy from the S3 page. Backups never include email addresses.

Deleting your stuff

Sign in, click your name, open Edit my profile and choose Delete my account. That removes your profile, service number, service record, ribbons, pins, voice time, classified-ribbon notes, time in WARDOGS, your Steam link and achievements, your WARDOGS stats from wardogs.tools (and their history), battle buddy pairings, profile extras, linked accounts, standing orders, pings, games, role switches, leave history, DM settings (and any DMs waiting for your quiet hours), service milestones, Wrapped cards, saved seats, bench spots, war room keys, Field PDA notes and settings, and award recommendations (ones you made and ones about you) for good, takes your name off any op you led, week you were Regular of the Week or war room drawing, and has the bot take your rank, ping, game, Founder, Squad Leader and Battle Buddy roles off you in the Discord (for that, your Discord account ID is kept until it's done, a week at most). Discord reminders clear themselves two days after each op. Promotion shout-outs the bot already posted in the Discord (with their certificate pictures) stay up; ask the S3 if you'd like them taken down. Tickets and appeals aren't part of your account: they stay for their year (see above). You can also ask the S3 in Discord to delete your account for you. The Owner can remove an account from the site too (for example, someone who has left Dad Ops). That deletes it exactly the same way, and the S3 log notes who removed it and when. Backup copies made before then still hold your records until they're deleted, 30 days at most.

Age

Dad Ops is for adults 21 and older only.

Last updated November 2026.