REVIEWPRO AND REVIEWPRO PREMIER TERMS: A QUICK GUIDE
ReviewPro and ReviewPro Premier Terms: A Quick Guide
What it is. ReviewPro reviews your contracts inside your selected word-processing tool e.g. Microsoft Word or Google Docs against your chosen playbook. ReviewPro Premier adds a hosted document repository, intake workflow, and routing to e-signature.
Who Owns What
| You Own | We Own |
Documents | Contracts you upload, the marked-up documents we return, your comments and redlines | Nothing |
Playbooks | Your edits to a LegalSifter standard playbook; the substance of any playbook we configure for you (rules, logic, decision trees, legal guidance) | LegalSifter standard playbooks (the 100+ library); formatting (system-level implementation, trade secret); structural architecture, prompts, code |
AI in / out | Your submitted text and the customer-facing reviewed document | Our prompts, JSON results (the machine-readable plumbing behind the reviewed document), API responses, machine-readable outputs, classifier results, system metadata |
Premier add-ons | Contracts and metadata you store, ticket content you create, documents you route for e-signature | Repository platform, ticketing engine, integration code, system performance metadata |
How Data Flows
How It's Licensed
The order form specifies your selection.
| Credit-Based | Per-User Subscription |
Who it suits | Law firms, consulting firms, professional services providers, and customers who want flexible pay-as-you-go usage | Internal teams reviewing your own contracts; one named, non-transferable seat per User |
Use scope | Your own contracts AND clients' contracts (within the rules) | Your own contracts only |
Hard prohibitions | No direct client access unless those clients are also licensed Users; all general use restrictions apply | No service bureau, no managed review for third parties, no commercial output reuse, no automation or APIs |
Fee mechanic | Pay-up-front credits debited per document; rollover during term; forfeiture on cancellation | Per-named-user fee for unlimited contract reviews under a fair use policy |
What We Keep Confidential
We Keep Your Stuff Confidential | You Keep Our Stuff Confidential |
Your contracts, the data inside them, your IP, and the substance of your custom playbook content | Our software, our standard playbooks, our formatting, our prompts, and our underlying technology |
What We Do With Your Data
During the Term: we use it to provide and support the service to you.
Anonymously and aggregated only: we use it for security, analytics, benchmarking, R&D, and product improvement; we cannot identify you, your users, or any individual.
We do not: train AI on your data without your written consent.
Who to Contact:
Commercial Counsel: Cherryn-Paige Bissett — [email protected]
VP Sales: Matt Darling — [email protected]
Annex A: Glossary
Term | Plain English Meaning |
Service | ReviewPro and, where licensed, ReviewPro Premier, including the Add-In, the AI engine, the API, and any LegalSifter-hosted infrastructure. |
Add-In | An extension to the selected third-party word processor software (Microsoft Word, Google Docs, etc.) that lets the user access the Service from inside that software. |
Standard Playbook | One of LegalSifter's 100+ pre-built playbooks. Licensed for use within the Service. Not transferred. |
Customer Provided Custom Playbook | Your in-product edits to a Standard Playbook to reflect your preferred positions. The substantive content is yours. We do not use it for any other customer. |
Custom Playbook Architecture | A bespoke playbook LegalSifter builds for you for a fee. The substantive content is yours; the underlying structural architecture, and Standard Playbook components and Formatting remain LegalSifter Property. |
Formatting | The proprietary system-level implementation that makes any Playbook executable inside the Service. Trade secret. Not transferred under any tier. |
LegalSifter Property | The Service, Add-In, Standard Playbooks, Formatting, prompts, JSON results, and the LegalSifter IP embedded in any Custom Playbook. Owned by LegalSifter; licensed only as the Service Terms expressly permit. |
Customer Data | Documents you submit, and reviewed documents the Service generates for you. Excludes LegalSifter Property, Standard Playbooks, Formatting, prompts, and de-identified or aggregated analytics, safety, and operational metadata. |
AI Third-Party Components | The LLM providers we use to deliver the Service. Used under Zero Data Retention ("ZDR") terms: Customer Data is not saved to disk by the AI Third-Party Component provider, not logged for human review, and not used to train models. |
Classifier Results | Trust and safety flags the Service and AI Third-Party Components generate while processing. They contain no Customer Data. They are LegalSifter operational metadata. |
Personal Information | Information that identifies an individual or household. Customer is the Controller; LegalSifter is the Processor. International transfers rely on the EU-US Data Privacy Framework (with UK Extension and Swiss-US Framework); EU SCCs (Module 2 or 3) apply automatically as fallback. Sub-processors at legalsifter.com/subprocessors. |
Annex B: Frequently Asked Questions
Will my contracts train the LLM?
No. Zero Data Retention provisions are in place with the AI Third-Party Component providers. We do not train without your written consent.
Can I use a Custom Playbook outside the product?
You can use the substantive content (rules, logic, guidance). You cannot lift Formatting, prompts, JSON outputs, positions taken from Standard Playbooks that have been incorporated into your Custom Playbook, or the structural architecture.
Where is data hosted?
Service infrastructure is on enterprise-grade cloud. AI Third-Party Components operate under ZDR. Detailed security FAQ is available on request.
Premier specifics?
Repository size is set in the Order Form. Supported E-Signature Provider list is available on request. LegalSifter is not liable for the third-party e-signature provider's enforceability or service performance.
What happens at termination?
We delete or return Customer Confidential Information per our standard retention and deletion processes, subject to legal, audit, and backup-cycle exceptions.
Are sub-processors disclosed?
Yes. The current list lives at legalsifter.com/subprocessors. We give at least 30 days' notice before adding a new sub-processor where practicable. You may object on reasonable data-protection grounds.
What's the difference between a Customer Provided Custom Playbook and Custom Playbook Architecture?
A Customer Provided Custom Playbook is your in-product edit to a Standard Playbook. Custom Playbook Architecture is a bespoke playbook LegalSifter builds for you for a fee. In both cases the substantive content is yours; Formatting, LegalSifter Standard Playbook elements and the structural architecture remain ours.
Who to Contact
Commercial Counsel: Cherryn-Paige Bissett — [email protected]
VP Sales: Matt Darling — [email protected]