SaaS Ranking
Menu

Security and compliance / Container and cloud workload security

Sweet Security

What Sweet Security publishes on sweet.security, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Transparency 17/100 FBand F

Rank 5 of 8 in Container and cloud workload securitycategory median 19.5checked 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

Sweet Security

sweet.security · Container and cloud workload security

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

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

Sweet Security

sweet.security · Container and cloud workload security

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

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://sweet.security/legal/dpa – reached, no match (HTTP 200)
  2. https://sweet.security/dpa – reached, no match (HTTP 200)
  3. https://sweet.security/legal/data-processing-agreement – reached, no match (HTTP 200)
  4. https://sweet.security/data-processing-agreement – reached, no match (HTTP 200)
  5. https://sweet.security/legal/data-processing-addendum – reached, no match (HTTP 200)
  6. https://sweet.security/legal/gdpr – reached, no match (HTTP 200)
  7. https://sweet.security/trust/dpa – reached, no match (HTTP 200)
  8. https://sweet.security/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://sweet.security/legal/subprocessors – reached, no match (HTTP 200)
  2. https://sweet.security/subprocessors – reached, no match (HTTP 200)
  3. https://sweet.security/sub-processors – reached, no match (HTTP 200)
  4. https://sweet.security/legal/sub-processors – reached, no match (HTTP 200)
  5. https://sweet.security/trust/subprocessors – reached, no match (HTTP 200)
  6. https://sweet.security/privacy/subprocessors – reached, no match (HTTP 200)
  7. https://sweet.security/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-02.

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

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

Show the 5 addresses we checked
  1. https://sweet.security/pricing – reached and rendered, no match
  2. https://sweet.security/pricing/ – reached, no match (HTTP 200)
  3. https://sweet.security/plans – reached, no match (HTTP 200)
  4. https://sweet.security/en/pricing – reached, no match (HTTP 200)
  5. https://sweet.security/pricing-plans – reached, no match (HTTP 200)

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://sweet.security/ – third-party requests before any interaction: 39802835.fs1.hubspotusercontent-na1.net, accounts.finsweet.com, ad.doubleclick.net, alb.reddit.com, api.claydar.com, cdn.claydar.com, cdn.jsdelivr.net, cdn.prod.website-files.com, collector-54933.us.tvsquared.com, connect.facebook.net, d3e54v103j8qbb.cloudfront.net, fonts.googleapis.com, fonts.gstatic.com, hubspotonwebflow.com, js.adsrvr.org, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hscollectedforms.net, pixel-config.reddit.com, region1.analytics.google.com, static.claydar.com, stats.g.doubleclick.net, us-assets.i.posthog.com, www.google.com, www.google.de, www.googletagmanager.com, www.redditstatic.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://sweet.security/legal/subprocessors – reached, no match (HTTP 200)
  2. https://sweet.security/subprocessors – reached, no match (HTTP 200)
  3. https://sweet.security/sub-processors – reached, no match (HTTP 200)
  4. https://sweet.security/legal/dpa – reached, no match (HTTP 200)
  5. https://sweet.security/dpa – reached, no match (HTTP 200)
  6. https://sweet.security/legal/data-processing-agreement – reached, no match (HTTP 200)
  7. https://sweet.security/trust/subprocessors – reached, no match (HTTP 200)
  8. https://sweet.security/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://sweet.security/security – reached, no match (HTTP 200)
  2. https://sweet.security/trust – reached, no match (HTTP 200)
  3. https://sweet.security/trust-center – reached, no match (HTTP 200)
  4. https://sweet.security/compliance – reached, no match (HTTP 200)
  5. https://sweet.security/legal/security – reached, no match (HTTP 200)
  6. https://trust.sweet.security/ – 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://sweet.security/.well-known/security.txt – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Published evidence 3
✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://sweet.security/ · checked 2026-09-02

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

Source: https://www.sweet.security/ · 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.sweet.security/ · checked 2026-09-02

Keep going