EnlivenHealth
enlivenhealth.co · Pharmacy software · checked 2026-09-03
Rank 7 of 16 in Pharmacy software, where the median is 9.
- 1 found
- 11 not found
- 0 not measured
We measured 12 of 12 criteria for EnlivenHealth on 2026-09-03. We found 1 with a source and did not find 11 at the addresses we checked. That is a transparency score of 9 out of 100, band F.
Overview
Transparency labelsaas-ranking.com
EnlivenHealth
- A
- B
- C
- D
- E
- F
Published commitments0 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- not foundPublic pricing×2
- not foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
Checked 2026-09-03. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.
We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.
The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.
Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that EnlivenHealth has no such document.
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://enlivenhealth.co/legal/dpa– reached, no match (HTTP 404)https://enlivenhealth.co/dpa– reached, no match (HTTP 404)https://enlivenhealth.co/legal/data-processing-agreement– reached, no match (HTTP 404)https://enlivenhealth.co/data-processing-agreement– reached, no match (HTTP 404)https://enlivenhealth.co/legal/data-processing-addendum– reached, no match (HTTP 404)https://enlivenhealth.co/legal/gdpr– reached, no match (HTTP 404)https://enlivenhealth.co/trust/dpa– reached, no match (HTTP 404)https://enlivenhealth.co/privacy/dpa– reached, no match (HTTP 404)
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://enlivenhealth.co/legal/subprocessors– reached, no match (HTTP 404)https://enlivenhealth.co/subprocessors– reached, no match (HTTP 404)https://enlivenhealth.co/sub-processors– reached, no match (HTTP 404)https://enlivenhealth.co/legal/sub-processors– reached, no match (HTTP 404)https://enlivenhealth.co/trust/subprocessors– reached, no match (HTTP 404)https://enlivenhealth.co/privacy/subprocessors– reached, no match (HTTP 404)https://enlivenhealth.co/legal/subprocessor-list– reached, no match (HTTP 404)
Data location stated
weight 3 of 3No statement about data location found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://enlivenhealth.co/security– reached, no match (HTTP 404)https://enlivenhealth.co/trust– reached, no match (HTTP 404)https://enlivenhealth.co/legal/privacy– reached, no match (HTTP 404)https://enlivenhealth.co/privacy– reached, no match (HTTP 404)https://enlivenhealth.co/privacy-policy– reached, no match (HTTP 404)https://enlivenhealth.co/compliance– reached, no match (HTTP 404)https://enlivenhealth.co/legal/privacy-policy– reached, no match (HTTP 404)
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-03.
Show the 3 addresses we checked
https://status.enlivenhealth.co/– The name "status.enlivenhealth.co" could not be resolved.https://enlivenhealth.co/status– reached, no match (HTTP 404)https://enlivenhealth.co.statuspage.io/– Could not be fetched: fetch failed.
Public pricing
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-03.
Show the 5 addresses we checked
https://enlivenhealth.co/pricing– reached, no match (HTTP 404)https://enlivenhealth.co/pricing/– reached, no match (HTTP 404)https://enlivenhealth.co/plans– reached, no match (HTTP 404)https://enlivenhealth.co/en/pricing– reached, no match (HTTP 404)https://enlivenhealth.co/pricing-plans– reached, no match (HTTP 404)
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://enlivenhealth.co/– third-party requests before any interaction: ad.doubleclick.net, browser.sentry-cdn.com, cdn.prod.website-files.com, connect.facebook.net, d3e54v103j8qbb.cloudfront.net, distillery.wistia.com, embed-ssl.wistia.com, fast.wistia.com, fast.wistia.net, px.ads.linkedin.com, region1.analytics.google.com, snap.licdn.com, stats.g.doubleclick.net, www.facebook.com, www.google.com, www.google.de, www.googletagmanager.com
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://enlivenhealth.co/legal/subprocessors– reached, no match (HTTP 404)https://enlivenhealth.co/subprocessors– reached, no match (HTTP 404)https://enlivenhealth.co/sub-processors– reached, no match (HTTP 404)https://enlivenhealth.co/legal/dpa– reached, no match (HTTP 404)https://enlivenhealth.co/dpa– reached, no match (HTTP 404)https://enlivenhealth.co/legal/data-processing-agreement– reached, no match (HTTP 404)https://enlivenhealth.co/trust/subprocessors– reached, no match (HTTP 404)https://enlivenhealth.co/legal/sub-processors– reached, no match (HTTP 404)
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://enlivenhealth.co/security– reached, no match (HTTP 404)https://enlivenhealth.co/trust– reached, no match (HTTP 404)https://enlivenhealth.co/trust-center– reached, no match (HTTP 404)https://enlivenhealth.co/compliance– reached, no match (HTTP 404)https://enlivenhealth.co/legal/security– reached, no match (HTTP 404)https://trust.enlivenhealth.co/– The name "trust.enlivenhealth.co" could not be resolved.
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://enlivenhealth.co/legal/sla– reached, no match (HTTP 404)https://enlivenhealth.co/sla– reached, no match (HTTP 404)https://enlivenhealth.co/legal/service-level-agreement– reached, no match (HTTP 404)https://enlivenhealth.co/trust/sla– reached, no match (HTTP 404)https://enlivenhealth.co/uptime– reached, no match (HTTP 404)https://enlivenhealth.co/legal/uptime-sla– reached, no match (HTTP 404)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://enlivenhealth.co/.well-known/security.txt– reached, no match (HTTP 404)
Named privacy contact
weight 1 of 3No named privacy contact found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://enlivenhealth.co/legal/privacy– reached, no match (HTTP 404)https://enlivenhealth.co/privacy– reached, no match (HTTP 404)https://enlivenhealth.co/privacy-policy– reached, no match (HTTP 404)https://enlivenhealth.co/legal/privacy-policy– reached, no match (HTTP 404)https://enlivenhealth.co/legal/privacy-notice– reached, no match (HTTP 404)https://enlivenhealth.co/trust/privacy– reached, no match (HTTP 404)https://enlivenhealth.co/datenschutz– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 1
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://enlivenhealth.co/ · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.