Terms of Service

Version 1.1 · 2026-11-17

1. Who these terms are with

These terms are an agreement between you and Dor Tagger, trading as Attify ("Attify", "we", "us"). They cover the Attify website and web app, the API, the MCP server, badges, attestations and reports (together, "the service").

If you use the service for an organization, you accept these terms for it and confirm you may bind it. "You" then means that organization too. The service is for businesses, not consumers.

Contact: hello@attify.app.

2. What Attify does

Attify independently audits the outcomes that AI agents claim. Each job type has a published standard that asks whether the outcome happened, whether it stuck, and whether a person had to redo it. Attify reports an audited rate next to the claimed rate, with 95% intervals, against the fairest version of the vendor's own counting rule.

The service has these parts:

  • Upload check (free): upload a help-desk export, see the claimed rate against the audited rate at the rules tier, and ask for a full judged audit by email.
  • Buyer dashboards: connect your own systems read-only and see, each month, what your AI agents' claims are worth: audited against claimed, and the cost of each audited outcome. Free while you contribute anonymous data to the Attify Index (section 10), or on a paid plan, with one 14-day trial of the Team plan, no card needed.
  • Vendor Verification: run verification programs on your customers' connected systems, or on witnessed data your customers have reconciled (section 10), with published scores, signed attestations, a registry listing and a live badge.
  • Traction Reports (one-off): a signed report of what your AI agent did at your customers, shareable with investors.
  • Investor (subscription): request audited traction reports from companies and receive them on your dashboard.

The API and agents

Every result, report and attestation is also available as typed JSON with a versioned schema, through the API and the MCP server, so agents can read it.

  • The read-only verification API needs its key. Do not share a key outside your organization, and do not use it to read data you are not entitled to see.
  • Field names and schema versions are stable within a version. A breaking change is a new schema version, and the previous version stays available for at least 90 days after the new one is published.
  • Agents acting for you are bound by these terms as you are. You are responsible for what they do with your access.

3. Access

Published pages, the standards, the registry, the Index and the MCP server are open to anyone. Your organization's data needs a sign-in, or the link or token we sent you.

4. Accounts

  • Sign-in runs through our identity provider (Clerk). Keep your sign-in secure; you are responsible for activity under your account.
  • Organizations have owners and members. Only an owner can agree to a program's scope, connect or disconnect the organization's systems in a program, create or delete a deployment, start a checkout, share or withdraw a report, and export or delete the organization.
  • A check or a connected audit started without an account is private to whoever holds its link or token. Keep it safe: anyone holding it can see the results and, for a connection, disconnect it.
  • Give us accurate information, including your organization's name and kind (vendor, company or investor).
  • API keys, deployment keys and access tokens are yours to protect. Tell us at once at security@attify.app if one leaks.

5. Your data and your instructions

  • You keep all rights in the data you upload or connect. You give us the rights we need to run the service on it, as described in the Privacy Policy and the Data Processing Agreement.
  • For the data in your connected systems and uploads, you are the controller and we are your processor. For witnessed data, we process it on the instructions that section 10 and the DPA (section 2.4) describe. The DPA forms part of these terms.
  • Uploads are deleted within 30 minutes or when the full audit finishes. Message text from a connected system is deleted 30 days after the record's last update; scores and per-record outcomes (no text, no customer id) are kept. Disconnecting deletes everything we read from that connection.
  • Message text in witnessed data is redacted when it arrives and deleted at most 30 days after it arrives, whether or not the customer consented. Event metadata (ids, times, sequence numbers, a digest, how the request was authenticated) and scores are kept, without text. Deleting a deployment deletes everything it sent.
  • Results we compute (scores, rates, intervals, reports, attestations, Index editions) are Attify's work product. Section 9 says how you may use them.

6. Acceptable use

You must not:

  • upload, connect or stream data you have no right to share with us, or that breaks a duty you owe to the people in it, or attest to a right you do not have;
  • try to game a standard: for example by choosing which conversations an upload holds and presenting the result as connected, editing or filtering records before connecting, creating artificial conversations or bookings, leaving interactions out of a witnessed stream or sending ones that did not happen, or steering which customers count in a program;
  • misrepresent a result: present an uploaded (self-reported) result as connected, witnessed data not yet reconciled as reconciled, a rules-tier number as judged, an expired or withdrawn attestation as current, or one job type's result as another's;
  • alter a badge, an attestation, a report or a score, or show a copy of a badge hosted anywhere but our domain;
  • try to identify a customer or a brand behind a pooled or numbered result;
  • get around access controls, rate limits, spending caps or role permissions, or probe the service for weaknesses without our written permission;
  • use the service to send spam or to harass anyone, or resell it without our agreement;
  • reverse-engineer the service, except where the law allows it.

We may suspend access to stop a breach of this section.

7. Neutrality and what results mean

  • Results are opinions. Every result is Attify's opinion under a published standard, at a stated evidence tier, with stated uncertainty (95% intervals). It is not a guarantee of how an AI agent will perform, a certification of fitness for any purpose, or financial, investment or legal advice.
  • Provenance matters. Every result states where its data came from: connected (we read it from the customer's own systems, with the customer's authorization), witnessed (the vendor streamed it to us as it happened, section 10) or uploaded (a file). An uploaded result is self-reported: whoever supplied the file chose what it contains. Only connected data, or witnessed data the customer has consented to and reconciled, can support a vendor verification, a badge or a traction report.
  • We are neutral. We describe where and why outcomes fail. We never advise a vendor on how to raise its own score, and no payment buys a better score, an earlier publication or a different status. The price never depends on a result. A buyer checking its own deployment may get suggestions for improving it.
  • Publication gates. A score publishes only after its 7-day review window, once the judge is validated against people for the current standard version, the score's own human audit is complete, and enough of its customers pass the independence checks in the published rules. During the review window the vendor can add one public comment; nobody can change a number.
  • Public surfaces show pooled results only. Per-customer results go only to the vendor running the program, and per-customer reports are not for publication.

8. Published standards and versions

  • Each standard is public, with its judge prompts and a changelog. Every result names the standard version it was measured under.
  • We may change a standard. Any change is a new version, logged with the reason. A result keeps the version it was measured under; a new score uses the current one.
  • When a change could move a result, the old rule stays visible as a secondary view where the standard says so.
  • Standards are published for comment. Send comments to standards@attify.app. We decide what changes.

9. Badges, attestations and reports

  • Badges. A badge is an SVG served from our domain and always drawn from the program's current status. Embed it inside a link to the vendor's Attify profile. A copy hosted elsewhere is not an Attify badge.
  • Attestations. Each attestation is signed (Ed25519), names its standard version, evidence tier, provenance, period, status and numbers, and expires (a vendor attestation 44 days after issue; a traction report's 90 days after issue). Anyone can check one at /verify.
  • Status can change. A published score's claim can read not confirmed, or a program Lapsed, under the published rules, or be Revoked by an Attify admin with a public reason. A revocation is final. A newer attestation, an expiry or a revocation makes an older one stale.
  • Traction reports. A report's numbers never change. The company can revoke a share link or withdraw a report at any time; /verify then says withdrawn.
  • Your use. You may show your own badge, attestation and report, unaltered and with their date, standard version and status. You must stop presenting a status as current once it lapses, is revoked or expires.

10. Vendors, customers and buyers

  • A vendor invites its customers. Each customer decides for itself whether to agree to the scope and connect its systems. The vendor cannot connect a customer's systems for it.
  • Genuine customers. A vendor attests that every customer it invites is a genuine, independent customer: a separate company that uses its product, whose organization, systems and invited address the vendor does not control. A customer counts only once it passes the independence checks in the published rules, and Attify may ask any customer directly whether it uses the product. If Attify finds a customer is not genuine, it revokes the vendor's score and says why in the public changelog. A revocation is final.
  • The vendor sees each customer's results and consent records, never its conversations, meetings or bookings.
  • Publishing. A vendor's first audit is private, and the vendor decides whether to publish it. Once the vendor publishes, every later score publishes too, after its review window; a published score cannot be hidden, withdrawn or edited. Stopping verification leaves the profile Lapsed with its published history, and that history stays public after the vendor's account is deleted.
  • A vendor may share a traction report with investors it chooses. Customers appear as numbered customers unless a customer opts in to being named. Only the customer can opt in.
  • A customer can disconnect at any time. The program then follows the published rules (a lapse, or a new random draw).
  • Buyers and the Attify Index. A buyer may contribute its anonymous audited outcomes to the Attify Index, under a consent it gives and can withdraw in the app. The Index names no company, vendor or agent, and publishes a job type only when at least 5 companies contributed and none holds more than half of the claims. A buyer's data reaches a vendor only if the buyer opts in to that vendor's program.

Witnessed data

Some AI agents run on the vendor's own platform, not in a system we can read. The vendor can then stream each interaction its agent has at a customer to us as it happens, through the Ingest API, an SDK or OpenTelemetry: this is witnessed data. Each deployment (one agent at one customer) has its own key, issued by us. Every request is authenticated with it, and we timestamp every event when it arrives. We sign a receipt of every batch we receive, stating what arrived and when, with our Ed25519 attestation key.

  • The vendor's attestation. Before a deployment can stream, the vendor attests that it has the right to share that customer's interaction data with us for verification. We record who attested, when, and the version of these terms. The vendor is responsible for that right, for its own notices to the end users in the data, and for not sending data it may not share. A false attestation breaches section 6: we may suspend the vendor's access (section 17) and revoke any score it supported (section 9).
  • The customer's consent. Witnessed data counts toward a vendor's verification or badge only after the customer itself records its consent in Attify (who agreed, when, the scope and the retention), as for connected data, and then reconciles it every month: it confirms the month's total from its own records or the vendor's invoices, and checks a random sample of interactions against its own systems. Where the customer has connected its own help desk, we may answer the sample from it. The vendor cannot consent or reconcile for its customer.
  • Without the customer's consent, we use witnessed data only for the vendor's own private report on that deployment.
  • Withdrawal. The customer can withdraw its consent at any time. The vendor's interactions then count only toward the vendor's private report.

11. Fees and payment

  • Prices are shown on the pricing page and may change; a change applies to a subscription from its next renewal after we tell you. Current plans: the upload check (free); for buyers, a free plan while you contribute anonymous data, and the Team and Business plans (monthly subscriptions, priced by the AI interactions audited each month, whatever their result); for vendors, verification plans (monthly subscriptions, priced by the customers a program covers, free while vendor pricing is off); Traction Reports (a one-off purchase of one report credit); Investor (monthly subscription). Enterprise terms are agreed in writing.
  • Polar is the merchant of record. It charges you, handles tax and invoices, and runs the billing portal. Polar's own terms apply to the payment.
  • Subscriptions renew monthly until cancelled. You can cancel in the billing portal; the plan stays active until the end of the paid period.
  • A Traction Report credit is used when a report is built. A report that cannot be built gives the credit back. A report that answers an investor's request is covered by the investor's subscription.
  • Judged runs are estimated before they start and stay within spending caps.
  • Payments are not refundable, except where the law requires it, where these terms say so, and when we end a paid plan for a reason other than your breach: we then refund the unused part of the period you paid for.
  • If a payment fails, paid features may stop until it is settled.

12. Third-party services

The service relies on third parties: the systems you connect, Anthropic (the LLM judge), our hosting, sign-in, payment and email providers. Your use of your own systems stays under their own terms. We are not responsible for a third party's outage or changes, but we will tell you when one affects your results.

13. Availability and changes to the service

We aim to keep the service available and correct, but it is provided as it is and may change, pause or have errors. We may add, change or remove features. We will give at least 30 days' notice before removing a paid feature you rely on.

14. Disclaimers

To the extent the law allows:

  • the service, results, standards, badges, attestations and reports are provided "as is" and "as available";
  • we make no warranty that results are free of error, that redaction removes every personal detail, or that the service meets your particular needs;
  • you are responsible for the decisions you make using a result, including buying, investing and hiring decisions.

15. Limitation of liability

To the extent the law allows:

  • neither party is liable for indirect, incidental, special or consequential losses, or for lost profits, revenue or data, even if warned of them;
  • each party's total liability under these terms in any 12 months is limited to the fees you paid us in the 12 months before the event that gave rise to the claim, or USD 100 if you paid nothing;
  • these limits do not apply to liability that the law does not allow to be limited (for example for fraud or wilful misconduct), to the fees you owe us, or to your obligations under section 16.

16. Indemnity

  • Yours. You will defend and compensate us against claims from third parties arising from data you uploaded, connected or streamed without the right to do so, from an attestation you made that was not true, or from your breach of section 6.
  • Ours. We will defend and compensate you against claims from third parties that the service itself, used as these terms allow, infringes their intellectual property. This does not cover your data, a badge or result you altered, or the service combined with something we did not provide. Our obligation is subject to the limits in section 15.
  • The party claiming must tell the other promptly, let it control the defence, and give reasonable help.

17. Suspension and termination

  • You can stop using the service at any time. An organization owner can delete the organization; consent records and audit-log entries are kept as evidence of what was agreed, with no message text.
  • We may suspend or end your access if you breach these terms, if your payment fails, or if the law requires it. Where we can, we will tell you first and give you a chance to fix it.
  • When access ends, connected systems are disconnected and what we read from them is deleted. Published scores, Index editions, the public changelog and issued attestations stay as the record of what was published, with their status updated.
  • Sections 5, 7, 9, 14, 15, 16 and 19 survive termination.

18. Changes to these terms

We may change these terms. We will post the new version here with its number and date, and tell organization owners by email at least 30 days before a material change applies. If you keep using the service after that, the new terms apply. If you do not agree, stop using the service and, if you pay, cancel before the change applies.

19. General

  • Governing law and courts: these terms are governed by the laws of England and Wales, without regard to their conflict-of-law rules. The courts of England and Wales have exclusive jurisdiction, except that either party may ask any competent court for urgent interim relief.
  • Entire agreement: these terms, the Privacy Policy, the DPA and any order you accept are the whole agreement on their subject.
  • Assignment: you may not transfer these terms without our consent. We may transfer them with our business, including to a company formed to run Attify.
  • Severability: if a part of these terms is invalid, the rest still applies.
  • No waiver: not enforcing a right now does not waive it.
  • Notices: to you, by email to your organization's owners; to us, at hello@attify.app.