1. Introduction & Single Purpose
This Privacy Policy governs the browser extension Peekly for FACEIT (“Peekly”, “the Extension”, “we”, “our”), developed to enhance the competitive matchmaking experience for players on the FACEIT competitive platform (faceit.com).
In full accordance with the Google Chrome Web Store Developer Program Policies, Peekly operates under a strict Single Purpose mandate: to compute and render transparent match performance intelligence (recent match statistics, rating dynamics, map balance radar, and match history insights) directly inside authorized FACEIT matchroom interfaces.
2. Data Collection & Usage
Peekly is engineered on strict privacy-by-design principles. We explicitly state that the Extension does not collect, store, sell, trade, or transfer any Personally Identifiable Information (PII) to external developers or commercial third parties.
Specifically:
- No Personal Identifiers: We do not collect or process your real name, email address, physical address, phone number, or IP address.
- No Account Credentials: Peekly never accesses, logs, or stores your FACEIT passwords, Steam authentication credentials, API tokens, or payment methods.
- No Private Communications: The Extension does not inspect, read, or record private chat messages, friend lists, or direct communications.
- No Browsing History: Peekly does not monitor, track, or record your web browsing activity outside of authorized
faceit.commatchrooms and profiles. - No Third-Party Trackers or Analytics: Peekly contains zero analytics SDKs, tracking pixels, telemetry scripts, or advertising trackers (including Google Analytics, Yandex Metrika, Sentry, or Mixpanel).
3. Data Processing Architecture
All data processing is executed strictly client-side within your local web browser session:
- Direct Official API Requests: Statistical queries (e.g., K/D ratio, ADR, HLTV rating, match history) are performed directly from your browser to official public FACEIT API endpoints (such as
https://open.faceit.com/*andhttps://api.faceit.com/*). - No Intermediate Servers: Peekly operates without proprietary proxy servers, relay endpoints, or cloud databases. No query or session data passes through third-party infrastructure.
| Data Category | Collection Status | Processing Method |
|---|---|---|
| Personal Identity & Contact Info | Not Collected | Never accessed or transmitted |
| Passwords & Authentication Cookies | Not Collected | Never accessed or stored |
| Lobby Match Statistics (K/D, ADR, ELO) | Ephemeral / Not Collected | Fetched directly from FACEIT API into browser runtime memory |
| User Preferences (Language, Toggles) | Stored Locally Only | Persisted on the local device via chrome.storage.local |
4. Local Storage (chrome.storage.local)
Peekly uses the native Google Chrome Storage API (chrome.storage.local) exclusively for client-side functionality:
- User Configuration: Remembering user interface settings, selected display language (e.g., English, Russian, Polish, etc.), active module toggles, and notification preferences.
- Ephemeral Match Cache: Temporarily caching recent match stats with an automated Time-To-Live (TTL) expiration to avoid redundant API queries when refreshing lobby views.
All stored information remains strictly on the user's local machine. It is never synchronized across devices, never transmitted to external servers, and inaccessible to any other website.
5. Permissions Justification
In adherence to the Chrome Web Store policy of minimal permissions, Peekly requests only the permissions strictly necessary for its declared functionality:
6. User Rights & Data Deletion
Because all data generated by Peekly is stored exclusively on your local machine, you have complete ownership and control over it:
- Complete Deletion: Removing the extension from your browser (via
chrome://extensions→ “Remove”) permanently and instantly deletes all stored preferences, configurations, and cached data from your machine. - Feature Control: You can disable any specific module or feature at any time through the Peekly popup menu without altering other settings.
7. Contact Information
If you have questions, feedback, or compliance inquiries regarding this Privacy Policy or Peekly's data practices, please contact us:
8. Changes to This Privacy Policy
This Privacy Policy may be updated periodically to maintain compliance with relevant browser extension policies or platform modifications. Any updates will be reflected on this page with a revised Effective Date.