Your health data belongs to you.
FarmakoMed is designed so that your medical records and core AI processing remain on your own device whenever possible.
Privacy by Design.
Each principle is something you can verify in the product today.
Local-first architecture
Core features are designed to run and store data on your device by default, not in the cloud.
Minimal data collection
FarmakoMed collects only what is needed to provide the features you use. There is no advertising.
No account required for core features
You can use medication tracking, reminders, documents, and the health profile without creating an account.
Offline-capable workflows
Core features, including AI-assisted medication recognition, are designed to work without an internet connection.
Clear cloud boundaries
Optional cloud backup and sync are architecturally separate from local processing and require your explicit choice.
Where your data lives.
Select any card for a detailed explanation.
Privacy starts with architecture.
Rather than describe a policy, here is what actually happens on your phone when you scan a document.
Everything above happens inside the phone. No step in this pipeline requires a network connection.
Compare architectures.
This compares architectural approaches, not products or companies.
FarmakoMed's core AI features are designed to process information locally instead of requiring a cloud AI service.
Explore every component.
Select any component to see its purpose and where its data goes.
- Purpose
- Where the data goes
- Internet required
- Data leaves the device
Security.
How FarmakoMed is designed to protect your health information.
Mobile-first design
FarmakoMed is designed as a mobile app. Your health data is processed and stored primarily on your device.
Local data storage
For Personal Plan users, all health data is stored locally on your device using the platform's secure storage.
Optional cloud backup and sync
If you enable cloud backup, your data is encrypted before being transmitted using TLS and encrypted at rest.
Authentication for cloud features
Cloud features require authentication using standard, secure authentication practices.
No public web patient portal
There is no web-based patient portal in the current release. Your health data cannot be accessed from a web browser.
Responsible handling of health information
We do not sell your data, do not use it for advertising, and do not share it with third parties without your consent.
Reporting a security concern
If you believe you have found a security vulnerability in FarmakoMed, please report it responsibly to support@farmakomed.eu.
Don't take our word for it.
Every claim on this page is traceable to the product, our policies, or our public engineering writing. Here are the public resources you can check for yourself.
Architecture diagrams & Explorer
The data-flow diagrams and component-by-component Architecture Explorer above describe the actual architecture of FarmakoMed's AI features.
Privacy documentation
Our full Privacy Policy, covering data collection, retention, and your rights.
Security model
How FarmakoMed handles authentication, encryption, and cloud storage for the optional Personal Plus and Family plans.
Engineering Journal
Technical articles by the engineers who build FarmakoMed, including trade-offs and constraints.
Open source & licences
Third-party models and public data sources FarmakoMed's on-device AI depends on.
Offline verification
Turn off your internet connection and test core features yourself, using the protocol below.
Transparency reports
Periodic reporting on data requests and incidents.
Report a discrepancy
Every technical statement here is traceable to the product itself, the Privacy Policy, or the Engineering Journal. If you find one that isn't, tell us.
Engineering Journal.
Long-form articles on the architecture behind this page.
Privacy by Architecture
Why local AI changes software architecture — not just privacy policies.
Read article →AI Should Wait for the User
Why building seamless on-device AI forced us to redesign our application architecture.
Read article →The Hidden Cost of AI Isn't Compute. It's Dependency.
What it means to rent intelligence by the request — and why on-device AI offers a different vision.
Read article →The Engine Isn't the Car
FarmakoMed runs its AI model entirely on-device. Why depending on an external model doesn't make it beholden to its vendor.
Read article →Exactly what FarmakoMed does.
Never hide limitations — transparency builds trust. Here is what happens today, plainly stated.
- What stays on the device: your medication list, health profile, documents, health timeline, and all on-device AI reasoning.
- What optional cloud services exist: Personal Plus and Family provide encrypted backup and sync. They are off by default and require your explicit opt-in.
- What AI model is used: An on-device model for medication recognition, document understanding, and the health assistant — full details on our Licenses page. See why this model was chosen.
- What happens when internet is unavailable: core features keep working. Only medication-database lookups and cloud backup/sync require a connection.
Open Source.
FarmakoMed depends on openly published models and public data sources. Here is what, and why.