SaaS Ranking

Julep

julephosting.de · Video and podcast hosting · checked 2026-09-04

10/100FBand F

Rank 26 of 29 in Video and podcast hosting, where the median is 22.

We measured 11 of 12 criteria for Julep on 2026-09-04. We found 1 with a source and did not find 10 at the addresses we checked; 1 we could not measure at all. That is a transparency score of 10 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

Julep

julephosting.de · Video and podcast hosting

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 10of 100 Rank 26 of 29

Published commitments0 of 9 found

Measured behaviour1 of 2 found, 1 not measured

Checked 2026-09-04. 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 Julep has no such document.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-04.

Show the 8 addresses we checked
  1. https://julephosting.de/legal/dpa – reached, no match (HTTP 200)
  2. https://julephosting.de/dpa – reached, no match (HTTP 200)
  3. https://julephosting.de/legal/data-processing-agreement – reached, no match (HTTP 200)
  4. https://julephosting.de/data-processing-agreement – reached, no match (HTTP 200)
  5. https://julephosting.de/legal/data-processing-addendum – reached, no match (HTTP 200)
  6. https://julephosting.de/legal/gdpr – reached, no match (HTTP 200)
  7. https://julephosting.de/trust/dpa – reached, no match (HTTP 200)
  8. https://julephosting.de/privacy/dpa – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-04.

Show the 7 addresses we checked
  1. https://julephosting.de/legal/subprocessors – reached, no match (HTTP 200)
  2. https://julephosting.de/subprocessors – reached, no match (HTTP 200)
  3. https://julephosting.de/sub-processors – reached, no match (HTTP 200)
  4. https://julephosting.de/legal/sub-processors – reached, no match (HTTP 200)
  5. https://julephosting.de/trust/subprocessors – reached, no match (HTTP 200)
  6. https://julephosting.de/privacy/subprocessors – reached, no match (HTTP 200)
  7. https://julephosting.de/legal/subprocessor-list – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Data location stated

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-04.

Show the 7 addresses we checked
  1. https://julephosting.de/security – reached, no match (HTTP 200)
  2. https://julephosting.de/trust – reached, no match (HTTP 200)
  3. https://julephosting.de/legal/privacy – reached, no match (HTTP 200)
  4. https://julephosting.de/privacy – reached, no match (HTTP 200)
  5. https://julephosting.de/privacy-policy – reached, no match (HTTP 200)
  6. https://julephosting.de/compliance – reached, no match (HTTP 200)
  7. https://julephosting.de/legal/privacy-policy – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-04.

Show the 3 addresses we checked
  1. https://status.julephosting.de/ – reached, no match (HTTP 200)
  2. https://julephosting.de/status – reached, no match (HTTP 200)
  3. https://julephosting.de.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-04.

Show the 5 addresses we checked
  1. https://julephosting.de/pricing – browser: page.goto: net::ERR_CERT_COMMON_NAME_INVALID at https://julephosting.de/pricing Call log: - navigating to "https://julephosting.de/pricing", waiting until "domcontentloaded"
  2. https://julephosting.de/pricing/ – reached, no match (HTTP 200)
  3. https://julephosting.de/plans – reached, no match (HTTP 200)
  4. https://julephosting.de/en/pricing – reached, no match (HTTP 200)
  5. https://julephosting.de/pricing-plans – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-04.

Show the 8 addresses we checked
  1. https://julephosting.de/legal/subprocessors – reached, no match (HTTP 200)
  2. https://julephosting.de/subprocessors – reached, no match (HTTP 200)
  3. https://julephosting.de/sub-processors – reached, no match (HTTP 200)
  4. https://julephosting.de/legal/dpa – reached, no match (HTTP 200)
  5. https://julephosting.de/dpa – reached, no match (HTTP 200)
  6. https://julephosting.de/legal/data-processing-agreement – reached, no match (HTTP 200)
  7. https://julephosting.de/trust/subprocessors – reached, no match (HTTP 200)
  8. https://julephosting.de/legal/sub-processors – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-04.

Show the 6 addresses we checked
  1. https://julephosting.de/security – reached, no match (HTTP 200)
  2. https://julephosting.de/trust – reached, no match (HTTP 200)
  3. https://julephosting.de/trust-center – reached, no match (HTTP 200)
  4. https://julephosting.de/compliance – reached, no match (HTTP 200)
  5. https://julephosting.de/legal/security – reached, no match (HTTP 200)
  6. https://trust.julephosting.de/ – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-04.

Show the 6 addresses we checked
  1. https://julephosting.de/legal/sla – reached, no match (HTTP 200)
  2. https://julephosting.de/sla – reached, no match (HTTP 200)
  3. https://julephosting.de/legal/service-level-agreement – reached, no match (HTTP 200)
  4. https://julephosting.de/trust/sla – reached, no match (HTTP 200)
  5. https://julephosting.de/uptime – reached, no match (HTTP 200)
  6. https://julephosting.de/legal/uptime-sla – reached, no match (HTTP 200)

Is this wrong? Send us the URL

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-04.

Show the 1 address we checked
  1. https://julephosting.de/.well-known/security.txt – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-04.

Show the 7 addresses we checked
  1. https://julephosting.de/legal/privacy – reached, no match (HTTP 200)
  2. https://julephosting.de/privacy – reached, no match (HTTP 200)
  3. https://julephosting.de/privacy-policy – reached, no match (HTTP 200)
  4. https://julephosting.de/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://julephosting.de/legal/privacy-notice – reached, no match (HTTP 200)
  6. https://julephosting.de/trust/privacy – reached, no match (HTTP 200)
  7. https://julephosting.de/datenschutz – reached, no match (HTTP 200)

Is this wrong? Send us the URL

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 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://julephosting.de/ · checked 2026-09-04

Not measured by us 1

No third-party tracking before consent

weight 2 of 3

Not measured. The page could not be loaded in a browser, so this was not measured.

Show the 1 address we checked
  1. https://julephosting.de/ – page.goto: net::ERR_CERT_COMMON_NAME_INVALID at https://julephosting.de/ Call log: - navigating to "https://julephosting.de/", waiting until "domcontentloaded"

Is this wrong? Send us the URL

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare