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 does all the work on your document — reading it, recognising the text, matching the tests and assembling the card — inside your browser. There is no place where we could store or process your files, because no such place exists.

What happens to your file

• The file — a PDF or a photo — is opened in your browser tab's memory only. It never reaches a disk on our side, because there is no such side.
• The text recognition (OCR) tooling and its language model are downloaded into your browser and do the work there. The tools travel to your file, not your file to the tools — the raw scan and its image are never uploaded anywhere.
• Recognised test names are matched to LOINC codes against a dictionary loaded with the page — also locally.
• You save the finished card as a file or hand it to Apple Health via a link. Either way its contents stay on your device.

The only moment anything leaves: signing the card

The finished card is cryptographically signed on our side — that's how Apple Health can confirm it came out of LabCard. Signing only needs a digital fingerprint of the card: an irreversible 43-character string computed from its contents. It has exactly the same length whether the card holds one result or a hundred — because it carries no values, no test names, no patient data and no dates. That is enough to sign the card cryptographically before it is generated. It's the only thing that leaves your browser.

If you have no connection at that moment — for instance because you deliberately went offline after opening the page — LabCard will offer to sign the card locally, with a one-off key generated in your browser. Then nothing leaves at all, not even that fingerprint. The card works the same (values, units, trend charts); the one difference is that Apple Health will not show the “Verified” badge on it, because the issuer will be unknown to it. Local signing never kicks in on its own — it always asks.

What the page loads from elsewhere

Fonts, styles, scripts and the test dictionary are all served from our own hosting — no Google Fonts, no library CDN. You can verify that yourself in your browser's developer tools, under “Network”. There are exactly two exceptions, and both show up there:

• The OCR models — the text-recognition engine weighs several to a dozen-odd megabytes and is fetched from a public CDN (jsDelivr), but only once you add a file to be read. It is one-way traffic: the browser downloads the model and sends nothing about you or your document. Those files sit outside our hosting for one reason — bandwidth considerations.
• The Cloudflare page-view counter — described below. It is the only script loaded from a third-party domain when you simply open the page.

Site statistics

• Hosting log (Azure Static Web Apps) — your IP address and request timestamp, standard for any website.
• Cloudflare Web Analytics — page-view counts: page URL, referrer, browser and device type, country, page-load timings. No cookies, no fingerprinting, no cross-site tracking.

By default, local browser storage holds interface settings only: the table layout you picked, and the fact that you dismissed the “Add to Home Screen” hint or the tip next to the table settings, so they do not keep coming back. No results, no dates and no personal data.

The exception is something you switch on yourself, in the table settings (the gear icon above your results). Both switches are off by default:

• “Keep results in this browser” saves the results table along with the collection date, so it survives closing the tab. The copy is updated on every change to the table; “Reset” empties it and uploading a new file replaces it.
• “Keep my personal details” saves your name, sex and date of birth, so you don't have to type them for every card.

This is health data and personal data, so it is worth knowing where it lives: only on this device, in this browser. Nothing from that storage is ever sent out and we never see it. Anyone using the same browser can, though — so don't turn this on on a shared computer. Turning a switch off deletes what it saved right away; clearing site data in your browser settings removes it too.

The “Donate” and “Support the project” buttons are plain links — there is no payment form or provider script here. Until you click one, your browser never contacts Stripe at all. Clicking takes you to their payment page, which has its own privacy policy and its own cookies; all we pass along is the fundraiser identifier — nothing about you or your results. We never see your card details at any point.

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.

The controller of the data processed when you simply visit the site — technical hosting logs (IP address, request time) and the page-view statistics described above — is the owner of the labcard.io and labkarta.pl domains:

Jakub Misiura
Contact: labcard_io@icloud.com
Poland

You have the right to access that data, to have it corrected or erased, to restrict its processing and to object to it — just write to the address above. You can also lodge a complaint with the Polish supervisory authority, the President of the Personal Data Protection Office (uodo.gov.pl), or with the data protection authority in your own EU country.

Disclaimer

LabCard is a hobby project, not a medical device or a medical service. It carries no certification, is not under medical supervision, and is not intended for making health decisions. It's built after hours, with no guarantee of availability or support.

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 card is signed with our key, so Apple Health will show it as verified. It's worth understanding what that badge actually means: it confirms only that the card was produced by LabCard and hasn't been altered since. It does not confirm that the numbers in it are correct. The values come from an automatic reading of your document or from your own input, so their reliability depends on the quality of that reading and on whether you checked them before generating the card. The card does not come from a laboratory and does not replace the original lab report.