Lumida.

Lumida

Privacy policy

This policy explains how Lumida handles personal data when you create an account, connect Google Health or use the service.

Last updated on July 14, 2026

Data controller

The controller for personal data processed by Lumida is Eddy Nicolle, sole trader.

Our core principle

Your health data remains yours. Lumida retrieves it only to display the features you request and does not build a permanent copy of your health measurements in its database.

Data we process

Depending on how you use Lumida, the following categories may be processed:

  • Account data: first name, email address, profile image when supplied by Google, verification state, role and account dates.
  • Authentication and security data: password hash, provider account identifier and, where required, tokens used for social sign-in, session token, session expiry, IP address, user agent, verification records and rate-limit counters.
  • Beta-access administration data: the Google account email you submit, request language, request date and approval date.
  • Service preferences and administration data: language selected through the URL, appearance stored on the device, temperature unit, latest coarse activity date and any account restriction information.
  • Google Health connection data: stable Google identifier, granted permissions, connection status and dates, and the encrypted refresh token needed to maintain the connection.
  • Health and fitness data requested on demand: activity and exercise, sleep, heart rate, oxygen saturation, recovery measurements, weight, nutrition, hydration and, when authorized, workout location routes.
  • Communications data: email address, message content and technical email metadata when you contact Lumida or receive a transactional message.

Purposes and legal bases

  • Providing the account, authentication, preferences and requested service features: performance of the contract formed by these terms.
  • Protecting accounts, preventing abuse, administering beta access and maintaining the service: Lumida’s legitimate interests in security and reliable operation.
  • Retrieving and displaying Google Health data: your explicit consent under Articles 6(1)(a) and 9(2)(a) of the GDPR.
  • Responding to requests and sending account, security and access messages: performance of the service and Lumida’s legitimate interest in answering users.
  • Complying with legal obligations and establishing or defending legal claims: legal obligation or legitimate interest, as applicable.

Google Health Limited Use

Lumida’s use of information received from the Google Health API adheres to the Google Health API Developer and User Data Policy, including its Limited Use requirements.

Read the Google Health API Developer and User Data Policy

How health data is handled

Health measurements pass through Lumida’s server only for the time needed to answer your request. They are not written to Neon or persistent browser storage. The interface keeps responses temporarily in memory: data becomes stale after 15 minutes and an unused entry is removed after 30 minutes; the complete cache is cleared on sign-out.

Google Health refresh tokens are encrypted at rest using AES-256-GCM. Access tokens remain server-side and are kept only in short-lived process memory. OAuth tokens and health data are never exposed to browser storage.

Recipients and service providers

Personal data is disclosed only as needed to operate Lumida, to the following categories of providers:

  • Vercel: application hosting and server execution (Vercel Inc., 440 N Barranca Avenue #4133, Covina, CA 91723, United States).
  • Neon / Databricks: PostgreSQL account database (Neon (Databricks), AWS eu-central-1, Frankfurt, Germany). Health measurements are not stored there.
  • Resend: transactional email delivery (Resend, AWS eu-west-1, Ireland).
  • Google: social sign-in, OAuth authorization and the Google Health API, when chosen by the user.
  • Cloudflare: DNS protection and routing of messages sent to Lumida contact addresses.
  • OpenStreetMap: map-tile delivery for a visible workout area; the complete route line is not uploaded to OpenStreetMap.

International transfers

The primary database region is Frankfurt and transactional email data is processed in Ireland. Some providers are established in the United States or may provide support from outside the European Economic Area. Where required, transfers rely on an adequacy mechanism such as the EU–US Data Privacy Framework, standard contractual clauses or another safeguard made available by the relevant provider.

Retention periods

  • Account data is kept while the account remains active, then deleted following a verified deletion request, except where retention is legally required.
  • Health measurements are not retained in the database; temporary server and browser-memory handling is described above.
  • Google Health connection data is retained until you disconnect Google Health or the account is deleted.
  • A Google Health OAuth transaction expires after 10 minutes, an email-verification link after one hour and a password-reset link after 15 minutes.
  • Correspondence is kept for the time needed to answer and manage follow-up, then archived only when necessary to establish or defend legal claims.
  • Technical security and hosting logs are retained for limited periods according to provider settings and legitimate security needs. Provider backups may remain until their normal rotation completes.

Cookies and local storage

Lumida uses only storage that is necessary to provide the requested service or remember interface preferences:

  • secure authentication and session cookies;
  • short-lived security and language cookies during the Google Health OAuth flow;
  • a sidebar cookie and local device storage for the appearance preference.

Lumida does not currently use advertising cookies, behavioural tracking or marketing analytics. These necessary mechanisms do not require an advertising-cookie banner.

Your rights

Subject to the conditions of the GDPR, you may exercise the following rights:

  • access and correct your personal data;
  • request erasure of your account data;
  • object to or request restriction of certain processing;
  • receive data you provided in a portable format where applicable;
  • withdraw consent at any time, without affecting prior lawful processing.

You may also lodge a complaint with the French data-protection authority, the CNIL.

Security

Lumida applies measures designed to protect personal data, including server-side OAuth handling, encryption of Google Health refresh tokens, secure cookies, access controls, input validation and rate limiting. No online service can guarantee absolute security; users should also protect their credentials and devices.

Adults only

Lumida is reserved for people aged 18 or over and does not knowingly provide accounts to minors. If a minor’s data is identified, it may be deleted after appropriate verification.

Changes to this policy

This policy may be updated when Lumida’s features, providers or legal obligations change. The effective date appears at the top of the page, and material changes will be communicated by an appropriate means.

Privacy contact

To exercise your rights or ask a privacy question, contact Lumida using the dedicated address below. Identity verification may be requested when reasonably necessary to protect the account.

Email address

Hidden until requested to limit automated collection.