The policies your site needs, written from your facts.
A privacy policy, terms of service and refund policy — drafted from what your business can actually state, hosted at a URL you control, with every assumption named and every gap listed. No bracketed placeholders. Ever.
Three documents, each written for its own reader
One call per document, not one call for all three. A terms of service has a different reader and a different failure mode than a privacy policy, so it gets its own prompt and its own budget.
Privacy policy
What personal data you collect, why, who it goes to, how long you keep it, and how someone gets it back or deleted.
Your description of the product, the data you say you collect, and the processors you name.
Terms of service
What the service is, who may use it, what a user agrees to, acceptable use, payment and cancellation, and how the terms change.
What you charge, who you serve, and what your own site already says.
Refund policy
What can be refunded, in what window, what is non-refundable, how to ask, and how long the money takes to come back.
Your billing model and the refund window you actually honour.
Type a short description, paste your homepage URL, or point it at your Ounie brains. A contact email is required — a policy nobody can be reached about is not a policy.
Each document is written, then scanned. Placeholders, template tags and fill-in-the-blank rules fail the check, and a failed draft is discarded before you see it.
Copy the markdown onto your own site, or link the hosted page while you wait for counsel. Revoke it whenever you like.
What it will assume, and what it refuses to invent
Every policy generator faces the same moment: a clause needs a fact the business never supplied. There are three things you can do about it, and only two of them are honest.
- Write at the level of generality your facts support
- Record what it assumed, inside the document
- Name every fact you still have to supply
- Cite the brain page a clause came from
- Insert a bracketed placeholder anywhere
- Invent an address or registration number
- Pick a governing-law jurisdiction for you
- Claim a certification you did not state
This is not legal advice, and we are not going to bury that.
This drafts a starting document from your facts. It is not legal advice and it is not a substitute for a lawyer. Read it, fill the gaps it names, and have a qualified lawyer in your jurisdiction review it before you publish it.
Every API response carries notLegalAdvice: true and the notice in full. An agent reading only JSON is still told.
The hosted draft leads with it, in the reading column, at body size. It is not a footer and not small print.
The seal is stamped after the document is written. The disclaimer is part of the artifact, not a wrapper around it.
What it is good for: getting from nothing to something a lawyer can review in minutes rather than weeks, and getting a real privacy URL in front of an app store reviewer today. What it is not good for: replacing the review.
Who reaches for this
Four situations where the gap between nothing and a reviewed document is the whole problem.
You are launching next week
You need three documents on the site before the first customer lands, and you do not yet have a lawyer on retainer. Get a draft that says what your business actually does, then hand it to counsel with the gaps already listed.
An app store is asking for a privacy URL
Apple and Google both want a live, reachable privacy policy URL before review. Every draft here is hosted at a public link the moment it is written, and you can revoke it later.
You run an agency and ship client sites
Every client site needs the same three documents, written from that client's facts rather than the last client's. Point it at their homepage and get a draft per client in one call.
An agent is building someone a website
The keyless x402 rail takes the business facts inline and pays in USDC on Base — no Ounie account, no key exchange. The agent gets markdown plus a hosted URL to link from the footer it just built.
Three ways in, and one of them needs no account
Policy Studio is an agent tool first. A key works on REST and MCP alike; an agent with no Ounie account pays per call in USDC.
The same endpoint the dashboard uses. A key can never overdraw — a short wallet is refused with 402 and a link to top up, before any work runs.
Streamable HTTP and legacy SSE from one endpoint. The Ounie AI Team, Claude, Cursor and the AI SDK all connect; hosts that cannot set a header pass the key in the URL.
No account, no key. Supply the business facts inline or a public URL. Bad input is refused before a price is ever quoted, and nothing settles until there is a document to hand back.
curl -X POST https://policies.ounie.com/api/policies \
-H "Authorization: Bearer $OUNIE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"documents": ["privacy", "terms", "refund"],
"contact_email": "hello@acme.dev",
"url": "https://acme.dev",
"jurisdiction_hint": "California, USA"
}'Priced per document, billed on what passed
15 credits for the set of three, 6 for one on its own. A credit is one cent, drawn from the same Ounie wallet every app in the fleet uses.
The set is cheaper per document than buying one, because the second and third document reuse the fact-gathering — including reading your site — that the first one paid for.
Reading a draft again, exporting it, and revoking its page are free forever. Drafting again re-bills, because it is new work.
See the pricing pageIt is struck from the bill, not discounted. A draft that comes back with a bracketed placeholder in it is discarded before you ever see it, and you are charged for the documents that passed — 6 credits each. If none pass, the whole run refunds.
The things people ask first
Is this legal advice?
No. It drafts a starting document from the facts you give it. It is not legal advice and it is not a substitute for a lawyer. Every copy of every document says so — in the API response, on the hosted page, and on this site. Have a qualified lawyer in your jurisdiction review a draft before you rely on it.
Will it put [Your Company Name] in my policy?
No, and that is enforced in code rather than asked for in a prompt. A draft is scanned for bracketed placeholders, {{template tags}}, fill-in-the-blank rules and TBDs before it is stored. If one is found the draft is discarded and you are not charged. What could not be filled comes back in "gaps" instead.
What if it does not know something about my business?
It does one of two things and tells you which. Either it writes the clause at the level your facts support and records the assumption in the document, or it drops the clause and names what you have to supply. It will not invent a postal address, a registration number, a governing-law jurisdiction, or a named data processor.
Where does it get the facts?
From whichever you give it: a short description you type, a public URL it reads, or your own Ounie brains. Reading your brains is free — the retrieval call is not metered — and the draft cites the brain page each part came from.
What does a draft cost?
15 Ounie credits for the full set of three, 6 for a single document. That is $0.15 and $0.06 — credits are worth one cent each. You are charged for documents that pass validation, not for documents you asked for.
Can I take the document down?
Yes, at any time. Each draft is hosted at an unlisted URL you control; revoking it stops the page resolving on the very next request. Restoring it brings back the same URL rather than a new one.
Is the hosted page indexed by search engines?
No. Hosted drafts carry noindex, both as a meta tag and as an HTTP header, and the URL is unguessable. A draft nobody has reviewed should not turn up in search results under your business name.
Get to a draft a lawyer can read.
Three documents, hosted, in one call — with the assumptions named and the gaps listed so the review starts from a real conversation.