Skip to content

Privacy Policy

Last updated: 2026-10-21

Who we are

RaidQ is run by PoGo.Tips LLC, a Wyoming limited liability company. Questions about this policy or your data: privacy@pogo.tips.

What we collect

Streamers

When you sign in to the RaidQ dashboard, we store your Auth0 account ID, email, display name and avatar URL (pulled from your Google or Twitch profile at sign-in), the platform (YouTube or Twitch) you signed in with, your channel ID, and a login/admin-action audit log. Your login sessions also store a hashed version of your IP address and browser user agent, used only to help us catch suspicious logins. If we remove a streamer account, the channel's raid history and our admin audit trail are kept (the audit trail follows the 12-month retention below); you can ask for !forgetme-style scrubbing separately by emailing privacy@pogo.tips. Streamers can download the data held for their channel from the dashboard as one JSON file (up to twice a day). The file includes each viewer's own chat-platform user id when RaidQ has it, the same id YouTube or Twitch already shows the streamer, and never any login or payment detail.

Viewers

Viewers join a raid queue by typing a chat command. There's no account to create. When you do, we store your chat handle, the platform's user id for your chat account (sent to us with each command, used so RaidQ keeps one record per viewer across chat-name changes), your registered Pokémon GO trainer name, your tier (a rank a streamer or mod can set), your streak and raid history, and, if a streamer uses the !snipe credit feature, a record of that credit. A name showing up in a queue just means someone typed a command in that channel's chat. It doesn't mean we know anything else about you. Tier and supporter status are shared only between channels PoGo.Tips pairs at both streamers' request.

To remove yourself: type !forgetme <your trainer name> in chat, then !forgetme yes within 5 minutes to confirm. This deletes your profile and queue entry right away. Your raid and snipe-credit history is kept, but your handle on it is replaced with a random token that is generated fresh for that request and is not derived from your name, so the history can no longer be traced back to you. This is permanent: we keep no mapping from the token back to your name, and we cannot undo it. A channel mod can also remove you immediately with !forgetyou, same scope as !forgetme. Deletion applies per channel — if you've raided in more than one streamer's channel, run !forgetme in each one. If you want your raid history fully erased rather than anonymized, email us and we'll handle it by hand.

Two roles

For queue state, streaks, and raid history we generate ourselves, we're the controller. We decide what's collected and why.

For a membership or subscriber list a streamer uploads (a YouTube or Twitch CSV export) so RaidQ can set viewer tiers, the streamer is the controller and we're the processor. We only use that list to run their queue, never for anything else. Membership levels come from the list the streamer uploads. RaidQ also sees whether a chatter is a member or subscriber from the chat bot when they use a command. RaidQ does not connect to YouTube's or Twitch's APIs. When a YouTube membership list includes member names, RaidQ stores each matched member's YouTube display name on their viewer profile so the streamer can recognize them, and !forgetme deletes it with the profile.

Who else sees your data

We use a small number of services to run RaidQ:

  • Cloudflare hosts the app and its database.
  • Auth0 handles streamer login, including Twitch and Google sign-in.
  • Stripe handles payment for paid plans. RaidQ stores your Stripe customer id, your subscription id, your plan and its status, a grace-period date, and a log of Stripe event ids and types. Your card number, billing address and the email you give Stripe never reach RaidQ.
  • Nightbot, the chat bot a streamer connects, is where chat commands come from. With each command, the streamer's Nightbot sends us the viewer's chat name, user level (for example member, subscriber or moderator), platform user id, and the command text, plus the channel's id and name.
  • GitHub (raw.githubusercontent.com) is where RaidQ fetches Pokémon boss images from when a streamer runs !set. The fetch is made by RaidQ's server, not your browser, and a copy of each image is kept in RaidQ's own storage.
  • Discord, if a streamer connects a webhook, receives deck-ready notifications for that channel.
  • jsdelivr serves the Chart.js library used to draw charts on the Raid Reports page. Your browser loads it directly from jsdelivr's servers, so jsdelivr sees your IP address when that page loads. jsdelivr also serves the Cropper.js image-cropping library (script and stylesheet) on the Custom bosses page, so jsdelivr sees your IP address there too.

Our documentation site (this page included) used to load Google Fonts in your browser. We've turned that off, so no font requests leave your browser when you read these docs.

We don't sell data, and we don't use it for ads or analytics.

Cookies

RaidQ sets two cookies on the streamer dashboard, both strictly necessary to keep you signed in:

  • rq_sess, your session, lasts 90 days
  • rq_hs, a short-lived login handshake, lasts 10 minutes

Neither is used for tracking or analytics. There's no cookie banner because there's nothing to opt into.

How long we keep things

  • Viewer profiles and queue entries: a viewer who has not typed a command in a channel for 12 months, and whose tier on that channel is free at that moment (a membership or subscription from the streamer's uploaded list, or a tier a mod set, normally gives a tier above free; !whoami shows your current tier), is removed from that channel automatically with exactly the same treatment as !forgetme: the profile and queue entry are deleted, the handle and trainer name are removed from the channel's member-file import log and lapsed lists, and the raid history stays under a fresh random token. A viewer with any tier above free is never removed automatically. The profile that belongs to the channel's own account (the one that holds the streamer's raid streak) is never removed automatically either; the streamer can still delete it with !forgetme. Viewers who are listed as members in RaidQ (from the streamer's uploaded membership list, or set by a mod) are never removed automatically, whatever their tier. The job runs hourly, a few viewers at a time, so removal can land a little after the 12-month mark.
  • Raid history (raids run, who took part, snipe credits): kept indefinitely. It is never deleted on a schedule. A viewer who runs !forgetme, or whom a mod removes with !forgetyou, has their handle on it replaced permanently with a random token.
  • Admin audit logs: kept for 12 months, then deleted automatically. Admin audit entries may include an email address an admin pre-approved; these follow the 12-month audit retention.
  • Streamer login sessions: expire after 90 days
  • A membership CSV a streamer uploads for preview: held for 20 minutes, then expires automatically whether or not it was applied
  • Member file import log. When a streamer uploads a member file, we keep for that channel: the latest import log (names marked lapsed or removed, plus each removed member's previous membership level, tier and tier lock), the last 10 lapsed-member lists, and one row count per platform. The next upload replaces the log. !forgetme removes you from the log and the lapsed lists.

Deletion

Viewers can self-serve a profile and queue deletion (which also permanently anonymizes their raid and snipe-credit history) with !forgetme, or ask a mod to run !forgetyou on their behalf (see above). For anything else, including full raid history erasure or a streamer account, email privacy@pogo.tips and we'll take care of it within 30 days.

!forgetme/!forgetyou and the automatic 12-month removal scrub the live database immediately. A copy of your data may still exist in our automated backups taken before that. Backups are never edited; they age out on a fixed schedule: hourly backups are kept for 2 days, daily backups for 30 days and weekly backups for 84 days, each in locked storage that cannot be shortened (deletion can lag the schedule by up to a day), and an offline copy of each weekly backup is kept for 12 months. So the longest any backup copy of your data can exist is 12 months after the scrub.

Under 13

We don't knowingly collect data from viewers under 13 beyond a chat handle typed into a queue, and we'll remove it on request. The streamer dashboard itself is for users 13 and up.

This is not legal advice. Contact us at privacy@pogo.tips with questions.