poro.LOL
Privacy policyTerms of service
Language
한국어English✓日本語简体中文繁體中文العربيةČeštinaDeutschΕλληνικάEspañolFrançaisMagyarBahasa IndonesiaItalianoPolskiPortuguês (Brasil)RomânăРусскийไทยTürkçeTiếng Việt

Titles, nicknames, posts, and other user content are shown in their original form.

Loading translations…

Privacy policy

Privacy policy

The PORO operation team processes information only to the extent necessary for the service, and reduces exposure of original game identifiers and unnecessary storage.
Effective date
Aug 25, 2026
Operator
PORO Operation Team

1. Scope of application and basic principles

This policy applies to the PORO website operated by the PORO operations team and its connected local Companion features. The PORO operations team processes the Riot ID and region entered by users to search and analyze match history and does not request Riot account passwords or payment information.

2. Information we process

  • User input: Riot ID (game name and tag), search region, and the search and analysis filters selected by the user
  • Traffic statistics: We process page categories, access times, referring site domains, permitted campaign tags, random browser and session identifiers, and secret-key hashes of connection IPs. Statistics do not store raw IP addresses, searched Riot IDs, emails, authentication links or full referring URLs. Unknown IPs are shown separately, and admin and account authentication screens are excluded from collection. Aggregated results are available only to authenticated administrators.
  • Riot game data: Public account information, ranks, match history, participants, champions, items, runes, timelines and current-game lookup results
  • Information on your device: Up to 3 recent searches, favorite settings, and an autocomplete index of up to 50 entries are kept in your browser's local storage. The autocomplete index contains only Riot IDs, regions, profile icons and levels, and the most recently observed solo queue rank at lookup time for accounts successfully searched on this device.
  • Public profile search directory: We may store the Riot IDs, regions, profile icons, levels, Ranked Solo/Duo information, first and last verification times, and verification counts of successfully searched accounts and participants in public matches on the server. Participants whose names Riot has not made public are excluded.
  • Match history display cache: To avoid requesting the same match from Riot repeatedly, we may store public match participants' Riot IDs, champions, teams, results, KDA, CS, damage, vision, objectives, runes, spells, items, and match times on the server. This display cache does not store original PUUIDs or raw Riot API responses. Server-only storage of originals is described in section 4 below.
  • Service operation information: Minimum technical information required for security and failure response, such as request time, error and call restriction status, etc.
  • Automatic rank tracking: We keep each searched account's public Riot ID, region, HMAC identifier, and collection schedule in a separate task list, and check its current rank periodically. This task list does not store original PUUIDs. Tasks are removed from the collection list 180 days after the last match history search.
  • Champion tier statistics: Check Emerald or higher accounts in the public rank list and collect the champion, position, wins and losses of the current patch. We keep public Riot IDs and pseudonym identifiers for collection operations, and match statistics use pseudonym identifiers instead of the original PUUID. Previous patch history is kept separate and the screen only provides aggregated statistics with no personal identifiers.
  • Inquiry information: Email address and inquiry content provided when the user inquires by email
  • Community member information: Login email address, nickname, password protected by a one-way hash, registration and email verification times, account permissions, and restriction status. Email addresses are not displayed in public posts and can be viewed only in the super administrator's member management. We use Google Gmail to send email verification and password reset instructions; the recipient's email address and verification link are transmitted through that service. The server-stored verification-link value is protected by a hash and expires after 30 minutes. Expired records are gradually cleaned up.
  • Community activities: Posts/comments/attached photos, creation/modification time, report details, and administrator's reason for processing/processing time. Nickname and administrator status are displayed in posts and comments. Attached photos are resized and re-encoded on the server.
  • Referred by: We store each member's referral code, their selected referrer at signup and the time signup was completed. Members can view their own code, referrer and referral signup count. Administrators can view referral relationships, rankings and member details. This information is retained while the account is in operation.
  • Community profile and points: We store nickname change history, records of points earned, spent, or reclaimed, owned items, and equipped profile images, borders, and titles. Equipped cosmetics appear on posts, comments, and public profiles. Your point balance and inventory are visible only to you.
  • Owner IP security: When IP restrictions are enabled, successful super-administrator authentication or access through an existing session from outside the designated IP and registered browsers results in storage of the IP address and blocking time, and permanent blocking of community use. The super administrator can view and lift blocks from the designated IP; we retain the time and reason for lifting each block. Device authorization is verified through a secure browser cookie. The server stores the cookie token's hash, the registered device name, and registration, expiration, and revocation times. Device authorization is valid for up to 1 year and is revoked if the super administrator revokes it or changes or resets the password.

3. Purpose of processing

  • Providing Riot ID match-history searches, rank, match and meta analysis, and selected comparison features
  • Provide search autocomplete that finds recently verified public Riot IDs from part of a game name
  • Provide a performance summary and detailed supporting evidence using observations of same-role opponents from the same matches in the current season
  • Providing current-game, Replay, and local Companion integration features
  • Improving statistical quality using pseudonymized match and rank observations
  • Automatically track rank changes for searched accounts and show their highest observed tier and LP since tracking began
  • Error response, compliance with call limits, service security and prevention of unauthorized use
  • Receiving and responding to inquiries
  • Understand service usage through pageviews, visitors, unique connection IPs and traffic sources grouped by period
  • Community member login, posting of posts, comments, and photos, processing of reports, management of administrator rights and prevention of spamming

4. Identifier protection and storage method

The original PUUID returned by the Riot API is used for server-side Riot API requests and pseudonymization. The browser does not receive the original PUUID. Instead, it uses an encrypted playerRef restricted by region, purpose, and expiration time. To restore saved results for previously checked accounts without making external requests, account linkage information is stored as authenticated ciphertext in server-only storage. Search keys are transformed using HMAC; original PUUIDs and playerRefs are not stored in plaintext. The pseudonymized statistics store uses secret-key HMAC identifiers instead of original Riot IDs or PUUIDs. The public profile search directory for autocomplete is separate from this statistics store and holds public Riot IDs and the minimum profile information listed above. To prevent duplicate counting, separate observation records associate public Riot ID search keys with match IDs. This directory and these observation records do not store PUUIDs, playerRefs, relationKeys, or raw Riot API responses. For fully analyzed matches, all ten players' scores, 12-axis metrics, team rankings, MVP/ACE results, and normalized rune, spell, item, and skill builds may be stored in match-level analysis snapshots and per-player match indexes linked to the model version, match ID, and participants' HMAC identifiers, so the same match does not need to be recalculated. These snapshots and indexes do not store original PUUIDs, Riot IDs, playerRefs, relationKeys, or raw Riot API responses. Event times and participation context for match moments are stored using the same pseudonymization method; replay videos are not stored. To reduce duplicate requests and fill in only missing analyses, original public match details and timelines received from Riot are compressed and encrypted in a separate server-only archive. These originals may contain Riot game identifiers; they are neither sent unchanged to the browser nor stored in plaintext statistics tables. To calibrate AI-estimated ranks, a pseudonymized player's analysis metrics at a given time are linked to subsequent changes in their actual official rank. Predictions themselves are not used as training ground truth. A display cache for quickly restoring the recent match history shown on screen is stored separately from analysis snapshots. It uses HMAC identifiers instead of original PUUIDs and stores only permitted public match fields with integrity verification values.

5. Retention periods and deletion

  • Encrypted playerRefs are valid for a default of 5 minutes, with a maximum reference lifetime of no more than 10 minutes.
  • Recent searches, favorites and on-device autocomplete index remain in the user's browser. You can remove it by deleting PORO's site data or local storage in your browser settings.
  • The server's public profile search directory is retained for the duration of the service so profiles can be searched again. Profile icons and levels are hidden from autocomplete responses after 30 days, and Ranked Solo/Duo information after 24 hours. To request removal of your Riot ID, use the contact details below.
  • Display information for verified matches is retained for the duration of the service to support repeat lookups and restore analysis results. Account links and the most recently verified profile, rank, win/loss record, and analysis summary are also retained for the duration of the service. Stored values retain the time they were verified; a lookup alone does not mark them as current. They are updated when a match-history refresh retrieves new information. You may also request deletion of account links through the contact details below. When a Riot ID deletion is requested, every displayed match containing that user is removed as a whole so their name does not remain in other participants' caches.
  • Inquiry records are retained for as long as needed to respond and handle disputes, then deleted.
  • Pseudonymized traffic statistics are retained for the service's operating lifetime to support year-to-year comparisons. Browser visitor identifiers remain valid for up to 365 days after creation, and session identifiers remain unchanged until 30 minutes after the last page navigation. Clearing or blocking browser storage may affect visitor counts.
  • Pseudonymized match and rank observations, match analysis snapshots and aggregate statistics, encrypted raw match data, and training and validation records for AI tier calibration may be retained for the duration of the service to prevent recalculation and maintain consistent results and statistical integrity.
  • If there is a separate preservation obligation under the law, it may be stored separately for the relevant period.
  • Community accounts and posts are retained for the duration of the service. Deleting posts or comments stops their public display, and photos attached to deleted posts can no longer be accessed through public URLs. Deleted content and administrative records are retained with access restricted to administrators for reviewing reports and restoring content. Permanent deletion of accounts or materials can be requested using the contact details below.
  • Community login sessions remain valid for up to 7 days. Sessions are revoked on logout, password changes, or account restrictions. Identifiers used to limit login and sign-up attempts are hashed, and records are progressively removed after the restriction period expires.

6. External services and data processing

During the service provision process, requests may be forwarded to or information may be processed by the following external services.

  • Riot Games API and Data Dragon: Account and match lookups, and static game data
  • OP.GG public search: When you submit a nickname search, the server sends the entered game name and region to OP.GG to find matching accounts. Browser cookies, member information, and Riot API keys are not sent. Candidate results are held in server memory for up to 5 minutes. The selected account's match history is retrieved through the Riot Games API.
  • Cloudflare: Website provision, security, request processing, operation of D1 database and R2 attached photo storage.

Each provider's terms and privacy policies may also apply to its processing. We will update this policy before adding new external services, such as analytics or advertising.

7. Cookies and local storage

PORO currently does not use cookies for personalized advertising or third-party behavioral tracking. Its own traffic statistics store the random identifiers and traffic source information described above in browser local storage. This information is not sent to an external analytics service and can be removed by clearing site data. Community login uses an essential session cookie valid for up to 7 days. Page scripts cannot read this cookie, and the server stores a hash instead of the original session value. Browser local storage also provides recent searches, favorites and search suggestions. You can clear PORO site data or block local storage in browser settings.

8. User request

Users may request access to, correction or deletion of, or an explanation of the processing of information they provided in inquiries. Corrections to game records follow Riot Games' procedures as the original data provider. Reasonable additional verification may be required to identify the information covered by a request.

9. Ensuring safety

The PORO team stores API keys and encryption secrets on the server rather than in client code, and applies transport security, purpose-limited tokens, rate limits, input validation, and identifier pseudonymization.

10. Contact and policy changes

Operator
PORO Operation Team
Contact
kartellgroupbusiness@gmail.com

Changes to this policy will be announced on the website before they take effect. Material changes to users' rights will be announced separately with reasonable advance notice.

© 2026 poro.LOLkartellgroupbusiness@gmail.com