Built for privileged work.

The requests, messages, attachments and documents that reach Neomatter through the channels and systems you connect, and the matters and work Neomatter produces from them.

It is encrypted in transit and at rest, scoped to your organization on every request, and every sensitive read or change is recorded in an audit log. Connection tokens are envelope‑encrypted, and production cannot start with default secrets.

No. Your data is never used to train generalized, public or third‑party AI models. Model requests run with response storage turned off, and only the content needed for the task is sent. Our AI provider may keep limited records for security and abuse monitoring under its terms.

Only the channels and systems you connect, with the narrowest permissions that work. Where read‑only access is enough, that is all Neomatter asks for.

No. Neomatter does the work and drafts the reply. A lawyer makes the call and presses Send.

Yes. An administrator can export your organization’s data or delete it. Deletion removes your data and revokes every connection token. Some records may be kept where security, legal or backup obligations require it.

We have completed a SOC 2 Type I audit by a licensed CPA firm, and our SOC 2 Type II audit is in progress. Dependency, code and secret scanning run on every change, and cross‑tenant access is covered by automated tests.

Email security@neomatter.com. We respond to every report.