Select market or region
Sign in

Navigation

PlatformSolutionsPricingResourcesEnterpriseCompany
Select market or region

Data protection

Data minimisation by design.

Eshmere collects only the account, preference, opportunity and service information needed to support procurement decisions, and keeps sensitive evidence out of public routes unless a reviewed process is approved.

Trust modelClear boundaries, useful confidence
01Monitor

Signals are organised against the supplier context.

02Analyse

Fit, risk, timing and evidence gaps are easier to inspect.

03Review

Higher-risk service outputs stay under human review.

04Approve

Customer-facing work is checked before use.

05Customer decides

Final claims and submission decisions stay with the customer.

Controls in plain English

How this boundary works.

What Eshmere may process

Eshmere keeps collection tied to the procurement decision or service request being supported.

  • Account and organisation details
  • Opportunity preferences
  • Service request information
  • Billing and account metadata
  • Internal review notes

What should not be sent through public forms

Sensitive evidence should use an approved handling route after the request has been reviewed.

  • Tax records
  • Financial evidence
  • AGPO evidence
  • Full bid documents
  • Sensitive identity records

How data is handled

The operating model is based on limited collection, review and controlled access.

  • Limited collection for a defined purpose
  • Internal review before deeper service work
  • Access controls for operational records
  • Retention review before long-term reliance
  • A support route for privacy questions

Reference route

Where to go next.

Next step

Start with the minimum useful information.

Use the request form for the enquiry only. Eshmere can explain any next handling route after review.