Verifier Terms

You do not need an account, a key or our permission to verify a bundle. By relying on a bundle you accept these terms.

In plain language: a valid bundle proves that Intramedial signed these exact fields, covering these exact record hashes, at this time. It does not prove that what the records describe is true, lawful or complete. Check the signature yourself before you rely on it.

2. What a valid bundle lets you rely on#

A bundle is valid when the Merkle root of its records matches the signed merkleRoot and its signature verifies against the Intramedial public key it names in signingKeyId, taken from our published key set, as described in Verifying ledger bundles. For a valid bundle you can rely on these things:

1. Integrity. The signed fields, and the record hashes the root commits to, are exactly what Intramedial signed. Nobody, including Intramedial, has changed them since.
2. Origin. Intramedial signed them, with a key that the ledger-bundles service holds as a secret and that no route of the Service returns. The Key management page says exactly how the key is held, and that it is not held in a hardware security module.
3. Time. snapshotAt is the time on Intramedial's servers when the bundle was sealed. The signature does not by itself involve a third-party timestamp authority. If the bundle carries an anchor proof, that proof separately shows that the root existed by the time of a Bitcoin block, as Verifying ledger bundles explains.
4. What Intramedial recorded. A bundle seals entries of a customer's audit chain. Some entries record decisions Intramedial itself made, such as whether it admitted or refused an action under a lease and a mandate. Others record events that the customer, a customer's agent or a connected system reported to Intramedial; for those, the bundle proves only that the report was recorded at that point in the chain. The Record Practice Statement lists which entries are which.

3. What a bundle does not prove#

A bundle does not prove, and you must not treat it as proving:

• that the content behind a record hash exists anywhere, is authentic, is lawful, or is what anyone says it is. A hash proves only that matching bytes were recorded when the entry was made;
• who the customer is, or which person stands behind an agent, beyond what the records themselves contain. Intramedial does not verify the identity of a customer's agents or staff for the verifier, and a bundle is not an identity document;
• that an agent, an AI model or any other third party behaved correctly, only what Intramedial admitted, refused or was told about it. A decision to admit an action is not a finding that the action was wise, lawful or authorised by anyone other than the holder of the lease and mandate;
• that nothing happened outside the range it covers, or where it records nothing. A bundle covers the range between rangeStart and rangeEnd, and a customer can seal several bundles over different ranges. There is no public list of all bundles issued. A bundle does not show that no other bundle exists, or that every event was recorded;
• anything about events before or after the time it states; or
• legal advice, an audit, a certification or an endorsement by Intramedial of any product, content or person. Intramedial holds no certification as to its own controls and a bundle does not suggest otherwise.

4. What you should do before relying on a bundle#

Verify the signature and the root yourself, with our published keys or an independent implementation, rather than trusting a copy of a verification result. Get the public key through a channel you trust and pin it, and check the Key management page for any notice that a key was compromised. Read the fields: the range, the scope, the count, and what the entries in it record. A bundle from which records have been removed no longer verifies. Decide for yourself how much weight it deserves for your purpose.

5. Our commitment to verifiers#

We publish every public key we use to sign production bundles, keep retired keys published so older bundles keep verifying, and publish a notice of any key compromise, as the Key management page describes.

If you believe a bundle that verifies was not issued by us, or that its fields do not match what our systems recorded, tell us at security@intramedial.com with the bundle. Where we still hold our copy of the bundle or the records it covers, we tell you whether our records agree with it, to the extent we can do so without disclosing a customer's data. If we find that a bundle verifies although we did not issue it, we treat that as a security incident and publish what we found.

6. Disclaimer and limitation of liability#

Apart from the commitments in section 5, bundles, our keys, the /verify page and the offline verifier are provided to verifiers as is, without any warranty, express or implied, including of merchantability, fitness for a particular purpose and non-infringement. Intramedial has no contract with you about any customer's use of the Service and is not responsible for a customer's conduct, for an agent's conduct or for decisions you make on the basis of a bundle.

To the fullest extent the law allows, Avonao, Inc. and its officers and contractors are not liable to a verifier for any loss arising from verifying or relying on a bundle, whatever the legal theory. Nothing in these terms limits liability that cannot be limited by law, such as liability for fraud, for intentional misconduct or gross negligence, or for death or personal injury caused by negligence, or the mandatory rights of a consumer.

7. Personal data in bundles#

A bundle you receive carries record identifiers and hashes rather than the content of the records, but identifiers, workspace names and ranges can still relate to a person, and the records a customer shares with you alongside a bundle can contain personal data, such as an agent owner's name or email address. If you keep or use it, you are responsible for doing so lawfully. A person named in a record can exercise their rights against us as our Privacy Policy describes.

8. Governing law#

These terms are governed by the laws of the State of Delaware, USA, without regard to its conflict-of-law rules. If you are a consumer, this does not remove the protection of mandatory law where you live, including your right to bring a claim in the courts of your country of residence.

9. Changes and contact#

We may update these terms and change the date at the top. The terms that apply to a bundle are the ones in force when you rely on it. Earlier versions are available on request. Questions: support@intramedial.com. Security concerns about a bundle or a key: security@intramedial.com.

EU notices

• Digital Services Act
• EU Data Act
• EU AI Act
• Right of withdrawal

Receipt practices

• Record Practice Statement
• Verifier Terms
• Key management
• Verifying ledger bundles
• Format versions and long-term verification
• Cryptographic agility and post-quantum status
• If Intramedial stops operating

Program terms

• Startup Program Terms
• Nonprofit Program Terms
• Education Program Terms
• Public Sector Program Terms