PRIVACY POLICY
How ValoHub handles user data. Plain-English summary followed by the full policy.
Last updated: May 26, 2026
Overview
ValoHub ("the site") is an independent, unofficial fan project. The site does not require an account, does not sell user data, and does not store user-submitted information in a database. The maintainer is slendertaker, based in Indonesia, who acts as the data controller for the limited personal data described below.
In short: ValoHub uses standard web analytics, runs a third-party ad network, and forwards user-entered Riot IDs to a public third-party API to look up Valorant player profiles. The site does not collect names, addresses, payment information, or other directly identifying information.
Account safety
ValoHub is a read-only stat lookup site. It has no Riot account integration, no OAuth, no login flow, and no way to authenticate against, modify, or access any Valorant account. The site will never request your Valorant password, account email, sign-in code, 2FA token, recovery code, payment information, or any other credential.
The only Valorant-related input the site asks for is a public Riot ID (the Name#Tag identifier that already appears on the in-game scoreboard and on Riot Games' own public pages). A Riot ID by itself is not a credential and cannot be used to sign in to an account.
If any page on valohub.co ever appears to ask you for a Valorant password or other credential, close the tab immediately and report it to [email protected]. For official Riot Games sign-in, use only account.riotgames.com.
Data we collect
The site processes the following categories of data:
- Analytics data. Standard request data (IP address, user agent, referrer, pages visited, approximate location derived from IP, screen size, device type) is collected by analytics providers listed below. This data is used to measure traffic and improve the site.
- Behavioral / session data. Anonymized session replays and heatmaps may be recorded by Microsoft Clarity on pages other than
/players. Clarity is intentionally disabled on player lookup pages to avoid recording the Riot IDs you type. - Riot IDs you enter. When you submit a Riot ID on the player lookup or leaderboard pages, the entered
Name#Tagis forwarded to the Henrik API to retrieve the corresponding public Valorant profile. A Riot ID is a public display identifier (the same handle visible on the in-game scoreboard), not a credential, and the site does not ask for, transmit, or accept Valorant passwords, account emails, sign-in codes, or 2FA tokens at any point. The site does not save your submitted Riot IDs to a database. Submissions may appear transiently in standard web server access logs maintained by the hosting provider, and recently searched IDs are stored locally in your browser so you can revisit them. - Rate-limiting identifiers. For protected API routes, an IP-derived identifier is briefly stored by Upstash Redis to enforce a sliding-window rate limit (25 requests per 60 seconds per identifier). These records expire automatically within the rate-limit window.
- Local browser storage. Some tools (composition builder, tier list maker, crosshair generator, etc.) store your in-progress work in your browser's local storage. This data never leaves your device and is not visible to the maintainer.
ValoHub does not knowingly collect government IDs, payment details, contact information, account passwords, or health-related data.
Third-party services
The site relies on the following third-party providers. Each operates under its own privacy policy:
- Google Analytics 4 (Google LLC). Aggregated traffic analytics. Enabled when the
NEXT_PUBLIC_GA_IDenvironment variable is configured. See Google's privacy policy. - Microsoft Clarity (Microsoft Corporation). Heatmaps and anonymized session replay. Disabled on
/playerspages. See Microsoft's privacy statement. - Umami Cloud (Umami Software, Inc.). Privacy-focused analytics that does not use cookies or collect personal data. See Umami's privacy policy.
- Adsterra. Third-party advertising network used to monetize the site. Adsterra and its downstream partners may set cookies and use identifiers for ad measurement and personalization. See Adsterra's privacy policy.
- Henrik API (api.henrikdev.xyz). Community-run Valorant API that receives the Riot IDs you submit and returns public profile, leaderboard, store, and server-status data.
- Upstash, Inc. (Redis). Serverless Redis used for short-lived API rate-limiting records.
- Hosting provider. The site is hosted on a major cloud provider, which processes standard request logs as a data processor on behalf of the maintainer.
Advertising
ValoHub displays ads through the Adsterra network to cover hosting and API costs. Adsterra and its downstream demand-side partners may use cookies, device identifiers, and similar technologies to serve and measure ads, including personalized ads where permitted by law.
The ad formats shown include standard display banners (including a sticky anchor banner pinned to the bottom of the screen), in-feed native units, a Social Bar overlay docked to the edge of the screen, and a Popunder that may open a single background tab on interaction. Standard banner and native ads, including the sticky anchor banner, may appear on any page. The more intrusive Social Bar and Popunder overlays may also appear, except on the player-lookup pages (where you enter a Riot ID), which are kept overlay-free. You can block any of these formats with a browser ad blocker.
ValoHub does not currently operate a dedicated cookie-consent banner. Where local law requires prior consent for non-essential or personalized advertising, you should use your browser's privacy controls (or an ad blocker) to limit advertising cookies until such a tool is in place.
The maintainer does not receive your individual ad-related data; only aggregated reporting is provided. To manage advertising preferences, you can use the controls offered by Adsterra and by industry programs such as YourAdChoices or Your Online Choices (EU).
Legal basis (EU/UK)
For visitors located in the European Economic Area, the United Kingdom, or Switzerland, the site relies on the following legal bases under the GDPR and UK GDPR:
- Legitimate interest for aggregated traffic analytics, abuse prevention (rate-limiting), and security logging.
- Performance of a request when you submit a Riot ID and the site forwards it to the Henrik API to return the profile you asked for.
- Consent for non-essential cookies and personalized advertising where required by local law. ValoHub does not yet provide a dedicated consent banner; until one is in place, visitors in regions that require prior consent should rely on browser privacy controls to limit non-essential cookies.
Your rights
Depending on where you live, you may have one or more of the following rights:
- Request access to the personal data the site processes about you.
- Request correction or deletion of inaccurate or unnecessary data.
- Object to or restrict certain processing, including personalized advertising.
- Withdraw previously given consent at any time.
- Request data portability where applicable.
- Lodge a complaint with your local data protection authority. EU residents can find their authority via the European Data Protection Board; UK residents can contact the Information Commissioner's Office (ICO).
Because ValoHub does not store user accounts or persistent profiles, most requests are limited to logs and analytics samples that can be identified by IP and approximate time window. Send any request to [email protected].
Data-rights requests follow the statutory response window under the GDPR and UK GDPR: verified requests are answered within 30 days, extendable by a further 60 days for complex cases as permitted by law. This is separate from the general 5 business days contact reply window listed on the contact page; the longer 30-day window may apply when identity verification or downstream-processor coordination is required.
Manage your preferences
The first time you submit a Riot ID on the player lookup, the site records a small acknowledgment in your browser's local storage so the third-party data notice is not shown on every search. Nothing about this acknowledgment is sent to the site or to any third party.
Loading your saved preference…
Data retention
- Rate-limiting records expire automatically within the sliding window (typically 60 seconds).
- Analytics retention follows each provider's default settings, generally 14 months for Google Analytics 4 and capped session-replay windows for Microsoft Clarity.
- Standard request logs from the hosting provider are retained for short operational windows defined by that provider.
- The site itself does not maintain a long-term database of user activity.
Children
ValoHub is not directed at children under the age of 13 (or under 16 in jurisdictions where that is the applicable threshold for the digital age of consent). The site does not knowingly collect personal data from children. If you believe a child has provided personal data to the site, please contact the maintainer and the data will be removed.
Changes to this policy
This policy may be updated from time to time. Material changes will be reflected in the "Last updated" date above and, where appropriate, surfaced on the site. Continued use of the site after changes take effect constitutes acceptance of the updated policy.
Contact
For privacy questions, data-rights requests, or other concerns about this policy, email [email protected] or use the contact page.