# signafAIde terms of service

Version: 1.3

Effective date: 14 November 2026

## 1. About these terms

1.1 signafAIde is provided by AIME TECH UK LIMITED, registered in England and Wales under company number 16819323, with its registered office at 42 Beaufort Court, Admirals Way, London, England, E14 9XL ("we", "us", "our").

1.2 These terms apply to your use of the signafAIde service: the hosted API, the web console, the sandbox and the public verification endpoints (together, the "Service"). They do not govern the open-source SDKs, CLI, MCP server, verifier or protocol specification, which are covered by section 13.

1.3 You accept these terms when you first do any of the following: create a sandbox (for example by running `signafaide init`), claim a sandbox, sign in to the console, create an organisation, start a paid plan, or send records to the Service with an API key. Each of these shows a link to these terms and our privacy notice at that point: `signafaide init` and the MCP `signafaide_init` tool print it when they create a sandbox, the sandbox API response carries it, and the console asks you to agree when you sign up, before you first use it after these terms change, and when you claim a sandbox. We record the version you accepted and when.

1.4 If you accept these terms for an organisation, you confirm that you have authority to bind it, and "you" means that organisation.

1.5 The Service is for business and professional use only. You confirm that you are not using it as a consumer.

1.6 If you have signed an order form or Enterprise agreement with us, it takes priority over these terms where they conflict.

## 2. Definitions

- **Agent key:** the Ed25519 key your agent generates and keeps on your machine. We never receive the private part.
- **API key:** a key starting `sfa_test_` (sandbox) or `sfa_live_` (live) that lets a client send records to a project.
- **Customer Data:** the records, hashes, agent and tool names, agent public keys, stored content and other data you or your clients send to the Service, and the receipts, heads, batches and exports we create from them.
- **Live record:** a record sent with a live API key.
- **Organisation:** the account unit in the console that holds projects, members and a plan.
- **Record:** one decision, outcome or note, as defined in the signafAIde protocol specification. A wrapped tool call is normally two records.
- **Sandbox:** a project created without an account, as described in section 5.
- **Stored content:** the optional content (for example inputs and outputs) of a record that you choose to send to the Service.

## 3. What the Service does

3.1 The Service receives records signed by your agent keys, checks them, countersigns them in batches with our service key, and returns a receipt for each record. Each batch carries the newest round we hold from the drand public randomness beacon, which shows the batch was not written before that round. About every hour, we build a Merkle tree over the batch hashes created since the last anchor and submit one hash per anchor to public OpenTimestamps calendars, which leads to a public timestamp showing the batches existed by that time. Only hashes are published.

3.2 **Local first.** The SDKs record locally and send nothing until a person either runs `signafaide init` (or the equivalent MCP tool) or sets an API key. Until then, no record, registration, usage event or sandbox request is sent.

3.3 **Hash-only by default.** For each record, the Service receives the hash of its content, together with the record envelope: the record kind, project, environment, agent name, sequence number, link to the previous record, time, tool or action name, and any reference to an earlier record. It does not receive inputs or outputs unless you turn on stored content.

3.4 **Stored content.** If you choose to send content with records, we store it encrypted at rest and keep it for one year from receipt, or seven years while your organisation has the retention add-on (section 6.10), after which it is deleted. Stored content on live records requires the Team plan or above. Sandbox projects may store content on any plan.

3.5 **Client header.** The SDKs, CLI and MCP server send a header with each request naming the SDK and its version, the language runtime and its version, the framework adapter, the coding agent detected when the project was set up, and how the call was made. You can remove the adapter and coding agent fields, and the related usage events, by setting `SIGNAFAIDE_TELEMETRY=0`. Details are in the privacy notice.

3.6 We may change, add or remove features. We will not remove a feature of a paid plan during a paid period without 30 days' notice, unless we must for legal or security reasons. Features shown as "soon" or "coming soon" are not part of the Service until released.

## 4. Accounts and sign-in

4.1 You can sign in to the console by an emailed one-time link, by GitHub, or, on Enterprise, by your own OpenID Connect identity provider once your email domain is verified.

4.2 You must give accurate information and keep your sign-in method, API keys, claim links and auditor links secure. Anyone holding an API key can send records to its project. Anyone holding a sandbox claim link can claim that sandbox. Anyone holding an auditor link can read what it covers until it expires or is revoked.

4.3 Within an organisation, members have one of four roles: owner, admin, developer or auditor. You are responsible for who you give access to and for their actions.

4.4 Tell us without delay at sales@signafaide.co.uk if you believe an account, API key or link has been compromised. You can revoke API keys, agent keys and auditor links in the console.

4.5 You must keep your agent private keys and your local records safe. We never hold your agent private keys and cannot recover them. In hash-only mode, the content of your records exists only on your systems: if you lose it, we cannot restore it.

## 5. The sandbox

5.1 A sandbox is a free project created without an account, email address or card, for testing. Each sandbox project may accept up to 5,000 test records a month and is rate-limited. Creation is limited per IP address.

5.2 An unclaimed sandbox, including any content stored in it, is deleted 30 days after it is created. Hashes already published in public timestamps cannot be withdrawn (section 16.5).

5.3 A sandbox is claimed by opening its claim link while signed in to the console, which moves it into an organisation. Whoever claims it first controls it.

5.4 Sandbox records are anchored in the same way as live records, but the sandbox is provided as is, with no service levels, and you must not rely on it for production evidence.

5.5 The person who creates a sandbox, including through a coding agent acting for them, is bound by these terms and the acceptable use policy.

## 6. Plans, fees and overage

6.1 **Free.** No charge. Includes 1 user (pending invitations count), 25,000 live records a month per organisation, up to 10 projects, and 1 active auditor link at a time that expires within 7 days. An organisation that had more users before Free became one user keeps them but cannot add more. When the monthly allowance is used, the Service refuses further live records until the next calendar month or until you upgrade. The SDKs keep refused records in the local outbox and send them later; none are dropped by the Service.

6.2 **Solo.** £19 a month or £190 a year. Includes 1 user, 100,000 live records a month per organisation, then overage at £5 per 100,000 records, charged per record and rounded to the penny (the same overage price as Team, whose £3 rate applies to extra records beyond 9,750,000 in the month). Solo is never refused for volume. Solo adds unlimited auditor links that expire within 90 days, a verification report for a period, and usage and chain alerts by email.

6.3 **Team.** £49 a month or £490 a year. Includes 250,000 live records a month per organisation, then overage at £5 per 100,000 records up to 10 million live records in the month, and £3 per 100,000 records above that, charged per record and rounded to the penny. Team is never refused for volume. Team adds unlimited users with roles, auditor links with any expiry, alerts by email and webhook, replay and A/B on past decisions, and stored content, and other features listed on the pricing page.

6.4 **Hash-only records.** On every plan, the Service keeps hash-only records (envelopes, signatures and receipts) with no time limit.

6.5 **Enterprise.** Priced and agreed by order form, billed annually. Enterprise features (such as audit packs mapped to the EU AI Act, ISO/IEC 42001 and SOC 2, SSO, customer-supplied content keys, a self-hosted witness, UK or EU data residency, service levels and custom retention) apply only as set out in the order form.

6.6 **Billing.** Paid plans are billed in advance through Stripe, monthly or annually, and renew automatically until cancelled. Overage is measured per calendar month (UTC) and invoiced monthly in arrears through a separate metered subscription, including on annual plans. Prices exclude VAT and other taxes, which you pay where they apply. Prices are in pounds sterling (GBP). If Stripe offers you payment in another currency at checkout, the amount it shows is its own conversion of the sterling price.

6.7 **Cancellation and changes.** An owner or admin can cancel or change billing interval through the Stripe customer portal linked from the console, and can move from Solo to Team in the console; the price difference is prorated by Stripe. Cancellation takes effect at the end of the current paid period. When a Solo or Team subscription ends, any overage in the period is invoiced. Except where the law requires otherwise or we agree in writing, fees are non-refundable.

6.8 **Failed payment.** If a payment fails, the organisation keeps its paid plan for 7 days, then moves to Free until the invoice is paid. Nothing is deleted on a downgrade: stored content stays readable until its retention ends (section 3.4), and accepted records keep their receipts. Features of the paid plan stop working while on Free.

6.9 **Price changes.** We may change prices with at least 30 days' notice, effective from your next renewal.

6.10 **Retention add-on.** On Team, an owner or admin can add 7-year retention for £10 a month per organisation, billed monthly through Stripe as a subscription of its own, whether Team is paid monthly or annually. While it is on, stored content is kept for seven years from receipt instead of one. It covers stored content only: Solo and Free store no content, and hash-only records are kept with no time limit on every plan (section 6.4). Enterprise sets retention in its order form. When the add-on ends (cancelled, or because the organisation leaves Team), stored content older than one year is deleted at the next daily deletion run; the records stay verifiable hash-only.

6.10 Verification is never charged. Anyone can verify a verification pack without the Service.

## 7. Fair use and abuse

7.1 You must use the Service in line with the acceptable use policy, which forms part of these terms.

7.2 We apply rate limits and quotas, and may change them to protect the Service. We may throttle, refuse or suspend traffic that is abusive or that puts the Service or other customers at risk.

## 8. What signafAIde attests, and what it does not

8.1 A receipt, anchor and verification pack can show, subject to the checks set out in the protocol specification: that a record was signed by an agent key that was active at the record's time; that we countersigned it; that it has not been changed since; where it sits in its chain; that its batch was not written before a given drand round; and that its batch existed by the time of a public timestamp.

8.2 **The Service attests integrity and timing only.** It does not assess, and we make no statement or warranty about, whether any decision, action or outcome recorded was correct, lawful, safe, fair, complete, authorised or appropriate, or whether the record accurately describes what your agent did. The Service only knows what your clients send it. Anything your integration does not record is not covered.

8.3 **Evidence, not certification.** Records, receipts, verification packs and audit packs are evidence that you may give to auditors, regulators or others. They are not a certification, attestation of compliance, audit opinion or legal advice. Where we describe records or audit packs as relevant to a law, standard or framework (including Articles 12, 19 and 26(6) of the EU AI Act, ISO/IEC 42001 and SOC 2), we mean only that they may help you produce evidence for a requirement. Using the Service does not by itself make you compliant with any of them, and whether you comply is for you, your advisers and your auditors to decide. We are not a notified body, conformity assessment body, certification body or auditor.

8.4 **Public services.** The drand beacon, OpenTimestamps calendars, the public ledger behind the timestamps and the block explorers we use to confirm timestamps are run by third parties and are outside our control. If drand is unreachable, a batch carries no drand round and verification shows this. A public timestamp stays pending until confirmed in the public ledger, which normally takes hours. We aim to anchor each batch within 2 hours of receiving it, but do not guarantee that public services will be available or will behave as expected.

## 9. Your responsibilities for what you record

9.1 You decide what your agents record, whether to store content, and what agent names, tool names and other data you send. You are responsible for that data and for having all rights, notices, consents and lawful bases needed to collect it, record it and send it to us.

9.2 You must not put personal data in agent names, tool or action names, or other envelope fields. If you need to record personal data, keep it in content (which stays on your systems by default) or, if you turn on stored content, make sure you have a lawful basis to do so and have assessed the transfer to us.

9.3 You are responsible for your own obligations under laws that apply to your AI systems, including the EU AI Act, data protection law and sector rules, and for keeping logs for as long as those laws require. In hash-only mode, the content of your logs is held only by you.

9.4 You must not use stored content for special category data, criminal offence data or data about children unless you have first agreed this with us in writing.

## 10. Customer Data

10.1 You keep all rights in Customer Data. You grant us a non-exclusive, worldwide licence to host, copy, process, transmit and display Customer Data only as needed to provide, secure and support the Service, to comply with law, and as described in the data processing agreement.

10.2 We may create and use aggregated usage and performance data that does not identify you or any individual (for example counts of records, error rates, SDK versions in use), to run and improve the Service.

10.3 Hashes we publish in public timestamps are not Customer Data in a form anyone can reverse; see section 16.5 on why they cannot be withdrawn.

## 11. Data protection

11.1 For account, billing, support and website analytics data, we are a controller. Our privacy notice explains how we use it.

11.2 For personal data in Customer Data, you are the controller and we are your processor. The data processing agreement at /legal/dpa forms part of these terms and applies to that processing.

## 12. Confidentiality

12.1 Each party will keep the other's confidential information confidential and use it only to perform or receive the Service, except where disclosure is required by law, or the information is public through no fault of the receiving party, was already known to it, or was independently developed. Customer Data is your confidential information.

## 13. Open-source SDKs and the protocol

13.1 The signafAIde SDKs, CLI, MCP server, Claude Code plugin, verifier, protocol core and protocol specification are published under the Apache License, Version 2.0. Your use of them is governed by that licence, not by these terms, except where you use them with the Service, in which case these terms govern your use of the Service.

13.2 Nothing in these terms limits your rights under the Apache License 2.0. Nothing in the Apache License 2.0 grants you any right to use the Service.

13.3 Verification packs can be checked with the open-source verifier without using the Service.

## 14. Self-hosted witness (Enterprise)

14.1 If your order form includes a self-hosted witness, you run the signafAIde server in your own environment, with your own service key, your own content master key, and your own choice of timestamp and randomness services. Records, stored content and keys stay in your environment and we do not receive them.

14.2 You are responsible for operating, securing, backing up and updating your instance, and for its keys. If you lose your content master key, your stored content cannot be read. The server software is proprietary: it is licensed only under an Enterprise order form, which also sets out any support. The protocol specification, SDKs and verifiers stay open source (section 13).

## 15. Availability and support

15.1 **Uptime.** We commit to 99.5% availability of the hosted witness (the API that receives and co-signs records) in each calendar month (UTC), which allows about 3 hours and 39 minutes of downtime in a 30-day month. The witness runs on a single machine on Google Cloud in London (europe-west2), so maintenance and failures of that machine count against this figure. If we miss it in a month, we will tell the owners of affected organisations the measured availability and the cause. Service credits apply only where an order form sets them out.

15.2 **What an outage means for your records.** An outage of the witness delays co-signing but never loses records already written on your machines: the SDKs keep them in the local outbox and send them, with their original times, when the witness is back, as long as they are at most 7 days old. Tools you run in strict mode do not run while the witness cannot be reached. Records kept on a disk that is lost (for example an ephemeral container that stops before sending) are lost with it; the production guide explains how to avoid this.

15.3 We may carry out maintenance, and will try to give notice of planned downtime.

15.4 Support is available by email to sales@signafaide.co.uk. Enterprise support terms are set out in the order form.

## 16. Suspension, termination and export

16.1 **Suspension.** We may suspend all or part of your access, with notice where reasonably possible, if: you breach the acceptable use policy; your use threatens the security or integrity of the Service or other customers; we are required to by law; or an invoice is unpaid after the grace period (in which case the organisation moves to Free under section 6.8 rather than being suspended, unless the breach is serious). We will restore access once the cause is resolved.

16.2 **Termination by you.** You can stop using the Service at any time. An owner can delete a project or the whole organisation, and any user can delete their own account, from the console; this takes effect at once, cannot be undone, and keeps only what section 16.5(a) and (b) describe. Deleting an organisation cancels its paid plan immediately, without the end-of-period run-off in section 6.7; overage measured up to that point is invoiced. Owners can also contact us at sales@signafaide.co.uk.

16.3 **Termination by us.** We may terminate these terms for your organisation: on 90 days' notice for any reason (with a pro-rata refund of prepaid fees for the unused period); immediately if you materially breach these terms and do not remedy the breach within 14 days of notice; or immediately if you become insolvent.

16.4 **Export.** While your organisation is active, and after termination for the export period, any member of the organisation can export verification packs through the console, and anyone holding a project API key can export through the API. One export holds up to 50,000 records; larger exports are split by agent or time range. A verification pack contains the records, receipts, batches, heads, anchors and inclusion paths needed to verify them independently, and stored content where it was stored. You should also keep your agent key manifest (`signafaide keys export`) and your local records. The export period is 90 days after termination where we terminated on notice for any reason under section 16.3, and 30 days after any other termination; there is none where termination was for your serious breach.

16.5 **After termination or deletion.** After the export period (or at once, when you delete an organisation, project or account yourself) we will delete your organisation, its projects, records, stored content, keys and account data within 30 days, except:
  (a) hashes we have published in public timestamp services (one hash per anchor, covering batches from many customers) are recorded permanently by third parties and cannot be withdrawn;
  (b) we keep anchors, service key history and, for each of your batches that was already anchored, its batch hash and its Merkle path in the anchor, because other customers' inclusion proofs point into the same anchors. These are hashes and do not contain record content, envelopes, agent or tool names, or any project, organisation or person identifier;
  (c) we keep billing records and other data for as long as the law requires; and
  (d) data in backups is deleted as backups expire, within 30 days.

16.6 Sections 8, 10.2, 12, 16.5, 16.7, 17, 18, 19, 20 and 22 survive termination.

16.7 **If we wind down the Service.** We will give at least 12 months' notice, by email to organisation owners and in the console, before we stop providing the Service to all customers. The export tools in section 16.4 stay available throughout. If AIME TECH UK LIMITED winds down the Service, we will release the source code of the witness server under the Apache License, Version 2.0, so that you or anyone else can run it. Verification packs you have exported keep verifying offline with the open-source verifier whatever happens to us, because checking them does not use the Service (section 13).

## 17. Warranties and disclaimers

17.1 Each party warrants that it has the authority to enter into these terms.

17.2 We will provide the Service with reasonable skill and care.

17.3 Except as set out in these terms, and to the extent the law allows, the Service is provided without any other warranty, condition or term, whether express or implied by statute, common law or otherwise, including as to satisfactory quality, fitness for a particular purpose, or that the Service will be uninterrupted or error-free. The Free plan and sandbox are provided as is.

17.4 Without limiting section 8, we do not warrant that the Service, any record or any audit pack will satisfy any law, regulation, standard, auditor or regulator.

## 18. Liability

18.1 Nothing in these terms limits or excludes liability for: death or personal injury caused by negligence; fraud or fraudulent misrepresentation; your obligation to pay fees due; or any other liability that cannot be limited or excluded by law.

18.2 Subject to 18.1, neither party is liable, whether in contract, tort (including negligence), breach of statutory duty or otherwise, for any: loss of profits, revenue, business or anticipated savings; loss of goodwill; loss or corruption of data, except our obligation to restore from backups where available; regulatory fines or penalties imposed on the other party, to the extent the law allows; or indirect or consequential loss.

18.3 Subject to 18.1, each party's total aggregate liability arising out of or in connection with these terms in any 12-month period is limited to the greater of: (a) the fees paid and payable by you for the Service in the 12 months before the event giving rise to the claim; and (b) £100.

18.4 We are not liable for: the content of records, decisions or actions of your agents; any failure of third-party public services described in section 8.4; loss of your agent keys, local records or content master key (for a self-hosted witness); or use of claim links, API keys or auditor links by anyone who obtained them from you.

## 19. Indemnity

19.1 You will indemnify us against claims by third parties, and resulting losses, arising from Customer Data you record or store in breach of these terms or of law, or from your use of the Service in breach of the acceptable use policy.

## 20. Changes to these terms

20.1 We may change these terms. We will give at least 30 days' notice of a material change by email to organisation owners or in the console, except where a change is required by law or relates to a new feature. If you do not agree, you may stop using the Service and, for a paid plan, cancel before the change takes effect. Continued use after the effective date means you accept the change.

## 21. Notices

21.1 We send notices to the email address of the organisation's owners or through the console. You send notices to sales@signafaide.co.uk and 42 Beaufort Court, Admirals Way, London, England, E14 9XL.

## 22. General

22.1 **Force majeure.** Neither party is liable for delay or failure caused by events beyond its reasonable control, including failures of public networks or third-party public services.

22.2 **Assignment.** You may not assign these terms without our consent. We may assign them to another company in the AIMETECH group or to a successor of the Service, with notice.

22.3 **Entire agreement.** These terms, the acceptable use policy, the data processing agreement and any order form are the whole agreement between us about the Service.

22.4 **Third parties.** No one other than the parties has any right to enforce these terms under the Contracts (Rights of Third Parties) Act 1999.

22.5 **Severance and waiver.** If any provision is found invalid, the rest remain in force. A failure to enforce a right is not a waiver of it.

22.6 **Governing law and jurisdiction.** These terms and any dispute or claim arising out of or in connection with them, including non-contractual disputes, are governed by the law of England and Wales. The courts of England and Wales have exclusive jurisdiction.