Overview

§7 · Privacy

What this site holds about you, and what the record is designed to hold.

What this site holds about a reader, the controls the records would be kept under, and what belongs in the agreement rather than here.

§7.1

True today

Privacy

It sets no cookies and runs no analytics. It has no forms, no accounts and no sign-up, and it holds no personal data of any kind.

Source:this website

§7.2

Designed, not built

The controls

Personal and medical data are handled under written rules, with access limited to those who need it and every access recorded.

Access is controlled row by row on every table; an operating team's access is scoped to its own country; every access is logged; the boundary around protected health information is written down; suppliers that handle health data are gated for eligibility; and documents are issued with identifiers that can be verified.

An operator reads what it needs, when it needs it, and every read is recorded. There is no bulk export.

What the operator has produced is the operator's, and it can be taken out: a country-filtered, recorded export of its own operational records.

If nobody has written and reviewed the consent wording in a language, the recording does not start in that language.

Recording is consented for each encounter, a person can withdraw it, and what is deleted is recorded as deleted. Recordings of a patient go only to suppliers under a signed data-protection agreement, and the system will not send them anywhere else.

See §5 · Method and limits.

Source:the plan for the response platform

§7.3

True today

Where the records sit, and under whose law

Data residency and governing law are settled in the agreement and answered in the room, not on a website. This site does not imply a residency it does not have.

See §A.4 · What is deliberately not said.

Source:this website