Anonymous Usage Metrics
Shield360 collects anonymous usage metrics by default so we can see which features are used and where to improve the product. Nothing here is meant to identify you personally - there is no email, name, password, secret, or span/trace content in what we send.
There is no in-app settings toggle for this. Opt out with an environment variable on the Shield360 deployment, then restart so the change takes effect.
How to opt out of telemetry
Section titled “How to opt out of telemetry”Set:
TELEMETRY_ENABLED=falseThat disables browser analytics, server-side usage events, and the daily install snapshot. Omit the variable (or set it to anything other than false) to leave collection on - Compose and .env examples ship with it enabled.
What identifies an install (anonymously)
Section titled “What identifies an install (anonymously)”| Signal | What it is |
|---|---|
| User | An opaque user id - never your email, name, or password |
| Organisation / project | Opaque organisation and project group ids - never names or member emails |
| Install | A stable random install_id per Shield360 deployment |
| Environment | Ordinary analytics context such as browser, OS, and approximate location |
What we track
Section titled “What we track”When enabled, Shield360 sends:
- Active usage - opaque user / organisation / project activity, login and registration, and page path visits as people use the UI
- Feature adoption - create/update/delete-style signals for prompts, rules, evaluations, dashboards, contexts, OpenGround, and database configurations (ids and counts, not names or contents)
- Auto features - whether Auto Pricing and auto evaluation are turned on, and run outcomes
- SDK-facing API use - success/failure when applications fetch prompts or Vault secrets through Shield360 (the Shield360 server records this; the SDK packages do not phone home on their own)
- Daily install snapshot - once per day, aggregate totals for that install: Shield360 version, counts of users / organisations / projects / database configs, whether auto pricing or auto evaluation is configured, and high-level ingestion volume counts
We never send emails, names, passwords, secrets, API keys, prompt or rule text, or the contents of your spans and traces.
Where metrics are stored
Section titled “Where metrics are stored”Usage metrics are sent to PostHog for secure storage and product analytics.
Frequently asked questions
Section titled “Frequently asked questions”Is there a UI switch to disable this?
No. Opt out only via TELEMETRY_ENABLED=false on the Shield360 process, then restart.
Does disabling this stop my own OpenTelemetry traces?
No. This only controls Shield360’s anonymous product usage metrics. Your application’s OTLP traces, metrics, and logs are separate.