Terms of Service

1. These terms, and who they apply to

These terms cover your use of Muniment, A dated, hash-chained record of every published version of your conversational assistants, delivered to a bucket you own, with an evidence pack showing exactly what was live at any timestamp you name.. They are a contract between Muniment Records, Inc., of 10 Dorrance Street, Suite 700, Providence, RI 02903, United States (“Muniment”, “we”) and the company that signs up (“Customer”, “you”).

The service is for businesses only, not consumers. By signing up you confirm that you are acting for your business and that you have the authority to commit your company.

The person who accepts these terms accepts them for the company, not for themselves. If you don’t have that authority, please don’t go ahead.

If documents disagree. This order applies: (1) a signed order form or agreement between us, (2) the data processing agreement, (3) these terms, (4) our Privacy Policy, (5) anything else on our website.

2. What the service is

Publish-triggered capture of every assistant you connect, the normalized dated record set and its manifest chain in your bucket, unlimited resolver queries and evidence packs, the review queue, the published schema and verification script, and email support on the connector and the schema.

3. What the service is not

These limits are deliberate, and they are part of what you are buying. They are not defects.

Not a restore path. We show you what a version contained. Putting it back into production happens in your platform, by your team. Kore.ai's own documentation describes a Restore option that replaces the in-development version with an earlier definition, and a platform-native restore will always beat an outside archive at that job.

Not a transcript archive. We do not ingest conversations, recordings or member records, so we can tell you what the assistant was configured to say on a date and never what it said to a named person. Joining our answer to your transcript happens in your CCaaS, on your side.

Not a testing, linting or QA tool. No sandbox, no regression suite, no scoring of whether a prompt looks risky. We record what you published. Judging it is a person's job and stays one.

Not a bot builder. We write nothing to your platform and hold no write scope. The credential we ask for is read-only, and we will refuse one that is not.

4. What you need to do, and why it matters

What you get from the service depends a lot on things only you control. Please read this section carefully, because sections 9 and 10 build on it.

The export credential. You issue a read-only export credential on your bot platform and keep it valid. A rotated or revoked credential stops capture, and a stopped capture is a hole in the archive that we can prove exists but cannot fill after the fact.

The bucket and its lock. You create the bucket and enable Object Lock in compliance mode before first capture. This is your cloud team's action, not your CX team's, and it is close to irreversible once set. Choosing a lifecycle rule that expires objects breaks the guarantee you bought.

The connector check. Someone on your side owns a weekly look at the capture feed. A dead connector is silent and looks exactly like a quiet release month, and the difference only becomes visible when it is too late to matter.

What you paste. Redacting an answer string before it reaches the resolver is your call and your obligation. We store what you send.

The review queue. Unresolved queries and low-margin lineage joins wait for a named person on your side. Left alone, they stay unresolved, which is safe and still useless.

Naming the estate. Mapping assistants to lines of business, and deciding who may pull an evidence pack, is work only you can do. It is usually written down nowhere before we ask.

5. Getting started, and what is free

The first capture and the coverage report are free and run before any contract, so you learn how far back your own archive can start before deciding whether to start it.

The backfill of whatever versions still exist at connection is free, however many that turns out to be.

The first six months are month to month, cancellable on 30 days' notice, with no annual commitment asked for.

If you leave, the archive stays: the Parquet, the raw exports and the manifests are already in your bucket, and the schema and verification script are published under an open license, so the evidence is readable without us.

6. Fees

Per assistant, per month. USD 1,450 per connected assistant per month, invoiced monthly. An assistant that publishes three times a week and an assistant that publishes twice a year cost exactly the same.

Nothing meters. Captures, versions, storage volume, resolver queries, evidence packs, reviewers, auditor accounts and readers are all uncounted. There is no session clock and no per-query charge, deliberately, because evidence you did not pull for cost reasons is evidence you did not have.

Not charged. First capture and coverage report, connection backfill, schema updates and the verification script are not billed at any point.

Egress and storage in your account. Your bucket is billed to you by your own cloud provider, not by us. A seven-year locked archive of a busy estate is a real line item on your cloud bill and we do not mark it up, resell it, or hide it inside a platform fee.

Disconnection. Disconnecting an assistant stops its capture and its fee at the end of the month. It does not delete anything already captured, and it cannot.

7. Delivery, availability and support

The drop. Parquet and JSON record sets plus a signed manifest written to your storage bucket on every capture and consolidated nightly, against a published, versioned schema with valid_from and valid_to on every row.

The evidence pack. One PDF and one JSON against a matter reference: the node definitions live at the timestamp you named, the raw platform export, its SHA-256, and the manifest chain that dates it. Generated on demand, at any volume.

The console and the queue. A thin web console for connecting assistants, running resolver queries and clearing the review queue. It is the doorway to the data, not the product; everything it shows is in your bucket in a documented format.

Support. Email, US business hours, on the connector, the schema and the verification script. We do not advise on your flows and we do not write your response to counsel.

Support. Support is by email at [email protected]. We aim to reply within one business day. That is a target, not a guarantee.

8. Snapshots, versioning and correction

A capture is never edited. Captured versions are append-only. A parsing error is fixed by publishing a corrected record set alongside the original, with both hashes and the reason, never by overwriting what was stored.

The chain is the proof. Every manifest hashes the one before it. A missing capture, a gap in the sequence or an altered object is detectable by anyone running the published verification script against your bucket, including a party who does not trust us.

Corrections are logged, not silent. Reviewer confirmations and corrections carry the person and the timestamp and never modify a captured definition. They change how a query resolves, not what the record says.

Redaction is deliberate and two-handed. Removing an object inside its lock period takes a signed instruction from two named people on your side and leaves a tombstone naming the instruction, the people and the date. There is no delete button anywhere in the product.

Export needs no permission. Your archive is already in your account in an open format. Nothing has to be requested from us and nothing is held back at the end of a contract.

9. What we promise, and what we don’t

We promise to provide the service with reasonable skill and care, and that we have the right to provide it.

We warrant that each captured version is a faithful parse of the raw export it names, that its hash and manifest chain verify, and that an evidence pack returns only rows whose valid_from and valid_to bracket the timestamp requested. We do not warrant that your platform's export API returns everything the platform holds, that a version created before you connected us can be recovered, or that a resolver match is the node that in fact produced a given answer, which is why every match carries its confidence and every miss is reported as unresolved.

Beyond that we give no other warranty. As far as the law allows, we exclude all implied warranties, including merchantability, fitness for a particular purpose and non-infringement.

10. Liability

10.1 Neither of us limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else the law says can’t be limited.

10.2 Losses neither of us covers. Neither of us is liable for lost profit, revenue, expected savings, business, goodwill or reputation, or for any indirect or consequential loss, however it arises.

10.3 Specific exclusions. We exclude liability for versions destroyed by your platform's retention rules before capture began, for gaps caused by a revoked or expired export credential or by changes to your bucket policy or lifecycle rules, for conclusions drawn from an unresolved or low-confidence match, for the contents of an answer string you pasted, and for the outcome of any regulatory, legal or internal proceeding in which an evidence pack is used.

10.4 Cap. Our aggregate liability in any twelve-month period is capped at the fees you paid us in that period. Where the archive is intact and verifiable, the loss it is meant to prevent has not occurred; where it is not, the cap is what you paid.

10.5 You accept that the limits in sections 9 and 10 are a fair way to share risk, given the price and your part under section 4, and that we could not offer the service at this price without them.

11. Confidentiality and data

Assistant definitions, resolver queries, pasted answer strings, evidence packs and anything you send us in support are confidential, are not used to train anything outside your own account except the platform grammar described above, are never used as examples or in marketing, and are deleted on request except where an Object Lock retention period you set prevents it.

How we handle personal data is set out in our Privacy Policy and in the data processing agreement between us, which forms part of these terms. If the DPA and these terms disagree about personal data, the DPA wins.

12. Who owns what

The connectors, the parser, the lineage and resolver models, the console and the record schema remain ours, licensed to you for the term.

Your assistant definitions, the captured record sets derived from them, your manifests, your evidence packs and your reviewer corpus are yours, permanently and without condition, including after the contract ends. They sit in your bucket and you need no license from us to read, copy or produce them.

The record schema and the verification script are published under an open license and stay published, so an archive can be read and checked by a third party, or by you, with no software of ours involved.

You may not use our name or logo in public, and we may not use yours, without written permission first.

13. How long this lasts, and how it ends

13.1 The contract starts when you sign up and runs until one of us ends it.

13.2 You can end it. Cancel at any time. It takes effect at the end of the current billing month, unless section 6 sets a minimum term.

13.3 We can end it. We can end it with 30 days’ notice. We can end it immediately if you seriously break these terms and don’t fix it within 14 days of being told, if you become insolvent, or if your use exposes us to legal risk.

13.4 What happens then. We stop delivering and stop billing. You keep everything already delivered to you, and your right to use it continues. We delete or return our working copies as the DPA says. Sections 9, 10, 11 and 12 continue to apply.

14. Changes to these terms

We may update these terms. A change that matters takes effect 30 days after we email you about it. If you don’t accept it, you can end the contract before then. Using the service after that date means you accept the change.

15. Contact

Muniment Records, Inc., 10 Dorrance Street, Suite 700, Providence, RI 02903, United States
[email protected]

← Back