Security and compliance / API security
Salt Security
What Salt Security publishes on salt.security, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.
Transparency 35/100 EBand E
Rank 3 of 12 in API securitycategory median 24checked 2026-09-02
8 gaps found: 8 criteria not found at the addresses we checked. 4 found8 not found0 not measured
Public transparency score, not a product or security rating.
Transparency labelsaas-ranking.com
Salt Security
- A
- B
- C
- D
- E
- F
Published commitments3 of 9 found
- not foundData processing agreement×3
- foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- not foundPublic pricing×2
- foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
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
Salt Security
- A
- B
- C
- D
- E
- F
Published commitments3 of 9 found
- not foundData processing agreement×3
- foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- not foundPublic pricing×2
- foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
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 3No data processing agreement found.
Checked 8 addresses on 2026-09-02.
Show the 8 addresses we checked
https://salt.security/legal/dpa– reached, no match (HTTP 404)https://salt.security/dpa– reached, no match (HTTP 404)https://salt.security/legal/data-processing-agreement– reached, no match (HTTP 404)https://salt.security/data-processing-agreement– reached, no match (HTTP 404)https://salt.security/legal/data-processing-addendum– reached, no match (HTTP 404)https://salt.security/legal/gdpr– reached, no match (HTTP 404)https://salt.security/trust/dpa– reached, no match (HTTP 404)https://salt.security/privacy/dpa– reached, no match (HTTP 404)
Data location stated
weight 3 of 3We found this behind a sign-in, so it is not published openly.
Seen at https://salt.security/privacy-policy · checked 2026-09-02
Show the 7 addresses we checked
https://salt.security/security– reached, no match (HTTP 404)https://salt.security/trust– reached, no match (HTTP 404)https://salt.security/legal/privacy– reached, no match (HTTP 404)https://salt.security/privacy– reached, no match (HTTP 404)https://salt.security/privacy-policy– found, but behind a sign-inhttps://salt.security/compliance– reached, no match (HTTP 404)https://salt.security/legal/privacy-policy– reached, no match (HTTP 404)
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-02.
Show the 3 addresses we checked
https://status.salt.security/– The name "status.salt.security" could not be resolved.https://salt.security/status– reached, no match (HTTP 404)https://salt.security.statuspage.io/– Could not be fetched: fetch failed.
Public pricing
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-02.
Show the 5 addresses we checked
https://salt.security/pricing– reached, no match (HTTP 404)https://salt.security/pricing/– reached, no match (HTTP 404)https://salt.security/plans– reached, no match (HTTP 404)https://salt.security/en/pricing– reached, no match (HTTP 404)https://salt.security/pricing-plans– reached, no match (HTTP 404)
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-02.
Show the 1 address we checked
https://salt.security/– third-party requests before any interaction: alb.reddit.com, cdn.cookielaw.org, cdn.jsdelivr.net, cdn.neverbounce.com, cdn.prod.website-files.com, connect.facebook.net, d3e54v103j8qbb.cloudfront.net, geolocation.onetrust.com, pagead2.googlesyndication.com, www.facebook.com, www.googleadservices.com, www.googletagmanager.com, www.gstatic.com, www.redditstatic.com, zzontar2hsjaawcn.public.blob.vercel-storage.com
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-02.
Show the 6 addresses we checked
https://salt.security/security– reached, no match (HTTP 404)https://salt.security/trust– reached, no match (HTTP 404)https://salt.security/trust-center– reached, no match (HTTP 404)https://salt.security/compliance– reached, no match (HTTP 404)https://salt.security/legal/security– reached, no match (HTTP 404)https://trust.salt.security/– reached, no match (HTTP 200)
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-02.
Show the 6 addresses we checked
https://salt.security/legal/sla– reached, no match (HTTP 404)https://salt.security/sla– reached, no match (HTTP 404)https://salt.security/legal/service-level-agreement– reached, no match (HTTP 404)https://salt.security/trust/sla– reached, no match (HTTP 404)https://salt.security/uptime– reached, no match (HTTP 404)https://salt.security/legal/uptime-sla– reached, no match (HTTP 404)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-02.
Show the 1 address we checked
https://salt.security/.well-known/security.txt– reached, no match (HTTP 404)
Published evidence 4
Subprocessor list
weight 3 of 3The actual list is published, not just a promise to keep one.
Source: https://salt.security/subprocessors · checked 2026-09-02
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://salt.security/ · checked 2026-09-02
Notice before subprocessors change
weight 2 of 3The vendor commits publicly to giving notice before the list changes.
Source: https://salt.security/subprocessors · checked 2026-09-02
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://salt.security/privacy-policy · checked 2026-09-02