Privacy

FloatAlpha is a CS2 market-intelligence product. This notice describes what it collects and what it shares with Google. It is written to match what the product actually does today, and will change as the product does.

Account and authentication

You can create an account with an email address and password, with Google, or with Steam. FloatAlpha stores the identifier your chosen provider supplies — an email address, a Google account identifier, or a Steam ID — together with which method created the account.

Steam does not supply an email address, so a Steam-created account has none unless you add one. Connecting a provider to an existing account links an identity; it does not create a second account.

You can delete your account from Settings. Deletion removes your FloatAlpha profile and the data attached to it. It does not reach data already sent to Google, which is governed by Google’s own retention, and it cannot remove information from backups or logs that have already been written.

Product data you create

Watchlist entries, manual portfolio holdings, saved screens, alert rules and market preferences are stored against your account. If you enable the Steam inventory integration, FloatAlpha reads the list of items in your CS2 inventory and stores what it observed, so it can show holdings and value them against observed market listings. That access is read-only: FloatAlpha cannot trade, move or hold items.

Analytics

FloatAlpha uses Google Analytics 4 on the production site only. Analytics records which pages are viewed and a small set of product events — opening an asset, using the screener, adding to a watchlist, completing signup, and similar.

These events deliberately carry no personal data. No email address, no name, no Steam ID, no account identifier and no search text is sent. Where an event counts a search it sends the number of results, never the query. The internal operations console is excluded from analytics entirely.

Advertising measurement

FloatAlpha measures whether advertising produces new accounts. When an account is created, a sign_up event is recorded with the method used — Google, email or Steam — and, where the visit arrived from a campaign, the campaign source, medium and name. No identifier for you is attached to it.

FloatAlpha is an advertiser measuring its own conversions. It does not sell data, does not operate an advertising network, and does not show third-party advertising on this site.

Google Consent Mode

In the EEA, the United Kingdom and Switzerland, advertising storage, advertising data use and ads personalization are switched off before you choose, and analytics storage is switched off with them. Nothing is granted until you act. Outside those regions they default on.

Your choice is recorded in a cookie and honoured for 180 days before FloatAlpha asks again. That interval is a FloatAlpha decision, not a Google requirement. You can change your decision at any time, sooner, in Settings — the change applies immediately.

Campaign information

If you arrive with campaign parameters in the address — for example utm_source or utm_campaign — FloatAlpha records them, along with the page you landed on, in a cookie that lasts 90 days. Only the first such visit is recorded, so a later direct visit does not overwrite it.

Google advertising click identifiers (gclid, gbraid, wbraid) are recorded in the same cookie when present. They are kept so FloatAlpha can reconcile its own records against Google’s reporting, and are not sent to Google Analytics — only the campaign labels above are.

This is FloatAlpha’s own record for understanding where accounts come from. It is not what Google uses to attribute advertising; Google does that with its own measurement.

Cookies and local storage

• fa_consent — your consent choice, 180 days.
• fa_cr — whether a consent choice is required for your region, so the banner is shown only where it applies.
• fa_acq — first-touch campaign information, 90 days.
• Session cookies, which keep you signed in. These are necessary for the product to work and are not used for measurement.
• Google Analytics cookies, set by Google, and only where analytics storage is permitted. Some product preferences are kept in your browser’s local storage and are never sent to us.

Where market data comes from

Market observations originate from third-party sources, described in data sources and methodology. That page also sets out what the numbers do and do not measure.

Google’s role

Google Analytics and Google Ads are operated by Google, not by FloatAlpha. What FloatAlpha sends is described above; what Google then does with it is governed by Google. See how Google uses data from sites that use its services.

Signing in with Google or with Steam involves those services directly, under their own terms. FloatAlpha receives only the account identifier each returns.

Changing your consent choice

Use the control below, or the same control in Settings. It appears only where a consent choice applies to you.

Contact

Write to info@floatalpha.com with any question about this notice or your data. Account deletion and your consent choice are both available directly in Settings.