Trust
Built to be allowed inside a regulated organisation.
Written for the CFO, the CISO and the head of compliance who decide whether a pilot can start. It covers what is in place today and says plainly what is not.
Opens an email to hello@pinavia.io.
Who decides
Your people. Pinavia prepares, checks and drafts. A named person in your organisation approves before anything becomes the record or leaves the workspace.
What is traceable
Every point links to the passage it came from.
Evidence that arrives without provenance, or with low extraction confidence, is quarantined until a person approves or rejects it. Where the evidence is too thin to support an answer, Pinavia says so instead of producing a plausible one.
Who sees what
People see only what their role allows, and the filtering happens before anything is retrieved. Access is authenticated and scoped to your workspace, restricted material is held back from retrieval, and each assistant works under a control profile that limits which evidence it may read. What it is refused is written to the audit trail.
Messaging surfaces carry less than the workspace: content linked to restricted evidence is blocked there, with a pointer back into Pinavia instead.
What becomes the record, and when
Nothing becomes the record until your people confirm it. Promoting a finding, approving a recommendation and sending a pack out each pass an approval gate held by a named person.
Each of those actions is written to an audit trail of who acted, on what, and when. Your administrators can export it.
Deletion
On written request, Pinavia runs a workspace purge that removes your workspace's content, and the records derived from it, from the production database, and confirms in writing what was removed.
Three things sit outside the purge, and we say so here rather than in small print: original files in object storage are held under a retention lock, backup copies expire under their own retention settings, and the audit record of the purge itself is kept.
Where it runs
Pinavia runs on managed cloud platforms. Traffic is served over TLS, and the platforms encrypt stored data at rest. Hosting locations are answered on request and listed with the subprocessor list.
Certification
SOC 2: certification under way, completing Q4 2026. Pinavia does not hold ISO 27001 certification today, and an external penetration test has not yet been completed.
Subprocessors and data processing agreement
A data processing agreement template and the full subprocessor list are available on request.
What Pinavia does not do
- It does not approve, file or sign. A named person in your organisation does.
- It does not write back to your source systems.
- It does not send anything outside the workspace without a person's approval.
The detail behind this page: Security · Data processing
Request the buyer pack