Separate collection
from private reads.
Public SDK write keys authorize site collection. Authenticated reports, profile edits, SQL reads, and MCP access use separate application permissions.
Project and workspace access
Projects belong to workspaces. Membership and roles gate application access. MFA protects sensitive administration paths, including MCP key creation. Supabase authentication and application state are separate from Tinybird analytics storage.
MCP and SQL
MCP uses private project-scoped credentials and currently exposes read-only tools. SQL Explorer mints a short-lived Tinybird credential filtered to the authorized project’s raw_events data, with a bounded read-only query path.
Optional collection
Explicit user IDs and scalar traits come from your application. Replay is opt-in, masks text and inputs by default, and supports blocking sensitive elements. Review your deployment configuration and the data you explicitly send.
Operational scope
These are implementation boundaries, not a claim of external certification or a hosted-service SLA. Hosted security contacts, subprocessors, and operational commitments will be finalized before public checkout.
Inspect the source · Read the collection model · Contact the maintainer