Optional website analytics

Measure visits and feature use; no typed chat or form text. Privacy policy

ScoutAI360Website enquiry assistant

Last updated 25 October 2026

Privacy policy

This page explains the practical data handling used by ScoutAI360 for accounts, widgets, visitor chats, lead capture, and subscriptions.

What ScoutAI360 collects

ScoutAI360 collects account details, business profile information, uploaded knowledge sources, and content from public pages a business asks us to scan. Our contact, audit, and pilot forms collect the email address and message you submit, plus your name or business website if provided. When a business has enabled its approved assistant, it can process visitor chat messages and the lead details a visitor chooses to submit.

How the data is used

Data is used to run the dashboard, answer visitor questions from approved business context, capture leads, enforce plan limits, improve reliability, and support billing and account management.

AI and knowledge sources

Uploaded documents, FAQs, crawled pages, and chat prompts may be processed by OpenAI to create searchable knowledge and generate answers for the configured business assistant. OpenAI's API data controls and retention terms apply. The optional TypeSafe AI intent service is off by default and runs only when explicitly enabled by the operator; it receives a shortened chat message with common email and phone-number patterns masked.

Service providers and data location

ScoutAI360 uses Vercel for application hosting, Supabase for database and authentication, OpenAI for AI features, Resend for transactional email, and Stripe for payments. An optional Typesafe intent service is off by default; if enabled, it receives a shortened message with common email and phone patterns masked. Resend states that email and log data is stored in the United States. Other provider locations, remote support access, and retention can depend on the service and account configuration. Some processing may take place outside the UK. The providers and transfer terms for a business pilot must be confirmed before that business enables live visitor capture.

Payments

Payments and subscription management are handled by Stripe. ScoutAI360 stores subscription identifiers and status, but card details are handled by Stripe.

Analytics and advertising pixels

After a visitor allows analytics, ScoutAI360 records public page views and selected actions using the event name, page path, and limited labels such as plan or demo type. A random browser-tab ID is stored with these event rows so we can group actions from the same tab. It is not sent to analytics vendors and is cleared from the browser when the tab closes or consent is revoked. The event table does not store query strings, form details, business URLs, or typed questions. Optional Vercel Web Analytics, Google Tag Manager, GA4, and Meta Pixel tracking can also measure page views and contact conversions when configured. Non-essential tracking stays off until consent. The choice is stored in this browser, declining does not affect the service, and preferences can be changed later using Cookie settings in the footer.

Access and deletion

Account owners can review and manage business records, leads, widget settings, and knowledge sources from the dashboard. Before an assistant is enabled for live visitor enquiries, ScoutAI360 and the business must agree in writing on the data collected, retention period, and end-of-pilot export or deletion steps. Provider logs, backups, and copies delivered to a business inbox may have separate retention periods. To ask about access, export, or deletion, use the contact form or email leads@scoutai360.com; do not include passwords or payment details.

Contact ScoutAI360