Lead Generation
Pharow
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 PHAROW SAS · www.pharow.com
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
Pharow is a B2B prospecting database from PHAROW SAS, a French-law company registered at RCS Créteil, scoped to companies and prospects in France, with lists built on NAF sector, revenue, ongoing recruitment, growth, team size and technology filters and email enrichment through bundled providers Dropcontact, FullEnrich and Zerobounce. The strongest score is CRM sync and export, at 4 across the table, on an Export 2.0 that feeds and updates the CRM without duplicates; sovereignty follows at 3-4, resting on the French contracting entity and site hosting at OVH. Weakest are data provenance and visitor identification, both ranging 1-2: judges found no published legal basis for the people in the database, no objection or removal route for them, and no source or mechanism behind the intent-data claim. Judges spread 2-4 on data coverage and prospecting compliance — lower scores cite missing record counts, refresh cadence, coverage beyond France and any do-not-contact provision, higher ones credit the filters and deduplicated export. No paid price is published; the trial reads "15 jours d'essai gratuit. 100 crédits offerts."
Speaks for it
- Export 2.0 feeds and updates the CRM without duplicates, with one-click export to CSV, webhooks and sending tools — CRM sync and export scored 4 across the table.
- Sovereignty scores run 3-4 on a French-law contracting entity — PHAROW SAS, RCS de Créteil 881 636 286, registered office at 10 rue de Penthièvre 75008 Paris — and site hosting at OVH.
- Targeting filters are concrete and checkable: NAF sectors, revenue, ongoing recruitment, growth, team size and technologies used.
- Email verification runs through named providers (Dropcontact, FullEnrich, Zerobounce) stated as included in Pharow subscriptions, with Kaspr, BetterContact and FullEnrich connectable for phone.
- A free trial is published plainly: 15 days with 100 credits offered.
Held against it
- Data provenance scores run 1-2 — we found no public statement of the legal basis for the people in the database, no notice to them, and no self-service objection or removal route.
- Visitor identification scores run 1-2 — the intent-data claim appears with no named source, no tracking mechanism and no consent position on the captured pages.
- We found no record counts, refresh cadence or accuracy method for the French database, and no public information on coverage beyond France.
- We found no public information on suppression or do-not-contact lists, country-aware flagging or lawful-outreach guidance; prospecting compliance scores spread 2-4 on this.
- We found no public location for the prospecting database itself, no subprocessor list and no transfer basis for the named enrichment partners.
Best for
- You run outbound to French companies and want segmented lists ready from NAF sector, revenue, hiring, growth, team-size and technology filters.
- Your pipeline depends on exports that land in the CRM deduplicated and stay updated without manual action.
- A French-law contracting entity and OVH site hosting are baseline requirements in your EU procurement.
- You want email verification bundled in the subscription and can connect your own Kaspr, BetterContact or FullEnrich accounts for phone numbers.
Avoid if
- You need prospect data for Germany, Austria or Switzerland — the captured pages scope the product to France.
- Your legal review requires a published legal basis, notice to listed individuals and an objection route before you contract.
- You are buying website visitor identification and need a named intent-data source and a consent position — the claim appears on the homepage without a mechanism.
The scores
Coverage, accuracy & freshness
Show reasoningHide reasoning
How this is scored
How much of the target market the database actually covers — judged on DACH and EU coverage as much as North American — and what the vendor documents about verification and refresh, because accuracy claims cannot be checked from outside.
0 — No stated coverage, no refresh cadence, no verification method; accuracy asserted as a percentage with nothing behind it.
3 — Headline record counts for the whole database, thin or unstated European coverage, and no description of how often records are re-verified.
5 — Coverage stated per country or region including DACH, email verification described, a stated refresh cadence, and firmographics beyond name and domain.
8 — Coverage broken down by country, industry and data type (email, direct dial, mobile), verification method and refresh cadence documented, company data drawn from official registers where available, and a bounce or credit-back guarantee with stated terms.
10 — The vendor is accountable for its data: per-country coverage and accuracy methodology published, every field carrying a last-verified date visible to the user, register-sourced company data, and credit-back terms that make inaccuracy the vendor's cost rather than the buyer's.
The SDR Team Lead
Pharow scopes itself to France — company, financial, legal and growth data on French companies, with filters on NAF sector, revenue, active hiring, team growth and technologies, which are firmographics I can actually work with. But we found no public information on record counts, a refresh cadence, an accuracy method behind the claimed connect quality, or any coverage of DACH and wider Europe beyond France. Email verification runs through named third-party providers (Dropcontact, FullEnrich, Zerobounce) rather than a documented method of their own. 1
The RevOps Manager
The positioning is squarely French companies with rich filters — NAF sector, revenue, ongoing recruitment, growth, team size, tech stack — and email verification leans on bundled third parties like Dropcontact and Zerobounce, but the captured pages give no record counts, no refresh cadence and no accuracy methodology. I found no public information on coverage beyond France, so DACH and the rest of the EU are simply not addressed. 1
The Data Protection Officer
Coverage is stated as French companies and prospects with firmographic filters on sector, revenue, hiring, growth, team size and technologies, and emails are verified through bundled partners. We found no public information on record counts, refresh cadence, verification of the underlying database, or accuracy guarantees for the records a buyer exports. 1
The ABM Marketer
The captured pages describe a France-only database with genuine firmographic depth — NAF sector, revenue, team size, technologies used and live recruitment signals — and 'Données légales' among the data categories suggests register-sourced company facts. But I found no record counts, no refresh cadence and no verification method, and no public information on DACH or any market outside France, so for a buyer working German accounts the coverage question is simply open. 1
The DACH Sales Director
Pharow scopes its whole database to companies and prospects in France, and we found no public information on coverage for Germany, Austria or Switzerland, which is my market. Beyond filter categories like NAF sectors and revenue, we found no public information on record counts, verification methods, or refresh cadence. 1
The Skeptic
The target market is stated as French B2B, with firmographic filters (NAF sectors, revenue, hiring in progress, growth, team size, technologies) and email verification delegated to bundled providers such as Dropcontact, FullEnrich and Zerobounce. We found no record counts for even the French market, no refresh cadence, no accuracy methodology and no bounce or credit-back terms, and nothing on DACH or wider-EU coverage. 1
Data sources & lawful basis
Show reasoningHide reasoning
How this is scored
Where the personal data in the database comes from and on what legal basis it is processed — as evidenced on the vendor's own pages. Covers Art. 6(1)(f) legitimate interest, the Art. 14 notice to the people in the database, and whether they can find, object to and remove their record.
0 — No statement of where contact data comes from or on what legal basis; "GDPR-compliant" asserted without explanation, and no way for a listed person to object.
3 — Sources described in general terms ("public sources", "partners"), legitimate interest named without any balancing, and an opt-out request form as the only route for data subjects.
5 — Source categories named (registers, company websites, contributory networks, licensed partners), legitimate interest stated as the basis for EU records, a dedicated privacy notice for the people in the database, and a self-service opt-out or removal process.
8 — The above plus an Art. 14 notification practice described (people informed when added), contributory or browser-extension collection disclosed as such, a legitimate-interest assessment summarised publicly, and EU records handled differently from US records where the law differs.
10 — Provenance is traceable per record: the source and collection date available for each contact, Art. 14 notices sent and documented, the balancing test published, objections honoured across the whole dataset and suppressed permanently, and no data sourced by scraping behind logins or from contributors' address books without their contacts' knowledge.
The SDR Team Lead
Company-side data looks register-based (the published categories include legal and financial data) and contact enrichment is outsourced to named providers, but we found no public information on the legal basis for processing the contact data, a privacy notice for the people in the database, or a self-service opt-out and removal route. A terms and privacy-policy link exists on the homepage; the captured pages give no visibility into its contents. 1
The RevOps Manager
The data categories hint at register-derived legal and financial data, and a privacy policy and cookie page are linked, but I found no public statement of the legal basis for processing the people in the database, no notification practice for those listed, and no self-service way for a listed person to object or be removed. For a database of people who never chose the vendor, that silence is the deciding fact. 1 3
The Data Protection Officer
Provenance appears as data-category labels — legal data, professional network, web data — plus named enrichment partners for email and phone, with no statement of the legal basis on which the people in this database are processed. We found no public information on an Article 14 notice to listed individuals or on any route for them to object to and remove their record, the first thing I look for once a list leaves the vendor. 1 3
The ABM Marketer
Source categories are named in general terms — financial data, legal data, professional network, Web Data — and the enrichment partners are identified (Dropcontact, FullEnrich, Zerobounce for email; Kaspr, BetterContact and FullEnrich for phone). I found no public information on the legal basis, no balancing of legitimate interest, and no route for a listed person to object to or remove their record, which is what I would need before defending this list in front of legal. 1 3
The DACH Sales Director
Sources surface only as broad categories — financial data, legal data, professional network, web data — alongside named email enrichment partners, and we found no public information on the legal basis for processing the people in the database, on a notice for them, or on a self-service objection route. A privacy policy is listed among the legal pages, and we found no public information on its contents. 1 3
The Skeptic
Sources are hinted at only through category names — legal data, web data, professional network — with no statement of the legal basis for processing the people in the database. We found no notification practice for listed people, no balancing summary and no removal or objection route; only that a privacy policy link exists alongside the terms. 1 3
Visitor identification & intent signals
Show reasoningHide reasoning
How this is scored
Identifying companies behind website visits and surfacing buying intent — scored on what is identified (company or person), how the tracking works, and whether the vendor states that its script needs consent under §25 TDDDG and how it behaves without it.
0 — No visitor identification or intent data, or person-level identification of EU visitors with no statement of legal basis.
3 — Reverse-IP company identification with a cookie-setting script, no statement about consent, and match rates claimed without method.
5 — Company-level identification with filters, visit history per company, a stated position that the script requires consent where it sets cookies, and a consent-mode or cookieless option.
8 — Company-level only for EU traffic by design, cookieless operation documented, integration with common consent management platforms, intent topics or page-level signals with the source of third-party intent data named, and alerts routed to owners.
10 — Identification that survives a DPO review: no personal data of visitors stored, the TDDDG and GDPR position published and specific, third-party intent data sourced from a named co-op or panel with its consent basis stated, and scoring on intent that the user can trace back to the underlying visits.
The SDR Team Lead
The homepage says Pharow reconciles intent data and business signals, but we found no public information on company-visitor identification, any tracking script, its consent behaviour, or where the intent data comes from. A cookie-conformity page for their own site is not a documented visitor-identification product. 1
The RevOps Manager
One sentence says Pharow reconciles intent data and business signals; beyond that I found no public description of any visitor identification mechanism, no tracking method, no consent position for a tracking script, and no named source for the intent data. Recruitment and growth filters are firmographic triggers, not identification of companies visiting a website. 1
The Data Protection Officer
Intent data and business signals such as ongoing recruitment and growth are reconciled and offered as filters, though the source of the intent data is not named. We found no public information on identifying the companies behind website visits, on any tracking script, or on how such a script behaves before consent. 1
The ABM Marketer
The homepage says Pharow reconciles "l'intent data et les signaux d'affaires" on French companies, which is the signal language I want to hear. But I found no public information on company-level website visitor identification, on a named third-party source behind the intent data, on how signals are tracked, or on alerts reaching an account owner while the signal is warm — intent as an ingredient is claimed, intent as a workflow is not in evidence. 1
The DACH Sales Director
The homepage mentions intent data and business signals reconciled into prospect lists, but we found no public information on website visitor identification, on whether companies or persons are identified, or on any consent position for a tracking script. A mention without method is not something I can take to a German DPO. 1
The Skeptic
Intent data and business signals are named as reconciled inputs, but we found no named third-party source, no description of what is identified about a visitor or how, and no position on cookies or consent for any tracking. An intent claim with no mechanism, no source and no consent statement is worth very little under review. 1
Prospecting workflow & outreach rules
Show reasoningHide reasoning
How this is scored
Search, list building and outreach — and whether the product helps the buyer stay within UWG §7 and the GDPR once the list exists, rather than leaving the legal risk entirely with the customer.
0 — A search box and an export button; nothing on the pages about what the buyer may lawfully do with the contacts.
3 — Filters on firmographics and job title, saved lists, and a terms clause making the customer solely responsible for compliance.
5 — Advanced filters including technographics and triggers, company-level lists and alerts, a global suppression or do-not-contact list, and guidance on cold outreach rules in the main EU markets.
8 — The above plus country-aware handling (for example flagging German contacts where cold calls and emails require consent), phone numbers checked against national do-not-call registers where they exist, and opt-outs from outreach synced back to the database.
10 — Compliance is part of the workflow: outreach channels restricted or flagged per country and contact type by default, suppression shared across the whole account and every export, the Art. 14 notice supported at first contact, and a documented record of how each contact entered the buyer's pipeline.
The SDR Team Lead
List building is real: NAF sectors, revenue, ongoing recruitment, growth and tech-stack filters with one-click exports to CSV, CRM, webhooks and sending tools, deduplicated. But we found no public information on a global suppression or do-not-contact list, country-level rules for cold email and calls, or outreach guidance beyond the existence of terms and a privacy policy. 1
The RevOps Manager
Search is genuinely strong — NAF sectors, revenue, recruitment, growth, team size, technologies — with segmented lists and one-click export to CRM and sending tools. But I found no suppression or do-not-contact list, no guidance on cold outreach rules in any market, and nothing that flags a contact's country or consent status, so the legal risk sits entirely with the buyer as far as the captured pages show. 1
The Data Protection Officer
Segmented list building is well evidenced — filters on sector, revenue, hiring, growth, team size and technologies, with one-click export to CRM and sending tools — and terms of use and a privacy policy are referenced. We found no public information on guidance for lawful cold outreach, a do-not-contact or suppression list, or country-aware handling of contacts, which leaves the outreach-law risk with the buyer. 1 3
The ABM Marketer
The filter set runs to technographics and live triggers like "recrutements en cours", and one-click export into sending tools means the list-building half of the workflow is real. I found no public information on a do-not-contact or suppression list, country-aware flagging of German contacts, or any guidance on what the buyer may lawfully send, so the outreach risk appears to sit entirely with the customer. 1
The DACH Sales Director
The filters are genuinely strong — NAF sectors, revenue, active recruitment, growth, team size, technologies — and segmented lists export without duplicates, which reaches into advanced territory. But we found no public information on a global do-not-contact list, on country-aware flagging of German contacts, or on guidance for lawful cold outreach, so the UWG §7 risk stays with the buyer. 1
The Skeptic
Search offers firmographic, hiring and technology filters and segmented list building is the core of the pitch. We found no public information on suppression or do-not-contact lists, on checks against opt-out registers, or on guidance for what a buyer may lawfully send, so nothing captured addresses the legal risk of the outreach itself. 1
CRM sync, enrichment & export
Show reasoningHide reasoning
How this is scored
Getting the data into the systems where sales works — CRM sync, enrichment of existing records, API — and what happens to exported data, and to the buyer's access to it, when the subscription ends.
0 — Manual CSV export only; no CRM integration and no API.
3 — A one-way push to one CRM, CSV export, and no statement on whether exported data may be kept after cancellation.
5 — Native sync with the major CRMs including field mapping and deduplication, enrichment of existing CRM records, and a documented API with stated limits.
8 — Bidirectional sync with scheduled re-enrichment, update and deletion propagated when a record changes or a person objects, webhook or API access with credit costs per call published, and data retention rights after cancellation stated plainly.
10 — The vendor treats the buyer's CRM as the system of record: objections and corrections propagated into synced records automatically, full change history per field, a versioned API with a deprecation policy, and exit terms that say exactly which data the customer may keep and for how long.
The SDR Team Lead
Export 2.0 feeds and updates the CRM without duplicates and without manual action, which covers my team's basic pipeline plumbing alongside CSV and webhook exports. We found no public information on which CRMs are supported, field mapping, enrichment of existing CRM records, a documented API with limits, or what happens to exported data when the subscription ends. 1 3
The RevOps Manager
Export 2.0 makes the claim I care about most — feeding and updating the CRM without duplicates and without manual action, alongside CSV, webhook and sending-tool exports — and update-rather-than-duplicate is exactly the right behaviour. But I found no field mapping, no named target CRMs, no documented API with limits, no scheduled re-enrichment, and nothing on what we may keep in our CRM after cancellation. 1 3
The Data Protection Officer
The Export 2.0 feature is described as feeding and updating a CRM without duplicates, with CSV, webhook, CRM and sending-tool export formats, which goes beyond a one-way push. We found no public information on which CRMs are supported, field mapping, a documented API with limits, propagation of objections and deletions, or what a customer may keep after cancellation. 1 3
The ABM Marketer
Export 2.0 is described as feeding and updating the CRM without duplicates — "alimente et met à jour le CRM sans doublon" — and exports go to CSV, webhooks and sending tools with no manual action, which covers the basics of getting data to sales. I found no public information on which CRMs are supported, field mapping, a documented API with stated limits, or what happens to exported data and access when the subscription ends. 1 3
The DACH Sales Director
One-click export to CSV, webhooks, the CRM and sending tools, with the CRM fed and updated without duplicates, reads as enrichment of existing records with deduplication built in. We found no public information on which CRMs are supported natively, on a documented API with limits, or on what the customer may keep after cancellation. 1 3
The Skeptic
One-click export to CSV, webhooks, CRM and sending tools, plus an 'Export 2.0' that both feeds and updates the CRM without duplicates, is more than a push button. But no CRM is named, field mapping is not described, no documented API with limits appears in what we captured, and we found no statement on whether exported data may be kept after cancellation. 1 3
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where a database of EU residents' personal data is held, who the contracting entity and controller are, and which subprocessors see it. Independently sourced by the sovereignty pipeline; weighted heavily here, because the product itself is personal data about people who never chose the vendor.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and EU residents' contact data processed outside the EU with no stated transfer basis.
3 — Non-EU contracting entity with an EU representative under Art. 27, or EU hosting offered while enrichment, support or AI processing stay non-EU.
5 — EU contracting entity and EU hosting as standard, but parts of the chain — data partners, enrichment sources, tracking infrastructure — are non-EU without an explained safeguard.
8 — EU contracting entity and controller, EU hosting on named infrastructure, subprocessor and data-partner list published, and any non-EU transfer named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, controller, hosting, data partners and every subprocessor European, certification published, and a DPA covering both the customer's data and the database records the customer exports.
The SDR Team Lead
The contracting entity is confirmed French on the vendor's own legal notice — PHAROW SAS, Paris, RCS Créteil — and the site is hosted at OVH. But we found no public information on where the prospecting database itself is hosted, on a subprocessor list, or on the jurisdictions of the named enrichment partners (Dropcontact, FullEnrich, Zerobounce, Kaspr, BetterContact) in the chain. 1 3
The RevOps Manager
The contracting entity is a French SAS registered in Paris with the website hosted at OVH, which is a sound start for a product built on French records. But I found no public information on where the prospecting database itself is hosted, who owns the vendor, or any subprocessor and data-partner list — the enrichment partners are named as bundled providers, yet the processing chain behind them is undocumented. 1 3
The Data Protection Officer
The contracting entity is confirmed French — a SAS registered at the RCS de Créteil with its office in Paris — the website is hosted at OVH, and the email and phone partners are named on the homepage. We found no public information on where the prospecting database itself is hosted, a subprocessor list, a data processing agreement, or the transfer basis for the named partners, so end-to-end EU processing rests on the entity's nationality rather than on stated facts. 1 3
The ABM Marketer
The contracting entity is a French SAS with its registered office in Paris under French law, and the site is hosted at OVH, which is a solid start for an EU buyer. But I found no public information on where the prospecting database itself is hosted, on subprocessors, or on the location of the named enrichment partners, so a French wrapper does not tell me where the personal data actually lives. 3 1
The DACH Sales Director
The contracting entity is a French SAS under French law, RCS-registered in Créteil, and the website runs at OVH — the right instincts, and a register-based foundation is what I want to see. But we found no public information on where the prospecting database itself is hosted, on a subprocessor and data-partner list, or on transfer safeguards around the named enrichment connectors. 3 1
The Skeptic
A French SAS under French law, registered office at 10 rue de Penthièvre in Paris, site hosted at OVH, and enrichment partners at least named (Dropcontact, FullEnrich, Zerobounce, Kaspr, BetterContact) — that is the whole of what is evidenced. We found no public information on where the prospecting database itself is hosted, on subprocessors and transfer bases, or on a data-processing agreement covering the records a customer exports. 1 3
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone — including credits per email, phone number and mobile, credit expiry, seat pricing, visitor-identification tiers and the API — in a category where the unit of billing is often invented by the vendor.
0 — No public prices at all; every tier is a sales conversation.
3 — A monthly headline exists, but what a credit buys, whether credits expire, or the cost of an additional seat is unstated — the invoice is unknowable.
5 — Tier prices public with credit allowances given, but at least one commonly needed piece (mobile numbers, extra seats, API access, CRM sync) is unpriced or behind a sales call.
8 — Every tier priced publicly with credits per data type, credit expiry and rollover, per-seat costs, overage rates, minimum term and VAT treatment stated.
10 — Complete price computability: the annual invoice derivable for a given number of seats, exported contacts by data type, identified companies and API calls, with every credit cost and the refund rule for inaccurate data published.
The SDR Team Lead
Only the trial is priced in public: 15 days free with 100 credits offered. We found no public information on tier prices, what a credit buys per data type, credit expiry, seat costs or overages — I cannot compute an annual invoice from what is published. 1 3
The RevOps Manager
The only pricing fact in evidence is the free trial — fifteen days with 100 credits offered. I found no public subscription prices, no credit cost per data type, no expiry or rollover terms, no seat pricing and no VAT treatment, so a real annual invoice cannot be computed from the captured pages. 1 3
The Data Protection Officer
The only pricing facts the captured pages yield are the trial terms — "15 jours d'essai gratuit. 100 crédits offerts" — which establish credits as the billing unit. We found no public information on paid tier prices, what a credit buys, credit expiry, extra-seat costs or API pricing, so a buyer cannot compute the annual invoice from what is published. 1 2 3
The ABM Marketer
The only pricing facts in evidence are the trial — "15 jours d'essai gratuit. 100 crédits offerts." — and that email verification providers are "inclus dans vos abonnements". I found no public information on tier prices, what a credit buys beyond the trial, credit expiry, seat costs or API pricing, so the invoice is not computable from what has been captured. 1 3
The DACH Sales Director
The only pricing information on the captured pages is the trial — "15 jours d'essai gratuit. 100 crédits offerts." — and we found no public information on tier prices, on what a credit buys, on credit expiry, or on seat costs. No buyer can compute an annual invoice from that. 1 3
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 FR | 3/3 pts | 3 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 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 — Subprocessors. 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.
- We found no public information on compliance on the pages we read (pharow.com, pharow.com/tarifs, pharow.com/mentions-legales, pharow.com/usage/synchronisez-transferer-donnees-crm-outil-envoi, pharow.com/nouveautes-produits/export-webhook-pharow). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 20 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
- 9 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 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
- 3 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 legal 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 (5)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.pharow.com Checked 22 Sep 2026 Details →
- 2 Pricing page www.pharow.com Checked 22 Sep 2026 Details →
- 3 Legal notice www.pharow.com Checked 22 Sep 2026 Details →
- 4 CRM sync, enrichment & export — found from sitemap www.pharow.com Checked 1 Oct 2026 Details →
- 5 CRM sync, enrichment & export — found from sitemap www.pharow.com Checked 1 Oct 2026 Details →