Trust
What leaves your machine, and what never does.
Jorv is downloadable software. Your work, your record and your keys stay on the machine or server where you installed it. This page says exactly what travels, to whom, and why, in plain words, so your security team can read it instead of sending us a questionnaire.
Where each kind of data goes.
| What | Where it lives | Who can see it | Leaves your machine? |
|---|---|---|---|
| Your work and your recordMissions, items, documents, decisions, files | Your machine, your server or your cloud account | You and the people you give access to. Never us. | No. |
| AI requestsThe text and files you ask the AI to work on | Sent directly to the AI provider you chose, under your own key; or nowhere, with a local model | That provider, under its terms. Never us. Jorv shows you every call. | Only to your provider.None with a local model. |
| Your AI keysProvider API keys | Encrypted on your machine, in the engine's vault | Only the engine. Never us. | No. |
| Your licenceYour Microsoft or Google sign‑in email, your organisation's name, the tier and seat count | Our licence service, in Australia | Us, to issue and renew the licence. This is the only data of yours we hold. | Yes, to us.When it is issued and renewed. |
| PaymentCard, invoice, tax details | Paddle, our merchant of record | Paddle, under its terms. We never see card numbers. | Only to Paddle.When you pay. |
| Usage dataTelemetry, analytics, crash reports | None is collected by default | Nobody. A crash report is sent only if you choose to send it, and you see it first. | No.Unless you send a crash report. |
Read more about where Jorv runs and your own AI keys on Your data.
How the software itself is protected.
Signed releases
Every build is signed by Atmospherique Pty Ltd and published with checksums. The licence is verified against a root key held in a hardware key service; the signing key is never on a laptop.
One engine, written in Rust
Memory safety checked by the compiler; thousands of automated tests before every release; dependencies scanned on every change.
Access and the record
Access follows the work; every act is written once; everything published states the AI's involvement. On every tier.
Offline and air‑gapped
An offline licence and local models for networks with no path to the internet. Enterprise adds control over what may leave the network.
Reporting a vulnerability
Write to security@jorv.ai. We acknowledge within two working days, fix on a published timeline, and write up what happened here.
Independent review
A dated third‑party code and penetration review, with the report linked here, is planned. Until it is done, this line says so.
Certifications, honestly.
We hold no SOC 2 certificate, and no ISO 27001 or ISO 42001 certificate yet, and we say so rather than imply otherwise. Those frameworks certify how a vendor runs the systems that hold your data. Jorv holds none of your data except your licence details: it runs on your infrastructure, under your controls, inside whatever certification your own environment already has.
What we do instead: this public trust page, saying exactly what travels and how releases are signed and vulnerabilities handled; a dated independent code and penetration review when it is done; and a security self‑assessment. If your procurement needs a questionnaire answered, send it; we answer it in full and publish the answers here.
Privacy
The licence details we hold are handled under the Australian Privacy Act.
AI regulation
The write‑once record and the statement of AI involvement are what these rules now ask of you; Jorv keeps them as a matter of course.
- 22 Jul 2026 · Tax Practitioners Board: an AI platform is a third party; client permission before disclosure
- 2 Aug 2026 · EU AI Act Article 50: transparency about AI involvement applies
- 10 Dec 2026 · Privacy Act: transparency over automated decisions
- Dec 2027 · EU AI Act Article 12: logging for high‑risk systems
- Oct 2025 · Australia's AI6 guidance on human control and shared information
Status and incidents
The licence service and this site are the only things of ours that can go down. A status page is coming; until then, any incident is written up on this page.
The activity record
The auditor's question, answered before it is asked.
Who read what, who drafted, who approved, which model, which sources: written once, never quietly changed.