CRM
folk
EU-Made 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 Folk SAS · www.folk.app
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
folk is a CRM pitched at sales teams of 20-50 people. The scoring favors integrations and contact management, both 6-7: judges credited a documented REST API with versioning, rate limits and webhooks across people, companies, deals and custom objects, native Gmail, Outlook and WhatsApp connections, and eight custom field types linking companies to people. The weak flanks are data portability at 3-4, where export is per group, yields two CSV files of contacts and notes, and excludes interactions, reminders and contact custom fields, plus sales pipeline at 4-5 and automation at 4 — the Workflow Assistant is a trigger, optional filters and one automated email, and we found no public information on forecasting, quota tracking or in-product branching. The genuine split is pricing transparency, 4-6: higher scores credited three published tiers and disclosed credit allowances; lower scores weighed the unpriced credit meter and captured pages giving different starting figures, 'From $20/user/month' versus '$24/member/month'. Sovereignty splits 4-5 between documented AWS Ireland hosting with a published DPA and subprocessor list, and a Delaware-named data controller with US-region processors on contact data.
Speaks for it
- A documented REST API with versioning, rate limits, webhooks and bearer-key management spans people, companies, deals, custom objects, notes, tasks and interactions
- Native Gmail, Outlook, WhatsApp and Google Calendar connections plus Zapier and Make apps cover the revenue stack
- Custom fields come in eight types including cross-record references, and companies carry native fields such as funding raised and employee range
- Three pricing tiers publish per-member figures with annual totals, unlimited members on every plan and a 14-day free trial
- A published DPA, a region-labeled subprocessor list and named deletion timelines — databases purged within 7 days — give auditable hygiene
Held against it
- Export is group by group, limited to two CSV files of contacts and notes, and excludes interactions, reminders and contact custom fields
- The Workflow Assistant is one trigger, optional filters and a single automated email, and each completion consumes a credit that disables the assistant when exhausted
- The captured pages give different figures for the starting price — 'From $20/user/month' versus '$24/member/month' — and we found no public information on monthly-billing prices or VAT treatment
- The captured pages give different information about the legal entity — Folk SAS, Paris, and Folk Inc., a Delaware corporation named as Data Controller in the privacy policy — and the subprocessor list routes contact data to US-region processors such as Apollo.io, OpenAI and WhatsApp
- We found no public information on deduplication, merge tooling, required fields per stage, forecast views or quota tracking, and removing a person from a group removes their custom field values
Best for
- You are a sales team of 20-50 people that wants a shared, rich contact database more than a forecast engine
- You plan to build your own tooling on a documented REST API with webhooks, and the Premium tier where API access sits fits your plan
- You capture contacts through Gmail, Outlook, WhatsApp and browser extensions and want them centralized
- You want published per-member prices with unlimited members on every plan before committing to a trial
Avoid if
- Your exit plan depends on a complete self-serve export — the documented path is per group, contacts and notes only, with interactions excluded
- You need multi-step in-product automation — the documented assistant sends a single email per trigger and is disabled when credits run out
- Your compliance posture cannot accommodate a Delaware-named data controller or US-region subprocessors processing contact data for enrichment and sync
- You need an enforced, forecast-driven sales process — the documented pipeline is shared stages and dashboards, with dashboards on the Premium tier
The scores
Contact & data model
Show reasoningHide reasoning
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Solo Seller
The field system is genuinely rich for a small CRM: eight custom field types including contact, user and object references, custom objects, and companies properly linked to people. But I found no public information on dedupe, merge tooling or field-level history, so duplicate hygiene is my problem, and custom objects live in the Premium tier. 4 5 2 13
The Data Protection Officer
People, companies, deals and custom objects are modelled, with eight custom field types including cross-record references to contacts, workspace members and objects, and companies carrying native fields such as funding raised and employee range. We found no public information on deduplication, merge tooling, field validation or field-level permissions, and custom objects and deals sit behind the Premium plan. 4 5 2
The Sales Ops Lead
People, companies and deals are genuinely related: an object field links deals and custom objects to contacts, and custom fields span eight types. But fields live per group and their values are removed when a record leaves the group, and I found no public information on required fields, validation, merge or deduplication tooling — exactly where a shared database rots. 4 5 13
The RevOps Integrator
The data model has genuine depth: companies with native firmographic fields linked to people, group-scoped custom fields in eight types including contact, user and object links to deals and custom objects, all reachable through the API. We found no public information on dedupe or merge tooling or field-level history, and removing a person from a group removes the custom field values with it — a hygiene landmine for a shared revenue database. 4 5 13 2
The Migrator
Custom fields come in eight types including references to other contacts, members and objects, custom objects and deals exist on the Premium tier, and companies link to one or more people — a deeper model than the standard three objects. But fields are group-scoped, removing a person from a group deletes their custom field values, and I found no public information on deduplication or merge tooling, which is the first thing a clean import needs. 5 4 2
The Skeptic
Custom fields come in eight documented types including references to contacts, workspace members and custom objects, and companies carry a real native field set with people and group relations — richer than cosmetic. But we found no public information on deduplication, merge tooling, field validation or field-level permissions, which is the hygiene that decides whether the database survives year two, and custom objects sit behind the Premium tier. 4 5 13
Pipeline & forecasting
Show reasoningHide reasoning
How this is scored
Whether the pipeline enforces a process and produces reporting a finance department accepts.
0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.
3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.
5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.
8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.
10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.
The Solo Seller
Shared collaborative pipelines with roles and permissions exist, and stages run the standard qualification-to-closed-won arc with win-rate and stage-conversion metrics. I found no public information on stage requirements, forecasting views or quota tracking, and dashboards sit in Premium — this is a kanban with reporting, not an enforced process. 1 6 7 2
The Data Protection Officer
Shared pipelines with customizable roles and permissions, stage sets from qualification through closed-won/closed-lost, and dashboards for deal velocity, win rate, pipeline coverage and conversion by stage are documented. We found no public information on required fields per stage, stage gates, quota tracking, weighted forecasting or historical snapshots, and dashboards are a Premium feature. 1 6 7 2
The Sales Ops Lead
There are shared, customizable pipelines with named stages, roles and dashboards tracking win rate, conversion by stage and pipeline coverage. But I found no public information on required fields per stage, stage probabilities, quota tracking or any forecast view — reporting stops at dashboards, and nothing here is enforceable process. 1 6 7
The RevOps Integrator
Pipelines are collaborative kanbans with named stages through closed-won and closed-lost, and dashboards track deal velocity, win rate, pipeline coverage and conversion by stage. But we found no public information on stage-level required fields, forecast views, quota tracking or historical snapshots — there is nothing here a finance department could forecast from, and dashboards sit behind the Premium tier. 6 7 2
The Migrator
Shared pipelines with named stages and dashboards tracking win rate, deal velocity, pipeline coverage, conversion by stage and activity per deal are evidenced, with dashboards sitting on the Premium tier. I found no public information on required fields or stage gates, and nothing on forecasting views, quota tracking or snapshots — a finance department cannot sign off on what the captured pages show. 6 7 2 1
The Skeptic
Shared, customizable pipelines with closed-won and closed-lost stages and dashboards tracking deal velocity, win rate, pipeline coverage and conversion by stage are documented, with dashboards listed on Premium. We found no public information on required fields per stage, stage gates, forecast views, quota tracking or historical snapshots — nothing captured shows a forecast a finance department would recognise, which is a loud silence for a product pitched at teams of 20-50 people. 2 6 7
Automation & workflows
Show reasoningHide reasoning
How this is scored
Triggers, sequences and routing that remove manual work without a consultant.
0 — No automation beyond email templates.
3 — Simple if-this-then-that on records; no multi-step sequences, no branching.
5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.
8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.
10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.
The Solo Seller
The documented Workflow Assistant is a trigger, optional filters and a single automated email; we found no public information on branching, delays or multi-step sequences, so anything fancier goes through Zapier. Worse for a solo buyer, each workflow completion consumes 1 credit, Standard carries 1,500 credits a month, and the assistant is disabled and prompts an upgrade when they run out — the feature is literally its own upsell. 8 9 1
The Data Protection Officer
The documented Workflow Assistant is a single structure — trigger on created or updated, optional filters, one automated email — with campaign analytics, and cross-group creation runs through Zapier, Make or a help recipe; we found no public information on branching, delays or per-step logs. Every workflow completion consumes one credit and the assistant is disabled when credits run out, so the feature is metered and capped rather than infrastructure. 8 9
The Sales Ops Lead
The native Workflow Assistant is a single-step construct — trigger on created or updated, optional filters, optional automated email — with campaign analytics for sent, opened and replied. It runs on a credit meter that disables the assistant when exhausted, and branching, delays and lead routing appear to live in Zapier and Make rather than in the product. 2 8 9
The RevOps Integrator
The native Workflow Assistant is a trigger on created or updated plus optional filters plus one send-email action, metered at one credit per completion and hard-disabled when credits run out — automation as its own upsell. Multi-step logic appears only through Zapier and Make; we found no public information on branching, delays or routing inside folk itself. 8 9 6
The Migrator
The Workflow Assistant pairs a trigger on created or updated records with optional filters and a single automated email, plus campaign analytics and an Update CRM action, and Zapier can copy a person into another group on a field change. I found no public information on branching, delays or round-robin routing in the builder, and every workflow completion consumes a credit that disables the feature and prompts an upgrade when exhausted — the automation is its own meter. 8 9
The Skeptic
The native Workflow Assistant is a trigger on created or updated, optional filters, and one automated email — we found no public information on branching, delays or multi-step sequences inside the product itself, with anything cleverer delegated to Zapier or Make. The metering is the tell: 'Each workflow completion consumes 1 credit', allowances run from 50 credits on the free trial to 1,500 on Standard and 10,000 on Premium/Custom, and 'If you run out of credits, the assistant is disabled and you'll be prompted to upgrade' — automation priced per completion is automation as its own upsell. 8 9 2
Integrations & API
Show reasoningHide reasoning
How this is scored
Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.
0 — No API, no sync; data enters by CSV and leaves never.
3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.
5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.
8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.
10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.
The Solo Seller
The REST API is properly documented with versioning, rate limits, webhooks and endpoints across people, companies, deals, custom objects, notes, tasks and interactions, and the native directory covers Gmail, Outlook, WhatsApp, calendar, six browser extensions and enrichment partners, plus Zapier and Make. Calendar sync reads one way into folk and API access starts at Premium, which keeps this below the top band. 10 13 11 2
The Data Protection Officer
A documented REST API over HTTPS with bearer auth, version pinning, documented rate limits and coverage of people, companies, deals, custom objects, notes, tasks, interactions and webhooks, alongside native Gmail, Outlook, Google Calendar, Google Contacts and WhatsApp sync plus Zapier and Make apps. API access is gated to the Premium plan, and we found no public information on calendar write-back or a public app marketplace. 10 13 11 2
The Sales Ops Lead
A documented REST API with versioning, rate limits, webhooks and endpoints across people, companies, deals, custom objects and interactions, plus native Gmail and Outlook sync, WhatsApp, browser extensions and a real enrichment and sequencing directory. Calendar sync is documented as import-only and the six-thousand-plus figure rides on Zapier and Make rather than a marketplace of the vendor's own. 3 10 11 13
The RevOps Integrator
This is the strong suit: a documented REST API over the full core object set including deals, custom objects and webhooks, with versioning, rate limits, bearer-key management, plus native Gmail and Outlook conversation sync, WhatsApp, enrichment partners and MCP endpoints for AI tools. The calendar connection operates on a read-only scope — event import, not two-way writeback — and we found no public information on public OAuth apps; several directory entries also route through Zapier or Make rather than native connectors. 13 10 4 11 3
The Migrator
A documented REST API with rate limits and versioning covers people, companies, deals, custom objects, groups, notes, reminders, tasks and interactions, with webhooks, and the native directory reaches the revenue stack — Gmail, Outlook, WhatsApp, Slack, Docusign, Pandadoc, sequencing, phone and enrichment tools. The published Google scopes show calendar access is read-only, API access sits on the Premium tier, and I found no public information on OAuth apps or a marketplace. 10 13 11 3 2
The Skeptic
A documented REST API with versioning, rate limits, webhooks and coverage of people, companies, deals, custom objects, notes, tasks and interactions, plus native connections for Gmail, Outlook, Google Calendar, WhatsApp and an MCP offering, is genuinely above the norm. Two caveats keep it honest: API access is listed under the Premium tier, and the syncs are described as imports ('Automatically import your calendar events into folk'), so we found no public information confirming full two-way calendar or email sync. The '5,000+' tool count also leans on intermediaries — '1000+ apps through our Zapier integration'. 10 11 13
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.
0 — US entity, US-default hosting, no public DPA or subprocessor list.
3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.
5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.
8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.
10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.
The Solo Seller
Hosting is AWS in Ireland with a published DPA, a named subprocessor list with regions, and SOC 2 and GDPR commitments. But the captured privacy policy names Folk Inc., a Delaware corporation, as data controller, and the subprocessor list shows broad US exposure on contact data and PII (Google Workspace, OpenAI, Stytch, Stripe, WhatsApp among others), with backups retained up to 730 days and application logs up to 930 days after a deletion request. 3
The Data Protection Officer
The privacy policy names Folk Inc., a Delaware corporation, as data controller, while hosting runs on AWS in Ireland by default with a published data processing agreement and a full subprocessor list — a list that routes contact data to US enrichment processors including Apollo.io, OpenAI, People Data Labs and Perplexity. Deletion clears databases in seven days but backups persist for 730 days and application logs for up to 930 days, and we found no public information on consent fields for contacts. 3 11
The Sales Ops Lead
Hosting is AWS Ireland with a published DPA, a published subprocessor list and deletion inside seven days. But the privacy policy names a Delaware corporation as data controller, and contact and interaction sync runs through US-region Google Workspace, Microsoft 365 and WhatsApp with enrichment via multiple US providers — broad named exposure, not the narrow residual kind. 3
The RevOps Integrator
Hosting is AWS Ireland with a published DPA and a region-labeled subprocessor list, but the captured privacy policy names Folk Inc., a Delaware corporation, as the data controller, while the vendor provenance in this sheet presents Folk SAS, Paris — the captured pages give different information about the entity. Core flows touch US-region subprocessors for contact and interaction sync (Google Workspace, Microsoft 365, WhatsApp) and enrichment (Apollo, OpenAI, People Data Labs), and deletion tails run to 730 days in backups and 930 days in application logs. 3
The Migrator
Hosting is AWS in Ireland with a published DPA, a published subprocessor list and named retention timelines — databases purged within 7 days, backups within 730, logs within 930 — which is real, auditable hygiene. But the privacy policy names Folk Inc., a Delaware corporation, as Data Controller, and the subprocessor list shows contact data flowing to a wide band of US processors — Apollo, Google Workspace, Microsoft 365, OpenAI, Sendgrid, WhatsApp among them — so core processing touches US entities broadly. 3 1
The Skeptic
The vendor carries an EU-made provenance, yet the privacy policy names 'Folk Inc., a Delaware corporation' as the Data Controller — the captured pages give different entities, and customers' contact data answers to the Delaware one. Hosting in AWS Ireland and a published subprocessor list are real positives, but that same list routes contact data and PII to US-region processors for enrichment, email sync, authentication and billing, and deletion only provably deletes from databases within 7 days while backups persist 'within 730 days' and application logs 'within a maximum of 930 days'. 3
Import, export & exit
Show reasoningHide reasoning
How this is scored
Getting in with history intact, and out with everything — the anti-lock-in criterion.
0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.
3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.
5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.
8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.
10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.
The Solo Seller
Export is a zip of two CSVs — contacts and notes only — done group by group because workspace-wide export isn't currently allowed, and it drops interactions, reminders and contact custom fields unless every column was displayed first. The API is broad enough to rebuild the database elsewhere with effort, which is the honest exit path, but API access starts at Premium. 12 13 10 2
The Data Protection Officer
Export works group by group — the help pages state exporting from the whole workspace is currently not allowed — and produces two CSV files of contacts and notes, excluding interactions, reminders, contact custom fields and connection data unless every field is displayed beforehand. CSV import, a migration service and an API covering more objects give a partial path out, but API access requires the Premium plan. 12 2 13
The Sales Ops Lead
Self-serve export is a per-group contacts and notes CSV — the help center says workspace-wide export is not currently allowed — and the documented exclusions list interactions, reminders and contact custom fields, which are the very fields a pipeline runs on. A Premium-gated API and a migration service soften entry and exit, but leaving with history intact is a rebuild, not a download. 2 10 12
The RevOps Integrator
CSV export covers contacts and notes only, per group rather than per workspace, and the vendor's own help page lists what is excluded — interactions, reminders, contact custom fields, strongest connection, people in the company view — with the export following whichever columns happen to be displayed. A migration service exists and the API reaches more objects than CSV does, but API access sits behind the Premium tier, and we found no public information on import dedupe or dry-run. 12 13 2
The Migrator
Export is a two-file CSV of contacts and notes, done group by group because the help center states whole-workspace export is not currently allowed, and it explicitly excludes interactions, reminders, contact custom fields and people in the company view, while only exporting the columns displayed beforehand. The API documents notes, tasks and interactions endpoints that could rebuild a database elsewhere with effort, but API access sits on the Premium tier, and I found no public information on import deduplication, dry-run imports or contractual data-return terms. 12 13 2
The Skeptic
Exit is the weak flank: export is per-group only — 'We currently don't allow exporting from the whole workspace' — produces two CSV files for contacts and notes, and the vendor's own help page lists what is excluded, among them interactions, reminders and the contact custom field, while warning that fields must be displayed before export or they are dropped. The API could rebuild a database elsewhere with effort, but it sits in the Premium tier, and the inbound side (CSV import, a migration service, 'Migrate my CRM') is documented far better than the way out. 12 13 2
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.
5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.
8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.
10 — Complete price computability: every tier, add-on, usage meter and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.
The Solo Seller
Standard, Premium and Enterprise carry public numbers ($24, $48 and from $80 per member per month) with unlimited members and no seat minimums, which I genuinely respect. But credits are a usage meter with unpriced overage (run dry and the assistant disables until you upgrade), the captured pages give different figures for the entry price ($20 versus $24 per user per month), and we found no public information on VAT treatment or monthly-billing rates. 2 8 7
The Data Protection Officer
Standard at $24 /member/month billed $288 yearly, Premium at $48 /member/month billed $576 yearly and Enterprise from $80 /member/month billed $960 yearly are public, with annual billing saving 20% and unlimited members on every plan. However automation and AI run on a credit meter — 1,500 credits a month on Standard, 10,000 on Premium/Custom, one credit per workflow completion, disabled when exhausted — and we found no public information on VAT treatment or monthly-billed rates. 2 8
The Sales Ops Lead
Standard, Premium and Enterprise carry real figures with the billing period stated, and the workflow credit meter is public per plan — 1,500 credits for Standard, 10,000 for Premium. But the captured pages give different entry figures, the annual and monthly split is not both shown, VAT treatment is unstated, and Enterprise is a from-price. 2 7 8
The RevOps Integrator
Standard, Premium and Enterprise all carry public per-member figures with annual totals, and the credit system is unusually well disclosed — monthly credits per plan, one credit per workflow completion, and the disable-and-upgrade behavior when they run out. We found no public information on VAT treatment or monthly-billing prices, and the captured pages give different starting figures for the product — $20/user/month in the comparison article versus $24/member/month on the pricing page. 2 8 7
The Migrator
Standard at $24/member/month ($288 billed yearly), Premium at $48 ($576) and Enterprise from $80 ($960) are public, with a stated 20% annual saving and unlimited members on every tier. I found no public information on monthly-billing prices or VAT treatment, the credit meter publishes caps — 1,500 credits on Standard, 10,000 on Premium/Custom — but no price beyond an upgrade prompt when exhausted, and the captured pages give different figures for the starting price, "From $20/user/month" on one article versus $24 on the pricing page. 2 8 7
The Skeptic
The pricing page puts real numbers on three tiers — Standard '$24/member/month $288 billed yearly', Premium '$48/member/month $576 billed yearly', Enterprise 'From $80/member/month $960 billed yearly' — and even the credit allowances per tier are published, which is more disclosure than most. But the captured pages give different figures for the entry point ('From $20/user/month' on one article versus '$24/member/month' on the pricing page), and we found no public information on monthly-billing prices, VAT treatment or renewal rules — so the real invoice at renewal is still a guess. 2 7 8
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 | Incorporated in US ⚠ unverified | 0/3 pts | 3 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 |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 Sep 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. Incorporation is stated only in the privacy policy; no imprint or legal-notice page was captured.
- 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.
- 7 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 integrations 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
- 1 data 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 product 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 (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.folk.app Checked 15 Sep 2026 Details →
- 2 Vendor pricing page www.folk.app Checked 15 Sep 2026 Details →
- 3 Privacy policy www.folk.app Checked 30 Sep 2026 Details →
- 4 Contact & data model — found from sitemap developer.folk.app Checked 1 Oct 2026 Details →
- 5 Contact & data model — found from sitemap developer.folk.app Checked 1 Oct 2026 Details →
- 6 Pipeline & forecasting — found from sitemap www.folk.app Checked 1 Oct 2026 Details →
- 7 Pipeline & forecasting — found from sitemap www.folk.app Checked 1 Oct 2026 Details →
- 8 Automation & workflows — found from sitemap help.folk.app Checked 1 Oct 2026 Details →
- 9 Automation & workflows — found from sitemap help.folk.app Checked 1 Oct 2026 Details →
- 10 Integrations & API — found from sitemap developer.folk.app Checked 1 Oct 2026 Details →
- 11 Integrations & API — found from sitemap www.folk.app Checked 1 Oct 2026 Details →
- 12 Import, export & exit — found from sitemap help.folk.app Checked 1 Oct 2026 Details →
- 13 Import, export & exit — found from sitemap help.folk.app Checked 1 Oct 2026 Details →