How Vital-Go Handles Health Data

Vital-Go is designed to support both Vital-Go-developed hardware and compatible third-party devices and services.

External providers may use their own companion applications, gateways, cloud platforms, algorithms, or connectivity systems before authorized information reaches Vital-Go.

Vital-Go's platform is designed so that adding or changing a supported device provider does not require replacing the core monitoring, clinician, patient, or alert architecture.

A number alone is not enough.

Where appropriate, Vital-Go preserves information such as:

• originating provider;
• device model;
• measurement method;
• measurement context;
• timestamp;
• available signal-quality or confidence information;
• whether a value was directly measured or derived.

This helps Vital-Go avoid treating measurements from different devices or methods as automatically equivalent.

Third-party providers may represent similar health measurements differently. Vital-Go may normalize authorized provider data into a common internal model so it can be displayed and processed consistently.

Normalization does not mean that two measurements become clinically identical. Measurement context and provenance remain important when deciding how information can be used.

Vital-Go's monitoring architecture is designed to evaluate health information according to configured monitoring logic.

A measurement may be restricted from a particular alert workflow if the sensing method, body site, timing, quality, or intended use is not appropriate for that rule.

Vital-Go uses layered protections intended to reduce unauthorized access and misuse. Depending on the system component, these protections may include:

• encrypted network connections;
• authentication and session protections;
• role-based access;
• controlled device authentication;
• secure handling of external-provider credentials and tokens;
• audit logging;
• rate limiting;
• authorization checks;
• monitoring of security-relevant events.

Vital-Go continues to review and strengthen these controls as the platform develops.

When a supported third-party account is connected to Vital-Go, the connection should use the provider's approved authorization mechanism where available.

Provider secrets and authorization tokens should be handled by Vital-Go backend services rather than exposed in browser code.

Users should be able to disconnect supported external integrations, subject to the provider's capabilities and applicable retention requirements.

Wearable devices and external platforms can experience synchronization delays, connectivity failures, incomplete readings, signal-quality problems, battery loss, outages, and other limitations.

Vital-Go is designed to support monitoring and care workflows, but users should not rely on Vital-Go or a connected wearable as the sole means of obtaining emergency assistance.

Vital-Go is currently in development and technical testing.

Current development environments use test accounts and test health data. Device integrations, monitoring behavior, data-handling practices, and product features will continue to evolve as the platform moves toward broader pilots and production use.

For privacy and data-practice questions, contact privacy@vital-go.com.

For product and technical support, contact support@vital-go.com.