Trust & data boundaries
Sources, review states and limitations belong in the record. The same principle applies to how we operate Epok.
Read our current posture01 / Evidence
Epok stores system facts, linked model and dataset records, evaluation and runtime evidence, reviewer notes and source-mapped draft sections. Draft documents use recorded evidence and deterministic templates. A reviewer can see what supports a statement and what remains missing.
02 / Private beta
Access is invite-based. Agree the systems, reviewers, evidence types and data-handling expectations with the Epok team before bringing production material into the workspace. Hosting, retention and enterprise deployment requirements need an explicit discussion; they are not implied by beta access.
03 / Your team’s controls
Your team selects the system context and evidence it provides, identifies accountable reviewers and decides what may be used in an internal pack. Start with metadata, synthetic, de-identified or already-reviewed evidence. Review workspace permissions and data obligations before uploading sensitive or personal data.
04 / External processing
Configured research features may send selected context to external providers when requested. Review that context and the provider setup before use. Keep API tokens and dataset credentials in your own environment or secret manager, outside prompts and evidence uploads.
05 / Review boundaries
An accepted internal finding is not automatically accepted governance evidence. An Evidence Pack is an internal review draft. Epok does not provide legal advice, certification, regulatory approval or a compliance guarantee.
Confirm access responsibilities, sensitive-data policy, hosting, retention and export expectations with us. We do not advertise SOC 2 certification, a standard self-hosted offering or enterprise service guarantees.
Scope a beta workspaceStart with one AI system
Private beta. A focused scope, agreed with your team.