Policies that stay true after the day you publish them.
Most generators hand you a document and walk away. A policy is only accurate on the day it is written — the interesting problem is every day after that, and it is the one this product is built around.
iLawForms generates a privacy policy, terms and conditions, a California privacy notice and a refund policy from one set of answers, then hosts them at a stable URL and keeps them current as the clause library is revised.
We are a company formed in the State of Florida, United States.
The parts that are different from a template.
These are claims you can check against the product rather than adjectives about it.
A reviewed clause library, not a template
There is no master document with your name dropped into blanks. Each policy is assembled clause by clause, and a clause that does not apply to you is simply absent — not greyed out, not left in with a caveat.
Your answers become facts, not prose
The questionnaire produces a structured fact set. Clauses declare the conditions under which they apply, and the document is the result of evaluating those conditions. That is why the documents agree with each other instead of contradicting themselves.
The same answers always produce the same document
Rendering is deterministic. Given the same facts and the same clause release, the output is identical down to the byte — which is what makes it possible to prove, years later, exactly what your policy said and why.
Every published version is kept
Each publication is immutable and timestamped, at its own permanent URL. When somebody asks what your policy said on a particular date, that is a link rather than an afternoon in your inbox.
When a clause changes, your policy changes
A revision to the clause library regenerates every affected document and republishes it. Documents whose wording did not actually change are left alone, so an update email means something happened.
Nothing is generated by a model
Legal text is written and reviewed by people. Where we use AI at all it suggests inputs a human confirms — classifying a tracker we do not recognise, or explaining a question — and it is structurally prevented from touching the text of a document.
What this product is not.
This category sells on fear, and the fear is mostly justified. That is not a reason to overstate what a document can do for you.
We are not a law firm
We do not give legal advice and we are not your lawyer. We can explain what our product does. We cannot tell you what the law requires of your business, and nobody here is in a position to.
A document is not compliance
A generated policy is an accurate description of what you told us you do. It does not make a cookie banner block trackers, build a deletion workflow, or stop a vendor moving data somewhere it should not go. Those are things you do, not things you publish.
It is only as accurate as your answers
The questionnaire asks in plain language and explains the harder questions, but if you tell us you do not use analytics when you do, you get a confident, well-typeset document that is wrong.
Coverage is deliberately narrow
EU, UK and California at launch. Each regime is a permanent maintenance commitment, not a checkbox, and we would rather cover three properly than list twelve.
How we handle your data
We hold the answers you give us, the documents generated from them, and the account details needed to bill you. What we collect, why, how long we keep it and who processes it on our behalf is set out in our privacy policy, with the full list in our sub-processors.
If you want to see, correct or delete what we hold, the request form linked from our privacy policy is the route — it verifies your identity, gives you a reference and starts a tracked statutory deadline. Emailing us does none of those things.
Security researchers: our security policy covers how to report a vulnerability and what we commit to in return.
Anything else — get in touch.