CYANLUNA / FIELD NOTES

Current hosting and service status

Cloudflare serves this information and the ARGO image at garmin-mcp.cyanluna.com and forwards protocol requests to the existing Google Cloud Run preflight service. Cloudflare processes HTTPS requests, including network metadata, paths and headers. Garmin account linking, activity collection and AI sharing are OFF; the backend currently reports not ready. Infrastructure providers may process operational or security logs under their service settings. Sensitive-value logging, retention and supported processing arrangements must be verified before live OAuth or health-data use.

PRE-LAUNCH INFORMATION
Garmin Developer Portal access is available and Starter app registration is being prepared. App creation, production readiness and downstream AI conditions are not complete. This service is not operational; no connection or signup is available.

A small cycling pilot / project proposal

ARGO

Your riding.
A clearer conversation.

A planned way to explore your own cycling performance with an AI assistant you choose.

Independent developer Gerald Park is preparing a noncommercial pilot for approximately 30 cyclists. The confirmed service name is Cyanluna Garmin MCP, operated by Gerald Park as an individual developer under Cyanluna.

01 / THE IDEA

Connect your account.
Ask about your ride.

The proposed read-only Activity API integration would use Garmin OAuth consent to link each participant’s own Garmin account. Data would be account-linked, not anonymous. Separate MCP authorization would limit access to that participant’s information for requested cycling training analysis, explanations and coaching; no write-back tools are planned.

No Garmin password or Personal API key would be collected. Developer Portal access does not establish production readiness or permission for every downstream AI use. Applicable Garmin conditions and provider controls must be confirmed before real-data use.

The intended Starter route is understood to deliver new data without historical backfill. Coverage may begin only after connection and supported deliveries; a 90-day retention window does not promise 90 days of history.

02 / PLANNED DATA

Performance, with choices.

Power & cadence included

Cycling performance and physiological metrics would support participant-requested summaries. Exact approved fields and granularity still need verification. Sleep, HRV and all-day health fields are undecided and off by default.

GPS is optional

Location would require separate informed consent. AI output would default to summaries such as distance and elevation gain. Precise coordinates or routes would require an explicit request within that consent.

03 / PLANNED CONTROLS

Only when you ask.

Before any AI transfer, participants would receive clear information and separately give explicit consent identifying the assistant and purpose. Only information necessary for a participant-requested analysis would be sent. Consent could be withdrawn; connecting Garmin alone would not start background AI sharing.

Activity-data retention requirement

The most recent 90 days.

Disconnecting would stop future collection. It would not automatically delete existing records. Deletion requests would remove server-held data under a procedure and deadline still to be finalized.

The intended use is inference for personal training analysis, explanation and coaching—not AI model training, evaluation or improvement. Consumer ChatGPT and Claude controls have limitations and exceptions; no universal provider guarantee is claimed. Live AI sharing would remain off until supported configurations and controls are verified and any necessary Garmin clarification is resolved. Participants could request access, correction, export and deletion of server-held data. This service could not automatically delete Garmin or AI-provider copies.

Read the pre-launch privacy overview →
04 / BEFORE LAUNCH

What still needs to be settled

  • Complete Starter app registration, confirm applicable Garmin terms and production requirements, and resolve downstream AI conditions.
  • OpenAI ChatGPT and Anthropic Claude configurations, no-training/evaluation/improvement requirements, login provider and individually tested compatibility.
  • Actual incoming payloads, cloud permissions, regions and data minimization.
  • Security, consent, 90-day purging and deletion behavior, including logs and backups.
  • Age/country scope, legal bases, final privacy notice and deletion deadline.

This is not an operating or medically approved service. AI interpretations may be inaccurate. The operator is independent, with no university endorsement or professor approval. Institutional resource use requires separate approval. Research reuse is outside this pilot’s scope; participant consent or research approval cannot override Garmin restrictions on model training, evaluation or improvement.

Questions: gerald.park@cyanluna.com