Skip to main content
Pensieve Labs

Search the register

Search all 586 artefacts by title, document ID or content.

Unlock NDA tier

Register

Sub-processors

Two lists, deliberately separated. The first is every party that can process a hospital’s Customer Data. The second is every party that serves this Trust Center and touches no clinical data at all. Vercel, Neon and Resend run this website, not your hospital. Publishing them together in one column would let a reviewer assume the mail provider sees patient records. It does not.

Group 1: 1 listed

Platform sub-processors: these can process Customer Data

Each of these processes Customer Data as defined in DPA-GL-001, in the deployment models marked. Adding one, replacing one, or moving one to a different country is a change notified 30 days in advance with a right to object.

Sub-processorPurposeData categoriesLocationApplies toStatusAdded
Google Cloud Platformcloud.google.comPrimary platform hosting: Cloud Run, Cloud SQL, Cloud Storage, Cloud KMSAll Customer Data, in the region selected for the deploymentasia-south1 (Mumbai) by default; region selectableIN1234active31 July 2026

Group 2: 3 listed

Trust Center sub-processors: no Customer Data, ever

These serve trust.pensievelabs.org, the site you are reading. They hold visitor records, access requests, NDA acceptances, document instances and the addresses this Trust Center mails. They hold no patient record, no clinical document and no hospital operational data, in any deployment model. Most vendors do not publish their own trust center’s supply chain; a trust center that hides its own is not one.

Sub-processorPurposeData categoriesLocationApplies toStatusAdded
Neon Inc.neon.techManaged Postgres for the Trust Center application onlyTrust Center visitor, access and document-instance dataAWS ap-south-1 (Mumbai)IN1234active31 July 2026
Resend Inc.resend.comTransactional email: access decisions, nudges, invoices, bulletinsName and email address of recipientsUnited StatesUS1234active31 July 2026
Vercel Inc.vercel.comHosting for the Trust Center application only. No Customer clinical data.Trust Center visitor and workspace dataGlobal edge; functions pinned to MumbaiUS1234active31 July 2026

The commitment

Thirty days’ notice, and a right to object

The mechanism is published rather than negotiated, in POL-GL-055, and the notice instrument is NTC-GL-001. A notice that does not state the objection deadline is not a valid notice, and the period runs again from a corrected one.

ChangeNoticeObjection window
Adding a sub-processor that will process personal data30 days, before15 days
Replacing a sub-processor30 days, before15 days
Materially extending what an existing sub-processor does30 days, before15 days
Moving processing to a different country30 days, before15 days, and see DIS-GL-008
Emergency replacement to preserve security or availabilityImmediate, notice within 3 business days15 days from that notice

Silence for fifteen days is acceptance. An objection is answered by the person who made the decision, within five business days, and most objections end there because most are questions. Where no alternative can be offered within thirty days, the customer may terminate the affected service. That is the sole remedy, and it is stated here rather than discovered later.

DM-3 and DM-4

On your own infrastructure, this list is shorter, and it is yours

ModelWho owns the infrastructurePensieve cloud sub-processors involved
DM-1, DM-2Edsol Edtech Pvt. Ltd.The platform group above, in full
DM-3The hospital owns and pays for the cloud projectNone. The cloud provider is the hospital’s own supplier, contracted directly by the hospital
DM-4The hospital owns the hardware and the roomNone. There is no cloud provider at all

Stated plainly so nobody has to work it out: a hospital on DM-3 or DM-4 has zero Pensieve cloud sub-processors in its data path. The register above still matters to it, because this Trust Center still holds its access records and its executed documents, but its patients’ records never leave infrastructure it owns.

Sources

The documents behind this page

This page is a rendering of the register, not a second copy of it. Where this page and a document disagree, the document governs.

DIS-GL-009DisclosureGL1234NDACritical pathReview due29 August 2026

Accept the mutual NDA to request access to this tier. Your acceptance is recorded at once and protects both sides; an administrator then grants access, with a target of four business hours.Accept the mutual NDAWait: four business hours (target)

DIS-GL-010DisclosureGL1234NDAReview due31 July 2026

Accept the mutual NDA to request access to this tier. Your acceptance is recorded at once and protects both sides; an administrator then grants access, with a target of four business hours.Accept the mutual NDAWait: four business hours (target)

NTC-GL-001NoticeGL1234NDA31 July 2026

Accept the mutual NDA to request access to this tier. Your acceptance is recorded at once and protects both sides; an administrator then grants access, with a target of four business hours.Accept the mutual NDAWait: four business hours (target)

POL-GL-055PolicyGL1234NDACritical path20 August 2026

Accept the mutual NDA to request access to this tier. Your acceptance is recorded at once and protects both sides; an administrator then grants access, with a target of four business hours.Accept the mutual NDAWait: four business hours (target)

POL-GL-135PolicyGL1234NDACritical pathReview due29 August 2026

Accept the mutual NDA to request access to this tier. Your acceptance is recorded at once and protects both sides; an administrator then grants access, with a target of four business hours.Accept the mutual NDAWait: four business hours (target)

ADD-GL-022ContractIN1234NDACritical path01 August 2026

Accept the mutual NDA to request access to this tier. Your acceptance is recorded at once and protects both sides; an administrator then grants access, with a target of four business hours.Accept the mutual NDAWait: four business hours (target)