Privacy Policy

1. Who is responsible

[COMPANY NAME], registered at [REGISTERED ADDRESS] (registration number [REGISTRATION NUMBER]), is the controller of the personal data described in this policy as it relates to operator users and site visitors. Contact: [email protected].

2. Data about operator users

When you create and use an account on InlineShield we process:

• your name and work email address;
• your password, stored only as a salted scrypt hash;
• your organisation name and domain;
• session tokens (stored as SHA-256 hashes);
• security and audit logs, including your IP address and user agent at login and signup;
• login-failure counters, keyed to the email address and IP address;
• usage counters (number of verifications per month);
• billing details you enter (name, address, tax ID and email) and the invoices issued to you;
• email-verification tokens, stored as SHA-256 hashes, and password-reset codes, held only as SHA-256 hashes in server memory (not in the database) and valid for 15 minutes.

3. Purposes and legal bases

• Providing the service: performance of our contract with you.
• Security and fraud prevention: our legitimate interest.
• Service emails (verification, password reset, alerts): performance of our contract with you.

We send no marketing emails, use no advertising trackers and do not sell data.

4. Visitors to our website

When you visit the site or call the API, the web server records your IP address, the date and time, the requested URL, the referrer and your user agent in its access logs, for security and troubleshooting (legitimate interest). Logs are rotated when they reach 10 MB and rotated archives are deleted after 10 days. We use no advertising cookies; analytics cookies are set only with your consent (section 6).

5. Signup screening and automated decisions

Operator signups are screened by InlineShield's own engine using the same signals as the product (email, username, IP address, user agent and form behaviour). Screening results are recorded in the platform's own verification records. Signups with a BLOCKED verdict do not create an account. This is an automated decision based on risk signals, and you are not told the reason. If you believe a signup was rejected wrongly, email [email protected] and a person will review it.

5a. What the browser check collects

For player screening, the InlineShield browser check, when an operator uses it, also sends the browser's time zone, its language list and indicators of browser automation (for example a webdriver flag), together with the existing form timing signals. The time zone is compared with the country of the IP address, and the automation indicators feed the bot score. This is not fingerprinting: no persistent identifier is created, nothing is stored in the player's browser, and the values are not combined into an identifier that follows a person across sites.

To spot the same mailbox used for several signups (for example dot or plus variants), the email address is reduced to a canonical form and compared as a keyed hash (HMAC-SHA256 with a server secret and the operator's identifier). The comparison happens only within one operator's own data, and the hash cannot be matched across operators. The canonical address itself is not stored.

5b. Service improvement

To improve detection, InlineShield keeps two kinds of learning data about screenings. Labels record whether an operator, its review decisions, its outcome reports or our own test runs marked a screening as fraud or legitimate, with an optional category and a short note. Feature snapshots record a privacy-safe summary of each screening: the email domain and provider type, the network (ASN and IP prefix: the /24 of an IPv4 address or the /48 of an IPv6 address), the country, bot signals and the engine's result. A snapshot holds no email local part and no full IP address.

Learning across clients uses only the email domain, the ASN, the IP prefix and counts of distinct operators. An operator's labels never train another operator's model, and its labels and notes are never shown to another operator.

Retention: the raw email address, username, IP address and user agent of a screening are removed after 180 days; views then show "Removed after 180 days". Label notes are removed 180 days after the label is recorded. Labels and feature snapshots are deleted after 13 months.

6. Cookies, local storage and third parties

The console sets no cookies. It uses your browser's local storage for the following, all of which stays in your browser:

• betshield_auth_token: your session token, so you stay signed in;
• betshield_auth_user: a copy of your signed-in profile (name, email, role, organisation);
• betshield_theme: your theme preference;
• betshield_alerts_history and betshield_alert_config: recent dashboard alerts and your alert settings;
• betshield_system_activity_v1: dashboard activity events.

Only when InlineShield support opens a client's console, that browser tab keeps betshield_support_token (the support session token) and betshield_support_tab in its session storage, which is cleared when the tab is closed.

Website statistics: on our public website (inlineshield.io) we use Google Analytics to understand which pages people find useful. We ask first. If you decline, or until you decide, no analytics cookies are set and Google only receives basic, cookie-free visit counts. If you accept, Google Analytics sets its cookies (_ga and _ga_*) so we can see how many people visit, which pages they read and how they found us. We never use it for advertising or ad personalisation. We remember your choice for 180 days in a cookie called is_consent, and you can change it at any time with "Cookie settings" at the bottom of every website page. The console, the admin area and the status page have no analytics at all. Fonts are served from our own servers.

7. Player data that operators send

Data about your players that operators send to the API is processed by us as a processor on the operator's behalf, as set out in the Data Processing Addendum. If you are a player, please contact the operator you registered with.

8. Recipients and sub-processors

• Contabo Inc.: server hosting in United States (St. Louis, Missouri). Our data is stored on these servers.
• Zylomail (smtp.zylomail.com): transactional email (verification, password reset, alerts).
• Google (Google Analytics): website visit statistics, only as described in section 6. It never receives anything from the console or about players.
• Public DNS resolvers (Cloudflare 1.1.1.1, Google 8.8.8.8): they receive the domain names of signup email addresses and of those domains' mail servers only, when we screen signups.

IP location and network lookups use a local database on our own servers, so no player data is sent to DB-IP. We download the free DB-IP Lite database and the Tor Project's public list of exit nodes; these are downloads only, and nothing is sent to it about players or operators.

IP geolocation by DB-IP (licensed CC BY 4.0).

VPN detection uses the X4BNet lists_vpn project (MIT licence), which is derived in part from IPLocate data (CC BY-SA 4.0). The list is downloaded to our servers, and nothing is sent to it. Time zones are matched to countries with the IANA time zone database (public domain).

Disposable-email screening uses public lists of disposable email domains and a public list of popular domains. The lists are downloaded to our own servers, and nothing is sent to them about players or operators. The player's email domain is checked against them locally. The mail servers of the player's email domain are looked up in public DNS, to recognise mail servers that serve disposable domains. A genuine mail provider can occasionally share mail servers with temp-mail services and be matched by mistake; the operator can fix this by adding the domain to the allow list in their Rules settings.

Disposable-domain lists: disposable-email-domains (CC0) and FakeFilter (BSD-3-Clause). Popular domains: Tranco list (CC BY).

9. International transfer

[COMPANY NAME] is established in Armenia, and our servers are in the United States. If you are in the EU/EEA or the UK, your data is therefore transferred to and processed in the United States and Armenia. Ask [email protected] about the safeguards we can offer. We have not appointed a representative in the EU or the UK.

10. Retention

• Operator account data is kept while the account exists, and is deleted or anonymised within 30 days of a verified deletion request after the account is closed.
• Backups are deleted automatically after about 16 days.
• Invoices (invoice number, amounts, dates, and the billing name, address, tax ID and email shown on them) are kept after account deletion because they are financial records.
• Security logs are kept while the account exists.
• Screening records (including those of blocked signup attempts): the raw email address, username, IP address and user agent are removed automatically after 180 days; the rest of the record (verdict, score, reasons with addresses removed, email domain and IP location) is kept until deleted on request.
• Learning data (section 5b): labels and feature snapshots are deleted automatically after 13 months; label notes are removed after 180 days.
• Accounts that never completed email verification (and their expired verification tokens), sessions and usage records are kept until deleted on request.
• Login-failure counters expire after their 15-minute window and are cleaned up periodically.

Apart from the automatic removals above, deletion happens on request.

11. Security measures

• HTTPS with HTTP Strict Transport Security;
• passwords stored only as salted scrypt hashes; session, API-key and verification tokens stored as hashes;
• tenant isolation of customer data;
• SMTP credentials stored encrypted (AES-256-GCM);
• rate limiting and login lockouts;
• nightly database backups, deleted automatically after about 16 days.

InlineShield support may access a client's console to provide support, only by a platform superadmin, for at most one hour at a time, and every access is logged and visible to the client in its activity log.

12. Your rights

You may ask for access, correction, deletion, restriction of processing, objection and portability by emailing [email protected]. We respond within 30 days. You may also complain to your local data-protection authority.

13. Changes to this policy

We will update this page when the policy changes and show the date of the latest revision at the top (currently 2026-10-31).