PRIVACY COMMITMENTS

Trust is part of the product.

VESFIT is in active development. These commitments guide its design; they are not a claim that every planned capability is complete.

You remain the authority

Aurora may explain and recommend. Important decisions stay with the user.

Access should be understandable

A capability should explain what it needs, why it needs it, and how to disable it.

Local comes first

Sensitive wellness information should stay on-device whenever practical. A returning connection must not trigger an automatic upload of everything.

Permission is specific

Health reading, Aurora processing, synchronization, and human viewing are separate choices—not one blanket approval.

Secrets remain secret

Credentials, private keys, and access tokens must not be placed in health records, AI context, or public content.

Current development boundary

Health Connect is the planned Android integration path for approved foreground reads. Offline local AI has been validated separately, but the local model is not yet integrated into VESFIT and does not automatically have access to Health Connect, VESFIT records, files, cloud accounts, or project memory.

Not medical care

VESFIT is being built as a personal wellness and understanding tool. Aurora explanations and recommendations are not a diagnosis, emergency service, or replacement for qualified medical care.