If Intramedial stops operating

3. What stops#

• Admission decisions, new leases and mandates, and every enforcement point that calls the Service.
• The dashboard, the REST API at api.intramedial.com, the MCP server at mcp.intramedial.com and the assistant.
• Fresh ledger bundles and new audit-chain entries.
• Our stored copies of your records. A record that exists only in our databases cannot be fetched once the Service is gone.
• The published key set at its usual address, unless it is kept up as described in section 4.

4. What we commit to if we wind the Service down#

If Avonao, Inc. decides to stop operating the Service, we will:

1. give at least 30 days' notice by email to every account owner and on the status page, as the Terms of Service provide, and refund the unused part of any prepaid fee;
2. keep exports working for the whole notice period, on every plan, so you can download your records, ledger bundles and the key set, and run the leave-with-everything export described in Exit objectives;
3. publish the final key set in at least one place that does not depend on our infrastructure, such as a release of the verifier that bundles it, and say on the status page where it is; and
4. stop signing before we stop publishing: no ledger bundle will be signed after the final key set is published.

If the business is sold or merged instead, the buyer takes over the Terms of Service, which we may assign with notice to you, and the protections of our Privacy Policy for your data continue.

There is no third-party escrow of keys or source code today. We do not describe the signing keys as held in a hardware module: they are Worker secrets, and when the Service ends we will retire them so that no successor can sign in our name.

5. What you can do today#

1. Export regularly. Use the exports in the dashboard and the export routes of the API, including the ledger bundle snapshot (Ledger bundles) and the exit export. Keep the result in your own storage, and export before a record passes your plan's retention window in any case.
2. Pin the keys. Store the key ids and public keys you rely on, as Key management explains.
3. Record bundles when you receive them, in a system you control with its own clock, so you can show when you held each one.
4. Keep a verifier you control, whether a copy of intramedial-verify from the time of your export or a few lines of your own code following Verifying records and Verify in code.
5. Check the exit objectives. The recovery time and recovery point we publish for each data class are in Exit objectives. A class that has not been measured is reported as unverified, never as met.

6. How we keep the Service running meanwhile#

Workspace data is stored in Cloudflare's databases and Durable Objects in the workspace's region, and signed ledger bundles are stored in regional Cloudflare R2 buckets. Cloudflare's point-in-time recovery (D1 Time Travel) lets us restore those databases to any minute of the last 30 days; we export the databases to dated copies as an additional step. Cold archive copies are kept in Amazon S3 Deep Archive. Self-serve plans carry no uptime commitment; Enterprise customers have the Enterprise SLA.

7. Changes and contact#

We update this page if any of these arrangements change. Questions: support@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