Status of this document
This list covers the sub-processors engaged for a BarrierLedger engagement. It is written from what the product actually uses. Jurisdiction-specific legal review is outstanding and is required before the first pilot.
Current sub-processors
| Sub-processor | Purpose | Data involved |
|---|---|---|
| Zoho (ZeptoMail) | Delivers enquiry and notification email | The contents of an enquiry sent through the website, and platform notification email |
| Cloudflare | DNS for barrierledger.com, and object storage for backups and exported files | Network metadata; encrypted backup and export objects |
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.
- Your own identity provider, where you use single sign-on: that relationship is between you and your provider.
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
There is no published BarrierLedger mailbox. Use the enquiry form or the FEEC contact page.