Your data
Privacy policy
Your training history, health measurements and location deserve clear privacy choices. This policy explains what Stigl collects, why we use it, who receives it, and how you can withdraw consent or request deletion.
Last updated:
Who is responsible for your data
Malte Granefelt, developing and operating the Stigl project in Sweden, is the data controller responsible for the personal information described here. Stigl is a pre-launch project and is not yet a registered company. This policy covers stigl.se, the Stigl web app, its testing site and companion mobile app. Contact support@stigl.se for privacy questions, consent withdrawal or a data request.
The Terms of Use explain the rules for using Stigl. Accepting those terms or reading this policy does not give consent to optional health processing, a connected service, marketing or a new use of your information.
Launch waitlist
Joining the waitlist provides your email address, signup time, consent to launch emails and the accepted version of the waitlist terms. We use this information, based on your consent, to send launch updates and tell you when signup opens. Joining does not create an app account or connect a training service.
Supabase stores the list. Simply.com and email providers process the contact and message information needed for delivery. Visitors cannot read or export the list. We retain it while launch communications are active, then delete it unless a legal obligation requires limited retention.
To leave or request earlier deletion, email support@stigl.se from your registered address. Withdrawal does not affect earlier lawful processing. The waitlist terms and conditions, international transfer information and rights below also apply.
Information we collect and its sources
- Account and profile: email address, account identifier, authentication information and details you provide, such as your name, photo, age, location and biography. An identity provider supplies basic account information if you choose social sign-in.
- Activities and routes: activity identifiers, sport, dates and times, distance, duration, pace, speed, elevation, GPS coordinates, recorded measurements, notes, photos, videos, equipment and training plans. These come from your entries, uploaded files or a connection you enable.
- Health and fitness: measurements included in your activities or enabled health connection, such as heart rate, power, calories, steps, sleep, resting heart rate and heart rate variability. Availability depends on the source, device and permissions.
- Community: follows, club memberships, event responses, comments, reactions, shared media and notification preferences that you or other members create.
- Technical and support: IP address, browser and device request information, session records, security and error logs, and messages you send to support.
Email and authentication information are necessary for an account. Other profile details, uploads and connections are optional. Declining them may limit the related feature; you can use the remaining service without connecting Garmin, COROS, Polar or Apple Health.
Google and Apple sign-in
If you choose Google or Apple sign-in where available, the provider supplies an account identifier, email address and available basic profile details. Supabase uses these to authenticate you, and Stigl uses them to create or access your account. A supplied name or photo may initialize your profile. Apple may provide a private relay email address.
Google sign-in does not request Gmail messages, Drive files, contacts or calendar access. Sign-in information is used for your account and authentication. Removing access in the provider's settings does not erase your Stigl account; contact support if you need help accessing or deleting it.
Optional training and health connections
Stigl's intended direct connections are Garmin Connect, COROS, Polar Flow through AccessLink, and Apple Health through HealthKit. Availability depends on provider access, configuration, your device and the app version. Listing a provider here does not mean a partnership has been approved or that its direct connection is available. The sections below distinguish existing import paths from planned features.
The intended use is to import your workouts and, where separately supported and enabled, daily health measurements for your training history, statistics and private health dashboard. Stigl requests access for the feature you choose. A provider may offer a broader permission than the specific records Stigl uses; that permission does not authorize Stigl to collect every available category.
For direct cloud connections, you sign in with the provider and authorize access on its own page. Stigl does not ask for or store your Garmin, COROS or Polar password. Stigl stores provider account identifiers, authorization tokens, permission and sync information needed to operate an enabled connection. Permitted data may arrive through provider notifications or be retrieved by Stigl's servers, depending on the connection.
Connecting and publishing are separate choices. Private daily health summaries are not community posts. An activity can contain heart rate, GPS or other sensitive measurements when you choose to share it. Importing does not authorize sending Stigl workouts or training plans to a provider; any future export would require a separate explanation and action.
You can withdraw optional consent through the available connection controls, the provider's permission settings or support@stigl.se. Revocation stops authorized future collection through that path. Previously imported records and posted activities may remain until you delete them or request deletion. Connecting the same device through another source, such as Apple Health, is a separate path that must be disabled separately.
Garmin activity data and Garmin Connect sync
Current availability: Stigl supports importing a Garmin data-export ZIP that you choose. Direct Garmin Connect sync is being implemented for the restricted test application and is not open on the public waitlist site. Developer-program access does not mean the integration is tested, activated or endorsed by Garmin.
Importing a Garmin export
You request your export from Garmin and select the ZIP in Stigl. The app reads the archive on your device and saves extracted activity records to your Stigl account; it does not upload the complete ZIP. Records can include activity identifiers, sport, title, dates, duration, distance, heart rate, calories, elevation, GPS tracks, timed samples and power measurements where present. The importer does not import unrelated account or wellness files from the archive.
Garmin ZIP imports create private activity entries. You can later change their visibility. The file-sharing limits below apply if you separately upload files or media. Importing an archive neither gives Stigl ongoing access to Garmin Connect nor sends Stigl activities back to Garmin.
Direct Garmin Connect connection
Stigl encrypts incoming delivery jobs while processing or retrying them. Completed jobs are removed; unprocessed jobs expire after seven days. Disconnecting clears queued jobs and stops new imports.
When enabled, the direct connection requires separate, explicit consent in Stigl for processing activity and workout health data, followed by your authorization through Garmin's own sign-in and permission screen. Stigl does not ask for or store your Garmin password. The connection receives activity summaries: sport, start and end times, duration, distance, elevation, and workout heart rate or calories when supplied. Detailed activity sync requires explicit consent to GPS routes and timed workout measurements, including recorded heart rate. Existing summary-only connections must opt in before Stigl saves these additional details. Routes may reveal your home, workplace or other sensitive locations. The connection does not import daily health, sleep or women's health data, request historical API backfill, or send workouts or routes to Garmin.
New summaries maintain your training log and ordinary training statistics. New imports are private. Supabase hosts Stigl's controlled backend functions and database and processes these records for Stigl; this provider and the delivery endpoint must meet Garmin's approval requirements before collection is enabled. Authorization and refresh tokens are encrypted before database storage, with the encryption key held separately in server secrets. Garmin data is not sent to AI services or used to create, train, test, evaluate or improve AI systems, models or datasets.
Use Settings → Connections → Disconnect Garmin to withdraw connection consent and stop new imports. Stigl stops ingestion before requesting deregistration from Garmin; a failed remote request remains visible for retry. You can also revoke Stigl through Garmin Connect's connected-app controls. Revocation or a reported permission change stops future imports; a permission change requires a fresh authorization. Existing activities remain until you delete them or request erasure under Retention and deletion. Small receipt records prevent a redelivered summary from restoring a deleted activity and are removed with your Stigl account. Contact support@stigl.se for access, correction, export or erasure. Deleting Stigl data does not delete Garmin's copy.
Garmin independently controls its own service. Read the Garmin Connect privacy policy for Garmin's processing and account controls.
COROS: planned workout and daily health imports
A direct COROS connection is planned and is not active in the current Stigl version. If access is obtained and the feature is enabled, Stigl will use the COROS authorization flow to import the workouts you permit and, with separate health consent, supported daily measurements. It will not collect data merely because you visit this page or have a COROS account.
Workout records may include the activity and device identifiers, sport, date, duration, distance, pace, speed, elevation, GPS route, heart rate, cadence, power, calories and available samples. Daily health imports, if offered, may include steps, energy, sleep, resting heart rate and heart rate variability. The actual categories and purposes will be identified before you enable that feature; not every COROS field or device measurement is necessarily supported.
Imported workouts are intended for your training log and progress statistics, with private health summaries used for your personal dashboard. The planned initial integration reads data from COROS; it does not send training plans, workouts or routes to COROS. You will be able to revoke Stigl's authorization through COROS's third-party connection controls or contact support. Ask separately to remove copies already stored in Stigl.
COROS controls its own accounts, devices and service under the COROS privacy policy. Workouts from COROS may also reach Stigl through Apple Health if you independently enable both sharing paths.
Polar Flow and AccessLink
Stigl includes Polar connection code, but use depends on an enabled AccessLink client and server configuration; this policy does not assert that live Polar access has been granted or tested. Where offered, you authorize Stigl through Polar Flow. Stigl receives a Polar user identifier and access token and registers the connection with AccessLink.
The current integration code requests the accesslink.read_all permission. It reads account and physical information supplied by Polar and exercise records, including sport, device, time, duration, distance, calories, heart rate, heart-rate zones and GPS routes where present. Account information may include your name, birthdate and sex/gender if returned by Polar. Physical information may include height, weight, maximum or resting heart rate, thresholds and VO2 max. Stigl uses those records to populate your training log and, where available, your heart-rate zone settings. Polar imports create private activity entries; you control subsequent sharing.
Daily activity, sleep, continuous heart rate and recovery imports are planned extensions, rather than a claim that the current importer reads them. A future extension would identify its categories and purpose and obtain required health consent before collection. The initial request does not include writing workouts or plans to Polar.
The implemented disconnect flow de-registers Stigl's AccessLink connection and removes its stored connection credentials when the operation succeeds. It does not delete imported Stigl activities or your Polar Flow account. You can also manage granted access with Polar; do not withdraw an unrelated mandatory Polar account consent merely to disconnect Stigl. Contact support for deletion of imported records. Polar processes its own service under its privacy notice.
Apple Health and HealthKit
Apple Health access requires a supported installed Stigl iPhone app with HealthKit enabled. A website or Expo Go preview cannot request access to your Health data. You choose which categories Stigl may read in Apple's permission controls; declining one category does not authorize another. Apple sign-in and Apple Health access are separate features.
The current reader requests workouts, steps, active energy, exercise minutes, walking/running distance, stand hours, heart rate, resting heart rate, heart rate variability and sleep analysis. Stigl imports supported workout details such as identifier, sport, start/end time, duration, distance, energy, average heart rate and recorded elevation, and computes daily summaries from permitted samples. The current HealthKit reader does not import workout GPS routes, clinical records or reproductive health data, and does not write data back to Apple Health.
When you enable sync, the app sends permitted workout records and daily summaries to Stigl's Supabase backend under your account so they can appear in your training log and private dashboard across your devices. This is a transfer from your device to Stigl, not solely local viewing. Background sync may run while the connection remains enabled, subject to your permissions and device settings.
Automatic workout posting is a separate opt-in with its own visibility choice. It does not publish your existing private history merely because you turn it on. Daily private health summaries are not posted. Review the recorded workout measurements and audience before enabling posting.
Disconnect in Stigl and revoke access in Apple's Health or device permission settings to stop that import path. Stigl's Apple Health controls can also delete private imported health summaries and workout records. Existing Stigl posts remain until removed separately; revocation or deleting a source workout does not automatically erase a published Stigl activity. Stigl does not delete your original Apple Health records.
Workouts recorded by Garmin, COROS or Polar can be received through Apple Health if you separately configure that provider to share them with Apple Health. This grants access through HealthKit, not direct API access to the device company. Apple explains its own handling in Health App & Privacy.
Purposes and legal bases
- Provide your account and requested features: authentication, activity history, statistics, route planning, community sharing and service notifications. The legal basis for ordinary account and service information is performance of our agreement with you, under GDPR Article 6(1)(b).
- Optional connections and health processing: import and display information you choose to provide. We rely on consent for optional connection processing, under Article 6(1)(a), and explicit consent for information revealing health, under Article 9(2)(a). A service connection does not replace any separate health consent required.
- Protect the service: detect abuse, investigate errors, moderate content and respond to support requests. Our legitimate interests under Article 6(1)(f) are keeping the service secure and usable and protecting members. You can object to this processing.
- Launch emails: send waitlist updates based on consent. Legal obligations: process limited information when required by applicable law, under Article 6(1)(c).
You can withdraw consent at any time by using the relevant connection or device controls or emailing support. This does not affect earlier lawful processing. If you withdraw health consent, you can request deletion of the affected records without deleting your whole account.
AI transparency and limits on data use
Stigl uses software calculations to produce training totals, trends and personal bests. It does not send activity or health records imported from Garmin, COROS, Polar or Apple Health to generative AI services, or use those records to train, fine-tune or improve AI or machine-learning models.
Separately, comment images and GIFs you choose to submit are sent to Sightengine for automated content moderation. This analyzes the attachment for inappropriate content, including text within an image; it does not receive your training history as part of that check. A screenshot you attach may itself contain personal or provider-derived information. You can post text comments without submitting an image. Contact support to challenge an attachment rejection.
Before introducing AI processing of connected training or health records, Stigl would explain its purpose, the data and providers involved, and consent withdrawal controls, and obtain any required explicit consent and provider permission. This policy does not authorize that future processing.
Stigl does not sell or rent your personal data, use Garmin, COROS, Polar or Apple Health data for advertising, marketing or unrelated data mining, or provide it to data brokers, employers or insurers for their own purposes. Training insights are informational, not medical advice. Stigl does not use them to make solely automated decisions with legal or similarly significant effects on you.
Providers and other recipients
- Supabase: authentication, account and training databases, the waitlist, connection records and uploaded files.
- Simply.com and email providers: website infrastructure, domain email, account messages, launch emails and support correspondence.
- Google and Apple: identity information when you choose their sign-in options. Apple Health supplies permitted records through HealthKit on your device.
- Garmin, COROS and Polar: their own authorization and data services when an available direct connection is enabled. Stigl sends the authorization and account-linking information needed to operate that connection. The planned initial integrations receive training and permitted health records; they do not send your Stigl training plans or routes back to those providers.
- Sightengine: the comment images or GIFs you submit for automated moderation, as explained above.
- Map and routing providers: map tiles and route requests, including your IP address and requested map area or selected route coordinates. These may include OpenStreetMap, Esri, OpenTopoMap and regional MapAnt services. Route planning uses routing.openstreetmap.de. Some map libraries are delivered through unpkg.
Providers receive information needed for their part of the feature. Authorized support or administration access is used to operate the service, handle requests and investigate abuse. Information may also be disclosed where legally required or necessary to establish, exercise or defend legal claims. Shared content reaches the audience described above.
International processing
Providers may process personal information outside Sweden and outside the EU/EEA. The location and safeguards depend on the service and destination. Transfers subject to the GDPR require an applicable transfer mechanism, such as an adequacy decision or Standard Contractual Clauses, and additional safeguards where necessary. Contact support@stigl.se for the locations, applicable mechanism and a copy of relevant safeguards for your information.
Retention and deletion
We retain account, activity and community information while needed to provide the features you use. Connection identifiers and tokens are retained while needed to maintain an authorized connection. Security logs and support records are retained according to the issue they document and any applicable legal obligation. We do not treat an account's existence as permission to retain health data after its consent has been withdrawn where no other lawful exception applies.
- Delete specific information: use the activity or profile controls, Apple Health's private-data deletion control, or email support. You can request deletion by source: Garmin, COROS, Polar or Apple Health. Identify whether your request covers imported activities, private health records, stored GPS tracks, measurements, associated derived personal data or all of them.
- Disconnect a service: stop future collection through that connection. Previously imported records and posted activities are not automatically erased by every disconnection. Ask for deletion as well if you want those removed.
- Delete your account: account settings start a 30-day deletion process, with restoration available during the first 29 days. You can contact support about immediate erasure or health-consent withdrawal; the restoration feature does not remove your statutory rights.
The account restoration period is not a promise that every database record, file or backup is erased on day 30. Deletion must address stored records and associated files; where limited retention is legally necessary, we will explain its reason and applicable period. Ask support for confirmation of what has been removed, any remaining copies and their retention. Garmin and other source services keep their own records under their policies.
Security
Stigl uses authenticated accounts and database access rules to control access to account and training records. Provider infrastructure processes storage and service requests. These controls do not remove the public-file limitation explained under sharing, and no online service can guarantee absolute security.
Report a suspected disclosure or unauthorized access to support@stigl.se. Avoid including passwords, authorization tokens, complete health exports or unnecessary sensitive information in your message.
Storage on your device
The app uses browser or app storage for your sign-in session and preferences, including theme and time format. A service worker can cache app files for loading and offline fallback. Clearing site or app data can remove local settings and sign you out, but does not erase your server account. External sign-in and map services may use storage under their own policies.
Your rights and how to contact us
Under the GDPR, where applicable, you can request access, correction, erasure, restriction and a portable copy of personal information. You can object to processing based on legitimate interests and withdraw consent at any time. Legal conditions and exceptions apply.
Email support@stigl.se from your account email and explain your request. You do not need to delete your account to request your Garmin, COROS, Polar or Apple Health data or withdraw optional health consent. We may verify your identity before disclosing or changing information. Never send your password.
We respond without undue delay and normally within one month of receiving a request. If a lawful extension is necessary because of its complexity or the number of requests, we will explain the reason within that first month. Requests are normally free.
You can complain to Sweden's Swedish Authority for Privacy Protection (IMY) or the supervisory authority where you live or work, or where you believe a breach occurred.
Changes to this policy
We publish updates here with a revised date. Before a materially different use, we will provide appropriate notice and obtain fresh consent where required. A policy update alone does not authorize a new provider connection, additional health categories, public sharing or AI processing.