Signals are organised against the supplier context.
Service providers
Service providers are used under controlled boundaries.
Eshmere may use specialist providers for authentication, billing, hosting, notifications, internal operations and AI-supported workflows, while keeping account identifiers and private setup details out of public pages.
Trust modelClear boundaries, useful confidence
Fit, risk, timing and evidence gaps are easier to inspect.
Higher-risk service outputs stay under human review.
Customer-facing work is checked before use.
Final claims and submission decisions stay with the customer.
Trust topics
Move through the Trust Centre.
Each topic explains one part of Eshmere's public data, review, responsibility and provider boundary model.
Purposeful data
Data protection
How Eshmere limits, handles and reviews account, opportunity and service information.
Review controlsAI & human review
Where AI may assist, where human review remains required and what is never automatic.
Clear ownershipService responsibility
How Eshmere supports tender decisions while customers keep final approval and submission responsibility.
Separated surfacesSecurity & boundaries
How public pages, customer workspaces, internal operations and provider setup stay separated.
Controlled providersService providers
How provider categories support the service while private credentials and setup details stay out of public pages.
Controls in plain English
How this boundary works.
Provider categories
Eshmere may use specialist providers for defined parts of the customer and operating model.
- Authentication
- Billing
- Hosting and database
- Email and notifications
- Internal operations
- AI support providers
What remains private
Public pages should describe categories and boundaries, not private setup details.
- API keys
- Private delivery URLs
- Workspace identifiers
- Internal account IDs
- Private storage URLs
- Operational logs
Review model
Customer-facing provider use should stay tied to approved features and plain-English privacy references.
- Providers are reviewed before broad production reliance
- Customer-facing use is limited to approved features
- Formal details belong in the Privacy Notice or provider notice
Reference route
Where to go next.
Next step
Review how provider use fits the wider trust model.
Use the Trust Centre to understand data, review, service responsibility and workspace boundaries together.