Questions we are asked before every trial

No. Customer documents are never used as training data and there is no shared learning pool between accounts. Inference runs in EU infrastructure under a zero-retention agreement with our model providers, meaning prompts and documents are not persisted by them at all. Inside Clauzy, documents are stored only for the retention period you configure, which defaults to thirty days and can be reduced to twenty-four hours.

On the benchmark set we publish to customers under NDA, clause segmentation on well-formed DOCX agreements is correct in the high nineties, and on scanned PDFs it drops several points depending on scan quality. More usefully: where Clauzy is uncertain, it marks the clause as requiring human attention rather than guessing. Silent errors are the failure mode that matters in this category, so the system is tuned to admit uncertainty rather than to maximise a headline accuracy figure.

It replaces the first pass. The markup a junior reviewer would spend two hours producing arrives in minutes, with citations, so the qualified person spends their time deciding rather than locating. Nothing is ever sent to a counterparty by Clauzy. Every suggestion requires a human to accept it, and the decision record shows who did.

Yes, and most teams start there. Clauzy ships with a market-standard baseline covering 62 clause types. During onboarding it reads up to fifty of your signed agreements and infers the positions you have actually been accepting, which is frequently different from what the policy document says. You then confirm, correct or reject each inferred rule, and the result becomes your first playbook.

DOCX, DOC, PDF including scanned documents, RTF and plain text, with schedules and annexes handled as part of the same instrument. Contract text is supported in English, Dutch, German, French and Spanish. Jurisdiction-aware commentary is available for England and Wales, the Netherlands, Germany, France, Ireland and Delaware; other governing laws are reviewed against your playbook with enforceability commentary marked unavailable rather than invented.

A Solo or Professional account is usable within ten minutes of signing up. A Business deployment with custom playbooks, routing rules and single sign-on typically takes two to three weeks, most of which is your team deciding what the fallback positions should be rather than anything technical. Enterprise migrations with historical contract backfill run four to eight weeks.

You export everything, including documents, ledgers, redlines, playbooks and decision records, in open formats, and we delete our copies within thirty days of termination including from backups on the next rotation. Playbooks export as readable rule documents rather than a proprietary blob, so the work you invested stays portable.

Yes. Outbound review checks your own draft against your playbook before it leaves, which catches the common failure where a template was edited for one deal and then reused. It also flags where your paper is more aggressive than your stated position, which tends to shorten negotiations rather than lengthen them.

Clauzy connects to Google Drive, SharePoint and Slack on Business, and offers a REST API with webhooks on Enterprise. There is a native integration with Ironclad, and customers on other platforms typically wire Clauzy in at the intake step through the API so review happens before the document enters the workflow.

Clauzy is a tool used by responsible people, and our terms are explicit that it does not provide legal advice and does not accept liability for review outcomes. That is not evasion, it is the honest position: no review tool can carry professional responsibility for a decision a person signs. What we do commit to is transparency of reasoning, so a reviewer can always see what was checked and what was not.