Legal / Terms
The terms for this website, and for the flow beta.
The website part asks almost nothing of you. The flow part sets out what your team may capture, who owns it and what happens when the beta ends.
What these cover
Two things, and one of them asks a great deal more of you than the other.
This website is the easy half. By using it you accept these terms, and if you do not, the remedy is simple: stop reading and close the tab.
flow is our product, and it is in beta. Every section below that names flow applies to anyone using it. The rest applies to the website.
For flow the agreement is with your company. You accept it by ticking the box at sign-up or by using flow, and in doing so you confirm you are allowed to commit your employer. Where this page says "you" about flow, it means that company.
Work we do for a client runs on a separate written agreement between us and that client. Where you have signed something with us that covers the same ground as a section here, that document wins and this one gives way to it.
Using the site
Read it, share it, quote it.
Do not try to reach parts of the site, or the systems that run it, which are not open to you.
Do not send malicious code, spam or unsolicited commercial messages through any of the addresses or numbers here.
Do not scrape, crawl or harvest the site by automated means without asking us first. Answer engines and search crawlers are welcome, and robots.txt says which ones and where.
Do not misrepresent who you are or who you work for when you get in touch.
Do not do anything that disrupts the site or is likely to take it down.
flow is in beta.
flow is invite-only and it is early. We provide it as it is, with no warranty that it works, that it is available or that it fits what you have in mind.
Three things follow from that.
We may change any part of flow or withdraw it, and we may do so without notice.
Data in the beta may be reset before general availability. Export anything you need to keep.
Nothing we show you or tell you we are working on is a commitment to build it.
There is no uptime commitment and no support commitment while the beta runs. Write to us and we answer as fast as we can.
Your account, and the people in it
flow is for business users, acting for the company they work for. It is not for consumers and it is not for anyone under 18.
An organisation owner invites people, sets what each one may do and removes them again. There are four roles: owner, admin, member and viewer.
You answer for what the people in your organisation do with flow. Keep sign-in credentials safe, tell us at once if an account is compromised and remove people who have left.
Where your own product's data is involved in what you capture, getting consent for it is yours to arrange.
Your AI key is your contract.
You supply the Anthropic or OpenAI key that flow uses. So you contract with that provider and you pay them directly, under their terms and their usage policies.
We are not liable for their outages, their rate limits, their content filters, their price changes or what they charge you.
flow carries rate and quota controls and they help. None of them is a guarantee about your spend, so watch your own provider dashboard.
What you may capture
This is the section that matters most, so it is written as promises you make to us.
For every page your team captures, you warrant that one of three things is true: you own it, you are authorised to access it or it is publicly available.
And you agree that you will not do any of this.
Use the extension to get past authentication, a paywall or any other access control.
Capture at a rate or a volume that puts load on somebody else's site.
Ignore the terms or the robots directives of a site you are capturing.
Capture pages whose main content is other people's personal data, without a lawful basis for holding it.
Upload anything you do not hold the rights to.
You promise two more things about personal data. Where a capture holds it, you have a lawful basis for holding it and you have given the people it belongs to whatever notice the law requires. And you will not point flow at pages built around health records, payment card numbers or government identity numbers.
We may suspend an account that breaks any of these, and we tell you why when we do.
What you may not do to flow
The section above is about what your team captures. This one is about the product itself, and it is shorter.
Do not reverse engineer flow, decompile it or work to derive its prompts, its scoring logic or its source.
Do not resell flow, rent it out or hand access to anyone outside your organisation.
Do not work around a rate limit, a quota, the URL blocklist or any other control in the product.
Do not upload malicious code, and do not use flow to attack anything.
Do not use flow or what it produces to build a product that competes with it.
Same consequence as the capture rules: we may suspend an account that breaks any of these.
Benchmarking, and how to ask for a takedown
Capturing other companies' websites is something flow is built to do, and it is an ordinary part of competitor research.
What your team captures of a third party is stored in your workspace as evidence for your own analysis. How you use it, who you show it to and what you publish from it are yours to answer for.
If you own a site and you want a capture of it taken down, write to start@form-three.com with the address. We acknowledge within 5 working days and act within 14.
How we handle your data
Our privacy policy says what we hold and why. This is the promise that goes with it, and it is the part your security reviewer will want.
For everything your team captures we act on your instructions and on nothing else. We keep it confidential, we hold it under the security measures the privacy policy describes, and we let only the people who need it near it.
We use sub-processors and they are named in the privacy policy. We tell you before we add one. If a new one does not work for you, you may end this agreement over it.
We help you answer a request from a person whose data is in a capture, and we help you meet a regulator's deadline after a breach. Neither costs you anything during the beta.
When the account closes we delete your content on the schedule in the privacy policy. If you ask inside the export window we hand it back first. Ask us for what you need to show an auditor that this is true and we will give you what we have.
Confidentiality
Each of us will see things the other does not publish, and neither of us passes them on.
Yours is your content, what your team captures and what you tell us about your product. Ours is flow itself: its prompts, its scoring logic, our pricing and anything we show you before it ships.
Both duties run for 3 years after the account closes. Neither covers what is already public, what either side worked out on its own or what a court or a regulator requires to be handed over.
flow is in beta, so what you see inside it is ours to announce.
Who owns what
You own what you put in and what comes out for you. That is your captures, your flows, the findings, the scores and everything you export.
We own flow itself: the platform, its code, its prompts, its scoring taxonomies and the models of the work behind them.
To run the service we need a licence from you, and it is a working licence and nothing wider. You grant us the right to host, store, copy, transmit, display and adapt your content. We may pass it to the sub-processors named in the privacy policy, so far as that is needed to provide flow to you.
Adapting is in there because it is what the product does: cutting a screenshot into tiles, redacting it, scoring it and building a presentation out of it. The licence ends when you delete the content or close the account.
We also read aggregate usage data to improve the product: counts, timings, error rates and which features get used. It carries no capture content, no page text, no client name and nothing that identifies a person. We may keep using it after your account closes. By then it is numbers and nothing else.
On this website, the writing, the case studies, the design, the photography and the code belong to us or are licensed to us, unless a page says otherwise. Client logos, product screenshots and brand assets belong to the clients they name, and appear here with their agreement.
You may link to any page, read it and quote a short passage with attribution to form-three and a link back to the page it came from. Ask us first before republishing a page in full or building something derived from it. The answer is usually yes.
What flow produces is not advice.
Findings, scores and generated copy come out of statistical models. They can be wrong or incomplete, and a wrong finding reads exactly like a right one.
Some of what flow produces touches accessibility and compliance. A score is not an audit, an assurance or a legal opinion, and nothing flow writes is legal, medical or financial advice.
A person has to review the output before anybody acts on it. That review is your job.
This site is not an offer.
The pages here describe what we do and what we have done. None of it is a binding offer of services, a quotation, or advice you should act on without talking to us.
Sending an enquiry or booking a call does not create a contract and puts no obligation on either of us. Work begins when both sides sign something that says so.
Numbers quoted in our case studies are the results those engagements produced, in those markets, with those teams. They are evidence of what we have done, not a promise of what your project will do.
Liability and links out
flow and this website are provided as they are. We work to keep both accurate and current, and we make no warranty that either is complete, correct or suitable for whatever you have in mind.
So far as the law allows, every term the law would otherwise read into this agreement is excluded. That includes any implied promise about quality, fitness for a purpose or non-infringement.
So far as the law allows, we are not liable for indirect or consequential loss, for lost profit, for lost data or for business interruption.
Our liability for everything arising out of flow or this website is capped at SGD 100. That is a total across everything, not a figure for each claim. Where you have paid us fees in the 12 months before a claim and they come to more, the cap is that amount. The beta is free, so SGD 100 is the cap today, and it is set there because you pay us nothing.
You indemnify us against claims arising from what your team captured or uploaded. That includes a claim from the owner of a site you captured and a claim from a person whose data was in a capture.
If such a claim arrives we tell you promptly, we let you run the defence and we do not settle without your agreement. You keep us in the picture and you carry the cost.
The cap above does not apply to that indemnity. Nothing here limits liability that cannot lawfully be limited, which includes death or personal injury caused by negligence, and fraud.
Where we link to another site, whether a client, a source or a tool, it is for reference. We do not control those sites, do not endorse them by linking and are not responsible for what is on them.
Ending it, and getting your data out
You can stop using flow whenever you want, and an organisation owner can delete the whole organisation from inside the product.
We can end your access with 30 days' notice. We can end it at once if you break the capture rules, break the rules about flow itself or put the service at risk. Where we suspend an account without ending it, we tell you why and what would lift it.
Either way you have 30 days to export what you want to keep, using the exports built into the product. After that we delete your content on the schedule set out in our privacy policy.
If we withdraw the beta, you get the same 30 days' notice and the same export window.
Ending it does not undo what is already settled. Ownership, confidentiality, liability, the indemnity, feedback and governing law all carry on afterwards.
Feedback
Tell us what is wrong with flow. It is a beta and that is what a beta is for.
Anything you send us about the product we may use, build on and ship. We may do that anywhere and for as long as we like, and we owe you nothing for it. That covers bug reports, feature requests and opinions.
It does not cover your content, which stays yours.
The rest of the small print
Short, and every line does a job.
This is the whole agreement. These terms and the privacy policy are all of it. Nothing said in a demo or an email adds to them.
One bad clause does not sink the rest. If a court strikes a line out, everything else carries on.
Letting something go once is not giving it up. We can enforce a term later even where we did not enforce it the first time.
Handing it on. You may not pass this agreement to somebody else without asking us. We may pass it to a company that buys our business.
Things nobody controls. Neither side is liable for a failure caused by something outside its reasonable control.
Notices. Ours go by email to the organisation owners. Yours come to the address at the end of this page.
Nobody else can enforce this. Only you and us, and the Contracts (Rights of Third Parties) Act 2001 does not apply.
Law, changes and who to ask
These terms are governed by the law of Singapore, and the courts of Singapore have exclusive jurisdiction over any dispute arising from your use of this website or of flow.
We update these terms from time to time, and the date at the top of the page is the last revision.
For a change that materially affects flow we email the organisation owners 30 days before it takes effect. If you do not accept it, close the account inside those 30 days and the old terms hold until you do. For the website, using it after a change means accepting it.
This site and flow are run by form-three Pte. Ltd., registered in Singapore under UEN 202321123E. Questions about these terms go to start@form-three.com, and security reports go to security@form-three.com. How we handle personal data is a separate page: our privacy policy.