No central hosting
Health data stays local unless the deployment explicitly uses a local team setup.
The policy is simple: data should remain close to the user, only be shared with permission, and never be routed through an unnecessary cloud service.
Health data stays local unless the deployment explicitly uses a local team setup.
Patients and providers decide what leaves the local boundary.
Aggregation happens only after privacy-preserving transformation.
For independent users, patients, and small teams, New Loka is not a hosting service. It is a local or locally distributed application that keeps health data in the user's chosen environment.
Records remain on the device or in the user's local storage environment. We do not receive routine copies of that data.
Locally distributed deployments keep data inside the team's own infrastructure and access boundaries.
If hosted services are introduced later, they will be separate, explicit, and governed by dedicated terms.
Depending on how the app is used, the system may process structured notes, uploaded images, message content, dictation transcripts, and user-entered metadata needed for search and retrieval.
Retention should follow the user's or institution's policy, not an opaque central platform rule.
Users decide when a record is exported, copied, or handed off into another system.
Anonymization and aggregation happen after direct care decisions have been supported.
We do not silently migrate user health data into our own servers or services.