SaaS Ranking
Menu

Retail, hospitality and services / Catering and event management

Caterease

What Caterease publishes on caterease.com, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Transparency 26/100 EBand E

Rank 1 of 9 in Catering and event managementcategory median 17checked 2026-09-02

9 gaps found: 9 criteria not found at the addresses we checked. 3 found9 not found0 not measured

Public transparency score, not a product or security rating.

Transparency labelsaas-ranking.com

Caterease

caterease.com · Catering and event management

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

Published commitments3 of 9 found

Measured behaviour0 of 3 found

Checked 2026-09-02. 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.

Show the full transparency label

Transparency labelsaas-ranking.com

Caterease

caterease.com · Catering and event management

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

Published commitments3 of 9 found

Measured behaviour0 of 3 found

Checked 2026-09-02. 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.

Not found, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-02.

Show the 8 addresses we checked
  1. https://caterease.com/legal/dpa – reached, no match (HTTP 200)
  2. https://caterease.com/dpa – reached, no match (HTTP 200)
  3. https://caterease.com/legal/data-processing-agreement – reached, no match (HTTP 200)
  4. https://caterease.com/data-processing-agreement – reached, no match (HTTP 200)
  5. https://caterease.com/legal/data-processing-addendum – reached, no match (HTTP 200)
  6. https://caterease.com/legal/gdpr – reached, no match (HTTP 200)
  7. https://caterease.com/trust/dpa – reached, no match (HTTP 200)
  8. https://caterease.com/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-02.

Show the 7 addresses we checked
  1. https://caterease.com/legal/subprocessors – reached, no match (HTTP 200)
  2. https://caterease.com/subprocessors – reached, no match (HTTP 200)
  3. https://caterease.com/sub-processors – reached, no match (HTTP 200)
  4. https://caterease.com/legal/sub-processors – reached, no match (HTTP 200)
  5. https://caterease.com/trust/subprocessors – reached, no match (HTTP 200)
  6. https://caterease.com/privacy/subprocessors – reached, no match (HTTP 200)
  7. https://caterease.com/legal/subprocessor-list – 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-02.

Show the 3 addresses we checked
  1. https://status.caterease.com/ – The name "status.caterease.com" could not be resolved.
  2. https://caterease.com/status – reached, no match (HTTP 200)
  3. https://caterease.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-02.

Show the 2 addresses we checked
  1. http://caterease.com/ – redirects to https://caterease.com/
  2. https://caterease.com/ – no HSTS header

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-02.

Show the 1 address we checked
  1. https://caterease.com/ – third-party requests before any interaction: a.clarity.ms, ad.doubleclick.net, api.livechatinc.com, bat.bing.com, bat.bing.net, browser.sentry-cdn.com, capi-automation.s3.us-east-2.amazonaws.com, cdn.livechatinc.com, connect.facebook.net, ddwl4m2hdecbv.cloudfront.net, dev-catereasetest.pantheonsite.io, fast.wistia.com, fonts.googleapis.com, fonts.gstatic.com, mv-prod-1-1053047382554.us-central1.run.app, r2.leadsy.ai, region1.analytics.google.com, scripts.clarity.ms, secure.livechatinc.com, stats.g.doubleclick.net, wordpress.livechat.com, www.clarity.ms, www.facebook.com, www.google-analytics.com, www.google.com, www.google.de, www.googletagmanager.com

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-02.

Show the 8 addresses we checked
  1. https://caterease.com/legal/subprocessors – reached, no match (HTTP 200)
  2. https://caterease.com/subprocessors – reached, no match (HTTP 200)
  3. https://caterease.com/sub-processors – reached, no match (HTTP 200)
  4. https://caterease.com/legal/dpa – reached, no match (HTTP 200)
  5. https://caterease.com/dpa – reached, no match (HTTP 200)
  6. https://caterease.com/legal/data-processing-agreement – reached, no match (HTTP 200)
  7. https://caterease.com/trust/subprocessors – reached, no match (HTTP 200)
  8. https://caterease.com/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-02.

Show the 6 addresses we checked
  1. https://caterease.com/security – reached, no match (HTTP 200)
  2. https://caterease.com/trust – reached, no match (HTTP 200)
  3. https://caterease.com/trust-center – reached, no match (HTTP 200)
  4. https://caterease.com/compliance – reached, no match (HTTP 200)
  5. https://caterease.com/legal/security – reached, no match (HTTP 200)
  6. https://trust.caterease.com/ – The name "trust.caterease.com" could not be resolved.

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-02.

Show the 6 addresses we checked
  1. https://caterease.com/legal/sla – reached, no match (HTTP 200)
  2. https://caterease.com/sla – reached, no match (HTTP 200)
  3. https://caterease.com/legal/service-level-agreement – reached, no match (HTTP 200)
  4. https://caterease.com/trust/sla – reached, no match (HTTP 200)
  5. https://caterease.com/uptime – reached, no match (HTTP 200)
  6. https://caterease.com/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-02.

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

Is this wrong? Send us the URL

Published evidence 3
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://caterease.com/privacy-policy/ · checked 2026-09-02

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://caterease.com/pricing/ · checked 2026-09-02

✓

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://caterease.com/privacy-policy/ · checked 2026-09-02

Keep going