Privacy Policy — MedCam Prototype

Last updated: 2 November 2026. This policy describes the code included in this prototype. Before launch, the site operator must identify itself, provide contact details and update this page for the selected hosting, analytics, consent and advertising configuration.

Local image processing

Camera previews, uploaded image decoding, quality checks, adjusted image generation, UMF parsing/packaging and PDF generation occur within your browser. The supplied app has no endpoint for uploading your medical image and no remote OCR, image AI or external image-processing API.

What is retained

Camera photos and uploads reside in browser memory until the page is closed or cleared; downloaded files are saved wherever your device/browser chooses. The app's service worker caches only program assets, never patient pictures. No account, medical history or patient identity field is requested by this version.

Risks of shareable files

UMF includes the original uploaded/captured image bytes, including any metadata that source may contain, such as EXIF location. Photos may visibly include names, dates, hospital identifiers and other private information. Derived JPG/PNG/PDF copies are re-encoded and do not intentionally copy source EXIF, but visible identifiers can remain.

Direct sharing to other apps

When you explicitly choose Share via apps, MedCam asks your browser/operating system to present its native share destinations for a locally prepared file. MedCam does not automatically post or upload that file. If you select WhatsApp, Messages, email or another receiving app, that provider may store, process, transmit or retain the picture under its own privacy terms. MedCam cannot control or verify delivery to the selected recipient. This feature requires supported browser APIs and user action.

Hosting and logs

A hosting/CDN provider may receive ordinary technical access information, such as your IP address, when you visit the site. The details and retention period depend on the operator's chosen infrastructure and need to be published before production. This demo does not include analytics, ads, or third-party tracking scripts. The public pages may make a single same-origin request to read the hosting server’s HTTP Date header to check the displayed clock; no medical photo is transmitted in that request.

Future ads and optional cloud

If ads, audience measurement, online storage or synchronization are introduced, a new privacy notice, legal basis/consent mechanism where applicable, safeguards and retention/deletion policy are required. Advertising must not target users based on medical information or images.

Security

The browser requires HTTPS to use camera permissions on a deployed site. Do not upload sensitive images to an unknown website. This prototype is not a certified health-information system.