Contract Management (CLM)
LinkSquares
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by LinkSquares, Inc. · linksquares.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.
LinkSquares at a glance
- Vendor
- LinkSquares, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 27 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 27 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 27 Oct 2026
- Panel verdict
- The AI panel rates LinkSquares 2.5/5, the mean of 6 judges. LinkSquares is a contract lifecycle management platform that scored highest on negotiation and approval, at 7 from minimum to maximum, and on repository and obligations, at 7 to 8. how scores are made
- As of
- Vendor pages captured 27 Oct 2026; evaluated by the panel 27 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
LinkSquares is a contract lifecycle management platform that scored highest on negotiation and approval, at 7 from minimum to maximum, and on repository and obligations, at 7 to 8. The captured pages show redlining that round-trips through Microsoft Word with time-stamped, numbered versions, approvals configurable as ordered or any-one and routed by term type under an audit log, and automatic extraction of renewal, termination and notice dates — legacy contracts included — feeding dashboards, reminders and recurring tasks. It is weakest on sovereignty, where scores spread from 1 to 3: the rationales rest on the same captured facts — hosting on AWS in the U.S., U.S. Cloud Act exposure, no public information on an EU hosting option, a subprocessor list, or where AI and OCR processing runs — so the spread reads as a difference in weight, not in findings. AI extraction control and integration and exit each scored 4 from minimum to maximum; authoring and templates spread 4 to 6. No prices appear on any captured page.
Speaks for it
- Negotiation and approval scored 7 at both minimum and maximum, on Word round-trip redlining, time-stamped numbered versions and ordered or any-one approvals routed by term type under an audit log.
- Repository and obligations scored 7 to 8, on automatic extraction of renewal, termination and notice dates — legacy contracts included — feeding dashboards, reminders and recurring tasks with assignees.
- A published commitment that contract data is never shared with or used to train third-party LLM providers, with citations and reasoning stated for every analysis.
- Built-in eSignature pushes signed agreements and signature certificates automatically into the repository, alongside a downloadable audit log.
- Published security posture includes ISO 27001, SOC 2 Type 2, AES-256 encryption at rest and TLS 1.2 in transit.
Held against it
- Sovereignty scores spread from 1 to 3, with hosting stated as AWS in the U.S., U.S. Cloud Act exposure noted, and no public information on an EU hosting option or a subprocessor list.
- AI extraction control scored 4 from minimum to maximum, with no public information naming the model provider, the location of AI or OCR processing, or an EU AI Act position.
- Integration and exit scored 4 from minimum to maximum, with no public information on a documented API, single sign-on, or an export of documents together with their metadata and versions.
- Authoring and templates scored 4 to 6, with no public information on clause versioning under named owners, or on German-language or German-law templates.
- No prices, tiers, pricing basis or minimum terms appear on any captured page.
Best for
- You run in-house legal, legal operations or contract management and need an auditable internal negotiation record — Word round-trip redlining, version comparison, configurable approvals and a time-stamped audit log.
- You hold a backlog of legacy contracts and want automatic renewal, termination and notice-date extraction feeding dashboards, reminders and recurring tasks with named assignees.
- You want sales and procurement teams producing first-pass drafts and reviews under enforced playbook guardrails from pre-approved template language.
- You want drafting, review and signature in one platform, with signed agreements and signature certificates pushed automatically into the repository.
Avoid if
- You need your contract repository hosted in Europe — the captured pages state multi-tenant and single-tenant environments hosted in the U.S. on AWS, with U.S. Cloud Act exposure noted.
- Your governance requires naming the AI and OCR providers that process contract text, or switching AI features off — the platform is built around agentic AI working across the document library, and we found no public information on a per-account off switch, the model provider or the processing location.
- Your exit plan depends on exporting documents together with their metadata and versions — the pages state a downloadable audit log, and we found no public information on a document export.
The scores
| Criterion | Panel median |
|---|---|
| Drafting, templates & clause library | 2.5 of 5 |
| Negotiation, redlining & approval | 3.5 of 5 |
| Repository, deadlines & obligations | 3.5 of 5 |
| AI extraction & review transparency | 2 of 5 |
| Integrations, signature & exit | 2 of 5 |
| European sovereignty | 1 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
Redlines survive the Microsoft Word round-trip with versions synced back, time-stamped and numbered; approvals can be ordered or any-one-required, with an audited record of who approved what and when, and routing by term type (CFO on liability caps, IT on security) is exactly how I run deals. What I could not find: counterparty access without a licence, value-based routing, delegation, or any separation of internal comments from what the other side sees. 5 6 9
The Procurement Analyst
A Word add-in that syncs versions back to the platform, tracked and numbered version histories with comparison, ordered or any-one approvals routed by term type, and a time-stamped audit log naming who approved what give me most of an auditable negotiation record. We found no public information on counterparty access without a licence, approver delegation, or internal comments kept separate from what the counterparty sees. 5 6 9
The Sales Ops Owner
Redlining round-trips inside Word with AI-suggested language, approvals can be ordered or any-one, auto-assigned from the initiating template or workflow, routed by term type, and a time-stamped audit shows who approved what and when — that covers most of the discount-and-value routing I run. We found no public information on counterparty access without a licence, approver delegation, or internal comments kept separate from what the counterparty sees. 5 6 9 7
The IT Integrator
The captured pages show time-stamped, numbered negotiation versions, a Word add-in that applies redlines and syncs them back, version comparison, and a genuinely configurable approval engine — ordered or any/all approvers, ad hoc additions mid-negotiation, routing by term type — all written to an approval audit log naming who approved what. We found no public information on counterparty access without a licence, delegation, or internal comments kept separate from what the other side sees. 5 6 9
The Data Protection Officer
The redlining workflow runs inside Microsoft Word with versions time-stamped, numbered and comparable, and approvals can be ordered or any-or-all, routed by term type, added ad hoc mid-negotiation, and are logged with who approved what and when across LinkSquares, Salesforce and Word. We found no public information on counterparty access without a licence, delegation of approvals, or internal comments being kept separate from what the counterparty sees. 5 6 9
The Skeptic
Redlining inside Word with versions synced back, time-stamped numbered iterations, version comparison, ordered or any-of approvals, routing by term type, and a time-stamped audit log of who approved what are all evidenced. We found no public information on counterparty access or external collaboration, on approver delegation, or on negotiation-duration reporting — the internal record is strong, but the other side of the table is invisible in the captured pages. 5 6 9 11
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 termination dates including notice windows are extracted automatically from both new and legacy contracts, tasks carry an owner, due date and recurrence with reminders before and when overdue, hierarchies and related documents are linked, and renewal dashboards give legal, finance and procurement the portfolio view I would be audited on. We found no public information on retention and deletion rules per contract type, and reminders being individually logged against a missed deadline is implied by the general audit log rather than stated. 1 6 7 8
The Procurement Analyst
Auto-renewals are detected proactively, notice periods surface in the alerts, obligations sit as tasks with a named assignee, due date and reminders that escalate when overdue, and renewal dashboards with analytics aimed at finance and procurement support renew, renegotiate or exit decisions — close to my cancellable-this-quarter report. What holds it down is that the pages do not show deadlines derived from a cited clause, logged reminder acknowledgements, or retention and deletion rules per contract type. 6 7 8 10
The Sales Ops Owner
Renewal, termination and notice dates are extracted automatically — legacy contracts included — and surfaced through dashboards, reminders and analytics, while obligations run as tasks with assignees, due dates and recurrence. Hierarchies and portfolio reporting on renewals, value and counterparties are evidenced. We found no public information on deadlines tied to a cited clause or retention rules per contract type, and traceable logging of a missed reminder is only implied by the general audit log. 7 8 6 11
The IT Integrator
Renewal, termination and notice dates are extracted automatically even from legacy paper, obligations live as tasks with owners, due dates and recurring reminders, and related contract hierarchies, renewal dashboards and role-based access are all shown. We found no public information on logged reminder acknowledgements, retention and deletion rules per contract type, or deadlines tied back to a cited clause, so it stops short of an auditable system of record. 6 7 8
The Data Protection Officer
Renewal and termination dates, notice periods and obligations are extracted automatically — including from legacy contracts — and surface in dashboards and reminders, while tasks carry an owner, due date, recurrence and status, alongside hierarchies and finance-facing portfolio analytics. We found no public information on retention and deletion rules per contract type, deadlines derived from a cited clause, or reminders and their acknowledgements being logged. 1 6 7 8
The Skeptic
Renewal and termination dates, notice periods, auto-renewal detection, dashboards, and tasks with assignees, due dates and recurrence are all evidenced, legacy contracts included, alongside hierarchies and spend-commitment visibility. But "never miss a renewal" is claimed while we found no public information on reminders being logged with acknowledgements so a missed deadline can be traced, on deadlines derived from a cited clause, or on retention and deletion rules. 1 6 7 8
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 commitment that contract data is never shared with or used to train third-party LLM providers, plus citations on every AI answer, is more than a generic privacy badge — but no model provider is named, the platform is hosted in the U.S., and we found no public information on disabling AI features per account, per-field accuracy, or an EU AI Act position. Their own models are described as trained on millions of real legal contracts with no statement on whether customer agreements feed that corpus. 2 9 10
The Procurement Analyst
There is a stated commitment that contract data is never shared with or used to train third-party LLM providers, and analyses come with citations and explanations — more than a general privacy nod. But no model provider is named, and we found no public information on where AI processing runs, on switching AI features off per account, or on an EU AI Act position. 5 9 10
The Sales Ops Owner
The captured pages commit that contract data is never shared with or used to train third-party LLM providers, and the assistant shows citations and reasoning for its analyses, which I like. But no model provider or processing location is named, and we found no public information on extracted values linked to their source passage, accuracy per field, an EU AI Act position, or a way to switch AI features off per account. 9 10 5
The IT Integrator
The stated commitment that contract data is never shared with or used to train third-party LLM providers, plus citations and reasoning for every analysis, gives partial control — but we found no public information naming the model provider, where AI processing runs, per-field confidence, an EU AI Act position, or a per-account off switch. Running my contract text through models I cannot identify, on infrastructure hosted in the U.S., is not something I can sign off for a European rollout. 2 9 10
The Data Protection Officer
The training statement I look for is published — contract data is never shared with or used to train third-party LLM providers — and LinkAI claims precise citations for every analysis. But no model provider or AI subprocessor is named, nothing says where the generative model or the OCR integration processes the text, and we found no public information on per-field confidence, an EU AI Act position, or AI features that can be switched off per account. 5 7 9 10
The Skeptic
A concrete commitment that contract data is never shared with or used to train third-party LLM providers, plus citations and reasoning for every analysis, lift this above a bare privacy line. But no model provider is named, the stated hosting is in the U.S., and we found no public information on per-field accuracy or confidence for extracted values, on disabling AI features per account, on an EU AI Act position, or on logging who confirmed or corrected an extracted value. 2 5 9 10
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
eSignature is built in with signed agreements and signature certificates auto-pushed to the repository and a downloadable audit log; Salesforce, Microsoft Word and OCR are the named integrations, and approvals complete inside all of them with the audit intact. But the signature page names UETA, ESIGN and eIDAS without saying which level applies, and we found no public information on a documented API, SSO, or an export of documents together with metadata and versions — nothing on exit at all. 1 5 11
The Procurement Analyst
Salesforce, Microsoft Word and OCR integrations are named, and e-signature is built in with signature certificates pushed automatically to the repository, eIDAS among the regulations Sign is designed to comply with — though we found no public information on which eIDAS level applies. We found no public information on an API, single sign-on, or a documented export of documents together with their metadata and audit trail, and exit is the part I check first. 1 5 7 11
The Sales Ops Owner
Draft, review and signature in one platform is exactly my flow, with built-in e-signature, signed documents auto-pushed to the repository, and Salesforce and Word integrations where approvals stay audited. The pages name eIDAS alongside UETA and ESIGN without stating the signature level, and we found no public information on a documented API, SSO, webhooks, or a bulk export that carries documents with metadata, versions and audit trail. 11 1 6
The IT Integrator
Salesforce and Microsoft Word are named as working integrations, e-signature is built in with certificates and a downloadable audit log, and eIDAS is named among compliance targets — but we found no public information on a documented API, SSO, SCIM or webhooks, on which eIDAS level the signature actually reaches, or on any export of documents together with their metadata and versions. As the one who would eventually migrate out of this platform, the absence of any documented export format is the deciding fact. 1 5 6 11
The Data Protection Officer
Salesforce and Microsoft Word integrations and a built-in e-signature whose certificates push automatically into the repository are documented, and the audit log is downloadable. The signature's eIDAS level is not stated — only that Sign is designed to comply with UETA, ESIGN and eIDAS — and we found no public information on a documented API, SSO, or a bulk export of documents together with their metadata and versions. 1 5 6 11
The Skeptic
Salesforce and a Microsoft Word add-in are named, e-signature is built in, and a downloadable audit log with signature certificates pushed to the repository is stated. But the eIDAS compliance claim is made without a level, and we found no public information on a documented API, SSO, webhooks or SCIM, or an export of documents together with their metadata — only the log itself is said to be downloadable, and I have seen that export leave the metadata behind. 1 5 11
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 contracting entity is a US-incorporated vendor, the captured hosting is U.S.-only on AWS with no named AWS entity or region, and we found no subprocessor list showing where AI and OCR processing of contract text happens. GDPR-compliant, ISO 27001 and SOC 2 Type 2 are published, but for a repository holding my counterparties' most confidential commitments a badge is not a location. 2
The Procurement Analyst
Hosting is stated as US-only on AWS with no EU option visible on the captured pages, no subprocessor list including the AI and OCR providers contract text passes to is published, and the AI processing location is unstated; ISO 27001 and SOC 2 Type 2 are published and GDPR compliance is claimed, but a US-hosted vault of my suppliers' most confidential commitments is not one I can sign for. The contracting entity's jurisdiction and ownership are unconfirmed on the vendor's own pages. 2 9
The Sales Ops Owner
Hosting is stated as AWS in the U.S. under a U.S. vendor, with U.S. Cloud Act exposure noted, and the published picture names no AI or OCR subprocessors with locations. GDPR compliance and ISO 27001 are claimed, and we found no public information on an EU hosting option or an EU contracting entity. A repository holding our and our counterparties' most confidential commitments deserves that detail in public before I sign. 2 7
The IT Integrator
The security page names AWS as host with multi- and single-tenant options hosted in the U.S., and we found no public information on the contracting entity's jurisdiction, an EU hosting option, a subprocessor list covering the AI and OCR providers the text is passed to, or where the models run. ISO 27001 and SOC 2 are published, but for a repository holding our most confidential commitments and those of our counterparties, U.S.-only hosting with no visible subprocessor chain caps it low. 2 9
The Data Protection Officer
Hosting is stated as AWS in the US with a US-incorporated contracting entity, so European customers' contract repositories — including the counterparties' personal data inside them — sit under US jurisdiction with no EU hosting option shown. No subprocessor list, no data processing agreement covering contract data, and no processing location for the AI models or the OCR integration are published; ISO 27001 and SOC 2 Type 2 attestations speak to security, not jurisdiction. 2 7 9
The Skeptic
This is a U.S. company offering multi-tenant and single-tenant environments hosted in the U.S. on AWS with U.S. CLOUD Act exposure, and we found no public information on an EU contracting entity, EU hosting, a subprocessor list including the AI and OCR providers the text is passed to, or where AI processing actually runs. GDPR compliance and ISO 27001 are asserted, but nothing on the captured pages evidences European processing or a safeguard for a repository holding a company's most confidential commitments. 2
Pricing transparency
not rated — the vendor publishes no price
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
We found no public prices anywhere in the captured pages — no tiers, no pricing basis, no minimum term — so the annual invoice is unknowable without a sales conversation. For a vendor claiming 1,200+ customers I would expect at least a starting figure to negotiate from. 1
The Procurement Analyst
We found no public information on prices, pricing basis, tiers, add-ons, onboarding fees or minimum term anywhere in the captured pages — every cost question is a sales conversation, and no invoice can be computed from what is published. 1
The Sales Ops Owner
We found no public information on pricing in any of the captured pages — no tiers, no basis per user or contract, no signature or AI add-ons, no onboarding fees, no minimum term. That makes the annual invoice uncomputable from public pages, and I cannot put a number into next year's budget without a sales conversation. 1 2 11
The IT Integrator
We found no public pricing information at all — no tier prices, no pricing basis, no add-on, onboarding, migration or minimum-term figures on any of the captured pages; the annual cost is not computable without a sales conversation. 1
The Data Protection Officer
We found no public pricing information on any captured page: no tiers, no pricing basis, no add-on prices for AI features or signature volume, no onboarding fees and no minimum term, so a buyer cannot derive any part of the annual cost from what is published. 1
The Skeptic
We found no public pricing information on any captured page: no tier prices, no pricing basis in users, contracts or modules, no add-on prices for AI, signatures or integrations, no onboarding or migration costs, and no minimum term. A buyer cannot derive even a starting figure from these pages; every number is a sales conversation. 1 7
European sovereignty — proven facts
1 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 | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 2 Report an error |
Questions about LinkSquares
Is LinkSquares European?
Not determined: the vendor’s pages as captured do not say where LinkSquares is based.
Where does LinkSquares store data?
Not stated on the vendor’s pages as of 27 Oct 2026.
Does LinkSquares have a free plan?
Not stated on the vendor’s pages as of 27 Oct 2026.
What are the best alternatives to LinkSquares?
As of 27 Oct 2026, the panel rates Tomorro (2.5/5), Precisely (2.5/5) and fynk (2.5/5) highest among the other 23 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: LinkSquares alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 27 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 — Data residency. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Subprocessors. The page names AWS as the host without identifying the contracting AWS entity or server region, so an EU AWS subsidiary cannot be ruled out.
- 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.
- We found no public information on pricing on the pages we read (linksquares.com, linksquares.com/security, linksquares.com/contract-automation/contract-creation, linksquares.com/products/finalize/features/templates, linksquares.com/ai-legal-assistant/contract-redlining-software, linksquares.com/demo-library/tasks-and-approvals and 5 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 2 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
- 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 support 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
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page linksquares.com Checked 27 Oct 2026 Details →
- 2 Security / trust page — found from the homepage linksquares.com Checked 27 Oct 2026 Details →
- 3 Drafting, templates & clause library — found from sitemap linksquares.com Checked 27 Oct 2026 Details →
- 4 Drafting, templates & clause library — found from sitemap linksquares.com Checked 27 Oct 2026 Details →
- 5 Negotiation, redlining & approval — found from sitemap linksquares.com Checked 27 Oct 2026 Details →
- 6 Negotiation, redlining & approval — found from sitemap linksquares.com Checked 27 Oct 2026 Details →
- 7 Repository, deadlines & obligations — found from sitemap linksquares.com Checked 27 Oct 2026 Details →
- 8 Repository, deadlines & obligations — found from sitemap linksquares.com Checked 27 Oct 2026 Details →
- 9 AI extraction & review transparency — found from sitemap linksquares.com Checked 27 Oct 2026 Details →
- 10 AI extraction & review transparency — found from sitemap linksquares.com Checked 27 Oct 2026 Details →
- 11 Integrations, signature & exit — found from sitemap linksquares.com Checked 27 Oct 2026 Details →