01Who we are

Prefire ("we", "us") is an independent, individually operated project for Counter-Strike 2 players. Prefire is not affiliated with, endorsed by, or sponsored by FACEIT or Valve Corporation. For anything in this policy, the data controller is the individual operator of Prefire, reachable at prefirecsdev@gmail.com.

02What this policy covers

• The Prefire browser extension (Chrome, Manifest V3), which runs only on faceit.com pages.
• The Prefire API — our scouting backend, including the Tactical Replay viewer pages it serves.
• The Prefire telemetry service — a separate, minimal analytics endpoint (see section 06).

This page itself stores exactly one thing in your browser: your EN/RU language choice, in localStorage. No cookies, no analytics scripts, no external fonts or trackers.

03The scouting flow — what data moves where

3.1 When you open a match room

On a FACEIT match-room or player page, the extension reads from the page and sends to the Prefire API over HTTPS:

• Public player identifiers — the FACEIT player IDs and nicknames of the players in the room you are viewing (data already publicly visible on FACEIT).
• Match context — the match/room identifier and the map, so the right report comes back.

Like any web server, ours sees standard connection metadata (your IP address, a user-agent header). We use it only for rate limiting and abuse prevention; it is not joined to scouting data, and technical logs are kept for at most 30 days.

3.2 The scouting database (server side)

Our server continuously builds scouting profiles from two public sources: the official FACEIT Data API (public rankings, player profiles, match history) and publicly available demo recordings of finished FACEIT CS2 matches. From these we store:

• Player registry — FACEIT player ID, nickname, country code, skill level / ELO.
• Match metadata — match ID, map, date, participating players.
• Derived gameplay features per player per match — positions, timings, opening duels, utility usage.
• Movement tracks per player per round — radar coordinates over time, grenade throws, key round events — for at most the last 30 matches per map (older ones are evicted automatically). The Steam ID that appears in the demo is stored alongside.
• Aggregated map profiles — per player per map, recomputed on a rolling window of the last 5 matches: aggression, positioning tendencies, heatmaps.

Raw demo files are deleted immediately after parsing; we keep only the derived data listed above. A scouting profile shows what any opponent could learn by watching the same public demos — automated and faster.

3.3 Resolving nicknames and rooms

When the extension needs to turn a nickname into a public FACEIT player ID, or read the public details of a match room, it asks the Prefire API, and our server queries the official FACEIT Data API using Prefire's own server credentials. You never create, paste or store any API keys, and no FACEIT credentials of yours are involved — only the public identifiers described in 3.1 travel from your browser.

3.4 Local settings

Your preferences (toggles, overlay dock side) live in your browser's local extension storage and never leave your device.

04What we do not do

• No accounts, names, emails, passwords, or FACEIT/Steam login credentials are collected.
• No browsing history, and no activity outside faceit.com pages — the extension has no permission to run anywhere else.
• No real-time or in-game data; Prefire works only with public, finished matches.
• No advertising identifiers, no cross-site tracking, no data brokers, and we never sell personal data.

Prefire's use of information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

05Purposes and legal bases (GDPR)

Processing	Purpose	Legal basis
Handling your scouting request	Fetch and display the report for the lobby you're viewing	Art. 6(1)(b) GDPR — performing the service you request
Building the scouting database from public match data	Pre-match analytics for the competitive CS2 community	Art. 6(1)(f) GDPR — legitimate interests (see balancing note below)
Telemetry & error reports	Understand feature usage, count active users, fix crashes	Art. 6(1)(f) GDPR — legitimate interests (anonymous, stops with the extension's master switch or uninstall)
Rate limiting, security logs	Keep the service up and abuse-free	Art. 6(1)(f) GDPR — legitimate interests

Balancing note. The scouting database processes data that players have already made public through ranked competitive play on FACEIT: public rankings, public match records, public demo files. It concerns in-game conduct only — never private life, never special categories of data. It involves no decisions with legal or similarly significant effects. And the interest is mutual: every profiled player can equally scout their own opponents. Against that we weigh the player's interest in control over their data — which is why the right to object is honoured unconditionally (section 08): one email removes the profile and permanently prevents a new one.

06Telemetry — anonymous

Builds without a telemetry endpoint configured send nothing at all. When telemetry is active, the extension sends to the Prefire telemetry service over HTTPS:

• a random install ID (a UUID generated on install) and a random session ID — not linked to your FACEIT account, Steam account, name, email, or IP-based identity;
• coarse feature events from a fixed allowlist (e.g. "room overlay shown", "replay panel opened", "settings changed") with the extension version;
• a periodic heartbeat so we can show how many users are online;
• the server derives a coarse browser/OS family (e.g. "chrome/windows") from the request and stores that — never the full user-agent string. Your IP is used transiently for rate limiting and is not stored with events.

Two sub-processors may receive parts of this stream when enabled: PostHog (product analytics; receives the events and the random install ID) and Sentry (crash reports: error stack plus extension/browser context). Sentry reports are relayed through our own server, so your IP address is never exposed to Sentry.

Telemetry stops together with the extension. The master switch in the Prefire settings turns the whole extension off — events, heartbeats and error reports included — and uninstalling the extension removes everything. No telemetry data is required for any scouting feature to work.

07Recipients, hosting, transfers

• Hosting providers run the servers for the Prefire API, its database, and the telemetry service.
• FACEIT receives requests when our servers fetch public data (including lookups made on behalf of your scouting request). FACEIT's own privacy policy governs their side.
• PostHog and Sentry (Functional Software, Inc.) act as processors for telemetry only, as described in section 06.

Where a recipient is located outside your jurisdiction (for example, US-based analytics processors), transfers rely on appropriate safeguards such as the EU standard contractual clauses or the EU–US Data Privacy Framework, as applicable. We share nothing with advertisers or data brokers.

08Retention — concrete numbers

Data	Kept for
Raw demo files (.dem)	Deleted immediately after parsing
Per-round movement tracks, grenades, events	Rolling window: last 30 matches per player per map; older evicted automatically
Aggregated map profiles	Assembled on demand from your stored match features (rolling last-5-matches window); not stored separately, so they disappear as soon as those features are removed
Player registry (ID, nickname, ELO) and match metadata	While the player appears in supported queues; reviewed periodically
Telemetry events	At most 12 months
Presence ("last seen") rows	One overwritten row per install; purged after 90 days of inactivity
Server technical logs (IP, user agent)	At most 30 days
Extension settings	On your device only, until you clear them or uninstall
Opt-out suppression list	Player ID only, kept indefinitely — that is what keeps the opt-out working

09Profile takedown & opt-out — for any player

• How: email prefirecsdev@gmail.com with your FACEIT profile URL or nickname. So we don't delete someone's profile at a stranger's request, we'll ask for a proportionate proof of control — e.g. a short message sent from the FACEIT account or a temporary line added to the profile.
• What happens: we delete your movement tracks and derived features — everything an aggregated profile is built from — and add your player ID to a suppression list so a new profile is never rebuilt — the pipeline skips suppressed players at ingestion, and the API will not serve them.
• When: within 30 days at the latest, with a confirmation reply. In practice much sooner.
• What may remain: basic public facts (nickname, rating, match participation) can re-enter our match registry as part of public ranking data — the same facts FACEIT publishes — but they are never again used to build a behavioural profile.

If you use the extension: uninstalling it stops all processing on your side and removes all local data.

10Your rights

Under the GDPR (and equivalent laws elsewhere) you can request access to your data, rectification, erasure, restriction of processing, data portability, and you can object to processing based on legitimate interests — section 09 is exactly that objection, honoured without weighing excuses. Write to prefirecsdev@gmail.com for any of these. You also have the right to lodge a complaint with your local supervisory authority.

11Children

Prefire is not directed at children under 16 and we do not knowingly process their data beyond what appears in public match records. If you believe a child's data should be removed, contact us and we will treat it as a priority takedown.

12Changes to this policy

We update the version and date at the top of this page. For material changes we also note it in the extension's store listing and release notes. Continued use after an update means you accept the revised policy.

13Contact

Anything about privacy — questions, requests, complaints: prefirecsdev@gmail.com.