Terms of Use

These terms are an agreement between you — the person using oloy, and any organisation you use it on behalf of — and Matan Green, who builds and runs oloy as an individual (“we”, “us”). There is no company behind oloy; if one is ever formed, these terms will name it. Using oloy means you accept them. If you are using oloy for an employer or client, you are confirming you may accept these terms on their behalf.

oloy is a monitoring service for web applications. You give it a URL; it explores the application in a real browser, decides which flows are worth watching, and then runs those flows on a schedule. When a flow stops working, oloy reports what broke and drafts a prompt you can hand to a coding tool.

oloy is early software under active development. Features appear, change and are removed. In some configurations the service will decline to start a check rather than run one it cannot finish, and it will say so plainly rather than pretend.

Sign-in is limited to addresses we have invited. There is no open sign-up, and an address we have not invited cannot create an account. We may withdraw an invitation at any time, and doing so ends the session it was using.

oloy costs nothing today and takes no payment details. If that changes we will say so before anything is charged, and these terms will change with it — the clauses a paid service needs are not written here, because there is nothing to pay for.

You sign in with a Google account. Keep it secure: anything done through your account is treated as done by you. Tell us if you think someone else has got into it. You must be old enough to enter into a contract where you live, and at least 16 in any case.

This is the one commitment we genuinely need from you. You may only point oloy at an application you own, or that you are clearly authorised to test. Automated sign-in, form submission and repeated traffic against someone else’s system without their permission is, depending on where you are, a breach of their terms or a criminal offence — and you would be the one directing it.

By adding an application you confirm you have that authority, that you may give us any sign-in details you provide, and that you may allow the recording described in the Privacy Policy — including of any other person’s data your application happens to display while a check runs. If you lose that authority, remove the app.

So there are no surprises, a check will:

• load pages, follow links, and sign in with any details you gave it;
• fill form fields with made-up values and submit them — which creates real data inside your application;
• click controls, and repeat all of it on the schedule you set;
• record what it saw, as set out in the Privacy Policy.

oloy holds back and asks you first only where it judges an action to be destructive. Everything else it considers ordinary use, and runs unasked. That judgement is made by software and it will sometimes be wrong in both directions: it may ask about something harmless, and it may go ahead with something you would rather it had not.

Given the section above: prefer a staging environment, or a production account you are content to see filled with test records. Use a dedicated test login rather than your own. Keep your own backups — oloy is not one, and we are not responsible for data created, altered or removed inside your application by a check you asked for.

You give us sign-in details for your own application so oloy can get past its login. We use them only to sign in to the application you gave them for. What is and is not stored is described in the Privacy Policy; the short version is that oloy’s database keeps the login method and the username, not the password, and that oloy is not a secrets manager. Give it a test account with the least access that still exercises the flows you care about.

Your application, and everything oloy records from it, remain yours. You give us only the permission we need to run the service you asked for: to access your application, to record and store what a check captures, to send the text described in the Privacy Policy to the AI provider named there, and to show it all back to you.

That permission does not extend to marketing, publication, or training models — we take no such licence, and would ask you first.

oloy itself — the service, its interface and everything in it that is not yours — stays ours. If you send us feedback we may act on it freely and without owing you anything for it.

A check shows us the inside of your application — the pages it renders, the screenshots and video recorded while it runs, and, because a person here reads an alert before it reaches you, whatever that alert describes. We treat all of it as confidential. We do not pass it to anyone else, and we will not publish it, quote it, or show it to another person without asking you first.

Three exceptions, and the Privacy Policy sets out each one:

• the text of your pages goes to the AI provider named there, in section 7 — that is how oloy works out what a flow does and whether it broke;
• the infrastructure that holds the rest — our host, our database — is named in section 9 of the same page;
• and the analytics processor of section 10, which we use to see how oloy’s own interface is used.

None of the three is an audience: they are how the service runs, and all three are written down rather than folded into a phrase about trusted partners. The third one needs a sentence of its own, because on a product like this the name alone would not tell you enough. What the analytics processor receives is not the inside of your application. The recording blocks every image and masks every text node in the browser before anything leaves it, by default on every screen rather than page by page — so what it can show us is you using oloy, never your app on the screen behind it.

This is the other half of the section above. That one is about the licence we do not take; this one is about what we do with what we already have. You have both, and they are not the same promise.

The flows oloy chooses, its verdicts about what broke, and the fix prompts it drafts are generated by software, partly by AI models. They are frequently useful and they are not guaranteed. oloy will sometimes miss a real break and sometimes report one that is not there.

Do not use oloy as your only check on whether your application works, and read a drafted fix prompt before you run it against your code.

Don’t:

• point oloy at a system you are not authorised to test;
• use it to load-test, stress, scrape at volume, or otherwise interfere with any system — yours or anyone else’s;
• use it to break the law, or to help anyone else do so;
• try to get at parts of the service that are not yours — other people’s accounts, other people’s results, our infrastructure;
• work around access limits, or resell the service as your own.

We may suspend or end access immediately if we think any of this is happening.

There is no uptime commitment. Checks may be delayed, may not run, and may be declined outright while the service is still being built. We may change, pause or discontinue any part of oloy, and we will try to give notice where a change would lose you something you were relying on.

You can stop at any time — ask us to delete your account and we will. We can end or suspend your access at any time too, including because the early-access period finished. When access ends, checks stop; ask and we will delete what we hold, as described in the Privacy Policy.

oloy is provided as it is, without warranty of any kind, to the fullest extent the law allows. We do not promise that it will find every problem, that what it reports is correct, that it will be available when you need it, or that it is fit for any particular purpose of yours.

To the fullest extent the law allows, we are not liable for indirect or consequential loss, for lost profit, revenue or data, or for anything that goes wrong inside your own application as a result of a check you asked us to run.

Beyond that, our liability for anything arising out of oloy is limited to the maximum extent permitted by law. Nothing here limits liability that cannot be limited by law — including for death or personal injury caused by negligence, or for fraud.

We may update these terms. The updated version appears on this page with a new date, and continuing to use oloy after that means you accept it. For a change that materially reduces what you get, we will tell you rather than rely on you noticing.

Write to hi@oloy.ai — for anything about these terms, a legal notice included. If something goes wrong between us, please write first: nearly everything is easier to fix that way.