Privacy policy · Effective 11 September 2026
TeraFlow is designed around minimised identity exposure, edge processing and configurable operational retention.
The static website does not use third-party analytics or advertising scripts. Contact, demo and subscription forms currently create a local interface state only and do not transmit a submission. If form delivery is enabled later, the form will identify the destination and purpose before submission.
Operational inputs depend on project scope and may include sensor observations, calibration data, system health, detections, tracks, zones and events. TeraFlow is designed to minimise unnecessary identity exposure, but no deployment should be treated as anonymous without a documented configuration and review.
Deployment data may be processed to operate, diagnose, secure and evaluate the scoped system. The deploying organisation remains responsible for establishing an appropriate legal basis, notices, access controls and operating policy for its jurisdiction.
Retention, edge processing, central transfer and authorised roles are configured per deployment. These settings and deletion procedures must be documented during acceptance. TeraFlow does not claim a universal retention period.
Data is not sold. Any infrastructure provider, integrator or service processor must be identified in the project scope and governed by an appropriate agreement.
TeraFlow uses scoped technical and organisational controls, but no system can promise absolute security. Suspected incidents should be reported through the Contact page with sensitive details withheld until a secure channel is agreed.
Requests concerning access, correction, deletion or other applicable rights should be directed to the organisation responsible for the relevant deployment. Website and policy questions can be submitted through Contact.
Material changes will be reflected on this page with a revised effective date. This policy is not a substitute for deployment-specific notices or agreements.