Privacy Policy — Dronapix Cadence

Version 1.3 — last updated: 28 October 2026

1. Who is responsible for your data

The data controller is:

Dronapix SNC (general partnership), enterprise number BE 1021.019.723
Rue Charles Bouvier 127, 5004 Bouge (Namur), Belgium
Website: https://dronapix.eu
Contact for any question about your data: contact@dronapix.eu

The processing of your data is subject to the General Data Protection Regulation (GDPR) and applicable Belgian law.

"Dronapix Cadence" is a connector that lets your AI assistant (for example Claude) create, schedule, list and delete running workouts in your Garmin Connect account so that they appear on your watch. This service is not affiliated with or endorsed by Garmin. "Garmin" and "Garmin Connect" are trademarks of their owners.

2. What we process, and why

In short: if you authorize it at Garmin, Dronapix Cadence receives your activities and recovery data (sleep, heart rate variability, Body Battery, resting heart rate, stress) so that your assistant can consult them. We keep only a condensed, encrypted summary, for 90 days at most (no GPS track, no detailed curves). We also keep your Garmin identifier, your Garmin access tokens (encrypted), the log of created workouts, and the connector's authorization data.

Data	Why	Retention
Garmin identifier (the technical identifier of your account for Garmin's API, which does not directly identify you) and the permissions you granted to Garmin.	To recognize you from one connection to the next and know what you authorized.	Until you disconnect, deregister at Garmin, or have your data deleted (§8).
Garmin access tokens (access token and refresh token), stored encrypted. We never receive or store your Garmin password.	To act in your Garmin account on your behalf, only when you ask your assistant to.	Same period. An unused token eventually expires at Garmin; you will then need to reconnect.
Log of created workouts: workout ID, name, scheduled date, creation date.	To name the workouts in your calendar and keep a record of what was sent to your watch.	Until you disconnect, deregister at Garmin, or have your data deleted.
Activities received from Garmin (type, date, duration, distance, average and maximum heart rate, pace, cadence, elevation gain, calories, device name): condensed summary, no GPS track.	To let your assistant look at your workouts and adapt your sessions.	90 days at most, encrypted; also deleted when you disconnect, deregister at Garmin, or on request.
Recovery data received from Garmin (sleep duration and stages, sleep score, overnight heart rate variability, Body Battery, resting heart rate, average stress, steps): condensed daily values.	To let your assistant judge your recovery before a session.	Same rules: 90 days at most, encrypted. This is health data: we process it only with your explicit consent.
Content of the workouts sent to Garmin (steps, durations, distances, paces, target heart rates).	To create the workout in your Garmin account. It is transmitted to Garmin (§4); we keep only the name and date in the log above.	Not retained by us.
Connector authorization data: your assistant's identifier, the connector's OAuth tokens (stored in hashed form).	To authenticate you and prevent unauthorized access.	Token validity period, then automatically deleted.
Session of the “My workouts” web area: one strictly necessary cookie (HttpOnly, secure) and, server-side, the fingerprint of that cookie linked to your Garmin identifier.	To keep you signed in to the web area and protect your actions. No advertising or analytics cookies.	8 hours, or until you sign out.
IP address (invitation-code attempt counter, during the closed beta only).	To limit abusive attempts on the consent screen.	15 minutes.
Technical logs: we do not enable retention of the service's runtime logs. Cloudflare, as host, may process technical request metadata for the security and operation of its network, under its own terms.	To operate and secure the service.	Not retained by us.

Your running workouts are personal data; they may reveal information about your physical condition. We process them only with your explicit consent, which you give on the consent screen before being redirected to Garmin.

3. Artificial intelligence transparency statement

Dronapix Cadence works through an artificial intelligence system: the AI assistant you use (for example Claude).

Nature and purpose of the processing. When you ask for a workout, the AI assistant prepares the workout's steps (names, durations, distances, paces, target heart rates, dates) and passes them to Dronapix Cadence; Dronapix Cadence sends them to Garmin. When you look at your calendar, the scheduled workouts (name, date, identifiers) are returned to the assistant so it can answer you. If you have authorized activity and health data at Garmin, the assistant can also read your activities and recovery data (sleep, heart rate variability, Body Battery, resting heart rate, stress) to answer you; they are then passed to it. The sole purpose is to create and manage your workouts and to follow your recovery, at your request.

Your explicit consent. Before any processing, the consent screen asks you to expressly agree to this information being processed by the AI assistant you use. Without this agreement, no connection takes place.

Withdrawing consent. You can withdraw it at any time, simply: ask your assistant to disconnect Garmin (the "disconnect_garmin" tool), or remove the connector in your assistant, and revoke access in your Garmin Connect account settings.

What we do not do with AI. Dronapix Cadence does not use this data, or anything derived from it, to train, test, evaluate or improve any AI model, and keeps no conversation history. The AI assistant's own processing is governed by its provider's policy, which we do not control: check the sharing and conversation-use settings in your assistant.

4. Garmin

The workouts you create are transmitted to Garmin Connect and attached to your account. Garmin is an independent controller for the data it receives and keeps; see the Garmin Connect privacy notice. Do not transmit workouts to Garmin if you are not allowed to. Your dealings with Garmin (login, authorizations) remain governed by Garmin's terms and policy.

5. What we do not do

We do not sell your data.
We do not use it for advertising or commercial profiling.
We do not use it to train artificial intelligence models.
We do not share it with anyone other than the providers and recipients listed in §6.

6. Who it passes through

Garmin: recipient of the workouts and provider of access to your account (§4).
Cloudflare, Inc. (United States, global network): hosts the service (Workers, D1 database, KV storage). Cloudflare acts as our processor.
Your AI assistant (for example Claude, provided by Anthropic): it sends and receives the information described in §3, under its provider's policy.

Some providers are located outside the European Economic Area, notably in the United States. These transfers rely on the EU–US Data Privacy Framework, under which Cloudflare is certified, and failing that on the European Commission's standard contractual clauses, provided for in Cloudflare's data processing addendum.

7. Security

All communications use HTTPS.
Access to the service requires an OAuth 2.1 authorization that you grant yourself; nothing is accessible without a valid token.
Garmin tokens are stored encrypted (AES-256), with a key separate from the database, and bound to your account.
The connector's tokens are stored in hashed form.
Activities and recovery data are stored encrypted (AES-256-GCM, a key separate from the database, bound to your account), reduced to condensed values, and deleted after 90 days.
Data pushed by Garmin is not signed: we accept only what carries the identifier of a registered user, and we never keep the raw message.
Logs record no token and no health data.

No system is infallible. In the event of a breach likely to harm you, we will notify you, and the competent authority and Garmin where the law or our contract requires it.

8. Your rights

At any time you may:

access the data we hold about you, have it corrected, request its deletion or portability;
disconnect and delete your data yourself: ask your assistant to disconnect Garmin (the "disconnect_garmin" tool). We then remove your authorization at Garmin and delete your tokens, your identifier and your workout log. Workouts already sent remain in your Garmin Connect account, which you manage with Garmin;
withdraw your consent (§3); if you withdraw the authorization from your Garmin Connect account, Garmin notifies us and we delete your data;
request deletion by email to contact@dronapix.eu; we reply within 10 days.

If you believe your rights are not respected, you may lodge a complaint with the Belgian Data Protection Authority (https://www.dataprotectionauthority.be), or with the data protection authority of your country of residence.

9. Minimum age

This service does not impose a minimum age. Where the law requires the consent of the holder of parental responsibility for the processing of a child's data (in Belgium, under 13), that consent is required to use the service.

10. Changes

We may update this policy. The version and date at the top show the latest version; each change receives a new version number and is recorded in the history below. For a material change (new data collected, new provider, new purpose), we will state it prominently on this page and, where the law requires it, ask for your consent again. Previous versions are available on request at contact@dronapix.eu.

11. Version history

Version	Date	Change
1.3	28 October 2026	“My workouts” web area: strictly necessary session cookie (8 hours).
1.2	28 October 2026	Receipt of activities and recovery data (sleep, heart rate variability, Body Battery) pushed by Garmin: condensed, encrypted summary kept for 90 days at most.
1.1	28 October 2026	Move to Garmin's official API: Garmin identifier and encrypted tokens, workout log, AI transparency statement, one-step disconnection and deletion, service name.
1.0	28 October 2026	First publication.