🐺 Wolf Pack — Privacy, in plain words

The spirit

This stuff exists to make raids easier to run when things get hectic — and to carry some of the load for the officers who prep at all hours. It is not here to grade anyone. We don't track who caused a wipe, and we never will. Parses are for coordination and a little friendly fun. Healers, tanks, DPS: a rough night is just a rough night. It's a game. Nobody here is “not doing enough.”

What we can't promise yet

We would rather tell you than have you find out.

• Most data has no deletion date. A few things expire (see How long we keep it); everything else is kept until someone asks us to remove it.
• There is no self-serve download or delete. You ask an officer, and it is done by hand.
• Opt-outs stop future uploads, not past ones. Switching something off does not delete what was already collected.
• Other raiders' Mimic records you too. Your own settings control your own Mimic, not theirs (see What other raiders' Mimic records about you).

Is it a keylogger? Is it a virus?

No — and you don't have to take our word for it.

What Mimic reads. EverQuest's files, and only for EverQuest:

• your EQ log files (and any old-log folders you point it at);
• Zeal's live data feed — your HP, mana, buffs, target, pet, zone and position, plus your group and raid;
• your EQ and Zeal settings and UI files, and the inventory, spellbook and Quarmy export files you create;
• Zeal's crash files, which it summarises on your own PC;
• the folders of GINA and EQLogParser, if you have them, so it can offer to import your triggers;
• the list of running programs, to see whether EverQuest is running.

It never records keystrokes, captures your screen, or reads your browser, passwords or clipboard. It uses a few global hotkeys you set; that is not a keyboard hook.

What Mimic changes on your PC.

• Installs for your Windows user only. No admin rights, no drivers, no services.
• Starts with Windows by default. Turn it off: tray menu → Start with Windows.
• In your EQ folder, only when you click the button for it: installs or updates Zeal and UI packs, and adjusts eqclient.ini / zeal.ini (Set up for me).
• On by default: moves a large EQ log that has gone quiet into a LogArchive folder, so EQ starts a fresh one. Nothing is deleted. It also keeps a few local backups of eqclient.ini.
• Two optional buttons ask for admin through the normal Windows prompt: adding a Defender exclusion, and fixing the Windows clock.
• It stops another program only when you click retire the old Parser.
• Uninstalling removes Mimic, not the changes above that you made in your EQ folder.

Who Mimic talks to: our guild's server; GitHub (updates for Mimic, and for Zeal and UI packs); public internet time servers (Microsoft, the NTP Pool and Cloudflare), so raid timers line up; and, only if you sign in to OpenDKP through it, Amazon's sign-in service, which OpenDKP uses.

Verify it yourself: scan the installer on VirusTotal (an unsigned installer can trip one or two over-cautious scanners); read the code; open the local dashboard, which shows how many items each stream is waiting to send. The pending-upload file is plain text you can open. Your live status goes out directly, so it never sits in that file.

The “unknown publisher” warning means the installer isn't code-signed. That costs money we haven't spent; it says nothing about safety.

The older standalone Parser (Parser.bat) works like Mimic, but keeps its token in a plain-text file in your EQ folder and sets itself up to start when you log in to Windows.

What leaves your PC

Nothing goes to our server until you sign Mimic in with Discord. Every upload then carries a personal token tied to your Discord account. Signing Mimic out (Disconnect) stops every upload to our server.

Sent by default once you are signed in:

• Fights: damage, heals and deaths for everyone in the fight, pets included.
• Guild and raid chat (/gu, /rs), with each speaker's class, level and race.
• /who results: every player shown who is level 50+ or anonymous, from any guild — name, level, class, race, guild and zone.
• Your live status, every few seconds while Zeal is connected: zone, position (x/y/z), HP, mana, buffs, target, pet and what is hitting you. This goes out in or out of a raid, and even with EQ logging off.
• The raid roster while you are in a raid: every raid member — including people from other guilds — with class, level, group, HP and position.
• Buffs and debuffs you see land; your casts; threat; guild trigger callouts; /sll lockouts; boss kills; PvP kills; faction; your PoP flags; /random rolls; what you loot.
• Your inventory, spellbook and Quarmy exports, if the files exist.
• Housekeeping: app versions, your main character, zone and a clock check.

Only if you turn them on: tell relay, crash reports, uploading old logs, UI backups, and attaching your log to feedback.

Never sent as chat: officer chat, group chat, custom channels (including the guild's tag channel), /say, OOC, shouts, auctions, and tells unless you turn tell relay on. The one exception is a hail — see below.

Tells

• Off by default. The switch is tell relay on /me, per character.
• When it is on, your tells in both directions — including the other person's words — are uploaded, stored, and sent to you as a Discord DM. They are never posted to a channel, and on the website only you can see them.
• The person on the other side of the tell has not agreed to this. Please keep that in mind before you turn it on.
• Turning relay off stops new uploads; it does not delete tells already stored.
• Mimic also has a Tells setting (Off / Local / Synced), which isn't wired up yet. It doesn't affect uploads — tell relay on /me is the switch that decides. Its description in Mimic still describes how it was planned to work, and we're updating it.

Hails (the one /say exception)

A /say line starting with Hail (Brackwyn says, ‘Hail, Seer Mal Nae’) gets past the filter, because hailing an NPC is how Planes of Power flags are granted, and the game shows the confirmation only to the person who got it. When someone uploads old logs, we store who hailed, up to 48 characters of what followed “Hail”, the zone, the time, and whose log saw it. Nothing else that was said. This is evidence of a possible flag, never proof, and is shown that way. A player greeting another player the same way (“Hail, friend”) is stored too — we can't tell them apart.

What other raiders' Mimic records about you

Even if you never install Mimic, raiders who run it record what their game shows them:

• your damage, heals and deaths in fights they're in;
• your guild and raid chat;
• your /who presence — from any guild, at level 50+ or anonymous;
• your HP and position while you're in a raid with them;
• buffs landing on you, your /random rolls, PvP kills, and hails.

Your own opt-outs don't stop this — that was a deliberate choice, because the fight happened to everyone in it. If you want something removed, ask.

Crash reports (off by default)

Turn on Share crash reports in the tray menu. Mimic then sends, for each Zeal crash: the crash details Zeal writes (including your character and zone), your Windows version, memory and graphics card and driver, fingerprints of nine game files, and a summary Mimic works out from the memory dump. The memory dump itself never leaves your PC. Crashes older than 30 days are skipped the first time you turn it on, but older ones can still be sent later.

Feedback

The feedback form stores your message and, if you're signed in, your Discord id and nickname, and reposts it to our Discord #feedback thread. From Mimic you can tick attach log: up to 6,000 recent lines go with it, after Mimic removes tells, group chat, officer chat and custom channels. The filter isn't perfect — guild and raid chat stay in, and some chat can slip through when Zeal's short-chat format is on — so read the preview before you send.

Screenshots (up to three) are stored in a private folder that only the officers' inbox can open, and posted to the same Discord thread. Mimic's 📸 photographs your whole screen, which can include chat windows or anything else open, so you see each one first and choose which to send. On the website, screenshots need you signed in as a pack member.

The website (wolfpack.quest)

• Signing in uses Discord. We ask Discord who you are and which roles you have in our server, to check you're a member. Our sign-in provider also receives your email from Discord and stores it; we don't use it and never email you.
• Sign-in records: each signed-in session keeps your IP address and browser type.
• Page views: while signed in, each page you open is logged (the page, the page you came from, your browser). Officers can see how often each member visits and when they were last on. Signed-out visits are not logged.
• Cookies: the sign-in cookie (lasts up to 400 days), and two preference cookies for your time zone and raid layout (1 year). Other preferences stay in your browser. No advertising or analytics cookies.
• Third-party requests: none on member pages except your Discord avatar, which loads from Discord. The diagrams on /platform/architecture load fonts from Google. The beta mirror (b.wolfpack.quest) loads a Vercel preview script.

Who sees what

• ONLY YOUYour relayed tells; your /me page.
• YOU + OFFICERSYour inventory, spellbook and quest pages. Officers can also upload inventory for any character. Two switches on /me share them with members, separately: Quest page and Inventory page.
• GUILDSigned-in members: parses, DKP and bids, attendance, loot, kill timers, /who sightings, and each character's equipped gear and AAs. Members' Mimic can look up your current zone, HP and buffs — that's how the buff queue and Target Info work.
• OFFICERSThe admin pages cover all of it, including chat history, member page views and feedback.
• DISCORDWhoever can read the channel: relayed guild and raid chat, parse cards (which name deaths), the night's damage leaderboard, deathrolls, PvP kills and feedback.
• ANONGuild-wide totals with no names (“the Pack summoned 4,000 stacks of food”).

Your stats on /me only count from when you joined us (PvP kills are public server events, counted from the start).

What your switches actually do

How long we keep it

Two copies live outside the hosted database, both on a server the guild lead runs (not a cloud provider):

• Backups: a full copy of the database every night, including sign-in records and emails, kept for 30 days.
• Archive: a permanent copy of what the hosted database deletes on the schedule above — positions, /who sightings, buffs and threat — plus chat, tells and page views.

Anything posted to Discord stays there until someone deletes it in Discord.

Who else handles it

See it, fix it, remove it

• See: /me shows your characters, stats, tells and inventory. It doesn't yet show your email, page views, sign-in records, chat history, /who sightings, positions, hails, crash reports or feedback — ask and we'll pull them.
• Download: no export yet. Ask.
• Remove: ask an officer (or #feedback). We remove it from the live database; the nightly backups age out within 30 days; the archive copy and anything already posted in Discord have to be cleaned up by hand, so say if you want those gone too.

If your guild runs this

Everything above applies to a deployment run for or by another guild exactly as it applies to ours. Five rules on top, written into the hosted terms:

• Observations made under your deployment belong to your guild — parses, timers, rosters, chat relays, everything your members' clients upload.
• Nobody operating the platform reads your guild's data without your express consent for a specific troubleshooting request. Access is per incident, never standing; the support tooling is built so its output cannot carry your secrets or your members' data.
• Anonymised aggregates only, computed inside your deployment before anything leaves it — counts and totals, never names or characters.
• Your /who observations are never ingested into anyone else's dataset. A future per-person “be known” opt-in may let an individual publish their own presence; it will be that person's choice, never the guild's, and it does not exist today.
• No tenant's observations are merged into another's as fact. Observations can be fabricated; separation is the protection.

If you self-host under the free license, these are yours to keep for your own members; the software is built to make them the default.