PRIVACY & SUPPORT

REP privacy notice

Updated October 8, 2026

This notice covers the REP Chrome extension, its reputation service at api.rep-gg.com, and the REP website. REP operates this service independently of FACEIT and Valve. Contact REP at faceitreputationtrackingREP@gmail.com for privacy requests or support.

Current launch beta: REP focuses on player profiles, teammate feedback, PUG connections, Community and contributions. Discover is a coming-soon preview; background performance collection and rankings are paused. Team Hub and Find a team have been removed from the current extension. Earlier team data is still covered by this notice.

What REP uses and why

FACEIT identity and public game information. Signing in supplies your FACEIT player ID and nickname. REP requests the openid and profile permissions, verifies the identity returned by FACEIT, and creates a REP session. Player photos, country, ELO, level, linked Steam identifiers and match history support profiles, lobby displays and teammate eligibility checks.
FACEIT page context. On FACEIT pages, the extension reads relevant match/player links, roster information and visible queued-group indicators to place REP information beside the correct players. It can remember up to 100 completed-match group snapshots locally for the 90-day match window. It does not collect general browsing history, passwords, FACEIT cookies or private messages.
Feedback. REP stores the reviewer and target player IDs, reviewer nickname, match ID, selected tags, optional review text, chosen rating, available map information, and submission/expiry times. These power reputation displays and community rankings. Reporting a review stores your player ID, report reason and time so REP can investigate.
Community features. REP stores your LFT mode and any listing you publish. Private Play again saves store your selected players, optional notes and shared-match context. Explicit teammate requests store the two players, their profiles, a verified shared match, request status and times. Optional Ready to queue status is stored until it expires.
Looking to PUG and notifications. If you make yourself available, REP stores your public FACEIT profile snapshot, ELO and availability expiry. Signed-in players can find available players from recent matches or within 400 ELO. Accepted REP friends appear across ELO levels; REP does not import your FACEIT friends list. Play invitations store the two players, public profile snapshots, response status and timestamps. PUG blocks store the two player IDs. Feedback notifications store a reference to the feedback and your read state. An authenticated live connection updates the REP bell and invitations. Optional Chrome desktop alerts cover incoming PUG invitations and accepted invitations; your alert preference and short-lived delivery markers are stored locally to avoid duplicate alerts.
Profile views and account totals. While signed in, opening another player’s REP profile records your player ID, the viewed player ID and date/time. Rankings count at most one view per viewer, player and UTC day. REP also keeps one player ID per account that has joined, to show the community account total.
Discover preview and earlier performance data. The launch beta shows a static coming-soon preview. REP has paused Discover’s background collection and performance ranking calculations. Earlier betas analyzed a limited sample of recent public FACEIT CS2 matches from REP accounts and nonmembers, including match outcomes, rounds, utility, multi-kills, clutches, opening duels and headshots, with public player profile snapshots. Existing records follow the retention and removal rules below. Opening the preview does not collect new match statistics. Normal profile history and teammate verification still use FACEIT. Contributor rankings use REP’s published feedback; they are separate from performance rankings.
Technical information. REP processes network addresses temporarily for rate limiting and records aggregate request status, timing and server health. REP’s application logs avoid review text, private notes, session tokens and player IDs. Hosting providers may separately process request and security logs.

Public text screening

New and edited written player feedback is screened before publishing. REP resumed automatic player-feedback screening on October 4, 2026. Text that passes can publish automatically; flagged text or checks that cannot complete wait for REP staff. Indicator-only feedback with no written text does not require a screening request. Verified teammate-match checks, feedback frequency limits, locked ratings/indicators, reporting and staff removal still apply.

REP sends submitted player-review text, Community captions, statuses, comments and replies, and public LFT listing text to OpenAI’s Moderation API. Older-client recruitment listings also retain that process. Listing text includes the public contact or availability details you entered. REP does not attach your account ID, nickname, ELO, selected review rating or indicators, authentication token, private notes, team-only documents, private applications or the video itself. Any identifying information you type into the submitted text is still part of that text.

Flagged text, incomplete checks and service outages leave the submission pending for REP staff. If automatic screening is not configured, submissions subject to screening wait for staff. Pending and rejected submissions are visible only to their author and REP staff. A captain can see their own pending recruitment listing. Editing published text removes that version from public display until the new check passes or staff approve it. Pending reviews do not affect public reputation counts, contributor rankings or feedback notifications. Screening does not change your chosen rating, indicators or original review expiry. Existing content, including feedback published during the earlier screening pause, is not automatically sent for a retroactive check.

Screening looks for potentially harmful content; it does not verify that a review is true, prohibit ordinary negative feedback or guarantee that every violation is caught. Staff consider game context and can approve false positives. You can edit rejected text for another check or contact REP to question a decision. REP stores the screening outcome, version and staff decision alongside the submission until its usual deletion or expiry; staff activity logs last up to 90 days. No additional copy of the submitted text is kept for screening.

OpenAI’s current API data controls list the Moderation endpoint as not using content for training and having no abuse-monitoring or application-state retention. These endpoint-specific controls differ from the disabled import described under earlier team features below. REP sends screening requests from its server and never puts its API key in the extension.

Community posts and videos

Community lets signed-in players submit captions, statuses and YouTube video links. REP stores your FACEIT player ID, public nickname, avatar, ELO and level snapshot, post text, video identifier, timestamps, version and moderation status. Approved posts are public in one newest-first feed and in the latest-posts area of your profile. Editing a published post returns it to review without moving it to the top.

In this beta, videos require REP staff review even when their captions pass automatic text screening. Text screening does not check the video, audio or thumbnail. Community text follows the public text screening process above.

REP does not load the YouTube player until you choose Play. Playback uses YouTube’s privacy-enhanced embed on youtube-nocookie.com, which still sends requests to Google/YouTube and may process your IP address, device information and viewing activity. Opening a submitted video on YouTube also uses that provider’s services and policies. REP stores links, not uploaded video files.

X/Twitter links in version 0.3.61 and later. REP stores the linked post’s numeric identifier alongside your caption and moderation record. Every X submission requires staff review, even when its REP caption passes automatic screening. REP does not automatically screen the linked text, images, quoted content, video or audio, and linked content may later change or become unavailable. Edits in REP return the submission to review; report a linked post if its content changes or violates the guidelines.

Choosing Show X post loads X’s official embedded post in a separate viewer. X may receive your IP address, browser and device information, cookies and the viewer URL. REP requests the embed’s do-not-track setting, which does not eliminate those requests. No REP sign-in token or private notes are passed to the embed. Open on X takes you to X directly. X’s privacy and cookie policies apply when you load or open that content. REP does not download or store the linked media files.

Use My posts to inspect decisions, edit an eligible post or delete it. Published posts remain until deleted or moderated, with up to 1,000 stored posts per account. Pending, rejected and hidden posts are removed after 30 days without an update. Deleting your REP data removes your posts, reports and Community hiding preferences. Minimal player-ID and timestamp records enforce a rolling three-post limit for 24 hours, including after deletion. Staff posting restrictions retain a player ID and expiry for up to 30 days, including after deletion.

Comments and replies store their parent post or comment reference and the same author, text and moderation information. Approved comments are visible in their thread; your own pending or rejected comments remain visible to you. Comment limits are 30 submissions per rolling 24 hours and up to 4,000 stored comments per account. Comments use the same 30-day cleanup for unpublished content. Deleting a post removes its comments and Likes; deleting one comment can leave replies without the deleted comment’s text. Likes store the reacting player ID and post or comment ID to enforce one Like per account; public responses show a count and your own Like state, not a list of people who reacted. You can remove your Like. Account deletion removes your comments and Likes. Reactions do not change the chronological feed order.

Report sends the post ID, your player ID, reason and timestamp to REP staff. Reports are private, retained for up to 90 days, and removed sooner with the post or reporter’s account. Hide this player changes only your Community feed and profile previews; it does not block other REP features or make public posts private. Hiding preferences last until removed or either account is deleted. Staff decisions are recorded in the existing 90-day activity log. You can question a decision using the support email above.

Only share CS2 content you own or have permission to share. Sexual or graphic content, hate, threats, harassment, scams, private personal information, spam and gambling promotions are not permitted. Staff can remove content or temporarily restrict posting.

Following players

Following stores your player ID, the followed player’s ID, your public nickname/avatar snapshot and the time. Everyone can see follower counts. Only the person being followed can see their incoming follower list; REP does not expose other people’s follower lists or anyone’s outgoing following list. REP uses your own relationship state to show Follow or Following. You can unfollow; deleting your REP account removes incoming and outgoing follow relationships.

What other people can see

Reviews, tags, reviewer nicknames, linked matches, public profile information, LFT status/listings and aggregate rankings are visible to other REP users, including through the FACEIT overlay. REP does not publish the identities of profile viewers. Private saves and notes are available to their owner; they do not notify the saved player. An explicit teammate request is visible to its recipient. Accepted teammates can see each other’s optional Ready to queue status. REP’s operator can access stored information when needed for support, moderation, recovery or security.

Storage and retention

Discover performance records are filtered out seven days after the match finishes and removed during periodic cleanup. Automatic refresh is paused. Existing REP-member profile snapshots remain until replaced or account deletion; existing nonmember snapshots follow the expiry rule below. Nonmember snapshots are removed after seven days without a newly observed recent match (or seven days after initial discovery if none is found). Deleting your REP data removes your Discover records and snapshots and stops automatic collection. Nonmembers can also request removal and exclusion by emailing the privacy contact above; we may verify FACEIT account ownership. A one-way hash of the player ID is retained to honor the exclusion, including after rejoining REP, unless you ask to reverse it. Raw FACEIT match-statistics responses are processed temporarily, not saved in the database.
Reviews and tags expire 90 days after their original submission; edits do not restart that period. Associated reports are removed when the review is deleted. Profile-view records expire after 90 days.
LFT listings expire after 30 days unless updated. ESEA-team LFT mode stays on until disabled or your REP data is deleted. New PUG availability sessions and their PUG badge expire after one hour, unless you turn them off sooner or renew them.
PUG availability is visible to other signed-in REP users while enabled. A play invitation and its response are visible only to the two participants, expire after 10 minutes, and are then periodically removed. Minimal player-ID and timestamp records enforce hourly invitation limits for up to one hour. Blocks remain until the blocking player removes them or deletes their REP data; another player’s block against you remains to prevent re-registration from bypassing it. Feedback notification records expire or are deleted with the linked feedback. Hidden feedback is excluded. Desktop delivery markers expire with a PUG invitation and are cleaned when the extension next processes alerts. Legacy scrim bell records expire or are deleted with their linked request; the current extension no longer subscribes to scrim alerts. Signing out or deleting your REP data removes local delivery markers.
Private saves and accepted teammate connections remain until removed or the relevant account data is deleted. Requests expire after seven days; related request/cooldown records can remain for up to 30 days. Ready to queue expires after one hour.
REP sessions last up to seven days. The extension keeps the session token in Chrome’s local extension storage; the server stores a hash. Signing out invalidates that session. Temporary sign-in transactions last up to ten minutes and one-use handoff codes up to one minute. FACEIT access and identity tokens are processed for sign-in, not stored as long-term REP credentials.
The community-account record remains until you delete your REP data. Minimal records containing player IDs and timestamps can remain for up to 90 days for review limits or 30 days for teammate request limits, even after deletion, to prevent resetting those limits.
Expired records are filtered from results and cleaned periodically while the service runs. Local match snapshots are discarded when expired cache entries are next processed. Uninstalling the extension removes its local storage.
Restricted recovery backups can retain information after deletion. Railway Pro captures the full service volume, including authentication data, on daily, weekly and monthly schedules, with configured retention of six, 27 and 89 days respectively. Manual snapshots and older downloaded recovery copies may remain until removed. Additional application snapshots rotate on a seven-day schedule and exclude sign-in sessions and temporary authentication data. The former scheduled download to the owner’s computer is paused. Before restored data is made available, subsequent deletion requests must be reapplied and restored authentication state cleared. Backups are restricted recovery copies, not public records.

Providers and transfers

The REP API and database are hosted by Railway in the United States. FACEIT supplies authentication and public player/match information. Profile images may load directly from their source hosting providers, which receive the network request. The informational website uses OpenAI Sites hosting. Discord and email are optional support/community channels operated by their respective providers; information you send there is also subject to their policies. Information may be processed in the United States and other countries where these providers operate.

REP does not sell personal information, use it for targeted advertising, or add advertising/analytics trackers to the website. Data is used for the REP features described here, support, moderation, security and service operation. It may also be disclosed when legally required. REP does not use private notes or support messages to train AI models.

Your controls

You can remove feedback you wrote, turn off LFT, remove listings and private saves, decline/cancel requests, remove teammates, and turn off Ready to queue. In REP, open your connected account and choose Delete my REP data to remove your authored feedback, reports, LFT settings/listings, private saves, your view records, teammate connections/requests, community-account entry and all REP sessions.

In Looking to PUG, choose Stop looking to leave discovery, accept or decline invitations, or block and unblock players. Blocking hides you from each other’s PUG discovery lists and prevents new invitations in either direction. The notification bell lets you read feedback updates and mark them as read. Enable desktop alerts only if you want notifications for incoming PUG invitations and accepted invitations. You can turn it off in REP or revoke Chrome’s notification permission. Alerts require Chrome to be running and may be hidden or silenced by your operating system. Account deletion also removes your PUG availability, invitations, outgoing blocks and incoming notification state. Hourly anti-spam records and other people’s blocks are retained as described above. Private Play again saves still do not notify anyone.

That action does not delete your FACEIT account, other people’s feedback about you or their own private saves. Feedback about you remains subject to the 90-day expiry and reporting/moderation process. To request access, correction, deletion or help with a privacy concern, email REP. We may need to verify your FACEIT account ownership before handling an account request. Do not send passwords, API keys or session tokens.

Earlier team-tool betas

Team Hub, Find a team, recruitment, shared scheduling and scrim tools are no longer in the current extension. Their stored records were not automatically deleted when the navigation was removed, and compatible older clients may still access the protected services. The details below describe those earlier features and their continuing retention/access rules, not features included in the current beta. For help removing earlier team data without those screens, contact REP; account deletion still applies as described below.

Earlier team data, access and deletion details

Data and access

Team hub. REP retrieves your FACEIT teams, rosters and reported ESEA membership information. It remembers the team you select and stores any weekly availability, time zone, playing role and team note you choose to share, with update and expiry times. These help your team find common practice windows.
Team sessions. Captains can schedule practices and prepare accepted scrims with a title, dates, invited lineup, maps, attached play references and optional connection instructions. Players submit their own attendance, version-specific play review status and debrief notes. REP stores these responses with player IDs, names where shown, timestamps and versions. These details are visible only to current members of that team’s FACEIT roster, which is checked on each request. An accepted scrim creates separate private preparation sessions for each team; opponents cannot see the other team’s assignments, attendance or connection instructions. Acceptance of a scrim does not confirm individual attendance.
Team playbooks. Current FACEIT roster members can share strategies containing a title, map, side, play type, plan and instructions for up to five player slots. A shared lineup links these slots to current roster player IDs and optional role labels; only the current captain can change it. Members can save a map-specific utility library of names and HTTPS links, then attach those links to player assignments. REP stores the team ID, creator and last editor IDs/nicknames for plays, version numbers and play timestamps. Only current roster members can read and edit plays and utility links; the creator or current captain can delete a play. Access is checked against the current FACEIT roster on each request. Playbooks are not published in team directories or player profiles.
Team directory and scrims. A current FACEIT captain can publish a CS2 team listing with its public FACEIT identity, region, self-reported division, maps, description and dated scrim windows. These appear to signed-in REP users. An optional contact is shared with the current roster of an accepted opponent, not in the directory. Scrim proposals store the two teams, captain IDs, team name/photo snapshots, dates, chosen map, optional message, status and timestamps. Proposals and bookings are visible only to current roster members of the two teams.
Team recruitment. Current FACEIT CS2 captains can publish openings with team identity, region, roles, self-reported division, preferred ELO, language, schedule and description. These are visible to signed-in REP users. Applying requires ESEA LFT mode, which displays a public LFT badge. Applications store the applicant and receiving captain IDs, team and player profile snapshots, role, message, status and timestamps. An application is visible to its applicant and original receiving captain while that captain still leads the FACEIT roster. Captain notes are visible only to that captain. Bell notifications store application references, recipients, event times and read state; they omit messages and notes. Applicants are notified of shortlisting, decline or closure, and captains of applications or withdrawals.

Retention

Shared playbook entries, lineup settings and utility links remain until removed or replaced. Deleting your REP account removes plays you created and clears your player ID from saved playbook lineups. Your edits to plays created by others remain, but your last-editor ID and nickname are cleared where present. Shared role labels and utility links are not attributed to an individual author and remain with the team. Teams can store up to 100 plays and 100 utility links; each account can create up to 200 plays across teams.
Practice sessions and their attendance, play review statuses and debriefs are removed 90 days after the session ends. Sessions linked to scrims are removed with the booking, normally 30 days after its end or sooner if that booking is deleted. Team activity entries are retained for 30 days. Minimal session invitation, change, cancellation and availability-reminder notices appear in the notification bell and expire after 30 days; they do not contain private instructions or debrief text. Availability-reminder limits retain the team ID and send time for 24 hours.
Team availability, time zone, role and team note are visible only to signed-in players currently listed on that team’s FACEIT roster. REP checks roster membership when the team hub is requested. These shared details expire 30 days after you last save them; you can clear them sooner. Your selected team remains until you change it or delete your REP data.
Directory listings and their optional contacts expire 30 days after saving. Removing a listing cancels pending proposals but keeps confirmed scrims scheduled. Unanswered proposals expire when their start time arrives or after seven days, whichever is earlier. Proposal and booking records are removed 30 days after their scheduled end. Minimal player/team IDs and send times enforce scrim invitation limits for one hour, including after account deletion.
Recruitment listings expire 30 days after publication or renewal. Applications, messages, captain notes and associated bell notifications expire 30 days after submission; edits and status changes do not renew them. Withdrawal leaves a closed record until expiry. Closing or expiring a listing closes active applications. Daily application limits use minimal player/team IDs and timestamps retained for up to 24 hours, including after account deletion.

Controls in earlier clients and account deletion

In Team hub, choose Clear my availability to remove your saved schedule, time zone, role and team note for that team. Deleting your REP data removes these details for all teams, along with your selected team.

In Team hub → Schedule, captains can edit or cancel practices; linked scrims are cancelled through Scrims so both teams are informed. Invited players control their own attendance and debrief, and can clear a debrief by saving it empty. Deleting your REP data removes your attendance, review statuses, debriefs, team notices and lineup membership, and clears your attribution from shared sessions and activity entries. Shared practices remain for the team until expiry. If your account deletion removes a scrim booking, its linked preparation sessions are also removed. A captain can remind teammates who have not shared availability at most once per team every 24 hours.

In Team hub → Playbook, roster members can add and edit shared strategies and utility links. The creator or current captain can delete a play for the whole team. Remove a utility link from its player assignments before deleting it from the library. The current captain can change or clear player slots and role labels, and use optional document import when enabled. If you leave a roster, you lose playbook access; deleting your REP data still removes plays you created across teams. Utility links open their original third-party website only when clicked, subject to that site's policies; REP does not fetch or embed their contents. Do not include passwords or other sensitive personal information in shared plans, role labels or links.

Captains can edit or remove their directory listings and accept, decline or cancel scrim proposals; either captain can cancel a confirmed scrim. Deleting a captain’s REP data removes their listings and associated proposals/bookings, freeing reserved times. Directory publication does not publish individual players’ private availability, roles or team notes.

In Find a team → My applications, you can inspect your applications or withdraw an active one. In Team hub → Recruitment, captains can edit or close listings, shortlist or decline applicants and edit private notes. Deleting your REP data removes your recruitment listings and applications where you are the applicant or receiving captain, including messages, notes and linked notifications. Daily limit records remain as described above.

Disabled playbook import

AI import is currently disabled. It is not available in the current extension.

When AI import is enabled, a current team captain can paste text or choose a .docx or .txt document. The extension reads files on your device; it does not upload the original file, images or comments. You can inspect and edit the extracted text before expressly choosing to send it to REP and OpenAI. OpenAI receives that text and the optional map context to identify draft plays and player instructions. Only import content you have permission to share. Do not include passwords or unnecessary personal information.

REP uses OpenAI’s API with response storage disabled. API content is not used to train OpenAI models by default, but OpenAI may retain abuse-monitoring logs containing inputs and outputs for up to 30 days, subject to its API data controls. This processing is separate from the informational website’s hosting.

REP does not save the source document or unfinished drafts in its database. Import processing and drafts use temporary server memory for up to ten minutes, and are discarded sooner when cancelled or retrieved and reviewed in the extension. Closing the extension ends local access to unsaved drafts; a server restart may also discard them. Captains review and explicitly save selected drafts before those plays become visible to current roster members. Saved plays and utility links follow the shared playbook retention rules below. Daily usage counters use a hash of the account ID and are retained through the current UTC day to enforce limits, including after account deletion. A hash, team ID, saved play IDs and request fingerprint are retained for up to 24 hours to prevent duplicate saves.

Feedback and support

Use Report on a review, or email REP with the player/match link and the issue. Reviews are community opinions, not verified findings. Spam, fabricated feedback, harassment, threats and disclosure of private personal information can be removed. Reporters’ identities and report reasons are not published. You can contact the same email to question a moderation decision.

This website and changes

The website is informational and does not itself accept sign-ins or reviews. REP adds no analytics scripts, advertising scripts or tracking cookies to it. This notice will be updated when data practices change, with a new effective date. Material changes will also be communicated in REP or through its release information.