No adjectives — statuses and dates

What we can prove today.

This page is written for the person who runs vendor risk. Where we hold a certification, it is named with a date. Where we do not yet, it says so. Anything marked “on request” is delivered under NDA within five business days: hello@amahub.io.

Certifications & assessments

Item	Status	Detail
SOC 2	Preparing	Controls mapped, evidence collection underway; Type I audit is the next milestone. We do not claim “SOC-grade” anything until the report exists — the trail-log design is documented and reviewable on request.
HIPAA	BAA on Enterprise	We sign a BAA on the Enterprise tier. Model traffic runs under your own provider agreement (your key, your BAA with the model provider) or under ours where offered — stated explicitly in the order form, never implied.
Penetration test	Scheduled	First external test is scheduled; summary letter will be available here and under NDA.
GDPR / DPA	On request	DPA with SCCs available for review before any data is connected.

Sub-processors

Everyone who touches your data, and what they touch. Changes are announced to admins before they take effect.

Vendor	Role	Data	Region
Anthropic	Model inference	Prompts and tool results of your sessions	Per your provider agreement (BYO key) or ours
Fly.io	Hosting: runtime, API, database	All workspace data at rest	Frankfurt (EU) by default; per-tenant region pinning
Resend (AWS SES)	Transactional email	Recipient address and message content of sign-in and alert emails	sa-east-1
Google Workspace	Corporate mailbox (hello@)	Email you send us	Google EU/US

How data is handled

· Per-person permissions — the agent inherits the individual's access via their own connector credentials, never a shared super-user.
· Egress default-deny — outbound traffic passes one gate; every allow and deny is logged with host, bytes and session.
· Credential vault — connector secrets are injected at call time and are not readable by the agent runtime; secret patterns in payloads are redacted at the gate.
· Trail logs — every session keeps a per-action trace (prompts, tool calls, egress decisions, cost). Retention: the life of the contract; export any time.
· Kill switch — owner, admin, or automatic policy can stop a session mid-step; the stop is itself logged.

Your exit

Audit logs, promoted processes and artifacts export in JSON/CSV at any time and on termination — the compliance record is yours, not a hostage. Workspace data is deleted on written request after export, with deletion confirmed in writing.

Questions we expect

Whose invoice carries model spend on each tier · how spend caps reconcile against provider billing · SSO and SCIM setup · region pinning per tenant · what happens to live sessions when a person is deprovisioned (they are cancelled) — ask, and you get the current written answer, not a demo: hello@amahub.io

← Back to amahub.io last updated 20 Aug 2026 · changes to this page are versioned in git