Trust starts with
knowing where we stand.

Check, Guard, and Response are described, with privacy and coverage limits. The landing page and intake were inspected in a local browser. You are viewing the deployed website preview. The security service remains prelaunch.

Encrypted contact storage, explicit intake consent, request protection, submission limits, and a saved-request receipt. A synthetic request completed in the browser. No payment, device access, or confirmation email occurs.

Host-restricted operator commands track separate assisted-session consent, permitted case transitions, repeat-check dates, a due queue, and minimal audit records. Automated tests use synthetic cases. Operator sign-in through a web dashboard is not available.

An offline client checks three macOS hardening settings and saves an encrypted report locally. Other platforms return unknown coverage. A consented Mac hardening pilot verified local execution and encrypted report save/decrypt, with a private local report viewer. These settings are not spyware detection; wider device acceptance and independent review remain ahead.

Offline checks validate signed approval manifests, artifact and indicator hashes, fresh signed revocation catalogs, and a local catalog checkpoint. No automatic download, installation, or scanner execution is implemented. No approved scanner releases exist yet.

Classification logic separates No Known Indicators, Needs Review, Strong Evidence, and Coverage Gaps. Missing engine verdicts stay gaps; strong evidence requires human confirmation. A development adapter for acquired iPhone backups now has signed-image gates and a restricted Docker command plan. A real Docker isolation probe passed using synthetic fixtures. Real forensic-engine execution, device acceptance, and detection-performance testing remain pending.

A private quote workflow has encrypted terms, expiring access, explicit decisions, and cleanup for unaccepted offers. A synthetic quote was reviewed and accepted in an actual Chrome test. The payment foundation checks signed events, exact agreed totals, duplicate delivery, and competing requests in PostgreSQL tests. An isolated payment sandbox has been created; real sandbox transaction testing, refunds, account readiness, seller terms and service delivery still need verification. Customer quotes, checkout, subscriptions, and live charging remain disabled. No final prices are public and no customer revenue is verified.

Repeat-check dates can be tracked in development. Automated reminders, customer report delivery, a staffed review cadence, and subscription activation are not connected. Guard does not continuously monitor your device.

Escalation and evidence-preservation requirements are documented. No response team, specialist availability, or response time is verified. This is not an emergency service.

Production configuration guards and container instructions exist. This website is hosted on Vercel with PostgreSQL and an authenticated daily retention job configured. Backup restoration, scheduled-run monitoring, independent review, and the security service remain unverified.