Viserio Cooldowns API: Acceptable Use

Not allowed

• Exceeding, evading, or attempting to circumvent rate limits. Quotas are per group and scale with the group’s boost; regenerating a group’s key does not reset them. Holding keys for the several real groups you operate is fine and expected; creating sham or duplicate groups, or using distributed requests, to multiply quota for one logical consumer is prohibited.
• Continuing to hammer the API while rate limited or while the service is shedding load. Repeated requests after a 429 or 503 escalate to a temporary block of your IP address.
• Intentional probing or enumeration: guessing or iterating identifiers, requesting groups you do not administer, or otherwise attempting to reach data you are not entitled to. We run automated abuse detection (anomalous volume, identifier scanning, elevated error rates) and act on it.
• Using battletags, character names, or any exposed data to harass, deanonymize, dox, or profile individuals, or for any unsolicited contact.
• Exposing a guild member’s information (for example their battletag) where that member has not agreed to it. Judge this yourself; the group opt-in is not a substitute.
• Creating a permanent mirror of the data, or retaining cached data beyond 30 days without refetching it. A refresh-based cache is fine; a permanent copy is not.
• Reselling or publicly republishing raw group data, or building a public directory of it, without the originating group’s consent.
• Providing a false or stale key description, or publicly exposing a group key. (Supplying the key to the third-party tool it is meant for is expected and fine; the description should just say what that is.)

Expected use

• Provide an accurate key description and keep it current. It is how we understand real usage in this early version and reach you about your integration. Feature requests go via Discord, not the description.
• Cache responsibly, prefer conditional requests (ETag / If-None-Match) and incremental polling over tight loops, and respect Retry-After.
• Treat group data as belonging to that group. Honor deletion and opt-out.
• Respect Blizzard’s Battle.net / WoW API terms for any data you store or display.
• Pin to /v1 and handle changes and outages gracefully.

Enforcement

We may throttle, suspend, or permanently revoke a key, and temporarily or permanently block an IP address, for any violation, without notice, to protect the service and the people whose data it carries. Good-faith use and an honest, current key description are what keep an integration in good standing.