Workspace data boundaries
Targets, results, jobs, exports, and settings are treated as workspace-owned operational data.
Privacy
Privacy and data ownership
PyroSync operates managed capture infrastructure while keeping workspace data ownership, retention, export, and deletion boundaries explicit.
workspace/default
Customer-owned data
ready
Control plane
scheduled
Worker fleet
customer
ownership
Customer-owned data remains scoped to the workspace with export, retention, deletion, audit, and downstream-delivery controls handled through the product and support paths.
Export and retention
Customers can plan around retention windows, exports, cancellation posture, and downstream data use.
Managed infrastructure separation
PyroSync manages browser workers, proxy capacity, schedules, and validation without turning customers into infrastructure operators.
Data use
PyroSync uses workspace data to provide managed capture, validation, export, support, and reliability workflows.
Data deletion
Retention and deletion requests are handled through plan controls, support workflows, and enterprise agreements where applicable.
Operational telemetry
Logs, health checks, and smoke evidence are used to diagnose reliability without intentionally exposing secrets.
Enterprise review
Dedicated data-plane, retention, SSO, RBAC, and SLA requirements can be scoped before production traffic moves.
Ready for a governed data plane?
Start with a safe workspace, prove the workflow, then promote to managed production capacity when migrations, tenant data, and authenticated smoke evidence are green.
Start Building