SaaS Ranking
Menu

Shoreline: what they publish

shoreline.io · Incident management · checked 2026-09-27

0/100FBand F

Rank 33 of 34 in Incident management, where the median is 30.

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

Jump to a criterion 12

Overview

3 days since the newest finding, 3 since the oldest. 12 of 12 criteria measured in the last 30 days.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Shoreline

shoreline.io · Incident management

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 0of 100 Rank 33 of 34

Published commitments0 of 9 found

Measured behaviour0 of 2 found, 1 not measured

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

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

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 Shoreline has no such document.

Where Shoreline sits in Incident management

  1. A0 0%
  2. B1 3%
  3. C4 12%
  4. D6 18%
  5. E13 38%
  6. F10 29%
34 vendors with a score. Bands have fixed thresholds, see how the score works.

The band of Shoreline is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

Gaps, heaviest first

✗

Data processing agreement (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-27.

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

Is this wrong? Send us the URL

Across the market: Data processing agreement in Incident management: 5 of 34 companies

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-27.

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

Is this wrong? Send us the URL

Across the market: Subprocessor list in Incident management: 8 of 34 companies

✗

Data location: where they say data is hosted

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-27.

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

Is this wrong? Send us the URL

Across the market: Data location stated in Incident management: 13 of 34 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-27.

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

Is this wrong? Send us the URL

Across the market: Status page with history in Incident management: 9 of 31 companies

✗

Public pricing with figures

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-27.

Show the 5 addresses we checked
  1. https://shoreline.io/pricing – browser: The name "shoreline.io" could not be resolved.
  2. https://shoreline.io/pricing/ – reached, no match (HTTP 200)
  3. https://shoreline.io/plans – reached, no match (HTTP 200)
  4. https://shoreline.io/en/pricing – reached, no match (HTTP 200)
  5. https://shoreline.io/pricing-plans – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Across the market: Public pricing in Incident management: 25 of 34 companies

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-27.

Show the 2 addresses we checked
  1. http://shoreline.io/ – redirects to https://www.nvidia.com/en-us/
  2. https://shoreline.io/ – no HSTS header

Is this wrong? Send us the URL

Across the market: HTTPS enforced with HSTS in Incident management: 24 of 34 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-27.

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

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Incident management: 7 of 34 companies

✗

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-27.

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

Is this wrong? Send us the URL

Across the market: Certifications named in Incident management: 17 of 34 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-27.

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

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Incident management: 2 of 34 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-27.

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

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Incident management: 4 of 33 companies

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-27.

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

Is this wrong? Send us the URL

Across the market: Named privacy contact in Incident management: 9 of 34 companies

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Not measured by us 1
–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://shoreline.io/ – page.goto: net::ERR_NAME_NOT_RESOLVED at https://shoreline.io/ Call log: - navigating to "https://shoreline.io/", waiting until "domcontentloaded"

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Incident management: 3 of 32 companies

History

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

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.