✦ tftclarity
Product Privacy Policy Terms of Service

Legal

Privacy Policy

Effective and last updated: August 13, 2026

Plain-language summary. tftclarity can be used without a tftclarity account. If you use match review or Player Pool features, you may submit a Riot ID to retrieve available player and match information. We do not currently use Riot Sign On, do not sell personal information, and do not use advertising trackers.

This Privacy Policy explains how the independent tftclarity project (“tftclarity,” “we,” “us,” or “our”) handles information when you use tftclarity.cn and its related web application (the “Service”). The Service is operated from the People’s Republic of China.

1. Information we process

CategoryExamples and purposeTypical retention
Anonymous visitor identifier A signed tft_visitor cookie is used for abuse prevention, request limits, anonymous settings, and separating one visitor’s conversation state from another’s. It does not contain a name, email address, or Riot identifier. Cookie lifetime: up to 1 year. Daily quota counters are organized by day.
Queries and result context The text you submit, a random browser-generated conversation ID, selected filters, structured query data, result metadata, and whether an AI-generated explanation was used. Server-side query snapshots: up to 30 days. Query cache: about 5 minutes. Active conversation context is used for the current interaction; structured Conversation Bridge records used for follow-up questions are limited to recent records and retained for no longer than 7 days.
Riot IDs, player profiles, and match facts For match review and Player Pool features, you may submit a Riot game name, tag line, and region for yourself or another player. We use them to resolve the requested profile and retrieve available recent match information, including match identifiers, timestamps, placement, final board, units, items, traits, augments, and derived composition signatures. Where an upstream provider returns a PUUID, it is stored only in encrypted form when a server-side encryption key is configured; otherwise it is not persisted. Riot IDs, normalized match facts, and collection records may remain in the shared server-side fact store after a player is removed from a Pool so that previously collected public match facts can be reused and audited. They are deleted or de-identified when no longer reasonably needed, or following a valid request where applicable.
Player Pools and sharing Pool names, member Riot IDs, selected environment, ownership scope, derived statistics, and an optional eight-character share code. Anyone who receives a valid share code can copy the Pool's current member list into an independent Pool. Pool membership remains until you remove a member, delete the Pool, clear the associated visitor data, or ask us to delete it. Deleting a Pool removes that grouping but does not automatically erase shared match facts that may also support another Pool.
Preferences and local settings Rank filters, sample thresholds, item scope, language, settings-panel state, and layout width. Some preferences are stored server-side under an anonymous scope; language and layout choices are stored in your browser’s local storage. Until reset, cleared, or no longer needed.
Optional feedback If you select “Helpful,” “Not helpful,” or save an alias candidate, we store the related query, normalized result details, rating, and a random feedback ID so we can diagnose quality issues. Until the feedback is reviewed, deleted, or no longer needed for product improvement.
Security and service logs Request time, requested path, browser user agent, network address, error details, and hashed network/visitor identifiers used for rate limiting, security, troubleshooting, and availability. Raw infrastructure logs follow the hosting system’s configured rotation. Security records are kept only as long as reasonably needed.

Please do not place names, contact details, Riot account credentials, API keys, or other sensitive information in a query or feedback message.

2. Account connection and information we do not request

  • No tftclarity account is required.
  • We do not currently use Riot Sign On. Entering a Riot ID does not prove that the visitor owns or controls that Riot account.
  • Do not enter Riot account credentials. We never ask for a Riot password, authentication code, or API key.
  • We do not collect payment information.
  • We do not sell personal information or share it for cross-site behavioral advertising.

3. How we use information

  • Provide natural-language TFT queries, aggregated statistics, and follow-up conversation context.
  • Resolve a submitted Riot ID, show available recent match history and final-board facts, and generate post-game review.
  • Create, manage, share, and compare user-selected Player Pools and their observed statistics.
  • Remember your anonymous preferences and maintain fair usage limits.
  • Generate structured parsing or evidence-grounded explanations when optional AI features are enabled.
  • Investigate errors, prevent abuse, secure the Service, and improve data and answer quality.
  • Comply with applicable law and enforce our Terms of Service.

Depending on the context, our processing is based on providing the Service you request, your choice to submit optional feedback, our legitimate interest in operating a secure and useful service, and compliance with legal obligations.

4. Cookies and browser storage

Strictly necessary cookie

tft_visitor is an HTTP-only, same-site cookie used to distinguish anonymous visitors, enforce request limits, and isolate settings and conversation state. In production it is transmitted only over HTTPS. It expires after up to one year. Because this cookie is necessary to protect and operate the public Service, disabling it may prevent some features from working correctly.

Local storage

The browser stores language, panel, and layout preferences under keys beginning with tftagent.. These values stay on your device until you clear site data or reset them in the application.

Quick-tool favorites, daily usage counts for a rolling seven-day window, recommendation visibility, and favorite-reminder choices are stored locally under tftagent.quickTools.v1. Only tools you explicitly favorite appear in My favorites. Counts help suggest shortcuts and occasionally offer to save a frequently used tool; they do not include chat content, are not sent to the model, and are not synced across devices. You can hide recommendations, remove a favorite, dismiss or disable a reminder for a tool, or clear site data to remove these records.

We do not currently use third-party advertising or cross-site analytics cookies.

5. Service providers and data sources

We may disclose limited information to service providers only where needed to run the Service:

  • Hosting and security providers process network and service logs to deliver and protect the site.
  • Configured OpenAI-compatible AI providers may receive the query and structured evidence required to parse or explain a result when an optional AI feature is enabled. The product remains usable with deterministic, non-AI fallbacks.
  • TFT data providers receive structured game-data requests. The current product uses third-party MetaTFT data, OP.GG-backed player lookup, and official or public static TFT sources. When you request a player or Pool feature, the relevant Riot ID, region, or provider identifier is sent to the provider required to resolve that player and retrieve match information.

These providers may process information in other countries. We use only the minimum information reasonably needed for the feature and require providers to handle it under their own security and privacy obligations.

6. Data security

We use HTTPS, HTTP-only signed visitor cookies, server-side secrets, scoped anonymous identifiers, access controls, request limits, and data minimization. Riot API keys and AI provider keys are intended to remain on the server and are not included in browser code. No system is perfectly secure, so we cannot guarantee absolute security.

7. Your choices and rights

You can clear browser storage through your browser, reset application preferences, clear the current conversation, remove a player from a Pool, delete a Pool, stop submitting feedback, or stop using the Service. Pool deletion removes the grouping; shared match facts require a separate deletion request. Depending on applicable law, you may request access, correction, deletion, restriction, or a copy of personal information associated with you.

Because the Service has no tftclarity login, we may be unable to connect a record to you without additional details. When making a request, include the approximate date and time, relevant Riot ID, Pool name or share code, and query or feedback concerned. If necessary, we may ask for the anonymous visitor identifier or reasonable proof that you are entitled to make the request. Do not post any of this information publicly.

Send privacy requests to tftclarity@outlook.com. We may ask for reasonable verification and will respond as required by applicable law.

8. Children

The Service is not directed to children under 13, or the minimum age required by local law. We do not knowingly collect personal information from children. A parent or guardian who believes a child provided personal information may contact us for deletion.

9. Changes to this policy

We may update this policy when the Service, providers, or legal requirements change. We will change the “last updated” date and, for material changes, provide a reasonable notice on the site.

10. Contact

Privacy questions and requests: tftclarity@outlook.com

Website: https://tftclarity.cn/

Riot Games notice

tftclarity isn't endorsed by Riot Games and doesn't reflect the views or opinions of Riot Games or anyone officially involved in producing or managing Riot Games properties. Riot Games, and all associated properties are trademarks or registered trademarks of Riot Games, Inc.

© 2026 tftclarity · Independent community project ProductTerms