Last updated: 14 October 2026
Outlier Hunt ("we", "us") is an internal analytics tool operated by an individual YouTube content producer ("the Operator") for the Operator and the Operator's production team. It is not open to the public: access is limited to named team members who sign in with a Discord account or a one-time access code issued by the Operator.
This policy explains what information the service collects, how it is used, and the choices available to team members. Contact: newsmach11@gmail.com.
Account information. When a team member is given access, we store their display name, and — if they sign in with Discord — their Discord username and avatar, as provided by Discord's OAuth service. If they sign in with an access code, we store only the display name the Operator assigned to that code. If they sign in with a username and password, we store the username and a salted one-way hash of the password — never the password itself. Discord sign-in is handled by Discord, and access codes are single-use. A team member may also request an account themselves on the sign-up page: we store the display name and username they choose (and their password only as a salted one-way hash, as above), and the account stays inactive until the Operator approves the request.
Activity logs. The service records team members' activity inside the app: sign-ins, pages viewed, searches and lookups performed, filters and options changed, channels enrolled for tracking, and videos opened, together with timestamps, IP address, and browser user-agent. These logs exist so the Operator can see who used the tool and what work was done. Logs are append-only (they cannot be edited or deleted through the app) and are visible to the individual member (their own history) and to the Operator (all history).
YouTube data. The service uses the YouTube API Services to retrieve publicly available information about YouTube videos and channels: titles, channel names, view counts, like counts, comment counts, subscriber counts, publish dates, and thumbnail images. We store time-stamped snapshots of the public statistics, records of title and thumbnail changes for tracked videos, and the public thumbnail images themselves, so that performance over time can be displayed as charts and histories. We do not access any private YouTube data, any data about a signed-in YouTube user's account, watch history, or subscriptions, and we do not collect comment text.
Derived metrics. From the public statistics above, the service calculates its own metrics — for example an "outlier score" comparing a video's views to its channel's typical views, and views-per-hour figures. These metrics are calculated independently by Outlier Hunt; they are not provided by YouTube and are labeled as our own calculations in the product.
Technical data. Standard server logs (timestamps, IP addresses, user-agent strings) are kept for security and troubleshooting.
Account and activity information stays within the service and is visible only to the signed-in member (their own data) and the Operator. Service infrastructure (hosting and database providers) processes data on our behalf. We disclose information only if required by law.
Access codes are stored hashed, and passwords are stored only as salted one-way hashes; sessions use HTTP-only cookies; the API key used for YouTube API Services is kept server-side and is never exposed to browsers or team members.
Material changes to this policy will be posted at this URL with an updated date.