Intramedial decides what agents may do and keeps the record. This page sets out how that works, what is pinned and where, and what we have not published yet. It claims no certification. Each statement links to the document or source behind it.
Legal entity Avonao, Inc., DelawareLegal documents last updated November 5, 2026
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
© 2026 Intramedial. All rights reserved. Intramedial is a product by Trustvice. Secured and supercharged by Avonao Labs.
Report abuseEvery action follows the same path. The gateway resolves the workspace, Intralock admits or refuses the declared intent, and the decision is appended to the ledger in the workspace's region. A bundle can be sealed from it.
The gateway resolves the workspace key to one workspace before any module runs. How keys are stored and how long they last is not yet published.
The request goes to the workspace's region. Once a region is live, an EU-bound request that reaches another region is refused with a 421, not served there.
Intralock is a pure function with no network call and no model. It admits the intent under a lease or refuses it with a reason, and the decision is appended.
On request, a range of the audit chain is sealed into a Merkle-rooted bundle and signed with Ed25519. The signer prefers the region's key; with none at all, it answers 503.
The bundle names its key id. Anyone with the bundle and the public key can check it offline with the verifier source, for as long as they hold that key.
A bundle is a precise, narrow statement. Read both columns before you rely on one, and before you ask someone else to.
Verification is independent. Trust is narrowed to a short, named list.
| You trust | Why | If it fails |
|---|---|---|
| The public key you verify against is ours | A signature shows who holds a key, not whose key it is. | A substituted key makes forgeries look valid. Pin the key id yourself. |
| Our signing keys are used only by the ledger service | The service seals what its code decides to seal. | A misused key could seal records that never happened. |
| We record admissions honestly, as written | Ledger rows say the plane saw this. | A compromised plane could write a false ledger row. |
| Our clock | Sealing time is our server time, too. | A skewed clock gives a wrong time. |
Ed25519 keys, one per jurisdiction, are shared by all workspaces there. Their public halves are meant to be published openly; the private halves are Worker secrets. Live serving of the key set is not confirmed.
| Address | Content |
|---|---|
https://intramedial.com/.well-known/ledger-bundles-keys.json | The key set, at its documented path now |
https://ledger-bundles.api.intramedial.com/.well-known/ledger-bundles-keys.json | The same key set, on the ledger worker's own host name today |
/api/v1/ledger-bundles/anchors | The anchors of the bundles already sealed |
/api/v1/ledger-bundles/snapshot | Creates a bundle (paid plan) |
Verifiable
curl -sSL https://ledger-bundles.api.intramedial.com/.well-known/ledger-bundles-keys.json -o keys.json
jq -r '.keys[] | [.kid, .jurisdiction] | @tsv' keys.json
// kid names the key; jurisdiction says which region'sFor the strongest position, fetch a key once, store its kid and x value in your own repository, and verify against that copy. /docs/ledger-bundles-snapshot
Every request carries a credential that the gateway resolves to one workspace before any module runs. What follows is what we can state today; the rest is marked not yet published.
The gateway resolves a workspace key (prefix av_workspace_) to one workspace. How keys are stored, how long they last and how they rotate is not yet published, so none of that is stated or implied here, at all.
Sign-in goes through Avonao ID. Session lifetime, idle timeout and cookie settings are not yet published here, so they are not stated. Plan on nothing beyond what the sign-in page shows.
A write that needs confirmation is refused until an approver issues a token. Eight scopes need two different administrators, and the break-glass seal is written to the ledger first.
Each region has its own database, and its workers read only that database. How tenants are separated inside a region is not yet published, so no claim is made about it on this page.
Intralock admits an intent only under a lease, within a mandate, and refuses it with a reason otherwise. Agents hold no standing cloud keys: iam.assume issues credentials that never outlast the lease.
An emergency stop halts agents, and quarantine isolates one. Request rate limits and abuse detection are not yet published, so no figure is stated for either of them, and none is implied.
Stated limits: credential storage, key lifetimes, session settings, rate limits and tenant separation inside a region are not yet published for Intramedial. Until they are, treat none of them as a commitment from us, and ask sales if one of them matters to your review.
The plane records the intents agents declare: an actor, a resource and a verb. It does not need the content of the work to admit or refuse it, and it keeps no copy of it.
An agent declares actor, resource and verb. That is what Intralock sees, not the work's content.
Intralock makes no network call and uses no model, so a decision depends on the intent, the lease and the mandate alone.
Records are appended under Merkle roots, and a bundle seals a range. Redaction and erasure routes are not described here yet, so nothing is claimed about them. Ask us if this matters to your review.
Actors, resources and verbs are in clear text in the ledger. Put nothing there you would not show its reader.
Coordination records, leases and the ledger are stored in the region chosen when the workspace is created. Billing runs in US West, and the operator planes are single. Asia-Pacific and Oceania are best effort only, by Cloudflare location hint, not pinned.
| Region | Code | Host prefix on the site | Storage |
|---|---|---|---|
| US West | wnam | us-west. | Location hint |
| Europe (EU) | weur | eu. | EU jurisdiction (enforced) |
| Asia-Pacific | apac | asia. | Location hint |
| Oceania | oc | oc. | Location hint |
A region says where data is stored. Rehoming copies a workspace's records to another region on request. An EU-bound request that reaches another region is refused with a 421.
Traffic reaches the service over HTTPS through Cloudflare. We state no encryption-at-rest detail of our own; what Cloudflare documents for its storage is Cloudflare's statement, not ours. Bundles are signed, so a change is detectable by whoever verifies one.
Deleting an account starts a 30-day grace period. When it ends, the erasable data is removed, and append-only audit rows that must remain are kept with a recorded reason. The Privacy Policy and the DPA are the binding text. A bundle you already hold stays verifiable by you whatever we do, because the check is offline and uses only the bundle and a key.
Privacy PolicyData regionsExit and recovery goalsSub-processors
Status is not published yet, and no service level is promised here at all. Verification never depends on us being up, because it runs offline.
For Enterprise plans with a signed order form, the Enterprise SLA sets the terms. Support is staffed during business hours and acknowledges Enterprise requests within 1 business hour, 4 business hours or 1 business day by severity. Self-serve plans carry no uptime commitment or service credits; their support response targets are on the pricing page.
| Monthly uptime | Service credit |
|---|---|
| Below 99.9%, at least 99.0% | 10% of the monthly fee |
| Below 99.0%, at least 95.0% | 25% of the monthly fee |
| Below 95.0% | 50% of the monthly fee |
| Severity | Meaning | Acknowledgement target |
|---|---|---|
| Severity 1 | Production use is blocked, or agents cannot be admitted at all, for a customer. | 1 business hour |
| Severity 2 | A major feature impaired or degraded, with a workaround. | 4 business hours |
| Severity 3 | A minor problem, question or request. | 1 business day |
No termination or refund right tied to uptime is published, because no uptime commitment is. Any such right would be in a contract with sales.
Verifying a bundle needs only the bundle and a public key. It keeps working when our service does not.
What we commit to when something goes wrong, and how to tell us about a weakness before anyone else finds it.
We notify the account owner by email without undue delay and in any case within 72 hours of becoming aware of a breach affecting customer personal data, with what is known: its nature, the people and records affected, the likely consequences and the measures taken. The notice is supplemented as we learn more.
Incidents will be published on the status page once it exists. Today there is no status feed, so none can be shown there. We name no notice period for Enterprise customers on this page; any would be in a contract.
Report through the form, with your contact details or anonymously, or by email. Good-faith research under the policy is authorised, and we will not take action against you for it.
| Step | Target |
|---|---|
| Acknowledge your report | Within 3 business days |
| Initial assessment and severity | Within 10 business days |
| Updates while the issue is open | At least every 14 days |
| Fix for critical and high severity | We aim for 30 days |
| Fix for lower severity | We aim for 90 days |
Targets, not guarantees. We ask for 90 days before public disclosure. There is no monetary bug bounty; we credit researchers by name on request.
This page claims no certification, audit or attestation. Each row says what is documented; the linked document is the binding text.
| Item | State | Detail |
|---|---|---|
| Data Processing Addendum | Not claimed | The addendum is among the legal pages. This page makes no claim about its terms. |
| International transfers | Not claimed | Transfer mechanisms are for the DPA to state, and it is the binding text. This page makes no claim about them and cites none. |
| Article 27 representatives | Not claimed | Representatives and contact details are for the Privacy Policy and the Imprint to state. No claim here. |
| Sub-processor changes | Not claimed | The list and its change terms are in the Sub-processors document. This page makes no claim about them. |
| Privacy rights requests | Not claimed | Receipt confirmed within 10 days; answered within one month under GDPR and UK GDPR, or 45 days under US state laws. |
| Security pack | In place | A short overview and a questionnaire that mostly says not yet answered, to read online or download. |
| Security questionnaire | Not claimed | Written answers to a reasonable questionnaire within 30 days, under DPA §9. |
| Customer audit | Not claimed | Customer audit terms are for the DPA to state, and it is the binding text. This page makes no claim about them and promises none. |
| Sub-processor compliance reports | Not claimed | No provider compliance report is cited or offered from this page at all. |
| Bug bounty | Not offered | No monetary rewards. Researchers are credited on request. |
Every legal document on this site, with the date of its current version. These pages are the binding text; this page only lists them and states no term of its own, so read the document itself first and in full.
| Document | What it covers | Updated |
|---|---|---|
| Terms of Service | The agreement for the website, API, MCP gateway and dashboard, as the document itself states it, in full. | |
| Privacy Policy | What personal data is processed and how, as the document states it, and how to exercise your rights. | |
| Data Processing Addendum | Processor terms, as the document states them: security measures, breach notice, audits and transfers. | |
| Sub-processors | The providers that process personal data, as listed in the document, and how changes are announced. | |
| Cookie Policy | Cookies and browser storage on our sites, as the document states them, and how to change your choice. | |
| Acceptable Use Policy | What may not be done with the service, how it is enforced and how to report abuse. | |
| Responsible disclosure | How to report a vulnerability, what is in scope, safe harbor and response targets. | |
| Digital Services Act | Points of contact for EU authorities and users, and notices of illegal content, as the document itself states them, in full. | |
| EU Data Act | Switching to another provider, exporting your data, and where each service runs, as the document states it. | |
| EU AI Act | How the EU AI Act applies to Intramedial and its evidence packs, as the document states it. Packs map controls and never certify. | |
| Right of withdrawal | For consumers in the EU and the UK: withdrawing from a paid plan, what you get back, and the model form to use. | |
| Imprint · Impressum | Who publishes the site, where the company is registered and its representatives, as the document states it. Also in German. |
Running a vendor review? Tell us what you need. We answer questionnaires in writing, and say plainly when something is not yet published.
Written answers within 30 days, as the DPA sets out. Send it to privacy@intramedial.com.
Email privacy@intramedial.com →EnterpriseFor an Enterprise evaluation: data residency, custom retention and the procurement paperwork.
Contact sales →SecurityQuestions about the security model, bundle keys or a finding. Vulnerabilities go through the report form.
Contact security →PrivacyData subject requests, sub-processor objections and questions about the DPA.
Contact privacy →Seeing Intramedial used against your systems? Report abuse →
