Security and privacy
Protect the private process while making the receipt verifiable.
Writing-process evidence can contain deleted thoughts, timing, account data, and unpublished material. HumanTyped separates the private session from the public receipt and collects only what the verification workflow requires.
Public/private separation
Receipt summaries are public only when shared; raw journals, private replay controls, and credentials stay off public routes.
Integrity before issuance
The server rebuilds the final text from ordered operations and rejects a normal seal when the result does not match.
Analytics minimization
Draft text, deleted text, keystroke events, raw timing, tokens, and private replay URLs are excluded from product analytics.
Data boundaries
The private workflow may process account information, ordered text edits, selections, session timing, integrity events, attached media metadata, receipts, and subscription state. It does not need clipboard contents, screen recordings, camera, microphone, location, or activity in unrelated applications.
Public receipt pages receive only the fields intended for readers. Private scoring features, raw journals, OAuth tokens, service credentials, and account-only controls must not be serialized into public pages or analytics events.
Receipt and media integrity
At sealing, server reconstruction checks the final text against the operation history. Digests bind the result, and the receipt signature lets the service detect later alteration of the signed payload.
Attached media is stored separately. The receipt can seal file hashes, type, size, and alternative text so the attachment set cannot change silently. Temporary signed access controls storage delivery; the hash does not prove who created the media.
Operational responsibility
Security also depends on access controls, secret management, dependency updates, logging discipline, retention jobs, incident response, and the providers used for hosting, database, email, billing, and X publishing. Credentials must remain server-side and never enter source control or public telemetry.
Users should protect their email account, review replay visibility, disconnect unused X access, revoke misleading receipts, and export or delete data through available account controls. Report suspected security issues privately rather than testing another user's data or replay.
Evidence, not certainty