Aiscovery

Legal

Acceptable Use and Responsible Testing Policy

The rules for testing stores with Aiscovery, and the limits our checker and AI agents keep on every site.

Last updated
Legal review
Not yet reviewed (draft)
Operator
Not set yet: legal entity name
Privacy contact
privacy@aiscovery.io

Draft: pending legal review

This policy is a draft prepared by the product team. It is not legal advice and has not been reviewed by counsel. It becomes final once legal review is complete, and it is part of our Terms of Service.

In short

  • Test only stores you own or operate, or have the owner's permission to test.
  • Our checker and agents read public pages only, follow robots.txt, go one page per second and stop before login, cart, checkout and payment.
  • Never put real personal data, passwords or payment details into a task.
  • Site owners can opt out at any time with robots.txt or by emailing abuse@aiscovery.io.

Test only what you're allowed to test

You may add a store, run site checks and run AI agent tasks only if you own or operate that store, or its owner or operator has allowed you to have it tested by a service like Aiscovery.

Agencies and consultants need their client's permission for each client store. Keep a record of it, such as an email or a contract, and show it to us if we ask.

If the owner of a store asks us to stop, we stop for every customer, even if you believed you had permission.

How our checker and agents behave

These limits are built into Aiscovery. You can't turn them off, and you must not try to.

  • One identified visitor. Our checker sends the user agent AiscoveryAudit/1.0 (+https://aiscovery.io/checker), and AI agents that run in our browser load pages through it.
  • robots.txt first. If a store's robots.txt asks our checker not to read a page, neither the checker nor an agent reads it.
  • One page per second, one request at a time, with a cap on requests, time and data for every check and run.
  • Public pages only. No login, account pages, cart, checkout, payment, bookings, or forms that send data. With the store's rules, an agent may type a search term into the store's own search.
  • No getting around protections. We never solve CAPTCHAs or work around firewalls or bot protection. If a store blocks us, the check ends.
  • Masked screenshots. Agent step screenshots hide form fields, embedded frames and text that looks like an email address, phone number, card, account or order number.

What isn't allowed

  • Testing, probing or monitoring a store you aren't allowed to test, including a competitor's store.
  • Trying to make our checker or agents log in, create accounts, place orders, submit forms, post reviews or messages, or reach pages that aren't public.
  • Trying to get around CAPTCHAs, firewalls, rate limits, robots.txt or our stop points, for example with task instructions written to trick an agent.
  • Putting real personal data, passwords, access tokens or payment details into tasks, store settings or Ask Aiscovery.
  • Using Aiscovery to overload a site, collect personal data or copy a site's content.
  • Presenting results as a verdict on a store you don't operate, or using them to mislead anyone.
  • Sharing accounts, reselling the service, getting around plan or credit limits, or using Aiscovery to build a competing product, without our written permission.
  • Interfering with Aiscovery, probing it for weaknesses without following our security policy, or trying to reach other customers' data.
  • Using Ask Aiscovery for anything unrelated to your results, or to create unlawful or harmful content.

Checkout rehearsal, coming later

Checkout rehearsal lets an agent go through checkout up to the order button. When it is released, it will run only on a store whose ownership a workspace owner has verified and for which the owner has given a separate approval.

It will use a made-up test shopper, and a payment provider's published test card only while that provider is in test mode. It will never place an order, and code, not the AI model, blocks the final step.

If you own a site we checked

Add these two lines to your robots.txt and our checker will read nothing else from your site: User-agent: AiscoveryAudit, then Disallow: /.

To stop every check of your site for every customer, email abuse@aiscovery.io from an address at your domain. We stop checks within one business day and don't reveal which customer asked for them. Our checker page explains more, including how to allow our checker if you want it.

Reporting misuse and security issues

Report misuse of Aiscovery, or traffic that claims to be ours but breaks these rules, to abuse@aiscovery.io. We reply the same business day.

Report security issues in Aiscovery itself to security@aiscovery.io, as described on our Security page and in /.well-known/security.txt. Testing Aiscovery itself also needs our permission.

What we do when rules are broken

We may stop a check or run, pause automatic checks, remove a website from a workspace, or suspend or close a workspace. Where we can, we tell you first and give you a chance to fix the problem. Serious or repeated misuse can end your account without a refund, as our Terms of Service describe.