Back to Glyde

Privacy Policy — Glyde

Effective date: July 13, 2026

Contact: glyderunning@gmail.com (Josh Edwards)

Glyde ("the app", "we") is a personal running and diabetes-management assistant for Type 1 diabetic runners. This policy explains what data the app collects, why, where it is stored, and the third parties that process it. The app is early-stage software provided to a limited set of testers.

1. Summary

  • We collect health data (continuous glucose monitor readings and manual blood-glucose entries), precise location (only to fetch weather for a run), your account identity, and fitness data you choose to connect (Strava, Dexcom, Google Calendar).
  • Data is stored in our Supabase backend and used to analyze your runs and coach you.
  • Run- and glucose-derived data is sent to a third-party AI provider (Anthropic) to generate analysis and coaching. We do not sell your data or use it for advertising.
  • You can export or delete your account and data at any time.

2. Data we collect

DataSourceWhy
Glucose readings (CGM)Apple HealthKit, Dexcom ShareCorrelate blood sugar with runs
Manual blood-glucose entriesYou (written to HealthKit)Fill gaps when CGM data is stale
Insulin & pump eventsYou / Tandem CSV importCorrelate insulin with glucose and runs
Heart rate & VO2maxApple HealthKitEstimate fitness (VDOT), HR zones, and effort
Food & fluid logs (carbs, sodium)YouModel fueling and its effect on glucose
Precise location & GPS routesDevice (while in use), Strava polylinesLive-run tracking, run maps, and weather lookup
Account identity (email, name, user id)Google or Apple Sign-InAuthenticate you and link your data
Activity / run data (distance, pace, splits, RPE, notes)Strava, manual entryBuild and analyze your training
Calendar eventsGoogle CalendarSync planned workouts
WeatherOpen-Meteo (by location)Enrich run records
Subscription statusApple App StoreManage Glyde Pro access
Waitlist signup (email, optional name and details you share)You (waitlist form on this site)Contact you about early access

We do not use advertising identifiers (IDFA), ad-tracking SDKs, or third-party analytics.

3. Apple HealthKit

The app reads CGM/glucose data from HealthKit and writes manual blood-glucose entries to HealthKit, only with your permission. In accordance with Apple's requirements:

  • HealthKit data is used solely to provide the app's run-analysis and coaching features.
  • We do not use HealthKit data for advertising, marketing, or data-mining.
  • We do not share HealthKit data with any third party for advertising or sale.
  • HealthKit data sent to our backend and to our AI provider (see §5) is used only to generate your analysis and coaching, not for any other purpose.

You can revoke HealthKit access at any time in iOS Settings → Privacy & Security → Health.

4. How we use your data

  • Analyze individual runs (pace, glucose response, weather context).
  • Generate coaching guidance, training-plan suggestions, and a weekly digest.
  • Answer your questions in the in-app coach chat.
  • The app does not provide insulin dosing or medical advice.

5. Third-party processors

We share the minimum data necessary with these services:

ProcessorDataPurpose
SupabaseAll app dataBackend database and serverless functions (system of record)
Google Firebase (Google Cloud)Waitlist and support submissionsHosts this site and stores waitlist/support form submissions
Google (Gmail)Waitlist email address and nameWaitlist and access emails are sent from our Gmail account
Anthropic (Claude)Run and glucose-derived dataGenerates run analysis and coaching text
OpenAIText embeddings of your contentSemantic search over your history (embeddings only)
GoogleIdentity, calendarSign-in and calendar sync
AppleHealthKit data, sign-in, purchasesHealthKit read/write, Sign in with Apple, subscription
StravaActivity dataImport your runs (with your authorization)
DexcomGlucose dataImport CGM readings (with your authorization)
Open-MeteoCoarse locationWeather lookup (no account/identity sent)

These providers process data under their own privacy and security terms. We do not sell your data and do not use it for advertising or profiling beyond app functionality.

6. Storage and security

Data is stored in our Supabase project (hosted Postgres) and protected by row-level security so you can only access your own records. Connections use TLS. Third-party access tokens (Strava, Dexcom, Google) are stored server-side.

7. Data retention

We retain your data while your account is active. When you delete your account, your data is queued for deletion and purged from our backend. Backups, if any, are cycled out on a rolling basis.

Waitlist submissions (email and any optional details you share) are kept until you receive access or ask us to remove you. To have your waitlist entry deleted, contact us via the support form.

8. Your rights

  • Export: request a copy of your data in-app (account export).
  • Delete: delete your account and data in-app; a short recovery window applies before permanent purge.
  • Revoke connections: disconnect Strava, Dexcom, Google, or HealthKit at any time.

9. Children

The app is not directed to children under 13 and we do not knowingly collect data from them.

10. Changes

We may update this policy as the app evolves. Material changes will be reflected by an updated effective date.

11. Contact

Questions or requests: glyderunning@gmail.com