FragLy
Home/Privacy Policy

Privacy Policy

FragLy has no user accounts and collects no personal information directly. This page sets out exactly what happens to the data that does pass through the site.


Summary

No accounts. No passwords. No personal profiles. FragLy stores your display preferences in your own browser, sends the Riot IDs you search to the game data API in order to look them up, and serves advertising through Google, which uses cookies. Everything below is the detail.

Information FragLy collects

Riot IDs you search

When you search a Riot ID, that name and tag is sent to the third-party Valorant data API in order to retrieve the match data. Riot IDs are public identifiers, visible to anyone in your game lobby. Searches may be cached briefly to reduce load on the upstream API. FragLy does not build a profile linking searches to you.

Data stored in your browser

FragLy uses your browser's local storage for preferences — the last Riot ID you searched so you do not have to retype it, your selected region, and interface settings such as your chosen crosshair in the aim trainer. This stays on your device. Clearing your browser data removes it, and FragLy cannot read it remotely.

Technical and usage data

Like effectively all websites, FragLy's hosting and analytics receive standard technical information with each request: IP address, browser type and version, device type, referring page, and the pages viewed. This is used to keep the site running and to understand which pages are used. It is not sold.

What FragLy does not collect

Third-party services

FragLy relies on the following third parties. Each has its own privacy policy governing the data it receives.

ServicePurposeWhat it receives
HenrikDev APIValorant match and rank dataThe Riot ID being looked up
valorant-api.comAgent, map and skin assetsStandard asset requests
Riot GamesOfficial news headlines, linked out toNothing until you click through
CloudflareHosting, caching, and the AI coach backendStandard request data
Google AdSenseDisplay advertisingStandard request data and cookie identifiers
Google FontsTypefacesStandard request data

The AI coach

When you request AI coaching, the match statistics shown on your report are sent to an AI provider — Cloudflare Workers AI, with Google's Gemini API as a fallback — to generate the written feedback. What is sent is the statistical summary, not personal information about you. FragLy does not retain these requests to train anything.

Advertising and cookies

FragLy displays advertising through Google AdSense to cover running costs. The following applies:

Where required by law, a consent notice is shown before personalised advertising cookies are set, and you can decline.

Your rights

Depending on where you live, you may have the right to access, correct, or delete personal data held about you, to object to processing, or to withdraw consent. Because FragLy operates no accounts and stores no personal profiles, in practice there is usually very little to act on — but any request sent to the address on the contact page will be handled.

To remove locally stored preferences yourself, clear site data for this domain in your browser settings. To reset advertising personalisation, use the Google Ads Settings link above.

Children

FragLy is not directed at children under 13 and does not knowingly collect information from them. If you believe a child has provided information, contact the address on the contact page and it will be removed.

Data retention and security

Cached API responses are short-lived and expire automatically. Preference data lives in your browser until you clear it. FragLy is served over HTTPS. No system is perfectly secure, but since the site holds no credentials and no payment data, the value of what could be exposed is deliberately close to zero.

External links

FragLy links to external sites, including Riot's official news pages. This policy does not cover those sites. Once you follow a link out, that site's own policy applies.

Changes to this policy

This policy may be updated as the site changes. The "last updated" date at the top of this page reflects the current version. Material changes will be noted on the page.

Contact

Questions about this policy, or any privacy request, go to [email protected]. Please include "privacy" in the subject line.