Skip to content

Who runs this site

Insanity Raid Tools is a free loot-council tool for World of Warcraft: Forever guilds. Any guild can be registered here by one of its members, and each guild's data is kept separate from every other guild's. The site has no paid features and shows no advertising.

This copy of the site is run by its operator, who decides what happens to the data stored here. Contact the operator at contact@insanityguild.com. For a question about the data a guild keeps here (its roster, loot history or voting sheets), you can also ask that guild's leader or officers.

What we store

  • Your Battle.net account id and BattleTag. You sign in with Battle.net. We receive your account id and your BattleTag and use them to recognise you. We never see your Battle.net password, and we do not keep the access token Battle.net issues: it is used once, at sign-in, to read your character list.
  • Your World of Warcraft accounts. Battle.net lists your WoW: Forever characters by the World of Warcraft account that holds each. We keep Blizzard's id of each of those accounts, which characters it holds and when Battle.net last listed it, and, for each browser you sign in with, which of them you chose to act as.
  • Your characters. Names, region, class, race, level, guild and guild rank, equipped items and avatar of your World of Warcraft: Forever characters, as published by Blizzard's API, and their in-game identifiers (GUIDs) when a guild's addon has seen them.
  • Characters of registered guilds. When a guild is registered, the site reads that guild's roster from Blizzard's API. Characters of its members are therefore stored even for players who have never signed in here. They are not linked to any account until their owner signs in.
  • Your memberships. Which registered guilds each of your World of Warcraft accounts belongs to, and its role in each. An account becomes a member of a guild automatically when you sign in and it owns a character in that guild's roster, or when one of the guild's officers adds it.
  • What you enter here. Best-in-slot lists, votes and comments on loot-council sheets, and loot data you import. An import from the addon or from Gargul holds the names, in-game identifiers and loot of everyone in that raid, and of anyone outside it a raid item was traded to.
  • Raid records. Which characters attended a boss kill, who received which item and whom it was traded to afterwards (also a player outside the raid or the guild), as recorded by a guild's addon or entered by its officers.
  • Sign-in sessions and an audit log. For each browser you sign in with: the IP address it signed in from, its browser identification, and when it was last used. Important actions (signing in, registering a guild, role changes, sheet and loot changes) are logged with the member who performed them and the IP address the request came from.
  • Request logs. The site logs every request it receives: when, the address of the page, the IP address it came from and how it was answered. Ballot comments, BattleTags, pasted imports and any long text are left out of its log. Heroku's router, which passes every request on to the site, logs it as well: when, the page's whole address, the IP address and how it was answered.

Who can see it

A guild's data is visible only to the active members of that guild. Members of other guilds, and the people who operate this site through its pages, cannot open a guild's pages. Inside a guild, the roster, gear, best-in-slot lists, loot history and attendance are visible to all its members; BattleTags are shown to its officers and leader only. A loot-council sheet, including its votes and comments, is visible only to the guild's officers and to the members invited to that sheet, and the sheet's own settings decide when even they see the votes; other members see the final priorities once a sheet is published, and nothing else.

Your best-in-slot lists belong to your character and are visible to the members of the guild the character is currently in. The operator of the site can reach the database and the logs directly, as whoever runs a server can. We do not sell or share data with anyone.

One Battle.net account can hold several World of Warcraft accounts, and here each of them is somebody of its own: its own role in each guild, its own seat and vote on a loot council, its own characters. After signing in you choose which of them you are playing, and you can switch at any time. Battle.net tells us which World of Warcraft accounts a Battle.net account holds, not who is at the keyboard: anyone who can sign in with a Battle.net account can act as any of its World of Warcraft accounts, and see and do what each of them may. Players who share one Battle.net login share that.

Where it is kept

In this site's database and logs, and in the database's backups, all hosted for the operator by Heroku, a Salesforce company. The site, its database and its logs are in Heroku's US region, in the United States, and Heroku keeps the backups in the United States too. Heroku makes a backup of the database every day and keeps each one for up to 14 days. The operator may also have the logs sent on to a logging service; there they are kept for as long as that service keeps them.

How long we keep it

  • Data obtained from Blizzard's API is refreshed regularly and is never kept for more than 30 days without being checked again. When Blizzard no longer lists a character, its API data is removed.
  • A sign-in session ends when you sign out, when your account is disabled, or after 30 days without use; a session nobody used for 30 days is then deleted, with its IP address and browser identification.
  • Audit log entries stay as long as their guild is registered here. Their IP addresses are removed after 30 days.
  • Request logs are kept until newer lines replace them, for a week at most: Heroku keeps only the newest 1,500 lines of the site's log. The counters that limit how often one IP address may sign in run out after ten minutes, and the site's cache drops them as it fills.
  • A loot import that an officer applied stays as part of its guild's loot records. One that was rejected, or could not be read, is deleted 30 days later.
  • When your character leaves a guild's roster, your membership in that guild lapses after a short grace period. When a guild is removed from the site, everything it owned here is deleted.
  • Heroku deletes the database's backups after 14 days at most. Something deleted here is gone from the backups once the last backup holding it has been deleted.

Deleting your account

You can delete your account from your account page at any time. Deleting it signs you out everywhere, removes your memberships, your seats on loot councils and the votes and comments you cast, and unlinks your characters from you. It also removes your sign-in history from the audit log, and your IP address from every audit log entry. A guild leader has to hand leadership to another member first.

What stays is what belongs to a guild's records rather than to you: the character names in a guild's roster and loot history, loot imports you submitted, and the guild's audit log entries. None of them carries your name any more: wherever the site recorded that you did something (submitted or reviewed an import, created a voting sheet, edited a loot entry), that record is cleared. A final loot priority that was already decided stays as it was decided. Heroku's backups of the database still hold your account until they are deleted (up to 14 days); ask the operator if you need it removed from them sooner.

Removing this site's access under "Connections" in your Battle.net account settings stops future sign-ins.

Cookies

At most three cookies, all strictly necessary and set only by this site: one that keeps you signed in, one that protects forms against forgery and carries a sign-in while it is under way, and - only if you hide the notice that offers a guild's leadership to its in-game guild master - one that remembers that you hid it. There are no analytics and no tracking cookies.

Third parties

  • Blizzard Entertainment. Sign-in happens on Battle.net; character, guild and item data comes from the Blizzard API. Blizzard's own privacy policy applies to your Battle.net account.
  • Wowhead. Pages that show items, loot-council sheets included, load Wowhead's tooltip script, and item icons are loaded from Wowhead's and Blizzard's image servers. Your browser contacts those servers directly, so they see your IP address and which item you hovered over. The site sends them nothing about your account or your guild, but their script runs in the page you are looking at.
  • The operator's providers. Heroku, a Salesforce company, hosts the site, its database, its logs and the backups, and holds them on the operator's behalf; so does any logging service the operator has the logs sent on to.