Access control
Customer data endpoints require an access key sent through the X-API-Key header. Unknown keys are rejected before account intelligence is returned.
Trust Center
Security, privacy, and data handling
A concise customer view of how Cybersignals.io protects access, limits data exposure, and handles public business signals.
Data sources
The platform is designed around public business signals such as job postings, technology evidence, procurement signals, and company profile data.
Evidence standard
Signals are scored with source quality, confidence, and buyer-fit checks. Noisy or thin-evidence records are held back from guided customer demos.
Budget transparency
Budget estimates are shown only when evidence supports them. Otherwise the app displays budget evidence pending instead of inventing a value.
Retention
Active intent signals are designed for a 90-day active evidence window. Usage logs support audit and billing review workflows.
Customer isolation
Tenant access is keyed per customer, and production use keeps sandbox access disabled.
Operational contacts
For privacy or deletion requests, use compliance@cybersignals.io.
For pilot support and signal-quality feedback, use the support contact provided in your onboarding email.