Atlas for FACEITBrowser extension for CS2 players

Atlas for FACEIT — Privacy Policy

Last updated: 2026-09-29

Atlas for FACEIT ("Atlas") is an independent browser extension that adds optional context, notes and shortcuts around your FACEIT matches. It is not affiliated with, endorsed by or sponsored by FACEIT. This policy explains how the current version handles data. Peak ELO is requested automatically from FACEIT's available CS2 season records when the metric is selected. Public FaceitAnalyser profiles you deliberately visit can also provide locally imported records. On Steam Community profiles you open, Atlas can show the FACEIT account linked to that Steam profile.

What is stored, and where

• Settings (theme, modules enabled/disabled, appearance, hotkeys, automation toggles) are stored on your device, in chrome.storage.local. Atlas never writes to Chrome Sync, so your settings are not replicated to your Google account. Older versions of Atlas did store settings in Chrome Sync; if your browser still holds such an entry, Atlas reads it once to carry your settings over and then deletes it.
• Player notes and tags you write about players are stored locally, up to 500 players and 2,000 characters per note.
• Page notes are a separate local store, keyed by the address of the FACEIT page you wrote them on, up to 200 notes and 4,000 characters each.
• "Have We Met" encounter history (a local record of players you've shared a match with) is stored locally, capped at 120 matches and 4 recent encounters per player.
• Local cache of match/player data fetched from FACEIT is stored locally with an expiry, purely to avoid repeated network requests and to work briefly offline. Cached data is never reused after 24 hours, and the cache is capped at 96 entries of up to 64 KB each.
• Optional peak ELO cache is separate: up to 200 public player records, refreshed after six hours when requested. It stores the public player ID, CS2 game, highest available record, source, consultation date, and available match/season counts and coverage indicator. Previously verified records can remain available with their consultation date for up to 30 days if the source is unavailable. A record lower than the player's current ELO is hidden until verified again. This cache is not part of exported backups.
• When you select the peak ELO metric and visit a supported FaceitAnalyser CS2 profile through View profile, Atlas can read the visible Overall → Highest ELO value and match count. It stores only the public player ID, game, record, match count, source and consultation date in that same local cache. Imported records are identified as page imports. An imported value refreshes when you revisit the profile; it is not a live connection to the website.
• FACEIT-on-Steam cache: when you open a Steam Community profile, Atlas keeps the answer to "which FACEIT CS2 account is linked to this Steam profile" locally — the public FACEIT nickname, player ID, country, level, ELO and lifetime K/D, win rate and match count, or simply "no account" — for 6 hours (1 hour for "no account"), up to 200 profiles. It is not part of exported backups.
• Automation diagnostics: if you enable automations, Atlas keeps a local log of up to 40 recent events (which action was attempted, the outcome, a short reason, a timestamp) so it can explain why an automation did or did not run.

None of the above is sent to Atlas's backend, to the extension developer, or to any third party.

From the Options page you can export a JSON backup of your settings, your player notes and tags, and your "Have We Met" history, optionally encrypted with a passphrase you choose. Page notes and the local cache are not included in the backup. You can also import a backup file, which overwrites those same three categories. Two separate buttons clear player notes and tags, or the encounter history, independently — each asks for confirmation first. Page notes are deleted one at a time, by saving an empty note on the page where you wrote it. Uninstalling the extension removes all of this local data.

What is sent over the network, and to whom

To show real FACEIT statistics (player profiles, ELO, match history, bans, etc.), Atlas queries a Cloudflare Worker operated by the developer at faceit-atlas-api.diogosilvasoares21.workers.dev, which in turn queries the official FACEIT API. Besides FACEIT's own website (next bullet), that Worker is the only address Atlas ever sends requests to — there is no second server.

• On faceit.com pages, Atlas also asks FACEIT's own website API for the per-match FACEIT Rating that FACEIT shows on its scoreboards and match history — the same numbers you can see on the site — for the players in your match room. These requests go to faceit.com itself, from the page you already have open, with the session that page already has. They carry only player IDs, and their answers stay in your browser: the Atlas Worker and the developer never see them.

• The FACEIT API key is never included in the extension. It lives only on the server side (the Cloudflare Worker), so it is never exposed in your browser, in the extension's code, or in any file you could inspect.
• Requests to the Worker carry only what is needed to answer the query — a player nickname, a player ID or a match ID. No notes, no tags, no page notes, no browsing history, and no identifiers beyond those needed to look up public FACEIT data.
• Those nicknames and player IDs include the other players in your lobby, party or match room, not only your own. That is what showing their public statistics requires. Nothing beyond the identifier is sent, and nothing you wrote is sent.
• If you select Peak ELO · CS2, Atlas requests the public player's season summaries directly from faceit.com/api/statistics/v1/cs2/players/<id>/seasons, through the FACEIT tab you already have open and its existing session. It reads the highest recorded ELO across the returned seasons, independently of the selected recent-match period. Only the player ID is sent to FACEIT; season records stay locally and are not sent to the Atlas Worker or FaceitAnalyser. Requests are queued, cached and paused after access refusals or rate limits. The lookup is off when the metric is not selected, Atlas is off, or the relevant statistics modules are off. The previous experimental FaceitAnalyser API adapter remains unpublished and is not called by this extension flow.
• The FaceitAnalyser page reader runs only on https://faceitanalyser.com/stats/.../cs2 profile pages identified by a FACEIT player ID, with the peak metric selected, the relevant Atlas module enabled and the FaceitAnalyser integration on. It reads visible public statistics after the page has loaded normally, rejects filtered or Last 50 data, and stops after one import or at most one minute. It does not inspect cookies, credentials, private account data or the site's network requests. Imported values go only to the extension's local storage; they are not uploaded to Atlas or the provider. It never opens profiles in the background.
• FACEIT on Steam: when you open a Steam Community profile (steamcommunity.com/profiles/... or steamcommunity.com/id/...), Atlas reads that profile's public Steam ID (SteamID64) from the page address or from the profile data the page itself contains, and asks the Atlas Worker which FACEIT CS2 account is linked to it; the Worker asks the official FACEIT API. Only that Steam ID is sent, and then the FACEIT player ID it returned, to fetch the account's lifetime statistics. Atlas reads nothing else on Steam — not your own Steam account, cookies, friends, inventory or messages — and does nothing on other Steam pages. It runs on the profile you opened, never in the background, and can be switched off in Options (FACEIT on Steam).
• The Worker keeps no database and no account records. It caches FACEIT answers to avoid repeated calls, and writes to its log only when something fails. It does not store a history of who looked up whom. As with any site you visit, the hosting infrastructure (Cloudflare) sees the connection itself.
• Atlas sends a small status check (/health) to the Worker when it is installed and each time your browser starts, to know whether statistics will be available. It carries no identifier of any kind, and it happens even if you never open a FACEIT page.
• Player avatars are ordinary images: Atlas puts the address that FACEIT itself returned into the page, and your browser loads it from FACEIT's image servers, exactly as the FACEIT site does.
• The published extension always uses that Worker. There is no setting that changes the backend address. A localhost development proxy and custom backend URLs exist only in the separate developer builds, which are not distributed on the Chrome Web Store.
• Atlas contains no analytics, no telemetry, no error-reporting service, no advertising network, and no third-party scripts of any kind.
• Optional external profile actions (FACEIT, Steam, Leetify, FaceitFinder, FaceitPerf and FaceitAnalyser) only navigate after you click a visible action. Atlas validates the HTTPS host and path locally and does not prefetch or open these profile pages automatically. The FaceitAnalyser profile action carries the player's public FACEIT ID in the page URL when available, otherwise their nickname. The page reader requires an ID-based CS2 URL; a nickname-only fallback opens the profile without importing. CSWatch and FaceitHound are currently hidden because a safe public route has not been confirmed.

How Atlas reads live match data on FACEIT pages

To show maps, server options and the state of the veto as early as the FACEIT page itself knows them, Atlas does not repeat FACEIT's requests. Instead, on faceit.com pages only, it places a passive observer around the page's own network functions (fetch and XMLHttpRequest) and reads copies of the answers the page has already received. In plain terms:

• It never changes a request or a response. The FACEIT page always receives the original, untouched answer.
• It looks at the address of the page's requests only to recognise three FACEIT match endpoints — /api/match/v2/match/<id>, /data/v4/matches/<id> and /democracy/v1/match/<id>/history. It reads the content of those, and of nothing else.
• Before keeping anything, it discards any field whose name looks like a credential, cookie, token, API key, chat or message, and it skips whole sections about players, teams, profiles, statistics, history and preferences. Other players' nicknames and IDs do not cross this bridge.
• What it keeps is a short allowlist: match ID and state, map names and bans, server and location options, and vote status. Responses over 1 MB are ignored and only the 4 most recent matches are held.
• The result lives in the memory of that browser tab. It is not written to disk, not stored in the cache, and never sent to the Atlas backend, to the developer, or to anyone else. It is gone when you reload or close the page. Part of it — the current match state — is also placed in an attribute on the page, which means the FACEIT page and other extensions can read it; see the next section.
• This observer starts as the FACEIT page loads, before Atlas can read your settings, so it runs even with the master toggle, all modules and all automations off. There is no in-app switch for it; disabling or removing the extension stops it.
• Server ping is not measured by Atlas. On the matchmaking page, the FACEIT site itself measures your ping to its server regions and keeps it in your browser's storage for faceit.com. Atlas reads that stored measurement to show it next to server names. It sends no ping or request of its own for this, and the measurement is never sent anywhere.

What the FACEIT page itself can see about Atlas

• Atlas makes some of its own module files readable by faceit.com pages, because the content script loads them on demand. A script running on faceit.com can therefore detect that Atlas is installed and read Atlas's own source files. It cannot read your settings, notes, tags or history this way.
• FaceitAnalyser pages can similarly read the single public parser module needed by the page reader. This exposes extension detection and parser source, not settings, notes, cache or other private extension data.
• Atlas writes diagnostic attributes on the page's root element (current match state, which match endpoints were observed, lobby detection status). Other scripts on the page, and other extensions, can read them. They hold Atlas's own state and match metadata, not other people's personal data. A developer debug mode, off unless deliberately switched on, can add the nicknames of players in your lobby to one of those attributes and to the browser console.

What Atlas does not do

• Atlas does not sell, rent, or share your data with advertisers or data brokers.
• Atlas does not run any advertising or behavioural-tracking scripts.
• Atlas does not collect passwords, payment or banking information, or any FACEIT account credentials. It never asks for your FACEIT password.
• Atlas has no account, no login and no server-side sync. Your notes, tags, page notes and encounter history are never uploaded, not even encrypted; the only way they leave your device is a backup file you export yourself.
• Atlas's main content scripts run only on faceit.com. A separate, limited reader runs on the FaceitAnalyser public CS2 profile pages described above, and a small card runs on the Steam Community profile pages described above. These scripts do not operate inside embedded frames, and Atlas does not read other websites.
• Atlas does not modify, block or redirect FACEIT's own network traffic, and it does not act on your FACEIT account except by clicking buttons or filling the chat box through automations you have enabled.

Automations

Atlas includes optional automations (auto ready-up, auto party accept, auto server connect, auto copy server data, auto map chat message). They act on the FACEIT page you already have open, as if you had clicked yourself. Every one of them is off by default and must be explicitly turned on by you in Options. No preset or "recommended" configuration enables them. Turning one off stops it immediately. While they run, Atlas records the local diagnostics log described above so you can see what happened.

Permissions

• storage: to save your settings, notes, encounter history, automation diagnostics and local cache.
• clipboardWrite: only for the explicit "copy" actions you trigger (copying a quick call, or the opt-in auto-copy-server-data automation).
• scripting: only right after Atlas is installed or updated, to put its own packaged scripts and styles back on the faceit.com tabs you already have open, so they work again without reloading them. It never runs code downloaded from anywhere, and never on other sites.
• Host permissions in the published extension are limited to faceit.com and the Atlas Worker (faceit-atlas-api.diogosilvasoares21.workers.dev). The local development backend (localhost/127.0.0.1) exists only in the developer builds and is not part of the permissions requested by the published extension.
• The declared FaceitAnalyser content script additionally requests site access restricted to https://faceitanalyser.com/stats/*/cs2*. The browser may ask you to approve this additional site access when updating. It is needed to read the public statistics you open and does not grant cookie access or access to unrelated sites.
• The declared Steam content script requests site access restricted to Steam Community profile pages (https://steamcommunity.com/profiles/* and https://steamcommunity.com/id/*). It is needed to read the Steam ID of the profile you open and to show the FACEIT card on it; it does not grant cookie access or access to other Steam pages.
• Atlas does not request the tabs permission. When you open the Atlas popup it reads the address of the tab you are on, to decide what to show; Chrome only reveals that address for sites Atlas already has permission for, which in practice means faceit.com.

Changes to this policy

If this policy changes, the "Last updated" date above will be revised. Material changes will also be reflected in the Chrome Web Store listing.

Contact

Questions about this policy, or about the data Atlas handles, can be sent to diogosilvasoares21@gmail.com.

Back to the overview