Redaction#
Before the service stores a line, it replaces thirteen kinds of value with placeholders such as [[ip:3]]. It keeps the real values in a separate store, the vault. The kinds are:
- connection strings that carry credentials
- IP addresses
- geographic coordinates
- Wi-Fi access point addresses
- Open Location Codes
- IMEI numbers
- email addresses
- payment card numbers
- US Social Security numbers
- credentials, such as passwords and API keys
- money amounts
- phone numbers
- tokens and private keys
The rules:
- Transcript lines, desktop activity, feed rows, the timeline, the journal, wiki pages, comments and heads-ups carry the placeholders, in storage, in exports and when a model reads them. Only the displays for authorized readers resolve a placeholder to its value.
- Redaction does not cover recordings, meeting names, recaps, work outputs or intelligence documents.
- Redaction finds the shapes above. It does not cover names or topics, or a value with no label and no known shape.
- If the redactor cannot process a line, the service never stores that line raw.
- A message a person types to their assistant goes to the model as typed. The service stores it redacted, with two exceptions: the copy that waits for an answer, and the copy the assistant keeps to continue a discussion about another person’s records.
Encryption#
- Every connection to the service uses TLS.
- The database is encrypted at rest. It sits in an isolated network segment and accepts no connection from the internet.
- The storage buckets for recordings and for the deletion ledger block all public access, enforce TLS and encrypt every object at rest.
- A desktop holds no cloud credentials. It uploads each part of a recording to an address that the service signs for one hour, with the part’s checksum signed in.
- The service verifies the whole file before the desktop deletes its copy. A playback address lasts 15 minutes and goes only to a reader the permission check allows.
Your AI provider and your key#
- Your organization chooses one model provider and brings its own key. The service has no provider key of its own.
- The service seals each key with AWS Key Management Service (KMS) under a context bound to your organization. A sealed key opens only to make a call. Admins can see that a key is set, never the key itself.
- Every model call goes from the service directly to your provider. There is no proxy, no second provider and no fallback. The service adds no tracking fields to the request.
- A model address your organization sets must use HTTPS, carry no credentials and resolve only to public IP addresses.
- The service makes no outbound call except to AWS, to your identity provider and to the model provider your organization chose. It never searches public tool registries.
Tenant isolation#
- The database keys every content row by organization and by person. The deletion of an organization cascades to every row it owns.
- Objects in storage sit under a prefix for your organization. The service uses ids of its own, never your identity provider’s ids.
Related#
- Model & provider: the provider, the key and what your provider receives.
- Retention and deletion: how long each kind of data is kept.