RiftPeek and your data.

What RiftPeek reads

RiftPeek works only on www.faceit.com. It reads the current FACEIT page and match context, player IDs and nicknames, profile country, and player and match statistics such as Elo, maps and recent results, to show its FACEIT features. Its background checks request match and account information from FACEIT using the sign-in your browser already has. Chrome attaches the existing session credentials; RiftPeek does not read or store your password or authentication-cookie values.

What stays in your browser

Your settings, notes about other players, activity list and recognised FACEIT account identity are saved in the browser's extension storage. Player and match data are also cached locally in memory and browser session storage so the same statistics do not need to be requested repeatedly. Session caches are temporary. Settings and notes persist between browser sessions; the activity list and automation state use bounded local records. Removing RiftPeek deletes its extension storage.

RiftPeek does not automatically upload local account records, player and match caches or saved notes to kiomad.com. If you choose to send a report, your message and the selected technical details described below, including on/off settings and scrubbed activity lines, are sent.

Notes backups you control

RiftPeek 1.1.2 and later include an optional Download backup action in the notes settings. Only when you choose it, RiftPeek prepares a JSON file on your device containing saved notes, player IDs, nicknames, Good/Avoid labels and update times. The file does not include browser credentials, cached match statistics or your automation settings. If you choose Import backup, the selected file is read locally, validated and previewed; you choose a conflict policy before saving the merged notes to this browser’s extension storage. Notes absent from the file are not deleted.

These backup and import actions do not send the file or note contents to KioMaD, FACEIT or a cloud backup service. Treat the downloaded file as private: anyone you give it to can read the notes. You control where the file is kept, shared or deleted. A file stored outside extension storage is not removed when you uninstall RiftPeek. Versions 1.0.5 and earlier do not include these backup controls.

What reaches kiomad.com

Only ordinary page visits that you can see:

• The welcome page, once after installing, with RiftPeek's version.
• The goodbye page, when you remove RiftPeek, with its version.
• A click on one of the two ads (Iranify or kiomad.com) or on the "Made by KioMaD" link, with the software and the screen the click came from.

These visits are counted as totals per day. The count holds no name, account, country, address, cookie or browser details. Your connection's address is used to answer the request and, for a short time in memory, to protect the site from floods; it is not written to these counts.

Store links and campaigns

The website’s Add to Chrome buttons and shared campaign links can pass through a fixed kiomad.com redirect to the same Chrome Web Store listing. We count repeatable navigations by a fixed campaign label and UTC day, without cookies, player/account IDs or note contents. Keyed network hashes are used in short-lived abuse-limit buckets, not stored with campaign counts. Fixed UTM campaign labels are sent to the store; Google’s own store analytics are separate. These clicks are not confirmed installs or unique people.

A report you send

The report form on this website sends what you write, and only when you press Send. If you leave the box ticked, the technical details shown on the form go with it: RiftPeek's and the browser's version, which switches are on, the result of the last auto-accept check and the latest lines of RiftPeek's activity list. They hold no name, account, match or server address.

A report is kept for 90 days and then deleted. To limit abuse, a scrambled form of your connection's address is kept for up to a day; the address itself is not stored with the report.

What RiftPeek does not do

RiftPeek sends no background analytics to kiomad.com. It opens the visible installation and removal pages described above, and its project links open only when you click them. It has no account of its own, sells nothing and uses no advertising network. Its two small ads, for Iranify (the team's own store builder) and for kiomad.com, take turns in one place and are marked as ads.

Limited Use

RiftPeek uses user data only for its disclosed FACEIT features and their operation, reliability and support. It does not sell user data, use it for personalised advertising or unrelated profiling, or supply it to data brokers. RiftPeek's use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Questions

Use the report form or the contact section on kiomad.com. RiftPeek is made by KioMaD as part of the Rift CS2 project and is not affiliated with or endorsed by FACEIT.