SaaS Ranking
Menu

Sweet Security: what they publish

sweet.security · Container and cloud workload security · checked 2026-10-14

13/100FBand F

Rank 17 of 26 in Container and cloud workload security, where the median is 22.

Public transparency score, not a product or security rating. Latest check: 2026-10-14. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

5 days since the newest dated result, 5 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

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

Sweet Security

sweet.security · Container and cloud workload security

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

Published commitments1 of 9 found

Measured behaviour1 of 3 found

Checked 2026-10-14. 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.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

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

Where Sweet Security sits in Container and cloud workload security

  1. A0 0%
  2. B0 0%
  3. C0 0%
  4. D4 15%
  5. E7 27%
  6. F15 58%
26 vendors with a score; 2 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Sweet Security 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.

What Sweet Security states

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-10-14.

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

Across the market: Data processing agreement in Container and cloud workload security: 3 of 26 companies

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-14.

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

Across the market: Subprocessor list in Container and cloud workload security: 2 of 26 companies

✗

Data location: where they say data is hosted

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-10-14.

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

Across the market: Data location stated in Container and cloud workload security: 9 of 26 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-14.

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

Across the market: Status page with history in Container and cloud workload security: 4 of 27 companies

✗

Public pricing with figures

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-10-14.

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

Across the market: Public pricing in Container and cloud workload security: 6 of 26 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-10-14.

Show the 1 address we checked
  1. https://sweet.security/ – third-party requests before any interaction: 39802835.fs1.hubspotusercontent-na1.net, cdn.prod.website-files.com, challenges.cloudflare.com, d3e54v103j8qbb.cloudfront.net

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Container and cloud workload security: 2 of 28 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-10-14.

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

Across the market: Notice before subprocessors change in Container and cloud workload security: 2 of 26 companies

✗

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-10-14.

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

Across the market: Certifications named in Container and cloud workload security: 8 of 27 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-14.

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

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Container and cloud workload security: 2 of 26 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-10-14.

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

Across the market: security.txt (RFC 9116) in Container and cloud workload security: 2 of 26 companies

Evidence

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

Published, with a source 2
✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000; includeSubDomains; preload

    Read at https://sweet.security/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://sweet.security/

    max-age=31536000; includeSubDomains; preload

    Read at https://sweet.security/

Source: https://sweet.security/ · checked 2026-10-14

Across the market: HTTPS enforced with HSTS in Container and cloud workload security: 22 of 28 companies

✓

Named privacy contact (DPO or privacy address)

weight 1 of 3

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

Source: https://www.sweet.security/ · checked 2026-10-14

Across the market: Named privacy contact in Container and cloud workload security: 10 of 26 companies

History

100 0 2026-10-07: 13 of 1002026-10-14: 13 of 100 2026-10-07 2026-10-14
Score over the last 2 runs we measured Sweet Security in: 13 (2026-10-07), 13 (2026-10-14).

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Sweet Security

2 found · 10 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-14.

Investigate 10 open evidence questions
  1. Data processing agreement

    Please share the current data processing agreement for the product and plan we are considering, including its annexes and signing process.

    Inspect this check
  2. Subprocessor list

    Which subprocessors apply to our product, what does each process, and in which countries? Please share the current list.

    Inspect this check
  3. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  4. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  5. Public pricing

    Please confirm the total cost for our seats and usage, including minimum commitments, add-ons, overages and renewal terms.

    Inspect this check
  6. Certifications named

    Please share the current certificate or audit report and its scope, covered legal entity, products and validity period.

    Inspect this check
  7. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  8. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  9. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check
  10. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check

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.