Contract Management (CLM)
Contractbook
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Scrive ApS · contractbook.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Contractbook at a glance
- Vendor
- Scrive ApS
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Contractbook 2/5, the mean of 6 judges. Contractbook, the contract management platform of Scrive ApS, Copenhagen, lands mid-table, persona-weighted totals 3.6 to 4.6. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Contractbook, the contract management platform of Scrive ApS, Copenhagen, lands mid-table, persona-weighted totals 3.6 to 4.6. Its strength is daily contract work: authoring and templates drew the top score (4 to 6), and negotiation and approval, repository and obligations and integration and exit each range 4 to 5, resting on German-language templates in ten categories, in-platform counterparty suggestions and AI-extracted renewal and expiry dates. Sovereignty (1 to 3) and pricing transparency (2 to 4) are weakest: the captured pages show a Copenhagen headquarters and a data processing agreement on the Danish Data Protection Agency's template, but leave hosting, the subprocessor list including the AI provider and the contracting entity's jurisdiction unconfirmed, and publish tier limits without price figures. Judges split on both: the sovereignty 3s credit the Danish signals while the 1 weighs the missing hosting and subprocessor disclosure as decisive; on pricing, rationales record the same absent prices yet scores run 2 to 4. AI extraction control sits flat at 4 on the terms' commitment not to use platform data for AI model training without consent.
Speaks for it
- Customisable templates in ten categories and five languages including German create contract drafts automatically when a HubSpot, Salesforce or Pipedrive deal stage changes.
- Counterparty recipients add suggestions directly in the platform without needing a licence, with private comments kept separate under individual permissions.
- AI extracts renewal and expiry dates, and renewal reminders carry assigned responsibilities on a central dashboard with savable filters.
- A documented API with webhooks and an API service level agreement for enterprise subscriptions joins HubSpot, Salesforce, Pipedrive, Slack and QuickBooks integrations and Okta or Microsoft Azure sign-in.
- Published tier limits — users 1, 5 and 10, contracts signed 100, 350 and 500 per year, templates 5, 15 and 25, 50 contract uploads — name which add-on sits in which tier.
Held against it
- We found no public information on where contracts and extracted data are hosted, on the subprocessor list including the AI or OCR provider, or on the contracting entity's jurisdiction.
- We found no public information on price figures for any tier or add-on, on onboarding or migration fees, on the minimum term or VAT treatment.
- We found no public information on a Word round-trip preserving changes, on redline comparison between versions, or on an approval audit trail naming who signed off which version.
- We found no public information on a bulk export of documents with their metadata, versions and audit trail — the terms grant only removal or archival within the platform.
- We found no public information stating the eIDAS level of the digital signature, or on certifications such as ISO 27001 or BSI C5.
Best for
- You want sales or operations users to generate contracts themselves from HubSpot, Salesforce or Pipedrive deal stages, negotiate in-browser with counterparty suggestions, and sign in the same flow.
- You need a central repository where AI-extracted renewal and expiry dates drive reminders assigned to named owners.
- Your contracts run in Danish, German, Swedish, Norwegian or English and you want ready templates across ten categories rather than a blank library.
- You require a contractual commitment that platform data is not used for AI model training without your consent.
Avoid if
- You must confirm hosting location, subprocessors including the AI or OCR provider, and the contracting entity's jurisdiction before entrusting your most confidential commitments — the captured pages leave these unconfirmed.
- You must compute the annual invoice before talking to sales — ask the vendor: the public pages we read do not show it
- Your negotiation process depends on Word round-trips with tracked changes, version-to-version redline comparison and an audit trail of who approved which version.
- You need a documented exit — a bulk export of documents with their metadata, versions and audit trail — before committing your portfolio.
The scores
| Criterion | Panel median |
|---|---|
| Drafting, templates & clause library | 2 of 5 |
| Negotiation, redlining & approval | 2.5 of 5 |
| Repository, deadlines & obligations | 2.5 of 5 |
| AI extraction & review transparency | 2 of 5 |
| Integrations, signature & exit | 2 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 1.5 of 5 |
Negotiation, redlining & approval
Show reasoningHide reasoning
How this is scored
Getting from draft to agreed text with a counterparty and through internal sign-off: redlining in Word and in the browser, external collaboration, version comparison, approval workflows, and a record of who approved which version.
0 — No negotiation support; versions are emailed back and forth outside the system.
3 — Comments and a version list inside the system, but no redline comparison, no Word round-trip, and approvals handled by email.
5 — Redlining with tracked changes, a Word add-in or round-trip that keeps changes, counterparty access without a licence, version comparison, and configurable approval steps by contract type or value.
8 — Conditional approval routing (value, deviation from playbook, risk), parallel and sequential approvers with delegation, an audit trail of every change and approval per version, and internal comments kept separate from what the counterparty sees.
10 — Negotiation is an auditable record: every concession traceable to who proposed and who approved it, approval rules an auditor or the board can read, negotiation duration reported per contract type, and the full history exportable with the signed version.
The General Counsel
Counterparties can drop actionable suggestions into the document in the platform, private comments and individual permissions exist, and a no-code builder drives conditional approval workflows. We found no public information on a Word round-trip that keeps tracked changes, redline comparison, or an approval audit trail naming who signed off which version — the concessions record I negotiate for. 2 7
The Procurement Analyst
Recipients add suggestions directly in the platform without needing a licence, individual permissions keep private comments separate from what the counterparty sees, a detailed version history is maintained, and a no-code builder sets conditional approval workflows driven by contract data. I found no public information on a Word round-trip, tracked-changes comparison, or an audit trail recording who approved which version. 7
The Sales Ops Owner
Counterparties can add suggestions directly in the browser, private comments stay separate from what they see, and the no-code automation builder sets up conditional approval workflows based on contract data — close to routing by value, though value and discount are not named as routing criteria. I found no public information on a Word round-trip, redline comparison between versions, or an audit trail of who approved which version. 7 8
The IT Integrator
Counterparty recipients can add actionable suggestions directly in the platform, private comments and individual permissions are supported, a detailed version history is kept, and a no-code builder sets conditional approval workflows based on contract data; we found no public information on a Word round-trip that preserves changes, redline comparison between versions, or an audit trail of who approved which version. 7
The Data Protection Officer
Counterparty recipients can add actionable suggestions directly in the platform without a licence, private comments and suggestions are kept separate by individual permission, a no-code builder runs approval and redlining workflows conditional on contract data, and a detailed version history is kept. We found no public information on a Word add-in or round-trip, version-to-version comparison, approver delegation, or an audit trail recording who approved which version. 7
The Skeptic
Counterparty suggestions inside the platform, private comments with individual permissions, conditional approval workflows and a detailed version history are published; we found no public information on a Word round-trip that keeps changes, a redline comparison between versions, or a record of who approved which version. 7 12
Repository, deadlines & obligations
Show reasoningHide reasoning
How this is scored
Knowing what has been signed and what it requires: a searchable repository with metadata, notice periods and renewal dates captured and reminded, obligations tracked to an owner, access rights by department, and reporting on the portfolio.
0 — A file store with folders; no metadata, no dates and no reminders.
3 — Metadata fields and an end date with an email reminder, but notice periods and auto-renewal are not modelled and reminders go to one person.
5 — Notice periods, renewal terms and end dates modelled as fields, reminders with escalation to named owners, full-text search including scanned contracts (OCR), and access rights per department or contract type.
8 — Obligations and milestones tracked with owners and status, contract hierarchies (framework, amendments, orders) linked, reminders logged so a missed deadline can be traced, and portfolio reports on renewals, value and counterparties.
10 — The repository is a system of record a company can be audited on: every deadline derived from a cited clause, reminders and their acknowledgements logged, retention and deletion rules per contract type, and a portfolio view a CFO can use for commitments and cancellations.
The General Counsel
Renewal and expiry dates are extracted by AI, reminders carry assigned responsibilities, metadata can be added with AI insights verified, and a central dashboard gives portfolio oversight. We found no public information on notice periods modelled as fields, OCR search of scanned contracts, department-level access rights, or deadlines traceable to the clause that set them. 1 2 9 12
The Procurement Analyst
AI extracts renewal and expiry dates and automatic reminders carry assigned responsibilities — the nearest thing to a named owner I found anywhere — with filtering by dates and data fields, savable filters, and a centralised dashboard. I found no public information on notice periods modelled as their own field, escalation chains, logged reminders, obligation tracking with status, or a portfolio report of commitments and what can be cancelled this quarter; for me that gap is the difference between a reminder inbox and a system of record. 1 9 10
The Sales Ops Owner
Renewal and expiry dates are AI-extracted, reminders come with assigned responsibilities, and contracts can be filtered by names, dates and saved data fields on top of a central dashboard with addable metadata. I found no public information on notice periods modelled as fields, per-department access rights, obligation tracking with status, or contract hierarchies linking framework agreements to amendments. 1 9 10 12
The IT Integrator
Contracts sit in one central store with AI-extracted renewal and expiry dates, user-added metadata, saved filters on names, dates and data fields, and renewal reminders with assigned responsibilities; we found no public information on notice periods modelled as fields, escalation of reminders, full-text search of scanned contracts, or access rights per department. 1 9 12
The Data Protection Officer
Central storage with user-added metadata, saved filters over names, dates and data fields, AI-extracted renewal and expiry dates, renewal reminders with assigned responsibilities and an oversight dashboard are published. We found no public information on notice periods and auto-renewal modelled as fields, OCR full-text search of scanned contracts, access rights per department, obligations tracked with owners and status, contract hierarchies, or portfolio reports on renewals, value and counterparties. 1 9 12
The Skeptic
Renewal and expiry dates are AI-extracted, reminders carry assigned responsibilities, and contracts filter by names, dates and data fields; we found no public information on notice periods as modelled fields, obligations tracked to owners with status, full-text search of scanned contracts, or logged acknowledgements that a reminder was seen. 1 2 9 12
AI extraction & review transparency
Show reasoningHide reasoning
How this is scored
Whether the AI that extracts dates and clauses or reviews a draft is disclosed, verifiable and controllable: named model provider and processing location, no training on customer contracts, extracted values shown with their source passage, and features the customer can switch off. A product without AI features is judged on stating so.
0 — AI extraction or review is marketed with no statement of the model, where it runs, or what happens to the contract text.
3 — AI features described as a benefit with a general privacy assurance, but no model provider named, no statement on training, and extracted values shown without their source.
5 — The model provider or subprocessor named, a stated commitment not to train on customer contracts, extracted values linked to the source passage for confirmation, and AI features that can be disabled per account.
8 — AI processing available within the EU, each AI feature documented with its purpose and inputs, accuracy or confidence shown per extracted field, review results traceable to the playbook rule that triggered them, and an EU AI Act position published.
10 — AI is an accountable assistant: customer choice of model or EU-only processing, no retention of contract text by the model provider stated contractually, every AI-suggested value logged with who confirmed or corrected it, and AI off by default until the customer enables it.
The General Counsel
The terms commit contractually not to use platform data for AI model training without consent, and users can verify AI-generated insights against added metadata — a commitment in the right document, not just marketing. We found no public information naming the model provider or processing location, a per-account switch to disable AI, confidence per extracted field, or a published EU AI Act position. 4 9 12
The Procurement Analyst
The terms state no use of customer data for AI model training without consent, and users add metadata and verify AI-generated insights themselves, which is something. I found no public information on the model provider, where AI processing runs, whether extracted values are shown with their source passage, a per-account off switch, or any EU AI Act position. 4 9 12
The Sales Ops Owner
The terms commit to no use of platform data for AI model training without customer consent, and users verify AI-generated insights with additional metadata. Beyond that I found no public information naming the model provider, the processing location, source-passage linkage for extracted values, or a per-account switch for the AI features. 4 9 12
The IT Integrator
The terms state plainly that customer data is not used for AI model training without consent, and users verify AI-generated insights and add metadata; we found no public information on the model provider, where the AI processing runs, whether AI features can be disabled per account, or a published EU AI Act position. 4 9 12
The Data Protection Officer
Built-in AI scans and extracts contract data, answers questions, spots red flags, rewrites clauses and recommends clauses while drafting, and the terms state that no data retained on the platform is used for AI model training unless the customer consents, with users able to verify AI-generated insights. We found no public information naming the model provider or subprocessor that receives the contract text, where the AI and any OCR processing run, an EU AI Act position, accuracy or confidence per extracted field, source-passage linkage for extracted values, or a per-account switch to disable the AI features. 4 9 12
The Skeptic
The terms commit that no customer data is used for AI model training without consent, which is a real statement on training; we found no public information on the model provider, where AI processing runs, per-field accuracy or confidence, extracted values linked to their source passage, or turning AI features off per account. 4 9 12
Integrations, signature & exit
Show reasoningHide reasoning
How this is scored
How contracts connect to the rest of the company and leave it again: CRM, procurement and ERP integration, e-signature (and which eIDAS level), SSO, an API, and a documented export of documents together with their metadata, versions and audit trail.
0 — No integrations, no API and no stated export; contracts can only be downloaded one by one.
3 — One CRM or storage integration and a bulk download of files, but metadata, versions and audit trail stay behind.
5 — A documented API, integrations with named CRM and storage systems, e-signature integrated with the level stated (simple, advanced or qualified), SSO, and a bulk export of documents with their metadata.
8 — Maintained integrations with systems common in DACH (SAP, Microsoft 365, Salesforce, DATEV-connected or procurement tools), qualified electronic signature available, webhooks, SCIM, and an export that includes versions, approvals and audit trail in an open format.
10 — Exit is designed in: a versioned API with a deprecation policy, a documented migration path in and out with the format stated, deletion after contract end confirmed, and the full repository — files, metadata, obligations and history — handed back without a professional-services fee.
The General Counsel
A documented API with webhooks and an enterprise API service level, HubSpot, Salesforce and Pipedrive connections, e-signature and Okta or Azure provisioning are all evidenced. We found no public information on the eIDAS level of the signature, SAP or Microsoft 365 integrations, or a documented export of documents with metadata, versions and audit trail for exit. 2 4 6 7 9
The Procurement Analyst
A documented API with webhooks and an enterprise API service level agreement, named CRM integrations (HubSpot, Salesforce, Pipedrive) plus QuickBooks, Slack and Zapier with 3,000+ cross-platform migrations, and sign-in via Okta or Microsoft Azure. E-signature is offered but the captured pages give no confirmed eIDAS level, and I found no public information on a bulk export of documents with metadata, versions and audit trail — the terms only let the customer remove or archive data within the platform, which is not an exit I could plan a migration on. 2 4 6 7
The Sales Ops Owner
A documented API with webhooks, named integrations for HubSpot, Salesforce, Pipedrive, Slack, QuickBooks and Zapier, identity-provider provisioning through Okta or Microsoft Azure, and digital signature in the same flow cover the quote-to-signature plumbing, with customer removal and archival rights in the terms. A help-centre article takes up the eIDAS question, but I found no public information stating which signature level applies, and none on a documented export of documents with their metadata, versions and audit trail. 2 4 7 9 13
The IT Integrator
There is documented API documentation with webhooks, an API service level agreement for enterprise API subscriptions, CRM integrations for HubSpot, Salesforce and Pipedrive, and sign-in through Okta or Microsoft Azure; we found no public information on the eIDAS level of the electronic signature, connectors for SAP or Microsoft 365, SCIM, or a documented export of documents with their metadata, versions and audit trail — the terms give only a general right to remove or archive data, plus a five-year retention rule that cuts the other way. 2 4 6 7 9
The Data Protection Officer
A documented API with an enterprise SLA, HubSpot, Salesforce and Pipedrive integrations, webhooks, Zapier and Make access, Okta or Microsoft Azure user provisioning and integrated digital signatures are public, and the terms let the customer remove or archive its own data. We found no public information stating the signature's eIDAS level, a bulk export of documents together with metadata, versions and audit trail, a documented migration path out with its format, or confirmed deletion after contract end. 2 4 6 7
The Skeptic
A documented API with an enterprise SLA, webhooks, named HubSpot and Salesforce integrations, and sign-in via Okta or Azure are published; we found no public information on the e-signature's eIDAS level or on a bulk export carrying documents out together with their metadata, versions and audit trail — the terms grant removal and archival rights but describe no export format. 2 4 6 7
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity is, where contracts and their extracted data are hosted, and who the subprocessors are — including the AI and OCR providers the text is passed to. Independently sourced by the sovereignty pipeline; weighted with care here because a contract repository holds a company's most confidential commitments and those of its counterparties.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and AI processing of unclear location.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent, or AI and OCR processing run outside the EU without saying so.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — AI models, OCR, email delivery, support — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published including AI and OCR providers with locations, and a DPA covering contract data as the customer's processing.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, AI processing within the EU on providers the customer can see, certifications (ISO 27001, BSI C5 or equivalent) published.
The General Counsel
The captured pages show a Copenhagen office and a data processing agreement built on the Danish DPA's template, yet they do not confirm the contracting entity and leave hosting, the subprocessor list and the location of AI processing unstated. For a repository holding our most confidential commitments and those of our counterparties, I would not put my signature to paper this thin. 4 5
The Procurement Analyst
A Copenhagen headquarters, support hours measured in Danish business days, and a data processing agreement based on the Danish Data Protection Agency template all point to a European operation holding the customer's contract data. But I found no public information on where contracts and their extracted data are hosted, who the subprocessors — including any AI and OCR providers receiving the text — are, or the contracting entity confirmed on the vendor's own pages, and a repository of a company's most confidential commitments deserves more than that. 4 5
The Sales Ops Owner
The vendor presents a Copenhagen headquarters and a data processing agreement built on the Danish Data Protection Agency template, with the company trail leading to a Danish entity under a Swedish group. Hosting location and the subcontractor list — including the AI and OCR providers the contract text is passed to — are areas where I found no public information, which leaves the chain unverified. 4 5
The IT Integrator
The captured pages leave the contracting entity's jurisdiction, the hosting location and the subprocessor list — including any AI and OCR providers — unstated, which is the decisive gap for a repository holding our most confidential commitments; what is published is a Copenhagen office address, a DPA based on the Danish Data Protection Agency's template, support hours tied to Danish business days, and the customer's ownership of contract data. 3 4 5
The Data Protection Officer
The headquarters address is in Copenhagen and a data processing agreement based on the Danish Data Protection Agency's template can be obtained through an automated workflow, covering processing of the customer's data — including counterparties' personal data in every contract — on the customer's behalf. We found no public information confirming the contracting entity's jurisdiction on the vendor's own captured pages, the hosting location for contracts and extracted data, or a subprocessor list naming the AI and OCR providers the contract text is passed to, and no certifications such as ISO 27001 or BSI C5 are mentioned. 4 5
The Skeptic
The contracting entity is Danish — Copenhagen headquarters and a DPA based on the Danish Data Protection Agency's template — and the terms place contract data with the customer; we found no public information on where contracts and extracted data are hosted, on subprocessors including the AI provider, or on certifications such as ISO 27001 or BSI C5. 3 4 5
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: the pricing basis (per user, per contract, per module), which features sit in which tier, add-ons for AI, e-signature volume or integrations, onboarding and migration fees, and the minimum term.
0 — No public prices at all; every tier is a sales conversation.
3 — A starting price exists, but the pricing basis (users, contracts, modules) or which features sit in which tier is unstated — the invoice is unknowable.
5 — Tier prices public with the pricing basis and main limits given, but at least one commonly needed piece (AI features, signature volume, integrations, extra users or onboarding) is unpriced.
8 — Every tier priced publicly with its basis and limits, add-on prices listed, onboarding and migration costs stated, minimum term and VAT treatment given.
10 — Complete price computability: annual invoice derivable for a given number of users, contracts and signatures, with every add-on, overage and implementation fee published.
The General Counsel
The pricing page is open about limits — users, signed contracts per year and templates per tier, plus which add-ons sit in which plan — which is more structure than most vendors show. But we found no public price figures for any tier, add-on, onboarding or migration, so the annual invoice is not computable from the page. 2 4
The Procurement Analyst
The pricing page publishes the basis and limits per tier — one, five or ten users, 100 / 350 / 500 signed contracts a year, five to 25 templates, 50 uploads — and states which add-ons sit in which tier, with fair usage limits on API access. I found no public information on the actual tier prices, onboarding or migration fees, minimum term, or VAT treatment, so a buyer cannot compute the annual invoice from what is captured. 2 4
The Sales Ops Owner
The pricing page publishes the tier basis and limits — users at 1, 5 and 10, contracts signed at 100, 350 and 500 per year, templates at 5, 15 and 25 — plus which add-ons like API access, Automations and user provisioning sit with which tier, and only fully signed contracts count toward the annual limit. I found no public information on the price of any tier, on add-on prices, onboarding or migration fees, the minimum term or VAT treatment, so the annual invoice stays a sales conversation. 2 4 12
The IT Integrator
The pricing page publishes the basis and limits per tier — users, contracts signed per year, templates and upload counts — and shows which add-ons sit in which tier, with a free tier named in the terms; we found no public information on price figures for the paid tiers, signature volume, onboarding or migration fees, minimum term, or VAT treatment, so the annual invoice is not computable from the captured pages. 2 4
The Data Protection Officer
Tier limits are published — users 1/5/10, 100/350/500 contracts signed per year, templates 5/15/25 and 50 uploads, with only fully signed contracts counting — and each add-on's tier membership is given. We found no public information on price figures for any tier or add-on, onboarding or migration fees, minimum term or VAT treatment, so a buyer cannot compute the annual cost from these pages. 2 4
The Skeptic
The pricing page publishes the basis — users, signed contracts per year, templates and uploads — and maps each add-on to its tier; we found no public information on the price amounts themselves, onboarding or migration fees, the minimum term or VAT treatment, and API access sits under unspecified fair-usage limits. 2 4
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Contractbook
Is Contractbook European?
Yes. whats-best.ai classifies Contractbook as EU-Made.
Where does Contractbook store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Contractbook have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Contractbook?
As of 21 Oct 2026, the panel rates Tomorro (2.5/5), Precisely (2.5/5) and fynk (2.5/5) highest among the other 19 Contract Management (CLM) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Precisely (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Contractbook alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 12 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 12 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage contractbook.com Checked 13 Oct 2026 Details →
- 2 Pricing page contractbook.com Checked 13 Oct 2026 Details →
- 3 Privacy policy contractbook.com Checked 13 Oct 2026 Details →
- 4 Terms of service contractbook.com Checked 13 Oct 2026 Details →
- 5 Drafting, templates & clause library — found from sitemap contractbook.com Checked 13 Oct 2026 Details →
- 6 Drafting, templates & clause library — found from sitemap contractbook.com Checked 13 Oct 2026 Details →
- 7 Negotiation, redlining & approval — found from sitemap contractbook.com Checked 13 Oct 2026 Details →
- 8 Negotiation, redlining & approval — found from sitemap contractbook.freshdesk.com Checked 13 Oct 2026 Details →
- 9 Repository, deadlines & obligations — found from sitemap contractbook.com Checked 13 Oct 2026 Details →
- 10 Repository, deadlines & obligations — found from sitemap contractbook.freshdesk.com Checked 13 Oct 2026 Details →
- 11 AI extraction & review transparency — found from sitemap contractbook.freshdesk.com Checked 13 Oct 2026 Details →
- 12 AI extraction & review transparency — found from sitemap contractbook.com Checked 13 Oct 2026 Details →
- 13 Integrations, signature & exit — found from sitemap contractbook.freshdesk.com Checked 13 Oct 2026 Details →
- 14 Integrations, signature & exit — found from sitemap contractbook.freshdesk.com Checked 13 Oct 2026 Details →