Scope of this list
This list describes third parties used to deliver the public website and the service. The signed order form identifies any engagement-specific hosting provider and region before customer data is processed.
Current sub-processors
| Sub-processor | Purpose | Data involved |
|---|---|---|
| Zoho (ZeptoMail) | Delivers website enquiries and platform email when configured for the engagement | Enquiry details and the content of email notifications sent through the service |
| Cloudflare | DNS, CDN/proxy and TLS for the BarrierLedger public domains | Requests and connection data carried by the proxied domains |
| Cloudflare (R2 object storage, EU jurisdiction) | Off-site storage of the platform’s encrypted nightly database and uploaded-file backups (client-side encrypted with restic before upload) | The encrypted backup files; Cloudflare holds no key to read them |
AI providers you connect — only when your tenant enables AI extraction
AI-assisted extraction from legacy well documents is off by default. It runs only after your tenant administrator enables it and accepts the data-processing notice, and only on your own account with the AI provider you choose. When it is enabled, the documents you upload for extraction (and nothing else from your register) are sent to that provider, which processes them under your agreement with it. BarrierLedger does not hold an AI provider account on your behalf.
| Provider (only if you connect it) | Purpose | Data involved |
|---|---|---|
| Anthropic (Claude — directly, or through Amazon Bedrock on your AWS account) | Drafts structured well data from a document you upload, for your engineer to review | The uploaded document and the extraction instructions |
| OpenAI or Azure OpenAI (your account) | As above | As above |
| Ollama (Ollama Cloud on your account, or your own self-hosted server) | As above | As above |
| An OpenAI-compatible gateway you configure | As above | As above |
If your tenant does not enable AI extraction, none of these providers receives any of your data.
Hosting
The hosting provider for a dedicated production host, and the region it runs in, are named in your order form and in the signed DPA before any customer data is shared. We do not publish a hosting provider name on this page that is not the provider actually used for your deployment.
A self-hosted licence has no FEEC hosting sub-processor at all: the platform runs inside your own infrastructure, under your own agreements.
What is not a sub-processor
- The marketing website’s font files. The IBM Plex typefaces are served from this site, not from a font CDN.
- No analytics, advertising or tracking provider. There is none on this site and none in the platform.
- A customer identity provider: single sign-on is not part of the current release. If offered later, the identity provider and the applicable processing terms will be identified in the order form.
Changes
We will tell you before a new sub-processor is engaged to process your data, and you may object. If you object and the engagement cannot continue without that sub-processor, you may terminate the affected part of the service.
Contact
Questions about sub-processors, or a request to be told of changes, go to privacy [at] barrierledger.com.