Privacy-first wearable data viewer
ExportVitals is built for local wearable data workflows. The goal is simple: help you inspect supported exports in a browser while keeping processing on your own device.
When you import an Oura export ZIP, parsing and metric generation run in your browser. Imported files and derived health data are stored locally on your device and are not sent to app server endpoints.
Local processing means your file is read by in-browser code on your device instead of being sent to a hosted parsing API. Local storage means imported records and derived summaries are saved in browser/device storage so you can reopen your dashboard later.
What ExportVitals does not collect in this workflow
Because there is no backend import pipeline or analytics tracker in this flow, ExportVitals is not collecting uploaded health files in the standard use path. That said, your local environment still matters.
Your responsibilities in a local-first model
- Protect downloaded ZIP files on disk.
- Use secure browser profiles and device access controls.
- Be careful on shared devices/accounts.
- Understand that device backups may include local browser data.
Never post private health exports to public GitHub issues, forums, or social posts. If you need help, share only minimal sanitized metadata.
Limits and guarantees
Local-first is a design choice for control and portability, not a blanket medical, legal, or security guarantee. ExportVitals is unofficial, not affiliated with Oura, and not a medical diagnostic tool.
FAQ
Does health data stay on device?
In normal use, yes: import parsing and derived data remain local to your browser/device.
Does ExportVitals require cloud sync?
No. It is designed for local import and local review.
Should I upload my export ZIP to public threads?
No. Avoid sharing private export files in public spaces.
Can I inspect how it works?
Yes. The project source is public on GitHub.
Is this affiliated with Oura?
No. ExportVitals is unofficial and not affiliated with Oura.