AInforce

Legal

Privacy policy

AInforce Ltd · Last updated: October 21, 2026

Overview

This policy explains what personal data AInforce Ltd ("AInforce", "we", "us") collects, why we collect it, how we use and protect it, and what rights you have over it. It covers the AInforce website (ainforce.ai), the AInforce SaaS platform, and the Shadow AI Monitor Chrome extension.

AInforce is a business product for AI adoption, spending, and security. For employee usage data processed on an organisation's instructions, the organisation determines the purpose of processing and the applicable agreement defines AInforce's processor obligations. For website enquiries and account administration, AInforce handles the information needed to respond and operate the service.

What we collect

Account and contact data. Work email address, first and last name, company name, and job title when you register, join the waitlist, submit a careers application, or start a trial.

Trial scan data. The domain name you submit for scanning, plus the signals we discover during the scan: DNS records, certificate transparency data, publicly observable HTTP response headers, inferred technology stack details, publicly visible job postings, and passive open-source intelligence gathered from publicly accessible sources. See the Scan Methodology section below for important caveats.

Usage and interaction data. Website records may include pages visited, referring URLs, browser information, IP addresses, and approximate country-level location. We use these records to understand site activity and diagnose issues. Do not assume IP records expire automatically after a particular interval; contact us about the applicable retention and deletion process.

Extension detection metadata. Covered in detail in the Chrome Extension section below.

Support and correspondence. Content of emails, support tickets, or other messages you send us.

How we use your data

We use the data we collect for the purposes below. The applicable legal basis and your rights depend on the service, relationship, and jurisdiction; UK GDPR and CCPA do not use identical legal frameworks.

Contractual necessity

  • Provisioning and operating your account and subscription
  • Generating your AI risk scan report and making it accessible via your report link
  • Managing customer order forms and issuing invoices
  • Sending transactional emails: report-ready notifications, account notices, and password resets

Legitimate interest

  • Improving scan accuracy by analysing aggregate patterns in detection data
  • Monitoring API and platform health to detect abuse and outages
  • Sending product update emails to existing customers (you can opt out at any time)
  • Fraud and security monitoring

Legal obligation

  • Maintaining records required by tax and financial regulations
  • Responding to lawful requests from competent authorities

Consent

  • Marketing emails to prospects who have explicitly opted in
  • Non-essential cookies and analytics (see Cookies section)

Contact us before submitting confidential information if you need specific restrictions on AI-provider processing, model training, or secondary use. Provider terms and the applicable agreement must be reviewed for the workflow you select. Website advertising measurement is optional and described below; it is separate from your demo request.

How web scans work — important limitations

When you submit a domain for scanning, AInforce queries publicly accessible data sources: DNS records, certificate transparency logs (crt.sh), publicly visible HTTP response headers including Content-Security-Policy, job boards (Greenhouse, Lever, LinkedIn), and passive fingerprinting of publicly observable HTTP responses.

Scan results are substantially inferred. We do not have privileged access to the scanned organisation's internal systems, email, documents, or private communications. Risk scores, technology stack attributions, detected AI tools, and remediation recommendations are generated by applying our detection models and scoring logic to these external signals.

Fine print — scan accuracy. A significant proportion of scan findings are inferences, not direct observations. Technology stack detection may be incomplete or incorrect if a vendor does not expose standard fingerprints. AI tool detections based on job postings reflect disclosed hiring intent, not confirmed deployment. Risk scores are heuristic assessments, not security audits, penetration test results, or compliance certifications. AInforce makes no warranty as to the accuracy, completeness, or fitness for any particular purpose of scan output. Findings should be treated as a starting point for investigation, not authoritative fact. See Section 7 of the Terms of Service for full limitation of liability.

Public-source scanning is not a penetration test. DNS lookups and HTTP checks may contact public services. A domain scan does not grant access to internal systems, and it does not establish that an inferred tool is deployed. Only submit domains or files you are authorised to review.

Chrome extension — Shadow AI Monitor

The distributed browser extension compares request hostnames with its AI-tool catalogue and supports local configuration diagnostics on the AInforce configuration-linter page. Its recorded metadata can include:

  • Tool domain (e.g. chat.openai.com)
  • Tool name and product category (e.g. ChatGPT — Generative AI / Chat)
  • Risk level (critical, high, medium, or low) from our static catalogue
  • Timestamp of detection (ISO 8601, to the nearest second)
  • Organisation key supplied by the IT administrator during setup
  • Extension version and browser type
  • Optional employee email hash and department supplied during configuration
  • Configuration diagnostics: scalar model settings, system-prompt length, rule outcomes, and a suggested scalar change on the supported linter page

The distributed extension does not collect or transmit:

  • The content of any prompt, message, query, or AI conversation
  • Page content, DOM, or rendered HTML from any tab
  • Clipboard contents, keystrokes, or user input of any kind
  • Authentication credentials, cookies, or session tokens
  • The full URL, query string, or path of any request — only the hostname is examined
  • Content from arbitrary websites; configuration diagnostics are restricted to the supported AInforce linter surface

The extension schedules detection uploads approximately once a minute, subject to browser availability and connectivity. Configured email hashes and departments may be associated with events. A hash is not a guarantee of anonymity. Administrators should disclose the monitoring scope to employees. The extension does not save or promote production model configuration; a user must review supported local changes.

Fine print — extension deployment. The extension is deployed by IT administrators to managed devices. Employees of subscriber organisations should consult their employer's acceptable use policy for information about monitoring scope and retention. AInforce acts as data processor for all extension detection data; the employing organisation is the data controller. Employee rights requests related to extension data should be directed to the employing organisation in the first instance.

Data sharing

The website uses service providers and public data sources for the purposes below. A public lookup source is not necessarily a contracted sub-processor. The separate application may use additional infrastructure, identity, or model providers; request the current provider list and applicable processing terms for your deployment.

Provider or sourcePurposeScope / location review
ResendWebsite transactional email deliveryConfirm applicable processing and transfer terms
Replit / cloud infrastructurePublic website hosting and databaseDoes not establish the application deployment region
ClerkWebsite sign-in and account verificationReview identity-service terms for account data
Google Ads (optional website measurement)Advertising conversion measurement, only after consentGoogle's applicable data-transfer terms
crt.sh / SectigoPublic certificate transparency lookups during scanningPublic data source
Greenhouse / LeverPublic job posting lookups during scanningPublic data sources

We may disclose data when required by law, court order, or regulatory authority, or when necessary to protect the safety of our users or the public. We will notify affected users of such disclosures where legally permitted to do so.

Retention and deletion

Retention depends on the record type, service configuration, contractual requirements, and applicable law. This page does not promise automatic deletion of scan reports, IP logs, or account records after a fixed period. Ask for the retention schedule, backup treatment, and deletion procedure before connecting regulated or sensitive data.

You may request deletion of your personal data at any time by emailing info@ainforce.ai. Deletion requests for B2B account data are honoured after the subscription has ended and any regulatory retention obligations are satisfied.

Your rights

Depending on your jurisdiction, you may have the following rights over your personal data:

AccessRequest a copy of the personal data we hold about you.
RectificationAsk us to correct inaccurate or incomplete data.
ErasureAsk us to delete your data where there is no overriding legal obligation to keep it.
PortabilityReceive your data in a structured, machine-readable format.
RestrictionAsk us to pause processing while a dispute is resolved.
ObjectObject to processing based on legitimate interest, including direct marketing.
Withdraw consentWhere processing is based on consent, withdraw it at any time without affecting prior processing.

To exercise any right, email info@ainforce.ai. We respond within 30 days. You also have the right to lodge a complaint with your national data protection authority (for UK users: the ICO at ico.org.uk; for EU users: your local supervisory authority).

Cookies

Executive report pages have a separate, optional checkbox for anonymous report-click measurement. It is off by default. If you opt in, we record the report name, edition and format when you select a PDF or online edition; we do not store your IP address, contact details or form answers with that event. You can untick the checkbox on any buyer page to stop future report-click events. This choice is separate from advertising consent.

We use essential cookies for session management and security. When advertising measurement is enabled, our public marketing pages offer a separate accept or decline choice. Google Ads tags are not loaded before you accept. Declining does not prevent scans or demo requests.

If you accept, Google Ads may use advertising cookies and click identifiers to attribute accepted scan and demo requests. We send a random conversion identifier, not your name, email, company, or form answers. Advertising personalization and enhanced conversions are not enabled. These tags are excluded from private product and compliance pages.

Use the Advertising privacy control on a public page to withdraw consent. Our local consent choice expires after 180 days; locally stored Google click identifiers expire after 30 days and are removed on withdrawal. Google manages the lifetime and processing of its own advertising identifiers under its terms. First-party request records are maintained separately from optional advertising measurement, so accepted requests are not proof of a booked meeting or a delivered email.

Security

Security configuration depends on the service and deployment. Request the relevant access controls, transport and storage protection, key management, and credential lifecycle evidence rather than relying on a universal protocol or encryption claim. See the security and trust page. Send responsible disclosures to security@ainforce.ai.

No system is perfectly secure. Where a personal data breach triggers notification obligations, the applicable law and our role determine the recipient and deadline. UK GDPR's authority-notification rules do not establish an identical 72-hour deadline for every individual notification.

Policy changes

We will update this policy when our data practices change in a material way. Changes affecting data you have already submitted will be notified by email at least 14 days before taking effect. The "Last updated" date at the top of this page reflects the most recent revision. Continued use of the platform after the effective date constitutes acceptance of the updated policy.

Contact

AInforce Ltd
Privacy enquiries: info@ainforce.ai
Security disclosures: security@ainforce.ai

Questions about the Terms of Service or EULA: read the Terms →