Privacy

What the control plane stores, what it never stores, and how to reach us about it.

Last updated: 26 October 2026

This page is a plain-language summary of how SentraZero handles data. It is not the governing legal agreement. Where a signed quotation, MSA, or DPA exists, that document governs.

Account data
Email address, organisation name, team size, and member name provided at signup. Authentication is handled by our Supabase-hosted control plane.
Operational metadata
Device identity and heartbeat, pipeline and job definitions, execution IDs, status, wall-clock timings, plugin names, and audit-log events.
Raw data
Never stored in the control plane. Datasets, intermediate step outputs, and final outputs stay in your storage — a local mount or an S3-compatible bucket you control.
Sub-processors
Supabase hosts the control plane database and authentication. Payment processing will be added when billing is enabled and will be listed here before it goes live.
Retention
Account and execution metadata are retained while your workspace is active. Ask us to delete a workspace and we will remove its metadata, subject to any legal retention obligations.
Requests
Email contact@sentrazero.com for access, correction, or deletion requests.

Sovereignty claim, stated precisely: raw data never leaves your storage. Only outcome metadata and audit logs reach the control plane. Data already in a cloud object store remains subject to that provider's terms.