We have no server that could see your lab results.
This isn't a promise. It's an architecture: LabCard is a static HTML/JS/CSS site that performs all operations (PDF reading, OCR, LOINC mapping, SHC card generation and signing) inside your browser. No endpoint exists we could send your PDF to, even if we wanted.
Exactly what happens to your file
- PDF is loaded into browser tab memory via
arrayBuffer(). - PDF.js renders pages to a canvas image — locally.
- Tesseract.js performs OCR — locally (library and language model are downloaded once and cached in the browser).
- WebCrypto generates a key and signs the card — locally.
- You download the card as a file. We send it nowhere.
What we do log (honestly)
The hosting serves the site's files over HTTPS. A standard server log (Azure Static Web Apps) includes your IP address and request timestamp — technically required to serve traffic and for security. These logs do not contain the contents of your tests, because those never leave your browser.
We use Cloudflare Web Analytics to count page views. It sets no cookies, does not fingerprint your browser and does not track you across sites. It collects aggregate traffic statistics only: the page URL, the referrer, browser and device type, country and page-load timings. It has no access to the contents of your tests — those never leave your browser, and the analytics script does not read them. We don't use Google Analytics or any cross-site tracking telemetry. We have no cookies apart from potentially technical language-preference cookies.
External resources
In this prototype version, PDF.js and Tesseract.js load from a CDN
(cdnjs.cloudflare.com), and fonts from Google Fonts. The analytics
script comes from static.cloudflareinsights.com. This means
Cloudflare and Google can see that you're loading these resources (they can't
see what you do with them). In the production version we'll move the OCR
libraries to our own hosting to fully close the "nothing leaves your
device" narrative.
Your rights (GDPR)
Since we don't collect your health data — we have none to share, correct, or delete. You are the controller of your own results from the moment you export the SHC card to your disk.
For technical hosting logs (IP addresses, processing necessary to provide the hosting service): the controller is the owner of the labcard.io domain. Contact: [email to fill in after deploy].
Disclaimer
LabCard transcribes values from your input into the SMART Health Card format. It does not interpret results, suggest diagnoses, or replace medical consultation. The "in range / out of range" status is shown only when we received a reference range in your PDF or from you — it reflects that data, not a medical judgment.
The SHC card generated by LabCard is unverified — Apple Health will mark it with a grey badge. That is truthful: the card comes from a conversion tool, not from a laboratory.