Data Attributions
Effective 2026-07-29. Brick integrates data from third-party services. Where required by licence or brand guidelines, credits appear next to the relevant data in the app. This page lists all third-party data sources and their terms.
Mapbox & OpenStreetMap
Activity route maps use Mapbox GL JS with outdoor and satellite basemap styles (Mapbox Outdoors, custom Studio styles when configured, and Satellite Streets). Mapbox map data incorporates OpenStreetMap and other sources.
Open-Meteo
Historical and forecast weather shown on activities and race planning is provided by Open-Meteo under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence.
Strava
If you connect Strava, Brick syncs your activities via the Strava API at your direction. Connect flows use the official "Connect with Strava" button. The Connections settings screen displays the "Compatible with Strava" mark. Strava-sourced activity detail pages include a "View on Strava" link. Strava data is governed by Strava's API Agreement and brand guidelines.
Garmin
Activity and wellness data may originate from Garmin devices synced through Strava, intervals.icu, or uploaded FIT files. When Garmin-sourced data is displayed, Brick shows device attribution (e.g. "Garmin Forerunner 965") on the activity detail page and on share images. Activity lists include a note when Garmin-sourced activities appear on the page. Readiness, recovery charts, and morning briefs note when insights may include Garmin device metrics.
intervals.icu
If you connect intervals.icu, Brick syncs activities, wellness (HRV, sleep, resting HR), and pushes planned workouts to your Garmin device via their bridge. intervals.icu data is used under their API Terms and Conditions. No intervals.icu logo is required; Garmin attribution rules apply to Garmin-sourced data within that feed.
Polar
If you connect Polar, Brick syncs exercises and wellness (sleep, Nightly Recharge / HRV) via the Polar AccessLink API at your direction. Polar data is governed by Polar's AccessLink partner terms.
Wahoo
If you connect Wahoo, Brick syncs workouts from the Wahoo Cloud API (ELEMNT / KICKR and related devices) at your direction. Wahoo data is governed by Wahoo's developer API terms.
WHOOP
If you connect WHOOP, Brick syncs recovery, sleep, strain, and optional workouts via the WHOOP Developer API at your direction. WHOOP data is governed by WHOOP's developer terms.
COROS
If you connect COROS, Brick syncs workouts (and wellness when available) via the COROS Open API at your direction. Access requires COROS partner approval. COROS data is governed by COROS's partner API terms.
Suunto
If you connect Suunto, Brick syncs workouts (including FIT files when available) via the Suunto Cloud API at your direction. Access requires Suunto partner / Apizone approval. Suunto data is governed by Suunto's Cloud API partner terms.
Hammerhead
If you connect Hammerhead, Brick syncs Karoo activities (and FIT files when available) via the Hammerhead Developer API at your direction. Optional structured workout push uses Hammerhead's workout file upload when enabled. Hammerhead data is governed by Hammerhead / SRAM API licensing terms.
Route thumbnails
Small route previews on calendar cards and activity lists are rendered as inline SVG from GPS polylines — they do not use map tiles and require no map attribution.
Questions
For privacy and data-processing questions, see our Privacy Policy. Contact legal@brick.training for attribution concerns.