Privacy Policy

• Discord account data. When the bot is in your server or you sign in to the web app, Hootus reads your Discord user ID, username, avatar, and the server memberships and roles relevant to guilds using Hootus. This comes through Discord’s own OAuth. Hootus never sees your Discord password.
• WoW character data. Character name, realm, class, spec, level, item level, and guild rank, pulled from Blizzard’s public game API. Verifying a character by name needs no Battle.net sign-in. Connecting a Battle.net account is optional and covered in the next bullet.
• Battle.net connection (optional). An earlier version of this policy said “you verify a character; you do not link a Battle.net account”. That is no longer true and the claim is withdrawn. You may now choose to connect a Battle.net account. If you do, Hootus stores your Battle.net account ID and BattleTag, and imports the list of WoW characters on that account: name, realm, class, race, faction, and level. It is opt-in, it is read-only, and it never sees your Battle.net password, email, payment details, or subscription status. No access token is retained. The token is used once during the import and then thrown away, which is why re-importing sends you back through Battle.net. Your BattleTag is there so Hootus can tell that these characters are yours, and that is the whole of its job. It shows on your own profile and link page so you can see which account is connected. It is not passed to your officers and it is not on any public page. You can disconnect at any time: the account ID and BattleTag are deleted, your characters stay exactly as they are, and they drop from verified to previously verified.
• Raid and guild activity. Signups, attendance, bench history, soft reserves, loot records, and the settings your officers configure.
• Voice timestamps for attendance. When you join or leave a raid’s voice channel during the raid window, Hootus records the time to mark attendance. It does not record, store, or listen to any audio.
• Sign-in cookies. A signed cookie keeps you logged in to the web app, and the recruitment application flow sets one of its own. That is the whole list. They exist for sign-in, not tracking, and Hootus sets no advertising or analytics cookies.

To run the things you came for: posting raids, checking signups against class and spec, syncing your roster, handling recruitment and PUGs, and the web planner. Nothing else. There is no advertising, no profile building, and no behavioural tracking across the web.

Hootus works the way your Battle.net account does. You get one identity with him, your Discord account plus an optional Battle.net link, and your characters hang off it across realms and across guilds. There is no separate Hootus account per Discord server. Calling it a sealed box per server would be a tidier story and an untrue one.

What does stay apart is what each guild sees. A guild is shown only the characters that belong to it, the ones on its roster or signed up to its raids. It is not shown your characters elsewhere, and it is not told which other guilds you are in. Raids, signups, notes, loot, and the settings your officers configure stay in the guild they were made in.

One consequence worth naming: a character can be claimed by one person only, and that claim holds across every guild Hootus is in. If a name and realm are already claimed by someone else, your import skips that character rather than taking it.

A guild using Hootus gets a page of its own at /guilds/your-guild, and a progression page beside it. Both are readable by anyone with the link, whether they are signed in or not. While recruitment is open, the guild is also listed in the public directory at /guilds and both pages sit in the sitemap for search engines to find. This is on by default, and your officers can switch it off.

What goes on those pages is about the guild, never about a person. Guild name, realm, region, faction and game version. Focus and goals. The classes, specs and roles being recruited, and how many of each. Raid nights and timezone. Loot rule and soft reserve count. Roster size and raider count, as numbers. How many raids ran in the last 90 days and which raids they were. The opening paragraph of the apply page your officers wrote. Boss progression with first-kill dates. The server’s public Discord invite.

What never goes on them: member names, character names, BattleTags, signups, attendance, bench history, officer notes, and loot records. Counts, never lists. Your own application status shows on the page only to you, after you sign in with Discord.

Two officer switches control it, both in the web app. Recruitment open or closed sits onSettings, Recruitment: close it and the page shows a “not recruiting right now” screen, drops out of the directory, and drops out of the sitemap. Public listing sits on Settings, LFG: turn it off and both pages ask search engines not to index them and leave the sitemap. Neither switch deletes the page. Anyone holding the link can still open it.

• It does not sell your data or share it with advertisers.
• It does not show one guild your characters in another, or tell it which other guilds you are in.
• It does not record voice audio.
• It does not see your Discord or Blizzard passwords.
• It does not put your name, your characters, or your BattleTag on the public guild page.

Only the services needed to run Hootus: the hosting provider and database that store the data, and the APIs Hootus calls on your behalf (Discord and Blizzard). No other third parties, and never for their own marketing.

One in-house exception, said plainly: the people who run Hootus can see data across every guild, because keeping the bot working and answering support tickets needs it. That access is logged.

Data is kept while the bot is in your server and you are part of a guild that uses it. Remove the bot from your server, or leave the guild, and Hootus stops collecting. What he already holds stays in the database until you ask for it to go, so ask: the support server linked from the bot takes removal requests at any time. If you connected Battle.net, the account ID and BattleTag are kept until you disconnect or ask for removal. No Battle.net access token is stored at all.

Officers control their guild’s settings. As a member you can unlink a character, leave, or request removal. Removing the bot from a server ends collection for that server. If you connected Battle.net, the disconnect control sits on the same page as the connect control: one click deletes the account ID and BattleTag, keeps your characters and their settings untouched, and marks them previously verified.

If this policy changes, the updated version lands here with a new date at the top. Material changes will be called out in the changelog.

HootusPlootus is an independent project. World of Warcraft and Battle.net are trademarks of Blizzard Entertainment. Discord is a trademark of Discord Inc. Hootus is not endorsed by either.