Typezo
Book

TypezoSecurity

Security and data handling.

These are the clauses the statement of work is sold against, plus the limits of this version stated up front. They describe what the architecture does, including the part where prompts pass through our gateway.

Rider to the statement of work

Security and data · 6 clauses
  1. 1

    Dedicated, not pooled.

    One tenant runs on one instance, one volume, one Postgres database and one bucket prefix. Postgres listens on localhost only. There is no shared pool and no per-tenant DNS record to leave behind.

  2. 2

    Key destruction on deletion.

    One KMS key per tenant encrypts the volume, database and backups. Deleting a tenant destroys the key first, wipes the volume, purges the bucket prefix and emits a signed receipt within 30 days. Backups age out under the same key, so they become unreadable immediately.

  3. 3

    No training. No control-plane copy.

    Customer documents are never used for training, by Typezo or by a provider. Prompts pass through the model gateway to a zero-retention provider, contractually barred from training on or retaining them. The control plane forwards prompt bytes in memory but does not write request or response bodies to disk and keeps no document text in its database.

  4. 4

    No standing support access.

    Tenant instances have no public SSH. Administrative access is SSM Session Manager, recorded in CloudTrail. Support access is a tenant-issued, time-boxed grant, visible in the tenant audit log, not a permanent account.

  5. 5

    Owner-approved break-glass.

    Break-glass requires TOTP plus a one-time code to the verified owner, is scoped to one IP, expires in eight hours or less, is written to the audit log and auto-expires. The owner approves every exception.

  6. 6

    The knowledge base is tenant data.

    Help desk articles are ordinary documents and spans in the tenant database, under the same key and the same deletion path as a solicitation. The control plane stores product entitlements; it stores no article text.

Certification: Typezo does not hold FedRAMP, CMMC or SOC 2, and nothing in this rider implies one. The honest security answer is that Typezo forwards documents to a zero-retention provider and does not store or log them at the control layer. It is not “we never see your documents”.

What the control plane sees

The model gateway is in the request path, so the control plane holds prompt bytes in memory for the duration of a call. It does not write request or response bodies to disk, does not log them, and does not persist them in its database. The control database holds routing metadata, billing, audit rows and provider configuration, and no document text.

The honest version of that sentence is “Typezo forwards your documents to the model provider and never stores or logs them at the control layer”. It is deliberately not “Typezo never sees your documents”.

Keys, deletion and logs

One KMS key per tenant encrypts the volume, database and backups, and deleting a tenant destroys the key first. Deleting a workspace deletes documents, extracted text, spans, embeddings, answers and exports. Backups age out under the same key, so key destruction makes them unreadable immediately.

Logs are allowed to carry ids, stages, durations, token counts, status codes and error codes. They are not allowed to carry document text, quotes, answers, prompts, completions, email addresses or tokens. The audit log records authentication, document access, export, allowlist changes, admin actions and support sessions; it is append-only and hash-chained, so modifying a row is detectable.

The provider rule

A provider is selectable for customer documents only if it contractually does not train on inputs and does not retain them. Bedrock, Anthropic direct, Azure OpenAI and Ollama Cloud are the default-eligible set after a residency review. The UI shows which provider a workspace used, and an export made while a non-compliant provider was configured is labelled in the audit trail.

Limits in this version

  • No FedRAMP, CMMC or SOC 2 authorization is held, and none is implied by anything on this page.
  • Uploads only. There is no URL ingestion, so a solicitation cannot be fetched from a link.
  • Help desk roles come from a deployment allowlist in this version; an in-product role editor is not built.
  • SSO and custom domains are not built. The tender workspace is one login.
  • Narrative bid sections are not generated. The output is a compliance matrix and a requirement-by-requirement draft.
  • English and US solicitations only, one solicitation plus up to 20 company documents per workspace.

The run itself — what the verifier re-checks, and what the tool will not do — is described on the technical details page.

Book a 20-minute walkthroughOpen the sample workspace