Beta testing now open. Free places are limited. Join the beta

Security and data protection · for reviewers

Security review,on one page.

For the people who approve .said at your organization: how memories are protected, where they live, who can read them, and the documents your review needs. Honest about what is certified and what is not yet.

PlannedSOC 2

Not certified yet. SOC 2 is planned: a Type I report in 2028 and a Type II report in 2029. Until then we answer your security questionnaire.

In preparationData processing agreement

A DPA template with Standard Contractual Clauses is in preparation.

PlannedData region

United States by default. Your own servers or another cloud are planned for the Marfa release (April 2028), and a choice of cloud and region for Victoria (December 2028).

PlannedPenetration test

An outside penetration test is planned before the production launch.

How memories are protected

Private by default.Checkable by design.

Sealed secrets

Secrets are sealed in the Wallet, and the online copy is sealed. Whole-file encryption is planned for the Irving release (December 2027).

Admins manage, never read

Administrators decide who is in and which tools and company memories they may use. They cannot read anyone's personal memory.

Hash-chained and signed audit

Sign-ins, administrator changes, sharing, refusals and sign-on events are recorded append-only, hash-chained and signed with Ed25519, and kept while the company uses .said and 1 year after it is deleted. Verify in the Console, or run said-mcp verify-audit on the export with the public key at /.well-known/said-audit-key: it names the first broken or forged entry. Administrators get the latest fingerprint by email every month. What is in anyone's memory is never recorded.

Company sign-on

Microsoft 365, Google Workspace or your own identity provider over OpenID Connect or SAML 2.0, with SCIM provisioning, and you can require it for staff. Disable someone there and they cannot sign in to .said; with SCIM they are offboarded at once.

Offboarding from the next request

A revoked key is refused from the next request. Offline file leases end within 1, 7 or 30 days.

Restore as stored

Items are restored as stored, refused on a hash mismatch. Original files come back byte for byte for code and text up to 1 MB; full original-file rebuild is planned for the Guadalupe release (October 2027).

Where data lives

The edge is the connection,not the storage.

Your organization's .said files

Company memories stay in your organization's .said files: in your own private cloud or network, or on your people's devices.

The sharing hub

Connects your approved AI's to your memory and stores nothing. Always On keeps a sealed copy.

Billing

Stripe holds billing details only: the plan, the card and invoices. No memory content ever goes to billing.

Documents

Everything your review needs,in one place.

Data processing agreement (DPA)PDF · with Standard Contractual Clauses and the UK addendumDraft Request
Security questionnaireCAIQ Lite and SIG Lite answers, as a spreadsheetDraft Request
Subprocessor listPDF · the table below, with 30 days' notice of changesDraft Request
Architecture overviewPDF · the file, the edge and the Console, one diagram eachDraft Request
SubprocessorWhat it does for .saidData it seesLocation
CloudflareConnection edge; hosting of the .said cloud for Home and Work accountsConnection metadata; online memories for accounts that keep them in the .said cloudGlobal network
StripePayments and invoicesBilling name, address and cardUnited States
ResendSign-in and account emailsEmail addressUnited States
Report a security issue

Found something?Tell us first.

Email privacy@saidhome.com with the details. A person replies, and we tell you what we fixed and when.