TrustPages.trustCenter
TrustPages.rootTitleLead TrustPages.rootTitleAccent
TrustPages.rootDek
TrustPages.collectTitle
TrustPages.collectIntro
Your name, email address, and a password.
To sign you in and address you properly. Nothing more is required to hold an account.
An email address or username you choose to check, or a company domain.
Only to run the check you asked for. Inputs are validated first; private hosts and reserved IP ranges are refused.
DNS records, TLS certificates, security headers, certificate-transparency entries, breach records.
All of it is public record. The audit never touches your private systems; it reads what the internet already shows.
Files you choose to upload. PDF, PNG, or JPEG only.
So your policy records and claim evidence live in one place, attached to your household.
The conversation you have with the dashboard concierge agent.
Stored with your account so the agent keeps context between sessions.
Your plan name and subscription state. Card numbers never reach our servers.
Payment happens on Stripe’s hosted checkout; we receive the outcome, not the card.
TrustPages.storedTitle
Passwords are never stored. We keep an scrypt hash derived with a per-account random salt, and we compare it in constant time. A password must be at least 12 characters and include a number and a symbol.
Sessions are signed, httpOnly, secure cookies that expire after 30 days. In production the server refuses to run without a real signing secret; there is no built-in fallback.
Application records, accounts, policies, intake drafts, live in Netlify Blobs, the managed store scoped to this site. There is no separate database to misconfigure.
The document vault accepts PDF, PNG, and JPEG, verified by reading each file's actual leading bytes rather than trusting its declared type. Each household member is capped at 50 documents and 250 MiB in total, 4.5 MB per file.
You can delete your account from the dashboard at any moment; the stored record is removed and your session is cleared. Privacy requests are honored within 30 days, as set out in our privacy policy.
TrustPages.aiTitle
The public audit and the dashboard concierge run on Anthropic's Claude models, called through the official @anthropic-ai/sdk and routed via OpenRouter. There are no hand-rolled calls to model APIs anywhere in the codebase.
The audit agent reasons over evidence we gather first: DNS, TLS certificates, security headers, transparency logs, breach records. It reads public evidence only and never reaches into private systems. Its score is informational and never sets your price; plans are fixed-price tiers from a published catalog.
Public audit reports are cached for up to 30 minutes against a one-way hash of the target, then regenerated. Concierge conversations are stored with your account; the agent reads your most recent messages for context and periodically condenses older history into a summary. Every agent request is rate-limited per IP and bounded: a fixed cap on tool calls and a hard wall clock under a minute.
EU users' personal data is never routed to an LLM provider whose home jurisdiction has no EU adequacy decision. This is enforced fail-closed in code, from a single source of truth, and is covered by tests. It is a jurisdiction floor, not a full GDPR Chapter V transfer assessment.
TrustPages.subprocessorsLabel
12 third parties can touch the platform today, across the site and the browser extension. Each one exists for a single, named reason. 2 more are planned for the 2.0 release and are listed separately on the detail page.
Hosts this site and its serverless functions; Netlify Blobs is the primary key-value store for accounts, subscriptions, seat-report ledgers, audits, policies and vault documents.
System of record for user accounts, password resets, and the org backend v2 tables (orgs, memberships, invites, seats, subscriptions, policies, reports, audit, budgets).
Payment processing and subscription billing. Hosted checkout; card data never reaches our servers.
Routes AI requests (public audit reasoning, dashboard concierge, and the extension's AI vision-escalation tier) to the underlying model provider.
Claude models behind the public audit reasoning agent and the dashboard concierge, called via @anthropic-ai/sdk with tool_use (never a raw fetch).
Optional Google sign-in, and Google Web Risk as one provider behind /api/extension/url-reputation.
URL reputation provider behind /api/extension/url-reputation, called when IPQS_API_KEY is set.
Transactional email — onboarding, password reset, invite delivery, and the 6-digit email-verification code.
Breach-exposure lookups for the account email you ask us to check, and (v3, when HIBP_API_KEY is configured) for named-breach detail; falls back to a k-anonymity Pwned Passwords presence check.
URL reputation read behind /api/extension/url-reputation when VIRUSTOTAL_API_KEY is set. Removal approved (O9); it stops at the next production deploy.
Search of existing scans behind /api/extension/url-reputation when URLSCAN_API_KEY is set. Removal approved (O9); it stops at the next production deploy.
IP reputation behind /api/extension/url-reputation when ABUSEIPDB_API_KEY is set.
full detail, with what each provider receives and its region →
we do not sell personal information. full detail in the privacy policy.
TrustPages.reportVulnerability
If you find something, we want to hear it from you first. We publish a security disclosure file under RFC 9116 at /.well-known/security.txt, and reports go to security@syba.io. Reports are handled within 72 hours; critical findings within 24.
Good-faith research within scope falls under our safe-harbor policy: we will not pursue legal action for testing that avoids privacy violations and service interruption, interacts only with accounts you own, and gives us reasonable time to remediate before public disclosure.