Privacy
Privacy Policy
Effective May 15, 2026
What Synteq Handles
Synteq is designed to monitor systems - not access them. We process operational metadata such as source identifiers, workflow or job identifiers, run status, timestamps, retry counts, incident state, alert configuration, and related reliability context.
Webhook Data Boundaries
Customers control what they send to Synteq. Send workflow execution signals, not customer records. Avoid forwarding names, emails, phone numbers, addresses, notes, message bodies, secrets, tokens, full CRM records, or raw customer payloads.
How Data Is Used
Operational metadata is used to authenticate ingestion, measure reliability, derive findings, surface incidents, and support configured alert delivery. Credentials and ingestion keys are used for verification and access control, not as analysis content.
Control
Workspace owners and admins can revoke or rotate ingestion keys, disable sources, disconnect supported integrations, and deactivate alert channels. Removing or disabling a source stops new accepted signals from that source.
Compliance Claims
Synteq does not claim SOC 2, HIPAA, PCI, or other formal certification unless a signed agreement or current Synteq documentation states otherwise.