Trust
Security and Trust
Designed to monitor systems - not access them.
Minimal Access Model
Synteq uses webhook and API-key ingestion paths for operational event metadata. The source type for generic webhook workflows remains webhook, including GoHighLevel outbound webhook setups.
What To Send
Send status, timing, workflow, job, run, source, and delivery identifiers needed for reliability analysis. Do not send raw CRM/contact records, names, emails, phone numbers, notes, message bodies, secrets, tokens, or full customer payloads.
Key Handling
Ingestion keys and webhook secrets authenticate senders. Use production-grade secrets, rotate exposed keys, and keep optional HMAC or signature verification enabled where supported by the configured integration.
Operational Truth
Monitoring becomes active after real workflow events arrive. Alert delivery depends on configured scheduler and email/webhook infrastructure. Synteq avoids claiming alert readiness when those dependencies are not verified.
Revocation
Owners and admins can disable sources, rotate or revoke keys, disconnect supported integrations, and deactivate alert channels from the control plane.