SPIDER® SPIDER®Command & Control · Powered by AI
Last updated: 29 April 2026

SPIDER® Privacy Policy

This Privacy Policy describes our policies and procedures on the collection and use of your information when you use the SPIDER® Services — the marketing website, the Command & Control web console, and the SPIDER® mobile app.

1. What this website collects

This domain (spiderc2.com) serves only static HTML, CSS and JavaScript. There are no analytics scripts, no cookies, no third-party trackers, no fingerprinting. The contact form opens your local mail client via a mailto: link — no data is submitted to a server. Web fonts are loaded from Google Fonts; no other third-party requests are made.

2. What the SPIDER® platform collects

The platform itself is deployed on customer-owned infrastructure (on-prem or airgapped). Operational data — video, sensor events, user activity, audio clips for voice biometric, face frames for face ID — never leaves the customer's network unless the customer explicitly configures egress (e.g. a Slack webhook for alerts).

The bundled LLM (Ollama / llama3.2) and biometric models (InsightFace, SpeechBrain) all run locally. No prompts are sent to any external API.

3. Information collected by the SPIDER® mobile app

App developers use your information strictly for the purpose of app functioning only while using this app. The SPIDER® app uses the following device information and stores the same on the user's company server machines:

  • Device Location — for incident reporting and patrol tracking.
  • Device Camera — for evidence capture and face enrolment.
  • Device Microphone — for voice notes, voice biometric enrolment and the AI assistant.
  • Photos & Media — for attaching evidence to incidents.

App users are bound by their company's policy for data usage, and this data may be used by their company for tracking their location and login profiles.

SPIDER® app developers declare and confirm that, with default installation configuration, this data is stored on the C2 servers specific to the user's company. App developers may access the data with the user's permission for support and maintenance activity only.

By using the Service, you agree to the collection and use of information in accordance with this Privacy Policy.

4. Biometric data on the platform

  • Face and voice enrolments are stored in the Greeter service's local database, on the customer's server.
  • Operators can delete their own enrolment from the AI chat panel at any time.
  • Site administrators can delete any enrolment via the Greeter API or admin console.
  • No biometric template is shared between deployments. No cloud copy. No vendor copy.

5. Logs & telemetry

The platform writes operational logs to local storage. There is no outbound telemetry, error reporting, or "phone home" channel. Customers may opt-in to send aggregated diagnostics on a per-deployment basis; this is off by default and never enabled silently.

6. Changes to this Privacy Policy

We may update our Privacy Policy from time to time. You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page; the "Last updated" date above will reflect the change.

7. Contact us

If you have any questions about this Privacy Policy, or to request a Data Processing Agreement for a specific deployment, you can contact us by email: spider@tataadvancedsystems.com.