Data Protection
Borlabs Cookie
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Borlabs GmbH · de.borlabs.io
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.
Borlabs Cookie at a glance
- Vendor
- Borlabs GmbH
- Headquarters
- Not stated on the vendor’s pages as of 20 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 20 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 20 Oct 2026
- Panel verdict
- The AI panel rates Borlabs Cookie 1/5, the mean of 6 judges. Borlabs Cookie is a WordPress consent plugin from Borlabs GmbH, scored strongest on integrations and automation, where the computed range runs 4 to 4 on a documented JavaScript API v3, PHP API and WP-CLI support, and on sovereignty, credited to a verifiable German entity — Amtsgericht Hamburg, HRB 171030 — development within the EU, and an architecture that keeps all visitor data on the customer's own server with none transmitted to the vendor. how scores are made
- As of
- Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Borlabs Cookie is a WordPress consent plugin from Borlabs GmbH, scored strongest on integrations and automation, where the computed range runs 4 to 4 on a documented JavaScript API v3, PHP API and WP-CLI support, and on sovereignty, credited to a verifiable German entity — Amtsgericht Hamburg, HRB 171030 — development within the EU, and an architecture that keeps all visitor data on the customer's own server with none transmitted to the vendor. Weakest are privacy management, rights and incidents and audit readiness: the captured pages document consent banners, content blockers, a sample privacy-statement text and IAB TCF labeling ('Non-TCF Standard'), but we found no public information on processing registers, data subject request workflows, breach registers or revision-safe audit evidence. Framework coverage rests on that single consent regime. Despite score spreads on sovereignty and framework coverage, the flagged splits report none. Orders run through Paddle.com as merchant of record, whose jurisdiction the captured pages do not state; a starting price of 'Ab 49 Euro' is published, excluding VAT.
Speaks for it
- Documented JavaScript API v3, PHP API and WP-CLI integration earn integrations and automation scores that run 4 to 4.
- Sovereignty scores of 4–6 credit Borlabs GmbH (Amtsgericht Hamburg, HRB 171030), development within the EU, and all visitor data kept on the customer's own server with none transmitted to the vendor.
- IAB TCF support is operationalized, with non-TCF service groups labeled 'Non-TCF Standard' once TCF is enabled.
- A starting price of 'Ab 49 Euro' is published, stated as excluding VAT, with anytime cancellation and a 30-day money-back guarantee.
Held against it
- Privacy management scores of 0–2: we found no public information on processing registers, DPIA workflows, processor management or technical and organizational measures.
- Rights and incidents scores of 0–1: we found no public information on data subject request intake, statutory deadline tracking, a breach register or deletion execution.
- Audit readiness scores of 0–1: we found no public information on revision-safe change history or exportable evidence packs, with one judge finding no public information on proof-of-consent logging.
- Integrations reach only the WordPress perimeter — we found no public information on directory import, ticketing, single sign-on or a REST API for the wider estate.
- The subprocessor list is available only on request, and all orders run through Paddle.com as merchant of record, whose jurisdiction the captured pages do not state.
Best for
- You run WordPress sites and want consent and content-blocking automation through documented JavaScript, PHP and WP-CLI interfaces.
- You require visitor data to stay on your own server, with none transmitted to the vendor, under a German entity that develops within the EU.
- You need IAB TCF consent handling with non-TCF service groups labeled in the same banner.
Avoid if
- You need a register system — records of processing, DPIA workflows, processor management or technical and organizational measures — rather than a consent plugin.
- You must run data subject request workflows, statutory deadline tracking or a breach register as operations.
- You need auditor-ready evidence such as revision-safe change history or exportable evidence packs.
- You need connectors beyond WordPress — directory import, single sign-on, ticketing or a REST API other systems can call.
The scores
| Criterion | Panel median |
|---|---|
| Records & DPIA depth | 0.5 of 5 |
| Data subject rights & incidents | 0 of 5 |
| Privacy regime coverage | 1 of 5 |
| Audit readiness & evidence | 0 of 5 |
| Integrations & automation | 2 of 5 |
| European sovereignty | 3 of 5 |
Records & DPIA depth
Show reasoningHide reasoning
How this is scored
The DSMS core: records of processing (RoPA/VVT), data protection impact assessments, processor/DPA management and TOMs — how deeply the legal artifacts are modeled and connected.
0 — Document templates in a folder tree; the "register" is a Word file with version numbers in the filename.
3 — A structured RoPA with basic fields and a DPIA questionnaire, but processors, TOMs and legal bases live outside the system.
5 — RoPA and DPIA as linked modules with templates; processor management and TOM assignment exist but are shallow, and group reuse is copy-paste.
8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA triggers derived from the record, reusable group templates, and outputs a supervisory authority accepts.
10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client/mandate capability included, and the documentation is audit-ready without manual assembly.
The External DPO
Borlabs Cookie is a WordPress consent tool, and the closest thing to a legal artifact in the captured pages is a sample text for the privacy statement. We found no public information on records of processing, DPIA workflows, processor management or TOMs — for thirty client mandates this product is simply not in the register business. 1 4
The In-House Counsel
The vendor states plainly that it provides no legal advice or representation, and the only legal artifact evidenced is a mustertext for the visitor-facing privacy statement. Structured service and provider records with TCF vendor lookups model third-party embeds on the website, but we found no public information on records of processing, DPIA workflows, processor management or TOMs. 1 4 7
The Drafted Generalist
This is a cookie-consent plugin for WordPress, and I found no public information on records of processing, impact assessments, or managing processors and technical measures. The only legal artifacts I could find are a sample privacy-statement text and the vendor's own data processing agreement offered for support access. 1 4
The Lead Auditor
The only legal artifacts the captured pages show are a sample privacy-policy text and order-processing-agreement handling for support access; we found no public information on records of processing, impact assessments, or technical and organisational measures. By register-maturity standards this sits at the document-template level. 4
The IT Integrator
The captured pages describe a WordPress consent tool plus a template text for a privacy notice, and we found no public information on records of processing, impact assessments, processor management or technical and organizational measures. From an integration standpoint there is no register data model here that a compliance platform could read from or feed into. 1 4
The Skeptic
The captured pages document a WordPress consent tool and nothing resembling a records system: we found no public information on a processing register, DPIA workflows, or processor and TOM management. The nearest artifact is a downloadable sample text for a privacy statement — a document template, not a register. 1 4
Data subject rights & incidents
Show reasoningHide reasoning
How this is scored
The operational half of the DSMS: data subject request handling with statutory clocks, breach register and authority notification, deletion concepts that actually delete.
0 — Requests arrive by email and live there; breaches are a phone call and a memo.
3 — A request log and a breach list exist, but deadlines are manual, intake is unstructured, and deletion rules are documentation rather than workflow.
5 — DSR workflows with the Art. 12 clock tracked, structured breach register with the 72-hour clock, deletion concepts assignable to records; automation is reminders.
8 — Intake channels for requests (portal/form), identity-check support, deadline automation with escalation, breach severity assessment and authority-report output, deletion rules tied to the RoPA with execution tracking.
10 — Rights and incidents as operations: end-to-end request handling an authority audit walks through, breach workflows that produce the Art. 33 notification, and deletion automation with evidence that the deletion happened.
The External DPO
We found no public information on data subject request intake, statutory clocks, a breach register or deletion tracking; the only request channel evidenced is the vendor's own support ticket system for product questions. The captured pages describe cookie consent handling, not rights and incident operations. 1 3
The In-House Counsel
We found no public information on data subject request handling, statutory deadline clocks, a breach register or authority notification — the operational half of a DSMS is unevidenced end to end. The only request-like channel shown is a support ticket system for product inquiries with an up-to-one-month response window. 3 4
The Drafted Generalist
I found no public information on data subject request workflows, breach registers, or deletion execution. The captured pages cover consent banners and content blockers, and the only rights process described is the vendor answering its own inquiries within a month through its ticket system. 1 3
The Lead Auditor
We found no public information on data subject request workflows, statutory deadline tracking, a breach register, or deletion execution; the captured pages describe a support ticket system with a one-month response window and retention rules written as prose in the privacy policy. The captured pages do not evidence rights or incident handling as operations. 3
The IT Integrator
We found no public information on data subject request intake, statutory deadline tracking, a breach register, authority notification or deletion execution. The documented APIs read and write cookie consent state, which is the closest the evidence comes to rights or incident operations. 1 8
The Skeptic
We found no public information on data subject request handling, statutory clocks, a breach register, or deletion execution — the entire documented operational surface consists of consent state queries and content unblocking. For a product sold in the data protection category, pages that never mention rights workflows is itself information. 1 8
Privacy regime coverage
Show reasoningHide reasoning
How this is scored
Which privacy regimes the product actually operationalizes — GDPR, BDSG, Swiss nDSG, UK GDPR, ePrivacy, EU AI Act privacy duties — and whether one record maps across them or each regime is a fresh island.
0 — One regime, hard-coded; anything else is "on the roadmap".
3 — GDPR plus one national law as separate checklists; the same processing activity is documented once per regime.
5 — The major regimes for its market with partial cross-mapping; newer duties (AI Act, ePrivacy changes) present as content packs of varying depth.
8 — Broad current coverage with one-record-many-regimes mapping and visible maintenance as regimes evolve.
10 — Regime coverage as a living product: multiple privacy regimes on one data basis, per-country variants, and documented update cadence when the law moves.
The External DPO
The evidence covers website consent duties plus the IAB TCF — once TCF is enabled, service groups are labeled 'Non-TCF Standard' — which is genuine standards work but essentially one consent regime. We found no public information on BDSG, Swiss nDSG, UK GDPR, ePrivacy variants or AI Act duties as operationalized content, and nothing that maps one record across regimes. 1 5 6
The In-House Counsel
The pages operationalize GDPR-style consent plus IAB TCF, with service groups labeled 'Non-TCF Standard' to meet TCF requirements, and offer a German privacy-statement mustertext. We found no public information on UK GDPR, Swiss nDSG, ePrivacy or AI Act duties, or on one record mapping across multiple regimes. 4 5 6
The Drafted Generalist
The one framework work visible is IAB TCF support, with service groups labeled 'Nicht-TCF-Standard' once TCF is enabled. Beyond that I found no public information on operationalizing GDPR, national data protection acts, UK GDPR, ePrivacy changes, or AI Act duties, or on one record mapping across regimes. 5 6
The Lead Auditor
The captured pages evidence consent handling with IAB TCF integration — when TCF is active, non-TCF service groups are labeled as such in the same banner — so one consent record spans the TCF and non-TCF worlds. We found no public information on national variants such as the Swiss or UK regimes, or on AI Act duties. 5 6
The IT Integrator
There is real work on one consent framework: with TCF enabled, service groups carry the 'Non-TCF Standard' label and providers can be looked up by IAB vendor ID. We found no public information on GDPR, BDSG, Swiss nDSG or UK GDPR as modeled regimes, per-country variants, or any one-record-many-regimes mapping. 5 6 8
The Skeptic
The only regime work in evidence is IAB TCF — service groups get labeled "Non-TCF Standard" once TCF is enabled — alongside a German sample privacy statement. We found no public information on mapping one record across GDPR variants, UK or Swiss law, or any documented cadence for legal updates. 4 5 6
Audit readiness & evidence
Show reasoningHide reasoning
How this is scored
Whether the system produces defensible proof: revision-safe history, evidence collection, reports for auditors, authorities and management.
0 — Exports are screenshots; history is overwritten in place.
3 — PDF reports exist but evidence is attached ad hoc and changes leave no reliable trail.
5 — Versioned records, standard report generators for the core registers, evidence attachments per activity; assembling a full audit file still takes days.
8 — Revision-safe change history, audit-scoped evidence packs on demand, management and authority reports current at a click, auditor access roles.
10 — Audit readiness as a standing state: continuous documentation status per regime and scope, exportable proof packs an auditor accepts as-is, and a defensible answer to "show me the state on date X".
The External DPO
We found no public information on revision-safe change history, evidence collection, or report generators for auditors, authorities or management; the captured pages only establish that consent data sits locally on the customer's own server. Nothing here assembles a client-ready audit file. 1 4
The In-House Counsel
We found no public information on revision-safe change history, report generators, evidence packs or auditor access roles — the pages evidence nothing that would answer 'show me the state on date X'. The only adjacent fact is that all data resides on the customer's own server, which concerns location, not defensibility. 4
The Drafted Generalist
I found no public information on revision-safe change history, auditor-ready reports, or exportable evidence packs. The outputs documented are consent handling on the customer's own server plus that sample privacy-statement text. 1 4
The Lead Auditor
The one audit-relevant architecture fact is that all data stays on the customer's own server and no visitor data is transmitted to the vendor, so whatever evidence exists remains under the operator's control. We found no public information on revision-safe change history, report generators, auditor access, or exportable evidence packs. 4
The IT Integrator
We found no public information on revision-safe change history, evidence packs, or auditor, authority and management reports; the captured resources amount to a status page and support channels. The one defensible point is architectural — consent data stays on the customer's own server — but that is hosting, not audit proof. 4 5
Integrations & automation
Show reasoningHide reasoning
How this is scored
Whether the platform feeds from the real IT estate — directory import, ticketing, API — and automates the recurring privacy work instead of re-typing it.
0 — A closed island: manual entry in, PDF out, no API.
3 — CSV/Excel import and export; no live connections, no API worth the name.
5 — Directory import (AD/Entra), a documented REST API for core objects, a handful of native connectors (ticketing or SSO); automation is reminders and recurrence.
8 — Real connector set (ticketing, HR or asset sources), webhooks, SSO/SCIM, workflow automation with delegation and escalation, useful AI assistance with human review.
10 — The platform behaves like infrastructure: API parity for the data model, event streams, bidirectional sync with the estate, and automation that measurably removes the recurring toil (reviews, attestations, evidence pulls) rather than renaming it.
The External DPO
The strongest part of this file: a documented PHP API v3, a JavaScript API v3 with consent, provider, service-group and content-blocker lookups including IAB vendor lookup, plus a WP-CLI integration for automation. But everything lives inside a single WordPress site — we found no public information on a REST API, directory import, ticketing or HR connectors, SSO or webhooks, so thirty client estates cannot be fed from one place. 7 8
The In-House Counsel
There is a genuine documented API layer — a PHP API, JavaScript API v3 with consent, content-blocker and TCF vendor lookups, plus WP-CLI automation and configurable auto-update modes. We found no public information on connections beyond the WordPress estate: no directory import, ticketing or HR sources, webhooks, SSO or SCIM. 7 8
The Drafted Generalist
There are real, documented developer interfaces — a JavaScript API, a PHP API and a WP-CLI integration — covering consents, content blockers, providers and service groups, which is more than manual entry and PDF exports. But the product is WordPress-only, and I found no public information on directory import, ticketing, SSO, or connectors to the wider IT estate. 1 7 8
The Lead Auditor
There are documented JavaScript and PHP APIs — consent checks, content blockers, provider lookups by IAB vendor ID — plus WP-CLI automation and configurable auto-update modes, which is genuine automation inside WordPress. We found no public information on directory import, a REST API over the data model, or connectors beyond the CMS, so this reads as a platform API rather than estate integration. 1 7 8
The IT Integrator
Credit where due: a documented JavaScript API v3 with consent, provider and content-blocker methods, a PHP API whose update compatibility is guaranteed only through borlabsCookieApi(), WP-CLI support and configurable auto-update modes. But the perimeter is WordPress itself — we found no public information on directory import, ticketing or HR connectors, SSO, webhooks or a REST API another system could call, so as an estate feed it stays inside one CMS. 1 7 8
The Skeptic
Credit where due: the JavaScript and PHP APIs are genuinely documented, with WP-CLI integration and selectable auto-update modes. But every documented method serves consent manipulation inside WordPress — we found no public information on directory import, ticketing, single sign-on, or any interface to the wider IT estate. 1 7 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the compliance record of the whole company actually lives and under whose law — entity, hosting, subprocessors, DPA. A platform that maps your processing is itself your most concentrated processing.
0 — Non-EU entity, non-EU-default hosting, no public DPA or subprocessor list — for the system holding your RoPA.
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 or undocumented.
5 — EU hosting is the default, DPA and subprocessor list published; the vendor or a critical subprocessor is still within non-European jurisdictional reach.
8 — EU entity, EU hosting with named data centers, published subprocessor list free of content-touching non-EU processors, DPA and TOMs public.
10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, on-premises or sovereign-cloud options, and the whole chain documented publicly.
The External DPO
The bones are European — Borlabs GmbH in Hamburg, development within the EU, and the product runs on the customer's own server with no visitor data transmitted to the vendor, which is the strongest hosting posture a client can get. But the subprocessor list is only available on request, we found no public information on a data processing agreement for the product itself (one is offered for support server access), and every order runs through Paddle.com as merchant of record, whose jurisdiction the captured pages do not document. 2 3 4 8
The In-House Counsel
The imprint and privacy policy establish Borlabs GmbH in Hamburg, registered at Amtsgericht Hamburg under HRB 171030, developed within the EU, and the product runs self-hosted on the customer's server with no visitor data transmitted to the vendor. Against that: the subprocessor list is available only on request, processing locations are described only as the provider's establishment and wherever involved parties sit, the vendor deems a data processing agreement unnecessary for the product itself, and the entire order, billing and support chain runs through Paddle.com as merchant of record, whose jurisdiction the captured pages do not state. 2 3 4 5
The Drafted Generalist
The company is verifiably German (Borlabs GmbH, Hamburg, Amtsgericht Hamburg HRB 171030) and the product keeps all data on the customer's own server, with no visitor data transmitted to Borlabs. Still, the subprocessor list is available only on request, the privacy policy describes processing wherever involved parties sit, and all orders run through Paddle.com as merchant of record — I found no public information on Paddle.com's jurisdiction. 2 3 4 8
The Lead Auditor
The imprint confirms a German entity — Borlabs GmbH, Hamburg seat, Hamburg register court, German VAT ID — and the product keeps all visitor data on the customer's server with an order-processing agreement available through the customer portal. The chain is not fully public: the subprocessor list is available only on request, and the order process runs through Paddle.com as merchant of record, for which the captured pages give no jurisdictional information. 2 3 4 5
The IT Integrator
Solid fundamentals: Borlabs GmbH of Hamburg with register court, HRB number and VAT ID, development within the EU, and consent data kept on the customer's server with no visitor data transmitted to the vendor. Against that, the subprocessor list is available only on request, we found no public information on TOMs or on the hosting of the vendor's own services, and every order is processed by Paddle.com as merchant of record, whose jurisdiction the captured pages do not state. 2 3 4 6
The Skeptic
The imprint gives a verified German entity — Borlabs GmbH, Amtsgericht Hamburg, HRB 171030 — and the architecture keeps all visitor data on the customer's own server with none transmitted to the vendor, which is the cleanest hosting answer a compliance tool can give. The chain around it is thinner: the subprocessor list is available only on request, we found no public information on ownership or where the vendor's own systems are hosted, and every order runs through Paddle as merchant of record, whose location and processing terms the captured pages never state. 2 3 4
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.
0 — No public prices at all; every configuration is a sales conversation.
3 — An entry price exists, but module add-ons, entity counts or bundled consulting make the real total incomputable.
5 — Most editions carry real numbers with billing period stated and software separated from services; at least one commonly needed module or scale step is unpriced.
8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated; only genuine corporate-group contracts are custom.
10 — Complete price computability: modules, scale steps, service packages and renewal rules public, so the invoice for a 100-employee company and a 10-client consultancy is a two-minute exercise.
The External DPO
An entry price is published — "Ab 49 Euro" — with VAT treatment stated ("Alle Preise in Euro exkl. USt."), anytime cancellation and a 30-day money-back guarantee. Beyond that entry figure we found no public information on license tiers, site counts, renewal rules or service packages, so the real invoice for a multi-site or multi-client portfolio is not computable from the captured pages. 1 2 4
The In-House Counsel
The public pages state a starting price of 'Ab 49 Euro', all prices in Euro excluding VAT, anytime cancellation and a 30-day money-back guarantee. We found no public information on edition or module pricing, billing period, or license and scale boundaries, so the real total is not computable from the public pages. 1 4
The Drafted Generalist
A starting price is public — 'Ab 49 Euro', stated as 'Alle Preise in Euro exkl. USt.', with anytime cancellation and a 30-day money-back guarantee. But I found no public numbers for further editions or scale steps and no billing period on the captured pages, and checkout is handled by Paddle.com as merchant of record. 1 2 4
The Lead Auditor
One figure is public — "Ab 49 Euro" — alongside VAT treatment stated as all prices in euros excluding VAT, a 30-day money-back guarantee, and anytime cancellation. We found no public information on billing periods, site or scale steps, or module pricing, so a buyer cannot compute the real invoice from the captured pages. 1 4
The IT Integrator
Public numbers exist: a starting price of "Ab 49 Euro", "All prices in EUR excl. VAT", cancellation at any time and a 30-day money-back guarantee. We found no public information on billing period, license or site boundaries, or scale steps, so the real invoice is not computable from the captured pages alone. 1 2 4
The Skeptic
An entry figure is public — "Ab 49 Euro", consistently stated as excluding VAT — together with anytime cancellation and a 30-day money-back guarantee. We found no public information on edition prices, billing period, or site-count tiers, so what a real order totals beyond that entry figure is not computable from the captured pages. 1 2
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Borlabs Cookie
Is Borlabs Cookie European?
Not determined: the vendor’s pages as captured do not say where Borlabs Cookie is based.
Where does Borlabs Cookie store data?
Not stated on the vendor’s pages as of 20 Oct 2026.
Does Borlabs Cookie have a free plan?
Not stated on the vendor’s pages as of 20 Oct 2026.
What are the best alternatives to Borlabs Cookie?
As of 21 Oct 2026, the panel rates preeco | datenschutz (4/5), Dastra (3/5) and caralegal (3/5) highest among the other 41 Data Protection 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 preeco | datenschutz (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Borlabs Cookie alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 20 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 — Subprocessors, Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 26 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
- 13 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
- 5 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
- 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
- 4 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
- 2 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 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 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page de.borlabs.io Checked 20 Oct 2026 Details →
- 2 Imprint — found from the homepage de.borlabs.io Checked 20 Oct 2026 Details →
- 3 Privacy policy — found from the homepage de.borlabs.io Checked 20 Oct 2026 Details →
- 4 Records & DPIA depth — found from sitemap de.borlabs.io Checked 20 Oct 2026 Details →
- 5 Privacy regime coverage — found from sitemap borlabs.io Checked 20 Oct 2026 Details →
- 6 Privacy regime coverage — found from sitemap de.borlabs.io Checked 20 Oct 2026 Details →
- 7 Integrations & automation — found from sitemap de.borlabs.io Checked 20 Oct 2026 Details →
- 8 Integrations & automation — found from sitemap de.borlabs.io Checked 20 Oct 2026 Details →