SECURITY · ALPHA DISCLOSUREAPRIL MMXXVI
Honest about alpha.
Dossier is a portfolio pilot. The posture below reflects where we actually are today — not where we would be if we were selling into a regulated buyer. If you are considering Dossier for a real IC, read this page first.
Data handling.
- — Only public surfaces are crawled. No authenticated content is ever fetched.
- — No user-uploaded documents are accepted in alpha.
- — Memo drafts persist only in the analyst's browser (localStorage); no server-side database.
- — Signed memos are rendered statically and served from Cloudflare's edge cache.
Model provenance.
- — Drafts are composed from deterministic pipeline stages, not a single end-to-end model call.
- — Each stage logs its prompt, its model version, and its output hash.
- — No inference is run on customer prompts from one memo that affects another.
- — Model context windows are never cross-contaminated between deals.
What we don't have yet.
- — SOC 2 attestation.
- — SSO / SCIM.
- — Per-tenant data residency.
- — A formal data-processing agreement.
We will ship these in order, with a deadline, when a paying customer asks. We will not lie about having them in the meantime.
Signed outputs.
- — Every memo is signed with the pipeline version that produced it.
- — Editing the signed copy breaks the hash; the reader surfaces this visually.
- — A memo can always be re-derived from its URL input and pipeline version — the audit trail is the artifact.
SECURITY CONTACT · security@dossier.alphalast updated · 2026-04-21