SaaS Ranking
Menu

People and HR / Scheduling

Shore

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

Transparency 22/100 FBand F

Rank 12 of 16 in Schedulingcategory median 35checked 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

Shore

shore.com · Scheduling

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 22of 100 Rank 12 of 16

Published commitments2 of 9 found

Measured behaviour1 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

Shore

shore.com · Scheduling

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 22of 100 Rank 12 of 16

Published commitments2 of 9 found

Measured behaviour1 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://shore.com/legal/dpa – reached, no match (HTTP 404)
  2. https://shore.com/dpa – reached, no match (HTTP 404)
  3. https://shore.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://shore.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://shore.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://shore.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://shore.com/trust/dpa – reached, no match (HTTP 404)
  8. https://shore.com/privacy/dpa – reached, no match (HTTP 404)

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://shore.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://shore.com/subprocessors – reached, no match (HTTP 404)
  3. https://shore.com/sub-processors – reached, no match (HTTP 404)
  4. https://shore.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://shore.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://shore.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://shore.com/legal/subprocessor-list – reached, no match (HTTP 404)

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

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

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.shore.com/ – The name "status.shore.com" could not be resolved.
  2. https://shore.com/status – reached, no match (HTTP 404)
  3. https://shore.com.statuspage.io/ – Could not be fetched: fetch failed.

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://shore.com/ – third-party requests before any interaction: api.hubapi.com, api.hubspot.com, api.usercentrics.eu, app.hubspot.com, app.usercentrics.eu, click.prod.mplat-ppcprotect.com, client.prod.mplat-ppcprotect.com, connect.facebook.net, consent-api.service.consent.usercentrics.eu, exceptions.hubspot.com, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.usemessages.com, pagead2.googlesyndication.com, r.clarity.ms, region1.google-analytics.com, scripts.clarity.ms, static.hsappstatic.net, track.hubspot.com, uct.service.usercentrics.eu, www.clarity.ms, www.facebook.com, 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://shore.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://shore.com/subprocessors – reached, no match (HTTP 404)
  3. https://shore.com/sub-processors – reached, no match (HTTP 404)
  4. https://shore.com/legal/dpa – reached, no match (HTTP 404)
  5. https://shore.com/dpa – reached, no match (HTTP 404)
  6. https://shore.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://shore.com/trust/subprocessors – reached, no match (HTTP 404)
  8. https://shore.com/legal/sub-processors – reached, no match (HTTP 404)

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://shore.com/security – reached, no match (HTTP 404)
  2. https://shore.com/trust – reached, no match (HTTP 404)
  3. https://shore.com/trust-center – reached, no match (HTTP 404)
  4. https://shore.com/compliance – reached, no match (HTTP 404)
  5. https://shore.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.shore.com/ – The name "trust.shore.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://shore.com/legal/sla – reached, no match (HTTP 404)
  2. https://shore.com/sla – reached, no match (HTTP 404)
  3. https://shore.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://shore.com/trust/sla – reached, no match (HTTP 404)
  5. https://shore.com/uptime – reached, no match (HTTP 404)
  6. https://shore.com/legal/uptime-sla – reached, no match (HTTP 404)

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://shore.com/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Published evidence 3
✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.shore.com/en/pricing · checked 2026-09-02

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

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

✓

Named privacy contact

weight 1 of 3

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

Source: https://www.shore.com/de/legal/datenschutz · checked 2026-09-02

Keep going