Privacy Policy

Last updated: October 9, 2026

MicPeek turns the voice chat recorded in CS2 demos into a translated comms review. That means we handle people’s voices, so this policy says exactly what we collect, why, who can see it and how to remove it.

The short version

We process a demo only when you ask: a FACEIT match you played, or a demo you upload.
The demo file is deleted right after processing. Reports are kept for 30 days unless a player from the match saves one.
Only players from that match can open its report, after signing in with FACEIT.
Any player can remove their voice from every report with one button: “Remove my voice”.
No selling data, no ads, no AI training on anyone’s voice, no voiceprints.

1. Who we are

MicPeek (micpeek.com) is operated from Illinois, USA (“MicPeek”, “we”, “us”). We decide how the personal data described here is used, so we are its controller. For anything about your data, write to support@micpeek.com.

This policy covers the MicPeek website, the MicPeek desktop app and the MicPeek browser extension. Using them is also governed by our Terms of Service.

2. What we collect

When you sign in with FACEIT

Your FACEIT player ID, nickname and avatar, and the Steam ID linked to your FACEIT account (from FACEIT’s public player data). Sign-in happens on FACEIT’s own page, so we never see your FACEIT password.

Demos you ask us to process

A CS2 demo is a recording of a match: rounds, positions, kills, player nicknames and Steam IDs and, for FACEIT and many private servers, the voice chat of every player who spoke. When you decode a FACEIT match by its link, we download its demo from FACEIT for you. When you upload a demo, we receive the file. We only process a demo when someone asks us to.

What we make from a demo

A report: each voice call as a short audio clip, its transcript, an English translation, the round and game time it was said, player statistics, the coach’s feedback and a 2D replay of every round: where each player stood and looked, their health and weapon, grenades and the bomb, drawn on the map’s radar picture.

Technical data

Your IP address, browser type and request logs. Our hosting provider and Cloudflare, which protects and delivers the site, keep these for security and troubleshooting.

Cookies

Only the cookies the site needs to work: sw keeps you signed in for up to 30 days, and sw_oauth protects the FACEIT sign-in step for 10 minutes. We don’t use advertising or analytics cookies, so there is no cookie banner to click.

Messages

What you write when you contact us, and your email address.

3. What we don’t do

No voiceprints. We don’t create voiceprints or any other biometric identifiers, and we don’t identify anyone by their voice. A call is credited to a player using the player ID recorded in the demo, not by analysing how the voice sounds.
No selling. We don’t sell or rent personal data and don’t share it for advertising.
No AI training. We don’t use voice recordings, transcripts or reports to train AI models.
No outside AI companies. Speech recognition and translation run on computers we operate, using open-source models. Your voice isn’t sent to third-party AI services.

4. How we use data, and why we’re allowed to

To run MicPeek for you: process the demos you ask for and show you the reports. Legal basis: our agreement with you.
Other players’ voices: a demo also contains teammates and opponents who may not use MicPeek. We process their voices so the players of that match can review it, which is a legitimate interest. We keep the impact small: only players of that match can open the report, reports are deleted after 30 days by default, and anyone can remove their voice at any time.
To keep the service safe: prevent abuse, fix errors and protect accounts. Legal basis: legitimate interests.
To answer you when you contact us, and to meet legal obligations.

5. Who can see a report

The person who asked for the report, and players of that match after they sign in with FACEIT (matched by their FACEIT or Steam ID). Nobody else can open it, even with the link. MicPeek staff access reports only to run the service, answer your requests, or investigate abuse.

6. How long we keep data

Data	How long
Demo files	Deleted right after processing, usually within minutes.
Reports (clips, transcripts, translations, stats)	30 days. If a player from the match presses “Keep it”, the report stays until a player of that match asks us to delete it.
Your account (FACEIT ID, nickname, avatar, Steam ID)	While you use MicPeek. Deleted within 30 days of your request.
“Remove my voice” list (your Steam ID)	Kept, so future matches skip your voice. Ask us if you want to be taken off it.
Security logs	Short term, normally no more than 30 days, unless needed to investigate abuse.
Emails to us	As long as needed to help you, then deleted.

7. Your choices and rights

Remove my voice. Sign in and press “Remove my voice” on the home page. Your voice clips and transcripts are deleted from every stored report, and new reports skip your voice.
Copy, correction, deletion, objection. Email support@micpeek.com. We reply within 30 days and may ask you to prove you own the FACEIT or Steam account first.
EU, EEA and UK: you also have the rights to restrict processing and to data portability, and you can complain to your local data protection authority.
US states with privacy laws (for example California): you can ask to know, delete and correct your data. We don’t sell or share personal information, and we won’t treat you differently for using your rights.

Providers that run the site for us: our hosting provider and Cloudflare, under terms that let them use the data only to provide their service.
FACEIT: when you sign in or decode a match by link, we call FACEIT’s API, so FACEIT sees those requests. Your FACEIT account itself is covered by FACEIT’s own privacy policy.
Google Fonts: our pages load fonts from Google, which receives your IP address and browser details.
GitHub: the 2D replay uses the radar picture of each map from the game. We download it once per map from a public GitHub repository. The request names only the map, and GitHub sees the IP address of the computer that makes it: our server, or yours when you use the desktop app.
When the law requires it, or to protect people and the service from harm.
If MicPeek is sold or merged, the new owner takes over the data under this policy, and we’ll tell you first.

9. The browser extension

The MicPeek extension for Chrome:

watches for finished downloads and checks, by file name and download address, whether the file is a FACEIT demo. Other downloads are ignored and not stored;
in “This PC” mode, passes the demo’s location to the MicPeek app on the same computer (127.0.0.1). Nothing leaves your computer;
in “Website” mode, uploads the demo to the MicPeek website you chose, from the same link FACEIT gave your browser;
on faceit.com, reads the page address to show the MicPeek button on match pages;
stores its settings and the names of your last 5 demos in your browser;
doesn’t read your browsing history, passwords, page contents or FACEIT sign-in, and doesn’t send anything anywhere else.

MicPeek’s use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

10. The desktop app

The MicPeek app for Windows runs on your computer. Demos, voices and reports stay there, and we don’t receive them. The first run downloads the speech-recognition model from Hugging Face, which sees your IP address like any other download. For the 2D replay, the app also downloads each map’s radar picture once from GitHub; the request names only the map. To turn that off, set MICPEEK_NO_RADAR=1, and the replay draws the map from where the players walked.

11. Children

MicPeek isn’t meant for children under 13, and we don’t knowingly collect their data. A demo can contain the voice of any player in the match. If you’re a parent and your child’s voice is in a report, email support@micpeek.com and we’ll remove it.

12. Where data is processed

We are based in the United States. Our servers and providers may be in the US and other countries. When EU or UK law requires it, we rely on the safeguards our providers offer, such as the European Commission’s Standard Contractual Clauses.

13. Security

The site uses HTTPS everywhere and signed session cookies. Reports are limited to the players of the match, and demo files are deleted after processing. No system is perfectly secure. If you find a problem, please tell us at support@micpeek.com.

14. Changes to this policy

When we change this policy, we post the new version here with a new date. If a change is significant, we’ll also show a notice on the site before it takes effect.