Shared platform across Business Solutions and Personal Assistant
One backend, identity model, entitlement system, API layer and shared packages are present in the monorepo.
Trust starts with a claim you can check.
The Trust Centre separates implemented controls from deployment facts, legal commitments and certifications that still need direct approval.
Security
Verified public-safe controls and clearly stated assurance gaps.
Privacy
Implemented privacy tooling separated from policy decisions still awaiting approval.
Responsible AI
Scoped actions, deterministic facts and honest capability disclosure.
Subprocessors
Production-use evidence without invented locations or contract terms.
Legal drafts
Approval status and unresolved inputs for every legal document.
Report a security issue
Use the trust-routed form without including credentials, customer data or unnecessary sensitive detail.
Public claims register
A concise view of what the repository does and does not prove.
Built and verified
Business Solutions outbound AI calling
Repository product context records real outbound calling as verified live; the corporate preview does not extend that to a blanket GA claim.
Follow-up Policy, lead management and conversations
Implemented screens, preview fixtures and tests exist. “AI Outreach” is a retired customer-facing name.
Business Solutions operational modules
Calendar, bookings, tables, orders, quotes, enquiries and payments have web and/or mobile modules in the repository.
Personal Assistant calls, tasks, reminders and AI tools
Implemented web and mobile surfaces are present with fictional preview data in the web app.
Developer REST API, OAuth2 and webhooks
API, developer-console and documentation code exist. Public production availability remains a separate deployment check.
Business Solutions and Personal Assistant mobile applications
Substantial Expo applications exist; current product context says store presence, native purchases and push readiness are not complete.
WhatsApp delivery
Integration and UI code exist, but the current product context says the sender is not configured.
Production availability across every product domain
Repository configuration identifies intended domains, but DNS, hosting state and go-live status were not inferred from code.
Formal security certification, penetration testing and data residency
No certification or current independent test is evidenced; provider regions and contractual transfer terms need direct confirmation.
Funding, revenue, customers and market traction
No publishable facts are present in the repository. The preview intentionally uses no metrics or customer logos.
Operational identifiers, provider secrets and privileged controls
Exact roles, identifiers, control procedures, credentials and exploit-relevant implementation details are excluded from the public site.