Skip to content

Human rights

What we will and will not do with a record about a person.

Pensieve holds medical records. The question therefore comes down to particulars: which reads are possible, who is permitted to make them, and what is written down when they happen. Each commitment below is followed by the place in the software where it is enforced.

The premise

A medical record is not our asset.

A medical record is a description of a person’s body, written down by people that person had to trust. It is held by the hospital that wrote it, and it is about the patient it describes. Neither of those is us.

The legal shape says the same thing. Under India’s DPDPA the hospital is the Data Fiduciary and Pensieve is the Data Processor, and the Data Processing Addendum binds us to process personal data only on that hospital’s documented instructions, except where the law requires otherwise.

The data model says it as well. Consent in Pensieve runs on two planes: the patient owns the data, and a hospital’s access is a gate that opens on admission and closes when that basis ends. Ownership is not a sentiment expressed on a page like this one. It is one of the two planes an access decision is computed from.

We hold the record. We do not own it, and nothing in the software is built as though we did.

Our commitments

Six commitments, and where each one is enforced.

A commitment is worth reading only if breaking it would be visible. Each of these is tied to a mechanism in the platform, a published document, or a log the institution reads for itself.

01

No secondary use.

We process a hospital’s records only on that hospital’s documented instructions, except where the law requires otherwise. There is no second product assembled on the side out of what those records contain. Access is scoped to a purpose by the authorization check on every read and every write. The system decides whether that purpose holds, at the moment of access.

Enforced in the Data Processing Addendum and Cirith authorization.

02

We sell no record, in any form, ever.

Our privacy policy states plainly that we do not sell personal data, and there is no arrangement under which a record reaches an insurer, an employer, an advertiser, or a broker. Every third party that processes data on our behalf is named in a published list, with what it does. The list is checkable, which means a change to it is visible.

Enforced in the Privacy Policy and the subprocessor list.

03

We do not train models on identifiable records.

Pensieve is a record system. Where a statistical model is used, we name it, the single task it is bounded to, and the audit trail its output is written to. This commitment stands on our contracts and on how we run the company. The two below it are enforced by the architecture.

Enforced in the Data Processing Addendum, and argued in full on Not AI: the record comes first.

04

Data minimisation by default.

Consent is a first-class data object the authorization system reads on every access, over the two-plane model set out above. Every grant and every withdrawal is audited. An auditor can later read the exact scope each access ran under.

Enforced in two-plane consent and visible to the person it is about in the patient app.

05

The patient lens is an architectural constraint.

A patient lens is applied at the database read path. A query for records a user is not entitled to returns nothing, and cannot be made to return them, because the restriction is applied before any row leaves the store. Hiding a button was never the mechanism, and neither is a rule in a handbook.

Enforced in the patient lens, and specified in the architecture.

06

An audit trail the institution can read against us.

Every action is written to the audit trail inside the same database transaction as the change itself, then archived to write-once storage where it cannot be altered afterwards. There is one complete answer to who accessed a patient’s record and when. The log belongs to the institution, and it reads the same whether the access it records was a clinician’s, an administrator’s, or ours.

Enforced in audit and write-once storage.

Refusals

What we would refuse.

These are requests we will not fulfill, whoever makes them and whatever is attached to them.

  • A request to widen or disable the patient lens for a class of users, for convenience or for speed.
  • A request to run a query across patients on behalf of anyone other than the hospital that holds those records, for a purpose that hospital has not documented.
  • A request to disable, shorten, or edit the audit trail. That includes a request from the institution that owns the log, and it includes a request from us. Write-once storage means the answer is already no.
  • A request for records outside lawful process. Where a lawful order compels disclosure, we comply with it and the disclosure is logged like any other access. An informal request, from any office and at any level, is not a lawful order and receives nothing.
  • A request to route a record to an insurer, an employer, an advertiser, or a data broker, whether identifiable or aggregated, whether sold or given.
  • A request to build a feature whose purpose is to keep an access hidden from the person the record is about.

A list like this is worth what we are willing to lose in order to keep it. Ours is written down, in public, and dated, so that a later decision can be checked against it.

Accountability

How to hold us to it

The first thing we would point at is the hospital’s own audit trail, which records every access in the same transaction as the change and cannot be edited afterwards. If we acted against the commitments above inside a hospital’s data, the record of it would sit in that hospital’s log, beyond our reach.

Beyond the log there are three routes, and all three are open.

What this page does not claim

No third party has audited these commitments. Pensieve holds no security, privacy, or data-protection certification, and we do not imply one; the compliance pages say the same thing in the same words. What stands behind the list is the mechanism named beside each line and the audit trail the institution holds.

Powerful. Responsible. Pensieve.

Get started