Governance, not security. Judgment, not detection.
Before anything reaches a cloud AI, a local AI evaluates how sensitive your input is —
and the policy you wrote decides where it goes.
Who it is for
Freelancers and sole proprietors working under NDAs. Lawyers, accountants and other professionals whose duty of confidentiality is imposed by law rather than by contract. Anyone who wants the record of their AI use to stay on their own machine.
For these readers the question is rarely "is AI useful". It is "what may I put into it" — and that question is usually answered by memory and attention, on a busy day, one prompt at a time. Covenant moves the answer out of your attention and into a rule you wrote once.
How it works
A local AI on your own machine assesses how sensitive the input is. The evaluation itself never leaves your device.
You define what counts as sensitive and where it may go. Sensitivity levels run from L1 (public) to L4 (top secret), and you decide what each one means.
What was sent, when, and why it was judged that way — logged on your machine. You can produce an audit report yourself, without asking us.
Out of the box
Covenant ships talking only to a local AI on your own machine. No cloud provider is configured. Cloud AI opens only after you do two things yourself: register your own API key, and change the destination. Neither one alone opens it.
Once cloud is open, ordinary input goes there without ceremony. When your policy marks something highly sensitive, Covenant does not send it automatically — it stops and waits for you to approve. Continuing with the local AI instead of stopping is a routing rule you write in your policy.
There is no hidden block list. What stops and what flows is what your policy says. That is the point: the control is yours, and it is inspectable.
Availability and languages
We would rather you decide not to buy than be disappointed after you did. So here is the scope, plainly.
| Where it is available | English-speaking markets. ⚠️ Not available in the European Union. We have not yet evaluated EU distribution requirements, so we have chosen not to offer it there rather than offer it without meeting them. |
|---|---|
| Application interface | English and Japanese. |
| End User License Agreement | English and Japanese. The Japanese version is the controlling original; in case of any discrepancy, the Japanese version controls (Article 16, Section 4). Read the full agreement in English. |
| Customer support | English, by email (contact-us@exapolicy.co.jp). |
| In-app help | English and Japanese. |
| Evaluation policy shipped with the app | English and Japanese. |
| Sample policy templates | Provided in Japanese. They are a starting point to edit, not a required part of the app — you can write your policy in English from scratch. |
Requirements
Honest notes
Demo — the actual screen
A normal request goes through and is answered locally → an input containing an unreleased product name stops for your decision → the same is checked in batch, and the audit report shows where everything went.
Every name and number in the demo is fictional. Waiting time is fast-forwarded, as marked on screen; response time varies with your environment.
Get Covenant
The app installs at no charge. Using it requires an in-app monthly subscription — JPY 5,000 in Japan, USD 29.99 in the United States; other storefronts show the equivalent in your local currency.
Questions before you buy? Write to contact-us@exapolicy.co.jp — we answer in English.
