SaaS Ranking

Piggy

piggy.eu · Loyalty and rewards · checked 2026-09-03

35/100EBand E

Rank 9 of 22 in Loyalty and rewards, where the median is 24.5.

We measured 12 of 12 criteria for Piggy on 2026-09-03. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 35 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Piggy

piggy.eu · Loyalty and rewards

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

Published commitments3 of 9 found

Measured behaviour1 of 3 found

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

Gaps, heaviest first

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://piggy.eu/legal/subprocessors – reached, no match (HTTP 404)
  2. https://piggy.eu/subprocessors – reached, no match (HTTP 404)
  3. https://piggy.eu/sub-processors – reached, no match (HTTP 404)
  4. https://piggy.eu/legal/sub-processors – reached, no match (HTTP 404)
  5. https://piggy.eu/trust/subprocessors – reached, no match (HTTP 404)
  6. https://piggy.eu/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://piggy.eu/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-03.

Show the 7 addresses we checked
  1. https://piggy.eu/security – reached, no match (HTTP 404)
  2. https://piggy.eu/trust – reached, no match (HTTP 404)
  3. https://piggy.eu/legal/privacy – reached, no match (HTTP 404)
  4. https://piggy.eu/privacy – reached, no match (HTTP 404)
  5. https://piggy.eu/privacy-policy – reached, no match (HTTP 200)
  6. https://piggy.eu/compliance – reached, no match (HTTP 404)
  7. https://piggy.eu/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-03.

Show the 3 addresses we checked
  1. https://status.piggy.eu/ – reached, no match (HTTP 200)
  2. https://piggy.eu/status – reached, no match (HTTP 404)
  3. https://piggy.eu.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-03.

Show the 1 address we checked
  1. https://piggy.eu/ – third-party requests before any interaction: ad.doubleclick.net, connect.facebook.net, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hsforms.net, js.hubspot.com, js.usemessages.com, region1.analytics.google.com, snap.licdn.com, static.piggy.nl, stats.g.doubleclick.net, www.datocms-assets.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-03.

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

Show the 6 addresses we checked
  1. https://piggy.eu/security – reached, no match (HTTP 404)
  2. https://piggy.eu/trust – reached, no match (HTTP 404)
  3. https://piggy.eu/trust-center – reached, no match (HTTP 404)
  4. https://piggy.eu/compliance – reached, no match (HTTP 404)
  5. https://piggy.eu/legal/security – reached, no match (HTTP 404)
  6. https://trust.piggy.eu/ – The name "trust.piggy.eu" 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-03.

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

Show the 1 address we checked
  1. https://piggy.eu/.well-known/security.txt – reached, no match (HTTP 404)

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 4

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.piggy.eu/legal/general-terms-and-conditions · checked 2026-09-03

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.piggy.eu/pricing · checked 2026-09-03

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://piggy.eu/ · checked 2026-09-03

Named privacy contact

weight 1 of 3

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

Source: https://www.piggy.eu/legal/privacy-policy · checked 2026-09-03

History

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

Compare