Enterprise-grade by construction, not by checklist.
pm.gold's guarantees are enforced in the data layer, so they hold even when something above them has a bug. This page describes what is built and provable today, and what is on the certification roadmap — labeled honestly, because that is the product's own standard.
Architecture guarantees
Enforced structurally in the database and proven by automated checks that run against the live system.
Tenant isolation, fail-closed
One private workspace per company. Row-level security is enabled and enforced on every content table, and it fails closed: a request without verified workspace context returns nothing — no context, no data. Cross-tenant isolation is exercised by live checks, not assumed.
Unforgeable identity context
Workspace and permission context is derived server-side from the verified session — never from client-supplied values. Membership and role are checked live on each request, so revocation takes effect on the next request, not the next login.
Permission-faithful knowledge
Source-level permissions are captured at ingest and enforced at retrieval through a single choke point. Content with unknown or missing permissions is quarantined — fail closed. Derived artifacts inherit the intersection of their sources' permissions; widening happens only through a governed, human-approved declassification step.
Human-in-the-loop commit gate
Agents propose; a person approves or rejects. Maker and checker are separated at the type level — the generation path has no commit capability. Nothing enters the record automatically.
Append-only audit
Every agent action, generation, approval, override, and administrative action is recorded with actor, timestamp, and source. The audit trail is append-only by database grant: no application role — including platform operators — holds permission to edit or delete entries. Audit records are content-free and outlive the records they describe.
Operators cannot read your content
Platform administration is a separate plane with zero grants on content tables — a content read by an operator is denied at the database, a property we probe directly. Any operator joining a workspace is an explicit, audited membership event that cannot be hidden or erased by the operator. There is no impersonation feature, by decision.
Prompt-injection defense
Ingested content is treated as data, not instructions. The structural injection paths are closed deterministically, and synthesis-content integrity is measured and reported as a metric — not claimed as an absolute.
Real deletion
Erasure both revokes access immediately and destroys the verbatim content — stored text, embeddings, and cached citation snippets — across all versions, in one atomic operation, leaving a content-free tombstone. Derived sections that mixed erased and surviving sources can be re-grounded from surviving sources only, making the replacement byte-clean by construction.
Honest scope. "Append-only" here means append-only against every application and operator role — the threat model that matters for insider misuse. It is not yet a cryptographic WORM store; a tamper-evident hash chain is the named upgrade for buyers who require provably untampered audit.
Identity & access
Bring your identity provider; keep your access rules.
SSO through your identity provider (Microsoft Entra ID or Google) via OIDC/SAML, bound to your tenant — we never see passwords. SCIM directory sync keeps membership and groups current, so your directory remains the source of truth for who can see what. RBAC separates what users can do (owner, admin, member, viewer) from what they can see (content permissions) — a workspace admin does not automatically read restricted content. First sign-in provisions a least-privilege account just in time.
Encryption & infrastructure
In transit: TLS 1.2 or higher. At rest: AES-256 via our managed cloud infrastructure. Secrets are held by environment reference only — never in code or documents. Dedicated single-tenant deployment is available for pilot customers with isolation requirements. Schema changes are forward-only and versioned.
AI & model security
Foundation models are accessed through commercial APIs behind a model-agnostic seam. Your content is not used to train generalized models — by API terms, and contractually in our DPA, passed through to subprocessors. Each generation cites its sources, and ungroundable claims are flagged rather than fabricated. Model calls carry cost and latency telemetry with personal information redacted. Bring-your-own-key is supported for teams that prefer their own provider relationship.
Compliance & certification roadmap
Where we are, stated plainly. Documents available on request under NDA: security@pm.gold.
| Item | Status | Notes |
|---|---|---|
| DPA with no-training commitment | AVAILABLE | Standard DPA for pilot customers; AI no-train terms passed through to subprocessors. |
| Security questionnaire (CAIQ-Lite) | ON REQUEST | We complete a CAIQ-Lite self-assessment on request for security reviews. |
| Subprocessor list | PUBLISHED | See Privacy Policy §7; change notice per DPA. |
| SOC 2 Type I | PLANNED | Targeted as we onboard our first production customers; controls are being built toward it. |
| Penetration test | PLANNED | Independent test planned; summary shareable under NDA once complete. |
| SOC 2 Type II / ISO 27001 | PLANNED | Follows Type I on the certification ladder. |
| Data residency options | PLANNED | Regional deployments when customer requirements demand. |
| DSR (subject-rights) workflows | IN PROGRESS | Erasure machinery built; access/correct/export workflows being productized. |
Responsible disclosure
If you believe you've found a vulnerability, email security@pm.gold. We commit to acknowledging reports within 2 business days, will not pursue good-faith research conducted within scope, and will credit reporters who wish to be named.
Questions
Security reviews move faster with the right documents. For the DPA, questionnaire responses, or a walkthrough of the architecture above: security@pm.gold.
Status markers reflect our program as of the date above and will change as we progress — we label what is built versus planned honestly and update this page as milestones are met. We are also finalizing our formal documentation with counsel. Provided for transparency; not legal advice.