Heroku security and compliance
Every line below says what we found and when we looked. A missing certification means we did not find evidence of it - never that the vendor does not have it.
At a glance
Security and compliance
4 documented attributes| Security and compliance | Value | State and source |
|---|---|---|
| HIPAA compliance stated | Yes | Verified64% confidenceEvidenceExcerpt ...he community. Security and Compliance Heroku regularly performs audits and maintains PCI, HIPAA, ISO, and SOC compliance – We are the simplest path to delivering engaging apps that meet... Excerpt kindrunning text Subject named in excerptyes Sourcehttps://www.heroku.com/ · Primary documentation · retrieved 3 times from 2026-09-02 to 2026-10-03 · every date Sourcehttps://www.heroku.com/compliance/ · Primary documentation · retrieved 2 times from 2026-09-02 to 2026-10-03 · every date Confidence64% - capped at the measured precision of this reader (64%) HistoryStatement history How it was read Read bytext pattern muster:\bHIPAA\bFirst observed2026-09-02 Last checked2026-10-03 Human reviewnot documented Source confidence90% Reader precision64% (measured by hand for this reader) Excerpt-kind precision85% (measured by hand over 417 statements of this kind) Confidence interpretationA heuristic informed by source assessment and reader samples, not a calibrated probability that this individual claim is correct. |
| ISO/IEC 27001 | Yes | Verified69% confidence Read from a menu, footer or link list, not from a sentence about the product EvidenceExcerpt ...ope of certifications PCI DSS Level 1 Service Provider HIPAA Protected Health Information ISO 27001, 27017, 27018 Security Management Controls, Cloud Specific Controls, Personal Data Protec... Excerpt kindnavigation entry (a menu, footer or link list, not a sentence about the product) Subject named in excerptno Sourcehttps://www.heroku.com/compliance/ · Primary documentation · retrieved 2 times from 2026-09-02 to 2026-10-03 · every date Confidence69% - capped at the measured precision of this kind of excerpt (69%, navigation), which is below the reader's own precision (87%) HistoryStatement history How it was read Read bytext pattern muster:(?<!(?:align|commit|working towards|pursu|accordance|based on|in line with|framework)[^.?!]{0,60})ISO[\s/]*(IEC[\s/]*)?27001(?![^.?!]{0,60}(?:in progress|underway|pursu|working towards|planned|road ?map|commitment|aligned|alignment|framework))First observed2026-09-02 Last checked2026-10-03 Human reviewnot documented Source confidence90% Reader precision87% (measured by hand for this reader) Excerpt-kind precision69% (measured by hand over 422 statements of this kind) Confidence interpretationA heuristic informed by source assessment and reader samples, not a calibrated probability that this individual claim is correct. |
| PCI DSS stated | Yes | Verified69% confidenceEvidenceExcerpt ...nd SOC compliance to further strengthen our trust with customers. Scope of certifications PCI DSS Level 1 Service Provider HIPAA Protected Health Information ISO 27001, 27017, 27018 Secur... Excerpt kindrunning text Subject named in excerptno Sourcehttps://www.heroku.com/compliance/ · Primary documentation · retrieved 2 times from 2026-09-02 to 2026-10-03 · every date Confidence69% - capped at the measured precision of this reader (69%) HistoryStatement history How it was read Read bytext pattern muster:\bPCI[\s-]?DSS\bFirst observed2026-09-02 Last checked2026-10-03 Human reviewnot documented Source confidence90% Reader precision69% (measured by hand for this reader) Excerpt-kind precision79% (measured by hand over 857 statements of this kind) Confidence interpretationA heuristic informed by source assessment and reader samples, not a calibrated probability that this individual claim is correct. |
| SOC 2 Type II | Yes | Verified85% confidenceEvidenceExcerpt ...data processed by the Heroku Platform relevant for the financial reporting of customers. SOC2 Type 2 Security, Availability & Confidentiality Reports The restricted to use SOC2 Type 2 report... Excerpt kindrunning text Subject named in excerptyes Sourcehttps://www.heroku.com/compliance/ · Primary documentation · retrieved 2 times from 2026-09-02 to 2026-10-03 · every date Confidence85% - capped at the measured precision of this kind of excerpt (85%, prose), which is below the reader's own precision (87%) HistoryStatement history How it was read Read bytext pattern muster:SOC\s*2\s*(Type\s*)?(II|2)\bFirst observed2026-09-02 Last checked2026-10-03 Human reviewnot documented Source confidence90% Reader precision87% (measured by hand for this reader) Excerpt-kind precision85% (measured by hand over 417 statements of this kind) Confidence interpretationA heuristic informed by source assessment and reader samples, not a calibrated probability that this individual claim is correct. |
Evidence
Every documented value links to the page we read it from, with the source tier and the day we retrieved it, in its row under Security and compliance. “Evidence” in that row opens the excerpt.
Not found yet (5)
These attributes are open in our research. We looked and found no reliable evidence; 34 addresses were checked and are listed below. That is a statement about our research and never about the product.
| Attribute | State | What we checked |
|---|---|---|
| Audit log | Not yet verified | Checked 3 addresses (10 reads), most recently on 2026-10-03: www.heroku.com, www.heroku.com/compliance, www.heroku.com/pricing |
| Data processing agreement offered | Not yet verified | Checked 2 addresses (5 reads), most recently on 2026-10-03: www.heroku.com, www.heroku.com/compliance |
| EU data residency stated | Not yet verified | Checked 3 addresses (9 reads), most recently on 2026-10-03: www.heroku.com, www.heroku.com/compliance, www.heroku.com/pricing |
| FedRAMP authorisation | Not yet verified | Checked 2 addresses (5 reads), most recently on 2026-10-03: www.heroku.com, www.heroku.com/compliance |
| GDPR compliance stated | Not yet verified | Checked 2 addresses (5 reads), most recently on 2026-10-03: www.heroku.com, www.heroku.com/compliance |
An open attribute describes our research and never the product.
Before you decide
Is Heroku suitable for your data?
The documented statements above do not settle suitability for your use. Match the evidence to your proposed plan, data and configuration, then resolve the requirements that remain open.
Check the scope
Does the source cover the exact service, region and plan you would buy? Review the document date and any exceptions.
Test your access
Try the roles, guest sharing and access removal your workflow needs. Record the result and the conditions of the test.
Own the follow-up
Give every unresolved question an owner. Request the relevant evidence before treating it as a passed or failed requirement.