Privacy in Rift CS2.

What stays on your PC

Rift reads local hardware, installed-app and Windows details to show settings and help with setup. Player preferences, profiles, CS2 choices and restore backups are stored locally. Portable profiles sit beside the app; installed profiles and PC-specific backups use the current Windows user’s RiftCS2 folder. You choose whether to export or share a profile. Uninstall keeps profiles and backups for recovery.

Some local restore points include PC or Windows-user identifiers. Steam names are shown locally, and captured key binds can contain your own chat text. The small local error log is not uploaded; you decide whether to share it. The full notice describes these feature-specific files and readings.

The app makes some connections

A bounded signed update check can run after startup while Rift is in front and CS2 is closed. Download and installation need separate actions. Update checks send normal app User-Agent and connection metadata, without profiles, installation IDs or usage events.

Displayed product illustrations load from fixed reviewed kiomad.com HTTPS URLs. The address includes a curated model key; the host receives normal IP, timing, User-Agent and connection information, which access logs may retain. Image requests carry no cookies, authentication, installation/report IDs, player fields, raw device names, USB identities or serial numbers. Pictures are checked and cached in bounded memory, not player folders. Turning usage sharing off does not stop these ordinary image requests.

Connection tests, certificate checks, official support pages and links you open also contact their respective services. Maker and Iranify links are counted when clicked. Those services receive ordinary connection information.

Usage sharing is optional

Help improve Rift is off by default. Enabling it registers a random installation UUID and app version. Participating installations can record a deduplicated successful-setup event and refresh their 30-day activity count. These are counts of participating installations and supported successful setups, not unique people or every run. Opening apps alone, skipped or failed flows, previews and tests do not qualify. There are no startup usage-sharing requests.

You review a diagnostic report before sending

Manual reports are separate from usage sharing. The full JSON preview shows a random report UUID, app version, Windows family/build and a fixed issue category/code. Include basic hardware starts unchecked; choosing it adds only CPU/GPU model names and installed RAM. Profiles, raw logs, account names, passwords and serials are not added.

Only Send this report submits it. An uncertain report remains in memory until Rift closes; an explicit retry keeps its payload and UUID. Changing the issue or hardware choice starts a new report. Sending without usage consent creates a report-only identity and does not count a participating installation. Requests still expose normal HTTPS connection metadata.

Text feedback is a separate choice

Submit feedback sends only the schema, draft UUID, app version, category, interface language and text you wrote. It adds no installation credentials, diagnostics, hardware, profiles, attachments or cookies. Leave private information out of the message.

The draft stays in memory while Rift is open. Uncertain delivery keeps the same draft and ID for an explicit retry; editing after an attempt starts a new submission. There are no automatic retries or startup submissions. Success requires a service acknowledgement. Authorized admins can read messages; the service keeps them for up to 90 days and can delete them earlier. The web host still receives ordinary connection metadata.

Turning sharing off, deletion and recovery

Turning sharing off stops future usage events locally, even if the service is offline. Delete anonymous server data & turn sharing off requests deletion of that identity’s events/reports and revokes its token. Success is shown only after acknowledgement. Historical aggregates remain; hashes of revoked credentials can remain for up to 90 days to support safe deletion retries.

Registration credentials are encrypted for the current Windows user and excluded from exported profiles. If saved report identity cannot be read or verified, it is preserved and sharing/report actions pause. A local recheck makes no service request and does not replace the identity. Separate text feedback remains available with its own explicit Submit.

Settings on a shared Windows account

Pointer speed and precision affect all mice in the current Windows account. Connecting a mouse or choosing a player profile does not apply pointer settings or firmware. Changes require an explicit pointer action or a requested routine that includes them; new routines leave that change off.

Use End my session before the next player starts, and check the result on that PC. Modern pointer restore points preserve later-changed speed and precision independently by comparing values; this is not per-device or per-player isolation. Legacy restore points keep their earlier behavior. Restore covers supported saved changes; the full notice explains exceptions, including CS2 video settings and Vanguard.

Browsers, installers and other apps

RiftPeek installation is manual: choose your Chrome profile, enable Developer mode and Load unpacked yourself. Rift opens the picture guide; Done records your confirmation in memory and does not verify extension readiness. Rift does not install the extension or read browser cookies, passwords or account data.

Manufacturer-page buttons open fixed official pages; compatibility is model-specific. Other websites, installers and apps follow their own privacy practices. Read RiftPeek’s separate privacy page