Trust Center
The evidence, published before it is asked for.
Pensieve holds no certifications today, and says so in the same place it says everything else. What it publishes instead is the whole argument: how access is decided, what is encrypted and by whom, what happens in an incident, what the contract commits to, and how a hospital leaves. The whitepapers and the document set behind them live in the Trust Center, where a gated document opens on one access request.
Every document listed below is published in the Trust Center at trust.pensievelabs.org, with its version, its publication date and a SHA-256 hash you can verify. The website notices open on this site, and the rest open on the Trust Center.
Start here
- SecurityThe architecture argument in one page: where the authorization decision is made, where the lens is applied, and what your network team is asked to approve.
- ComplianceThe seven regulatory frameworks an Indian hospital is measured against, and the mechanism inside Pensieve that carries each one.
- CTO evaluation guideThe questions worth putting to any vendor of a hospital platform, in the order they matter, with our own answer to each one.
- The full document registerEvery document the Trust Center governs, listed where it is published. Longer than this page, and complete.
The whitepapers
- Pensieve Security WhitepaperTwenty one sections on how the platform is built, hosted, operated and defended, qualified per deployment model throughout. Section 16 records what independent validation exists.
- Pensieve Architecture & Technical OverviewWhat the platform is technically: its layers, its tenancy model, how each hospital’s set-up is held as configuration, how it integrates, and where its limits are.
- Data Protection & Privacy WhitepaperWho is answerable for what under the DPDPA, how consent divides between the hospital and Pensieve, and how a data principal’s rights are routed and answered.
- Deployment Models Explained: DM-1 to DM-4The definitions of the four deployment models, and what each one moves from Pensieve to the hospital. The other documents cite these definitions from here.
- Trust & Assurance Overview: What Pensieve Has, What Is Coming, What It Does Not HaveThe register of what Pensieve holds today, what is in progress with dates and owners, and what it does not hold. Reviewed quarterly and re-dated in public when a target moves.
Security and disclosure
- Security AddendumThe security obligations Pensieve takes on contractually, written as an addendum a hospital’s counsel can attach to the agreement.
- Vulnerability Disclosure Policy and security.txtHow to report a security issue, what happens after you do, and the safe-harbour terms for the person who reports it. It also governs the security.txt file.
- Data Residency StatementWhere data is held per market, and the residency requirements Pensieve does not yet meet, each named.
- Subprocessor RegisterEvery third party in the processing chain, what it does, and where it sits. Removed entries stay listed, and an auditor can trace the list back through every change.
Privacy and patient data
- Privacy PolicyWhat personal data Pensieve holds as a company, on what basis, and for how long. The hospital is the fiduciary for patient data; this is the notice for everything else.
- Data Processing AgreementThe processing terms behind the platform: instructions, sub-processing, breach handling, and what happens to data at the end of the agreement.
- Notice to the Data Principal at the Point of CollectionThe notice a data principal is entitled to at the moment their data is collected, in the form the DPDPA asks for.
- Data Principal Rights Request FormHow a patient or a member of staff exercises a right over their data, who answers, and inside what time.
- Post-Termination Data Retention StatementWhat is retained after an agreement ends, for how long, and how the return and the deletion are evidenced.
The contract, published before you ask
- Platform Terms of ServiceThe terms the platform runs under, published for a procurement team to read before the cycle begins.
- Master Services Agreement: India MasterThe India master agreement, which is the paper most Indian hospitals will actually sign.
- Service Level AgreementThe availability commitment, how it is measured, what is excluded, and what a breach of it is worth.
- Use Case Restrictions and Prohibited UsesWhat Pensieve may not be used for. It is short, it is specific, and it is the boundary a clinical-safety reviewer asks about first.
- Support Policy and Escalation MatrixSeverity definitions, response times, and the escalation path with a named step at each level.
Continuity, exit and product boundaries
- Exit and Data Portability CommitmentHow a hospital leaves: the formats, the timetable, and the commitment that the exit is available for the whole time you are inside.
- Business Failure Continuity PlanWhat happens to a hospital running Pensieve if the company itself fails. Rare to publish, and it is the question a board asks about any vendor.
- Clinical Safety Boundary Statement: Why Pensieve Is Not a Medical DeviceThe clinical-safety boundary, stated as a boundary: what the platform decides, what it never decides, and where a clinician remains the decision.
- Responsible AI PrinciplesThe principles that govern any model in the product, and the disclosure of where one is used at all.
Accessibility and conduct
- Accessibility StatementThe conformance target, the known gaps against it, and how to report something that blocks you.
- Accessibility Conformance Report (VPAT): Template and Evaluation SpecificationThe conformance report itself, in the format a procurement team already knows how to read.
- Human Rights PolicyThe commitments the company holds itself to, including in a sector where software touches people who cannot walk away from it.
- Legal and Law Enforcement Request PolicyWhat Pensieve does when a government or a police force asks for data, who authorises the answer, and when the hospital is told.