Privacy-first architecture

Molarvia extracts market data, not patient identity.

Dental prices are useful for patients across Alberta. Patient names, insurance numbers, birth dates, and medical identity data are not useful for price comparison. Molarvia is designed around that separation.

No permanent invoice archive

Invoice files are meant to be processed for extraction, then discarded rather than stored as documents.

Only market facts

Molarvia needs clinic, city, procedure code, procedure description, price, and date when available.

Human confirmation

Users confirm extracted values before a price becomes part of the public comparison dataset.

Explicit consent

Receipt explanation, visit tracking, and price submission require an account and an affirmative consent step before processing.

Third-party extraction

Document extraction may use service providers such as OpenAI to turn uploaded files into structured facts.

Breach readiness

Molarvia should keep incident response, access controls, and security review processes appropriate for sensitive personal information.

Data minimization

What Molarvia should not store

Patient names, home addresses, dates of birth, insurance policy numbers, and treatment notes are outside the price transparency mission.

No patient names stored No insurance numbers stored No permanent invoice archive No medical advice or diagnosis