Privacy Policy

Last updated: July 2026 · Applies to SlotGuard for Chrome v1.2.5 and this website

This policy distinguishes between (a) this website, (b) the SlotGuard browser extension for Chrome, and (c) products that may exist in the future (mobile applications, API services). Only released products process data; sections below describe actual behaviour of the current extension version. If future products launch, this policy will be updated before they process any data — nothing in this document should be read as describing products that do not exist yet.

1. Data processed

The extension processes the following data, locally in your browser:

iframe URLs and network request hostnames on pages you visit — inspected locally to identify game-serving domains; not transmitted anywhere in normal operation;
the provider database — fetched from our database infrastructure (Supabase) and cached locally;
temporary tab verification state — stored in chrome.storage.session, cleared automatically when the browser closes;
when — and only when — you explicitly submit a report: the game domain and the casino origin. The casino URL is sanitized before sending: path, query string, fragment and any tokens are removed.

2. What is not collected

no permanent browsing history is stored or transmitted;
no payment data is collected;
no account registration exists — there are no user accounts;
no query parameters, session tokens or credentials are stored;
no personal data is sold to anyone.

3. Purpose

Data is processed for exactly one purpose: determining and displaying the verification status of the domain serving a casino game, and — for explicit user reports — reviewing unknown or suspicious domains to improve the database.

4. Data retention

Local verification state lives in session storage and is deleted when you close the browser. The locally cached provider database is refreshed periodically. User-submitted reports are retained in the review database as an audit log of database changes; they contain only the sanitized data described above.

5. Third-party infrastructure

The provider database and report storage are hosted on Supabase (managed PostgreSQL). Requests to fetch the database or submit a report are made directly to that infrastructure and are subject to standard transport encryption (HTTPS). No advertising or analytics trackers are embedded in the extension or this website.

6. This website

This website is static. It sets no cookies, runs no analytics, and embeds no third-party trackers. Outbound links (for example, to the Chrome Web Store) lead to services with their own privacy policies.

7. User reports

Reports are strictly opt-in: nothing is submitted unless you press the report button. A report contains the game domain and the sanitized casino origin. Reports are reviewed before any database status changes.

8. Security

Database access from the extension is read-only for provider data, restricted by row-level security policies. Report submission accepts only the sanitized fields described above. We follow the principle of data minimization: what is not collected cannot leak.

9. Children

SlotGuard relates to gambling content and is not intended for persons under 18 (or the applicable age of majority for gambling in your jurisdiction). We do not knowingly process data of minors.

10. Changes

We may update this policy as the product evolves — in particular before launching any new product (mobile app, API) that processes data. The current version is always available on this page with its revision date.

11. Contact

Privacy questions and data requests: support@slotguard.io. Responsible entity: Andrey Rozhkov.