Privacy Bee
privacybee.com · Privacy compliance · checked 2026-09-05
Rank 9 of 35 in Privacy compliance, where the median is 26.
- 6 found
- 6 not found
- 0 not measured
We measured 12 of 12 criteria for Privacy Bee on 2026-09-05. We found 6 with a source and did not find 6 at the addresses we checked. That is a transparency score of 48 out of 100, band D.
Overview
Transparency labelsaas-ranking.com
Privacy Bee
- 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
- foundPublic pricing×2
- not foundNotice before subprocessors change×2
- foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour3 of 3 found
Checked 2026-09-05. 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 Privacy Bee has no such document.
What they state
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.
- Named on that page ISO/IEC 27001 (unclear from the sentence), SOC 2 (unclear from the sentence), SOC 2 Type II (unclear from the sentence).
Show the 3 exact wordings
ernet.” Gerald from Washington, DC Certified and audited Privacy Bee is SOC 2 Type II certified and ISO 27001 compliant.
Read at https://privacybee.com/trust/g Privacy Manifesto Help Desk / FAQ Opens in a new tab Sign In Opens in a new tab Get Started AICPA SOC2 Certified Opens in a new tab Opens in a new tab Opens in a new tab Opens in a new tab Global He...
Read at https://privacybee.com/trust/y personal data from the internet.” Gerald from Washington, DC Certified and audited Privacy Bee is SOC 2 Type II certified and ISO 27001 compliant.
Read at https://privacybee.com/trust/ - Infrastructure providers named on that list Amazon Web Services, Cloudflare, HubSpot, SendGrid, Twilio.
Show the 5 exact wordings
Amazon Web Services
Read at https://privacybee.com/subprocessors/Cloudflare
Read at https://privacybee.com/subprocessors/HubSpot
Read at https://privacybee.com/subprocessors/SendGrid
Read at https://privacybee.com/subprocessors/Twilio
Read at https://privacybee.com/subprocessors/ - HSTS max-age 15552000 seconds (180 days).
Show the exact wording
max-age=15552000; includeSubDomains
Read at https://privacybee.com/ - HSTS options includeSubDomains.
Show the exact wording
max-age=15552000; includeSubDomains
Read at https://privacybee.com/ - The file expires 2027-06-03. It was still valid when we checked on 2026-09-05.
Show the exact wording
Expires: 2027-06-03T00:00:00.000Z
Read at https://privacybee.com/.well-known/security.txt
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-05.
Show the 8 addresses we checked
https://privacybee.com/legal/dpa– reached, no match (HTTP 404)https://privacybee.com/dpa– reached, no match (HTTP 404)https://privacybee.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://privacybee.com/data-processing-agreement– reached, no match (HTTP 404)https://privacybee.com/legal/data-processing-addendum– reached, no match (HTTP 404)https://privacybee.com/legal/gdpr– reached, no match (HTTP 404)https://privacybee.com/trust/dpa– reached, no match (HTTP 404)https://privacybee.com/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://privacybee.com/privacy-policy/ · checked 2026-09-05
Show the 7 addresses we checked
https://privacybee.com/security– reached, no match (HTTP 404)https://privacybee.com/trust– reached, no match (HTTP 200)https://privacybee.com/legal/privacy– reached, no match (HTTP 404)https://privacybee.com/privacy– reached, no match (HTTP 404)https://privacybee.com/privacy-policy– found, but behind a sign-inhttps://privacybee.com/compliance– reached, no match (HTTP 404)https://privacybee.com/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-05.
Show the 3 addresses we checked
https://status.privacybee.com/– reached, no match (HTTP 200)https://privacybee.com/status– reached, no match (HTTP 404)https://privacybee.com.statuspage.io/– Could not be fetched: fetch failed.
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-05.
Show the 8 addresses we checked
https://privacybee.com/legal/subprocessors– reached, no match (HTTP 404)https://privacybee.com/subprocessors– reached, no match (HTTP 200)https://privacybee.com/sub-processors– reached, no match (HTTP 404)https://privacybee.com/legal/dpa– reached, no match (HTTP 404)https://privacybee.com/dpa– reached, no match (HTTP 404)https://privacybee.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://privacybee.com/trust/subprocessors– reached, no match (HTTP 404)https://privacybee.com/legal/sub-processors– reached, no match (HTTP 404)
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-05.
Show the 6 addresses we checked
https://privacybee.com/legal/sla– reached, no match (HTTP 404)https://privacybee.com/sla– reached, no match (HTTP 404)https://privacybee.com/legal/service-level-agreement– reached, no match (HTTP 404)https://privacybee.com/trust/sla– reached, no match (HTTP 404)https://privacybee.com/uptime– reached, no match (HTTP 404)https://privacybee.com/legal/uptime-sla– reached, no match (HTTP 404)
Named privacy contact
weight 1 of 3We found this behind a sign-in, so it is not published openly.
Seen at https://privacybee.com/privacy-policy/ · checked 2026-09-05
Show the 7 addresses we checked
https://privacybee.com/legal/privacy– reached, no match (HTTP 404)https://privacybee.com/privacy– reached, no match (HTTP 404)https://privacybee.com/privacy-policy– found, but behind a sign-inhttps://privacybee.com/legal/privacy-policy– reached, no match (HTTP 404)https://privacybee.com/legal/privacy-notice– reached, no match (HTTP 404)https://privacybee.com/trust/privacy– reached, no match (HTTP 404)https://privacybee.com/datenschutz– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 6
Subprocessor list
weight 3 of 3The actual list is published, not just a promise to keep one.
- Infrastructure providers named on that list Amazon Web Services, Cloudflare, HubSpot, SendGrid, Twilio.
Show the 5 exact wordings
Amazon Web Services
Read at https://privacybee.com/subprocessors/Cloudflare
Read at https://privacybee.com/subprocessors/HubSpot
Read at https://privacybee.com/subprocessors/SendGrid
Read at https://privacybee.com/subprocessors/Twilio
Read at https://privacybee.com/subprocessors/
Source: https://privacybee.com/subprocessors/ · checked 2026-09-05
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://privacybee.com/pricing/ · checked 2026-09-05
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
- HSTS max-age 15552000 seconds (180 days).
Show the exact wording
max-age=15552000; includeSubDomains
Read at https://privacybee.com/ - HSTS options includeSubDomains.
Show the exact wording
max-age=15552000; includeSubDomains
Read at https://privacybee.com/
Source: https://privacybee.com/ · checked 2026-09-05
No third-party tracking before consent
weight 2 of 3No third-party requests before any interaction.
Source: https://privacybee.com/ · checked 2026-09-05
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
- Named on that page ISO/IEC 27001 (unclear from the sentence), SOC 2 (unclear from the sentence), SOC 2 Type II (unclear from the sentence).
Show the 3 exact wordings
ernet.” Gerald from Washington, DC Certified and audited Privacy Bee is SOC 2 Type II certified and ISO 27001 compliant.
Read at https://privacybee.com/trust/g Privacy Manifesto Help Desk / FAQ Opens in a new tab Sign In Opens in a new tab Get Started AICPA SOC2 Certified Opens in a new tab Opens in a new tab Opens in a new tab Opens in a new tab Global He...
Read at https://privacybee.com/trust/y personal data from the internet.” Gerald from Washington, DC Certified and audited Privacy Bee is SOC 2 Type II certified and ISO 27001 compliant.
Read at https://privacybee.com/trust/
Source: https://privacybee.com/trust/ · checked 2026-09-05
security.txt (RFC 9116)
weight 1 of 3Served at /.well-known/security.txt.
- The file expires 2027-06-03. It was still valid when we checked on 2026-09-05.
Show the exact wording
Expires: 2027-06-03T00:00:00.000Z
Read at https://privacybee.com/.well-known/security.txt
Source: https://privacybee.com/.well-known/security.txt · checked 2026-09-05
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.