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
- Every organization is a tenant. The tenant comes from your verified sign-in on the server. A request cannot choose one.
- Isolation is enforced in application code and again by row-level security in Postgres. Tenant-private tables cannot be read unless a trusted tenant is set for the transaction, and the database refuses everything else.
- Tarmiq’s database, sign-in, storage and keys belong to Tarmiq alone.
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.
- Private: only the member who recorded it.
- Team: that member and the active members of one named team.
- Organization: every member of the organization.
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:
- Sign-in. Proving who you are, through our authentication provider.
- Mailbox access. Not requested in the private beta. If it is ever offered, it will be a separate, optional consent with least-privilege scopes.
- Network contribution. There is none. Contributing anything to a shared network would need its own explicit, documented, revocable permission. Today the setting is “none” and the database enforces it.
Your data never becomes shared network data
- Your searches, research, supplier history and outcomes are not pooled with other customers’ data and are not used to train models.
- Every piece of evidence carries a rights class: public reference, private to your organization, or model inference. Research reads only public reference data and your own organization’s data.
- Licensed data is used only under your own rights and credentials, and is never redistributed.
AI is bounded
- Optional. AI-assisted review runs only when Tarmiq has configured a provider, and the Copilot that answers questions about a part is deterministic.
- Public evidence only. When a model is used, it receives public reference evidence only. It never receives your notes, customer references, memory or identity.
- Closed vocabulary. A model chooses from a fixed set of options and must cite evidence that exists in the run. Tarmiq writes the sentences. A model cannot mark anything “confirmed”.
- Citations or silence. Answers cite their evidence, or say there is not enough.
Nothing goes to a supplier unless a person sends it
- Tarmiq prepares drafts. It has no capability to send email to a supplier.
- A person reviews each draft and sends it from their own email app.
Where data is processed
- Providers: Clerk for sign-in, Neon for the database, and Render for hosting. Anthropic is an optional AI provider that receives public evidence only.
- GoHighLevel is used for marketing and early-access requests only. Product data is never sent to it.
- Google Tag Manager measures visits to this marketing website only. It is not part of the Tarmiq application, and no product data is sent to it.
- Details are in the privacy draft.
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
- An independent external penetration test.
- A formal support-access process. Tarmiq does not browse customer workspaces in ordinary operation, and a time-limited, reasoned, audited access process is being built before paid use.
- Enforced multi-factor sign-in for administrators.
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.