ElioHealth

Privacy-first wearable wellness insights
for a closed pilot community

Last updated: April 21, 2026

ElioHealth

Privacy-first wearable wellness insights for a closed pilot community

Illustrated ElioHealth wearable wellness dashboard preview

Privacy-first wearable wellness insights for a closed pilot community

ElioHealth is a privacy-first wellness platform operated by Tellme Technology Limited. The platform is designed to support multiple wearable integrations over time. In its current pilot phase, ElioHealth is evaluating Oura as the first supported wearable connection for a limited, invite-only participant group.

ElioHealth is built around a direct-identifier-free operating model. Participant wellness data is processed under random internal identifiers rather than real names, phone numbers, or personal email addresses. Direct personal identifiers are not routinely retained in the analytics environment. Where a technical account reference, OAuth credential, or optional communications routing detail must be processed for the service to function, it is stored separately under enhanced access restrictions.

Because wearable wellness data can still relate to an identifiable individual when combined with separately held information, ElioHealth treats such data as protected personal data and applies heightened privacy and security controls accordingly.

What ElioHealth does

With a participant’s explicit authorization, ElioHealth retrieves selected wearable wellness data and presents it in a structured dashboard environment. Depending on the participant’s consent settings and the pilot configuration, the platform may support:

  • a personal dashboard for the participant;
  • a program dashboard for authorized advisors or staff;
  • individualized wellness guidance; and
  • program-level reporting using aggregated or anonymized statistics where possible.

Where participant consent has been provided, authorized advisors may view participant data through role-restricted dashboard views that display platform-generated aliases rather than direct personal identifiers.

What ElioHealth does not do

ElioHealth is not:

  • a medical device;
  • a medical provider;
  • an emergency response service;
  • a diagnostic tool; or
  • a substitute for professional medical advice, diagnosis, or treatment.

The platform is intended to support general wellness, self-observation, and optional advisor guidance only.

How the pilot works

  1. Invitation and consent Participation is by invitation only. A participant decides whether to connect an approved wearable source and which permissions to grant.
  2. Pseudonymous participant setup The platform assigns a random internal identifier and platform alias for operational use. Routine analytics processing does not require the participant’s real name.
  3. Current wearable connection In the current pilot phase, ElioHealth retrieves selected data from Oura through the authorized integration flow.
  4. Secure dashboard and optional advisor support Data is displayed in a secured application environment. Any advisor visibility is subject to explicit participant consent, role-based restrictions, and audit logging.
  5. Withdrawal and deletion The participant may disconnect the integration or withdraw from the pilot at any time. Following revocation or withdrawal, ElioHealth stops retrieving new data and deletes retained personal data unless retention is required by law.

Privacy and security posture

ElioHealth is designed with privacy by default. Core safeguards include:

  • minimization of requested integration permissions;
  • separation of identity or token material from the analytics environment;
  • pseudonymous internal identifiers and alias-based advisor views;
  • encryption in transit and encryption at rest;
  • role-based access control and least-privilege administration;
  • audit logging for privileged access;
  • deletion workflows triggered by withdrawal, revocation, or account closure; and
  • end-to-end encryption for private messaging only where such functionality is actually implemented and message content is inaccessible to the platform operator in plaintext.

Current pilot scope

  • Status: private proof-of-concept pilot
  • Access model: invitation only
  • Current supported integration: Oura
  • Future architecture: designed to support additional compatible wearables over time, subject to technical, legal, and partner approval
  • Purpose: wellness tracking and optional advisor support for a small closed community
  • Public availability: not publicly available at this stage

Legal links