Contract Management (CLM)
fynk
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by fynk GmbH · fynk.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.
fynk at a glance
- Vendor
- fynk GmbH
- 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
- Yes, per the vendor’s own page source, captured 13 Oct 2026
- Panel verdict
- The AI panel rates fynk 2.5/5, the mean of 6 judges. fynk is contract-management software from fynk GmbH, Vienna, spanning templates, negotiation, e-signature and obligation tracking. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 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
fynk is contract-management software from fynk GmbH, Vienna, spanning templates, negotiation, e-signature and obligation tracking. Strongest are integration and exit, repository and obligations and negotiation and approval: a documented REST API with version pinning, signed webhooks, SCIM and SAML single sign-on, all three eIDAS levels including qualified signatures, renewal dates tracked with configurable reminders, and in-browser redlining where counterparties join by link without an account. Pricing transparency is the weakest criterion at 2-3: the pages claim clear prices and a free plan with unlimited documents, signatures included with no envelope fee, yet no paid-tier figure appears, so a paying annual invoice is not computable. AI extraction control scores 3-4 — extracted values are held for confirmation, but analysis triggers automatically on upload and no public information names the model provider or where processing runs. Authoring and templates spans 4 to 6 on a 175-template library with no public information on conditional clause logic or clause versioning; sovereignty scores 4-5 with hosting stated in ISO 27001-certified data centres in Germany and no public information on a subprocessor list.
Speaks for it
- Documented REST API with version pinning, per-response rate limits, signed webhooks with retries, SCIM and SAML single sign-on.
- All three eIDAS signature levels including qualified, selected per document, with signers requiring no account.
- Signed contracts file with parties, term and notice period extracted, renewal dates tracked and reminders configurable by timing, repetition and recipient.
- Redlining in one live document with per-change accept or reject, version comparison and counterparties reviewing by link without an account.
- Contracts generated from HubSpot or Salesforce deal records, with values, durations, tags and statuses exportable to Looker, Power BI or Tableau.
Held against it
- We found no public price figure for any paid tier, so a paying annual invoice is not computable from the captured pages.
- We found no public information on the AI model provider, training use or where AI processing runs, while analysis triggers automatically on every upload.
- Independently sourced sovereignty attributes list data residency and subprocessor exposure as unknown, and we found no published subprocessor list.
- We found no public information on conditional clause logic, approved fallbacks or per-clause versioning with owners.
- The stated "full export anytime" carries no public information on its contents, format or the audit trail.
Best for
- You run HubSpot or Salesforce and want contracts built from the deal record with signature and approval events pushed to your systems over signed webhooks.
- You need automated notice-period and renewal tracking with task owners, due dates and portfolio exports into Looker, Power BI or Tableau.
- You negotiate in-browser and want counterparties to review and comment without creating an account, with every change accepted or rejected one by one.
- You operate in Austria or Germany and want local template content, including board and circular resolutions, in a German-language product.
Avoid if
- You need a published price to budget an annual invoice before talking to sales.
- You require AI analysis to stay off until you enable it, since analysis triggers automatically on upload.
- You require independently confirmed data residency and a published subprocessor list before uploading confidential contracts.
The scores
| Criterion | Panel median |
|---|---|
| Drafting, templates & clause library | 3 of 5 |
| Negotiation, redlining & approval | 3 of 5 |
| Repository, deadlines & obligations | 3.5 of 5 |
| AI extraction & review transparency | 2 of 5 |
| Integrations, signature & exit | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 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
Browser redlining with one-by-one accept or reject, counterparties reviewing and commenting without an account, version comparison pitched at catching what the other side's lawyer quietly changed, and sequential or parallel approval chains with escalation reminders and a named, timestamped change history. Routing is conditional on contract step rather than on value or deviation from approved wording, and I found no public information on a Word round-trip that keeps changes, on delegation between approvers, or on internal comments kept separate from what the counterparty sees. 9 8 1 10
The Procurement Analyst
Redlining with one-by-one accept or reject of proposed changes, version comparison to catch what the counterparty's lawyer quietly changed, counterparties reviewing and commenting without an account, and approval chains in sequence or parallel reusable per contract type, with escalation reminders and checkpoints before review or signing. Every edit is logged with who, what and when. We found no public information on a Word round-trip, routing by contract value or playbook deviation, approver delegation, or keeping internal comments separate from the counterparty's view. 1 8 9 15
The Sales Ops Owner
Redlining with accept-or-reject of every proposed change, counterparties reviewing via a link without creating an account, version comparison against what the other side's lawyer quietly changed, and a change history logged with who and when — combined with multi-step approval chains in sequence or parallel, routes stored in templates, conditional triggers at contract steps, escalation reminders and real-time status. We found no public information on a Word round-trip add-in, approval routing by discount or contract value, or delegation between approvers, which is what my standard deals need. 9 1 8
The IT Integrator
Redlining in one shared live document with accept-or-reject on every proposed change, counterparties reviewing by link without an account, version comparison, and approval chains in sequence or parallel with routing by contract step and escalation reminders are all stated. I found no public information on a Word round-trip, routing by value or risk, or internal comments kept separate from the counterparty's view. 1 8 9
The Data Protection Officer
Redlining with accept/reject per change, counterparties commenting without an account, version comparison, and multi-step approval chains in sequence or parallel with step-conditional routing and escalation are all shown. We found no public information on a Word add-in or round-trip preserving tracked changes, on routing by contract value, or on keeping internal comments separate from the counterparty view. 1 8 9 10
The Skeptic
In-browser redlining with one-by-one accept or reject, a single live version, named and timestamped change history, counterparty access by link without an account, and version comparison are all evidenced, alongside automatically routed multi-step approvals with parallel or sequential reviewers, conditional routing at contract steps and escalation reminders. We found no public information on a Word add-in or round-trip that keeps tracked changes, on routing triggered by contract value or risk, or on keeping internal comments separate from the counterparty's view. 1 8 9
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
Parties, term and notice period are extracted into the repository at signing, with configurable reminders and repeat rules to named owners, a live deadline calendar, a notice-period calculator, and values, durations, tags and statuses exportable into Looker, Power BI or Tableau. I found no public information on contract hierarchies linking framework agreements to amendments and orders, or on deadlines traceable to the cited clause they derive from. 11 10 14 15 13
The Procurement Analyst
The signed copy is filed with parties, term and notice period extracted and the renewal date counting down as a reminder; reminders are configurable for timing, repetition and named recipients, each task carries an owner and due date, and task actions are logged. Search runs in plain language across the portfolio including scanned uploads, and values, durations, tags and statuses export to Looker, Power BI or Tableau — enough for a view of what can be cancelled this quarter. For the top of the scale I would want contract hierarchies linking framework and amendments, deadlines derived from a cited clause, and logged reminder acknowledgements; we found no public information on these. 10 11 13 14 15
The Sales Ops Owner
Once the last signature lands the contract files itself with parties, term and notice period extracted, renewal and expiry dates are tracked with configurable reminders to named owners, every task carries an owner and due date, and natural-language search plus dashboards and BI export cover the portfolio view. We found no public information on linking framework agreements to amendments and orders as hierarchies, or on retention and deletion rules per contract type. 15 13 10 11
The IT Integrator
Parties, term and notice period are extracted at filing with the renewal date counting down, tasks carry an owner and due date with triggers on dates or status, reminder timing and recipients are configurable, and values, durations and statuses flow into dashboards and BI tools. I found no public information on linking frameworks, amendments and orders into hierarchies, or on reminder acknowledgements being logged, which is what an audit would ask me for. 10 11 14 15
The Data Protection Officer
Parties, term and notice period land in the repository after signing, reminder rules cover timing, repeat and recipient, every task carries an owner and due date, and natural-language search reaches obligations and values across scanned uploads. We found no public information on contract hierarchies such as framework and amendments, deadlines derived from a cited clause, or retention and deletion rules configurable per contract type. 9 10 11 13 15
The Skeptic
Notice periods are taken seriously: parties, term and notice period are extracted on filing, the renewal date counts down, reminder timing, repetition and recipients are configurable, tasks carry an owner and due date with every action logged, and values and durations flow into Looker, Power BI or Tableau. What holds it back is that we found no public information on linking framework contracts and amendments as hierarchies, on deadlines tied to the cited clause they came from, or on logged acknowledgement of a reminder. 11 14 15
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
AI is marketed hard — analysis, review, summary, search, drafting — and extracted metadata is held for my confirmation before it is permanently saved, with a re-run option, which is a real control. But the captured pages give only a general GDPR assurance: I found no public information on the model provider, on whether customer contracts are used for training, on where AI processing runs, on an EU AI Act position, or on extracted values linked to their source passage, and for my clients' contract text that silence decides it. 13 12 15 3
The Procurement Analyst
Extraction runs automatically on upload, and every extracted value is presented for my confirmation before it is saved — with a manual-review mode versus auto-apply and a re-run when new fields are added — which is real control over what lands in the record. What I cannot see: the model provider, where AI processing runs, whether contract text is used for training, or an EU AI Act position, and the privacy policy as captured names no AI or OCR provider. That is a general GDPR assurance wrapped around an unnamed engine. 3 12 13
The Sales Ops Owner
AI is marketed hard across drafting, review, analysis and search, and extracted metadata is presented for confirmation before it is saved, which is a real control. But we found no public information on the model provider, where AI processing runs, or whether contract text is used for training — and AI analysis triggers automatically on upload rather than staying off until I enable it, with nothing on an EU AI Act position. 13 12 15
The IT Integrator
Extraction runs automatically on upload, every value is held for my review and only saved on my confirmation, with a per-run choice between manual review and automatic apply, and review checks defined by our own playbooks. I found no public information on the model provider, where contract text is processed, whether it is used for training, or any EU AI Act position, so I cannot verify the chain the text passes through. 12 13
The Data Protection Officer
Extracted values are presented for confirmation before anything is saved, the customer chooses manual review or automatic apply, and playbook results are traceable to their rules — but analysis runs automatically on every upload. We found no public information on the model provider, on where the AI or OCR processes contract text, on whether any provider retains or trains on it, or on an EU AI Act position; the GDPR assurances are general, and that silence is what a repository of counterparties' data needs answered. 3 4 12 13
The Skeptic
The AI functions are documented better than most: analysis triggers on upload, extracted data is presented for confirmation before anything is saved, and the account chooses between manual review and automatic application. But the disclosures I read for are missing — we found no public information naming the model provider, on training on customer contracts, on where AI processing runs, on the source passage beside an extracted value, or on accuracy or confidence per field. 12 13 15
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 REST API with an account-pinned version and a changelog, signed and retried webhooks, SCIM, SAML single sign-on, HubSpot and Salesforce integration, bulk API import with extraction, and all three eIDAS signature levels including qualified, with a published directory of eIDs and their levels. Exit is asserted rather than documented — the pages state "full export anytime" and I found no public information on what such an export includes, its format, or on SAP, Microsoft 365 or DATEV connections. 14 15 15 2
The Procurement Analyst
A documented REST API with per-response rate limits, accounts pinned to one version with a changelog, signed webhooks with retries, SCIM and SAML/SSO, plus all three eIDAS levels including qualified signature and a directory of supported eIDs — comfortably past the mid-point. On the exit side, no lock-in and full export anytime are stated, but we found no public information on the export format, whether versions, approvals and the audit trail come along, or a documented migration path and deletion confirmation after contract end. 2 14 15 15
The Sales Ops Owner
The quote-to-signature flow I own is evidenced end to end: the contract is built from the right template when the deal closes in HubSpot or Salesforce, signature and approval events go out over signed webhooks, all three eIDAS levels including qualified are selectable per document, SSO and SCIM exist, and the documented REST API is pinned to one version with a changelog. We found no public information on integrations with SAP, Microsoft 365 or DATEV, or on what the claimed full export anytime actually contains — formats, versions, approvals or audit trail. 14 2 15 13
The IT Integrator
This is close to what I need: a documented REST API with rate limits reported per response, the account pinned to one API version with a changelog, signed and retried webhooks, SAML SSO, SCIM, HubSpot and Salesforce generating contracts from deal data, and all three eIDAS levels including qualified signatures through a trust service provider. The gap is exit: "full export anytime" is stated with no documented content or format, and I found no public information on a deprecation policy or SAP and Microsoft 365 integrations. 2 14 15 15
The Data Protection Officer
A REST API with version pinning and a changelog, signed webhooks with retries, HubSpot and Salesforce connections, SCIM and SSO, and all three eIDAS levels including qualified signatures through a trust service provider are documented, with full export anytime claimed. We found no public information on SAP, Microsoft 365 or DATEV connections, on whether the export includes metadata, versions and audit trail in an open format, or on confirmed deletion after contract end. 2 14 15 15
The Skeptic
The API story is unusually solid — REST over HTTPS, role-scoped tokens, documented endpoints, rate limits reported per response, an account pinned to one API version with a changelog, signed webhooks with retries — and all three signature levels including qualified are stated with a directory of supported eIDs. But the exit claim "No lock-in Full export anytime" names no contents: we found no public information on whether the export carries metadata, versions and the audit trail, in what format, or on integrations with SAP, Microsoft 365 or DATEV. 2 14 15
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 fynk GmbH at a Vienna address with the Vienna commercial court register number FN580816t and an Austrian VAT ID, and hosting is stated as ISO 27001-certified data centres in Germany — the two pillars I look for. Behind them the chain is undocumented: I found no public information on a published subprocessor list, on the AI or OCR providers that contract text is passed to and their locations, or on a data-processing agreement covering customer contract data beyond a customizable DPA offered in the pro tier. 4 15 3 2
The Procurement Analyst
The imprint names fynk GmbH in Vienna with the Handelsgericht Wien as register court, and the vendor states hosting in ISO 27001-certified data centres in Germany — an EU contracting entity with EU hosting. But we found no published subprocessor list, no location for the AI or OCR processing the contracts are passed to, and the independently sourced attributes report data residency as unconfirmed, so I cannot evidence the chain end to end. 3 4 15
The Sales Ops Owner
The contracting entity is Austrian with a Vienna commercial register entry, hosting is stated as ISO 27001-certified data centres in Germany, and eIDAS and GDPR compliance are claimed. But we found no public information on the subprocessor list, the AI or OCR providers the contract text is passed to, or where AI processing runs — and for a repository holding our most confidential commitments and our counterparties', that undisclosed chain keeps this below the middle. 4 15 15
The IT Integrator
The contracting entity is fynk GmbH in Vienna with a commercial register number, hosting is stated in ISO 27001-certified data centres in Germany, and eIDAS and GDPR compliance are claimed. I found no public information on a subprocessor list — above all which AI or OCR provider sees the contract text and where it runs — nor on a certification held by fynk itself, which matters for a repository of confidential commitments. 4 15 15
The Data Protection Officer
The contracting entity is fynk GmbH in Vienna with the commercial register entry published, and hosting is stated in ISO 27001-certified data centres in Germany with log data deleted after 60 days. We found no public information on a subprocessor list, on the AI or OCR providers that receive contract text and their locations, or on a standard data processing agreement covering the counterparties' data as the customer's processing — for a system holding a company's most confidential commitments, that decides the score. 2 3 4 13 15
The Skeptic
The contracting entity is fynk GmbH in Vienna with a Vienna commercial register number, and hosting is claimed in ISO 27001-certified data centres in Germany — an EU entity and EU hosting on the vendor's own pages. The chain behind that stays dark: we found no public information on a subprocessor list, on any AI or OCR provider the contract text is passed to, or on where AI processing runs, and the ISO 27001 statement covers the data centres rather than a published company certification. 4 15 15
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 captured pricing page shows a free tier with unlimited documents, a claim of clear prices and no hidden costs, and named pro-tier features such as a success manager, SAML single sign-on and a custom SLA and DPA, alongside the statement that signatures are included with no envelope fee. I found no public euro figures, no pricing basis in users, contracts or modules, and no minimum term or onboarding costs, so a buyer cannot compute an annual invoice from the public pages. 2 1
The Procurement Analyst
The vendor claims clear prices, full transparency and no hidden costs, states signatures are included with no envelope fee and unlimited documents on the free plan, and promises no extra costs and no long commitments. But beyond the free tier we found no public price figure and no pricing basis — users, contracts or modules — on any captured page, so a paid annual invoice is not computable from public information. The transparency is asserted, not demonstrated. 1 2 15
The Sales Ops Owner
The pricing pages give me no euro figure anywhere — we found no public information on tier prices, the pricing basis per user or per contract, onboarding or migration fees, or VAT treatment; the only concrete signals are a free tier with unlimited documents, "Signatures included, no envelope fee", and claims of no extra costs and no long contract bindings. As a buyer I cannot compute a real annual invoice from these pages, and nothing here goes into next year's budget without a sales conversation. 2 1 15
The IT Integrator
The public pages show a free plan with unlimited documents, signatures included with "no envelope fee", and a claim of no extra costs and no long contract terms, but no price figures appear in the captured pages: I found no public information on tier prices, the per-user or per-contract basis, or what onboarding and the SSO-bearing plan cost. The annual invoice is not computable from what is published. 1 2 15
The Data Protection Officer
The captured pricing page shows a free start with unlimited documents, signatures included with no envelope fee, and the claim of clear prices and no hidden costs, but no paid tier figures. We found no public information on the pricing basis per user or contract, on which features sit in which tier, on add-on or onboarding costs, or on the minimum term, so the annual invoice cannot be computed from public pages. 1 2 7
The Skeptic
A free plan with unlimited documents and self-signup exists, "Signatures included, no envelope fee" is stated, and the pricing page claims clear prices with no hidden costs and no extra costs — yet we found no public price figure for any paid tier, no pricing basis in users, contracts or modules, and only a Pro feature list with no price attached. The annual invoice for a paying team is not computable from what is public. 1 2 15
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 | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about fynk
Is fynk European?
Yes. whats-best.ai classifies fynk as EU-Made.
Where does fynk store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does fynk have a free plan?
Yes. fynk has a free plan, per the vendor’s page captured 13 Oct 2026.
What are the best alternatives to fynk?
As of 21 Oct 2026, the panel rates Tomorro (2.5/5), Precisely (2.5/5) and Juro (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: fynk alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 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.
- 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.
- 64 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
- 11 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
- 10 subprocessors 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
- 9 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
- 4 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
- 4 hosting 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 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 (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage fynk.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 2 Pricing page fynk.com Checked 13 Oct 2026 Details →
- 3 Privacy policy fynk.com Checked 13 Oct 2026 Details →
- 4 Legal notice fynk.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 5 Terms of service fynk.com Checked 13 Oct 2026 Details →
- 6 Drafting, templates & clause library — found from sitemap fynk.com Checked 13 Oct 2026 Details →
- 7 Drafting, templates & clause library — found from sitemap fynk.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 8 Negotiation, redlining & approval — found from sitemap fynk.com Checked 13 Oct 2026 Details →
- 9 Negotiation, redlining & approval — found from sitemap fynk.com Checked 13 Oct 2026 Details →
- 10 Repository, deadlines & obligations — found from sitemap fynk.com Checked 13 Oct 2026 Details →
- 11 Repository, deadlines & obligations — found from sitemap fynk.com Checked 13 Oct 2026 Details →
- 12 AI extraction & review transparency — found from sitemap help.fynk.com Checked 13 Oct 2026 Details →
- 13 AI extraction & review transparency — found from sitemap fynk.com Checked 13 Oct 2026 Details →
- 14 Integrations, signature & exit — found from sitemap fynk.com Checked 13 Oct 2026 Details →
- 15 Integrations, signature & exit — found from sitemap fynk.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →