Four canonical inboxes. Each has a documented response SLA. Use the right one and you skip the queue. Beta operators see all four; enterprise contracts negotiate tighter SLAs in the MSA.
Response SLA · 1 business day
Pricing, pilots, enterprise procurement, custom contracts. Include your use case + headcount in the first email.
Response SLA · 1 business day (beta) · 4 hours (paid pilot) · 1 hour (enterprise)
Bug reports, onboarding help, account questions. Faster lanes activate when your contract has a higher SLA tier.
Response SLA · 1 business day acknowledgment · 72 hour full triage
Vulnerability disclosures, penetration test reports, incident-response coordination. PGP key on request.
Response SLA · 5 business days (standard MSA / DPA) · 10 days (custom terms)
DPA review, MSA negotiation, subprocessor questions, change-of-control notices. Standard NDA template available.
Live status + incidents
Public status page deploys on the day the first paid customer signs (plan in docs/status-page-plan.md). Until then, incident comms flow through security@fuvihub.com and the customer-facing comms templates in docs/customer-incident-comms-pack.md.
Security disclosures: please include reproduction steps, expected vs actual behaviour, and a CVSS estimate if you have one. We reply within one business day with an acknowledgment + tracking ID.
Probabilistic decision intelligence — not financial advice. Trust Score reflects evidence + audit + calibration quality, never an accuracy guarantee.
FUVIHUB · fuvihub.com · Strategic intelligence platform.