Security & data principles

Built for competitors to share a product, never data.

Sourcing knowledge is competitive. This page states plainly how Tarmiq keeps each organization’s data its own. Tarmiq is in private beta, and this page describes what is built and tested today, not what we hope to build.

Tenant isolation is enforced in the database

Memory visibility: private, team, organization

Records in your organization’s memory, such as companies, contacts and observations, carry a visibility chosen by the person recording them.

The database enforces this for the acting member. Admins and owners cannot read private memory in ordinary use. A record can never be visible to a wider audience than the thing it is about. Any exceptional governance access is a disclosed organization policy, off by default, limited in time, requires a stated reason, is audited, and is visible to the person concerned.

Three separate permissions

These are never bundled:

Your data never becomes shared network data

AI is bounded

Nothing goes to a supplier unless a person sends it

Where data is processed

What we do not claim

Tarmiq has not been audited or certified. We do not claim SOC 2, ISO 27001, ITAR, EAR, FedRAMP or CMMC compliance, or any other certification or compliance status. Please do not enter export-controlled technical data into the private beta.

Not done yet

Reporting a concern

Use the early access page to reach us. A dedicated security mailbox will be published here.

Last updated October 2026. This page describes the private beta and will be expanded before general availability.