ŚCIEŽKA LEGAL
Privacy Policy
Effective November 4, 2026
Ściežka is a free bicycle route-planning and maintenance application. This policy explains what personal data Ściežka processes and how users can control it.
Data we collect
- Account identifiers, display name, profile image, and email supplied by Firebase.
- Routes, bicycles, components, maintenance records, and settings you create.
- When you connect Strava: your Strava athlete identifier, granted OAuth scopes, encrypted access and refresh tokens, bicycle gear data, and cycling activity metadata needed for activity import and bicycle wear calculations.
- Strava webhook events used to reflect new, changed, deleted, or deauthorized data without polling.
- When you optionally connect Garmin Connect, Wahoo Fitness, COROS, or Suunto: your connected account identifier, granted OAuth 2.0 scopes, encrypted access and refresh tokens, user-selected planned courses exported to your devices, and imported cycling activity files (.FIT and summary metadata, including recording device model) plus webhook notifications for new workouts and deauthorization.
How data is collected and used
Data comes directly from you, from the authentication provider you choose, and—only after your express OAuth 2.0 consent—from Strava, Garmin Connect, Wahoo Fitness, COROS, and Suunto API responses and webhooks. Ściežka uses it to authenticate you, save your work, import your own activities, update your own bicycle-maintenance records, and render your personal exploration tile map (Explorer Tiles). Exporting a planned course to a connected account (such as “Send to Garmin” or “Send to Wahoo”) occurs only upon your explicit action with notice of transfer to that provider (including Garmin Connect's privacy policy at https://www.garmin.com/privacy/connect). Strava data is shown only to the athlete who authorized it, and imported activities from Strava, Garmin Connect, Wahoo Fitness, COROS, and Suunto remain private to the authorizing rider and are ineligible for public Community Routes.
Community Routes
When you intentionally submit a route for Community Routes, the approved route geometry, title, summary, description, public author label, locality, selected route places, cues, notes, itinerary events, and selected photos become public. Your account identifier and email are not included in the public route response. Routes originating from Strava, Garmin Connect, Wahoo Fitness, COROS, or Suunto are not eligible for Community Routes.
Uploaded originals are held briefly in a private quarantine area, checked for malware, decoded within strict limits, rotated, converted to metadata-free WebP derivatives, and deleted from quarantine. Approved derivatives remain private in storage and are delivered through Ściežka only when they belong to an approved public route. GPS and other EXIF metadata are not included in the published image.
Retention and deletion
Raw Strava activity and webhook payload data is treated as a short-lived cache and is retained for no longer than seven days. Under the current conservative policy, Strava-derived ride-wear records and their effect on maintenance totals are also reversed and deleted with the source cache; independent maintenance records you enter without Strava remain yours. Personal exploration tile map indices (Explorer Tiles) are retained as derived summary data and remain available until you disconnect Strava, request deletion, or delete the corresponding activity. Disconnecting Strava first permanently deletes local Strava-originated records and derived personal data (including your exploration tile map) and clears local tokens and identifiers. Ściežka then requests remote authorization revocation. If Strava is temporarily unavailable, an encrypted retry is durably queued and operationally alerted; Ściežka does not report upstream revocation as complete until it succeeds.
Disconnecting Garmin Connect, Wahoo Fitness, COROS, or Suunto (in Account & Privacy or Garage settings, via the provider's own account settings deauthorization webhook, by deleting your Ściežka account, or by emailing privacy@scezka.com) permanently deletes local OAuth tokens, connected identifiers, and provider-originated activity records from Ściežka and revokes upstream OAuth tokens. Users can access, export, or delete their data at any time via in-app controls or privacy@scezka.com.
Service providers and transfers
Ściežka hosts and stores connected account and activity data on Google Cloud Platform (Cloud Run and Cloud SQL PostgreSQL in europe-west1, Belgium, EU), uses Google Firebase Authentication for account sign-in, and uses Cloudflare for TLS/DNS edge routing and inbound email routing. Route waypoints are sent through Ściežka's server to BRouter for route calculation, while location-search text and selected coordinates are sent to Photon for forward or reverse geocoding. The current pre-commercial service may use their public endpoints, which have no availability guarantee and may throttle reasonable-use traffic. These providers process data only to operate the requested feature.
No sale or third-party sharing: Ściežka never sells, rents, licenses, monetizes, or shares Strava, Garmin Connect, Wahoo Fitness, COROS, or Suunto user data with third parties, advertisers, data brokers, analytics networks, or other users.
AI and machine-learning prohibition: Zero artificial-intelligence (AI), large-language-model (LLM), or machine-learning systems receive, process, analyze, cache, evaluate, benchmark, or train on Strava, Garmin Device Sourced Data, Wahoo Fitness, COROS, or Suunto data (whether raw, derived, anonymized, or aggregated).
- Resend: Transactional account welcome/service emails and optional opt-in product update broadcasts are delivered via Resend from notify.scezka.com and news.scezka.com. Marketing emails are sent only after explicit opt-in and include one-click unsubscribe.
- Garmin Connect: When you explicitly connect Garmin Connect, Ściežka exports user-selected planned courses to your Garmin devices via the Garmin Courses API and imports newly recorded ride files (.FIT) and device model metadata via the Garmin Activity API into your private ridden tracks, Explorer Tiles, and Garage maintenance records. Transfers to Garmin Connect are subject to Garmin's privacy policy (https://www.garmin.com/privacy/connect). Imported Garmin data displays required Garmin device model attribution, is never sold or shared with third parties, is never processed by or used to train AI/ML models, and is permanently deleted when you disconnect Garmin Connect or delete your account.
- Wahoo Fitness: When you explicitly connect Wahoo Fitness via OAuth 2.0, Ściežka syncs user-selected planned routes to your Wahoo ELEMNT cycling computers via the Wahoo Cloud API and imports completed .FIT workout files via webhook into your private ridden tracks, Explorer Tiles, and Garage maintenance records. Wahoo data is never sold or shared with third parties, is never processed by or used to train AI/ML models, and is permanently deleted when you disconnect Wahoo Fitness or delete your account.
- COROS & Suunto: When you explicitly connect COROS or Suunto via OAuth 2.0, Ściežka exports user-selected planned courses to COROS DURA cycling computers, COROS watches, and Suunto devices and syncs completed .FIT workouts (including via COROS EU regional API endpoints where applicable) into your private ridden tracks, Explorer Tiles, and Garage maintenance records. COROS and Suunto data is never sold or shared with third parties, is never processed by or used to train AI/ML models, and is permanently deleted when you disconnect the provider or delete your account.
- GitHub: When you submit feedback or issue reports, diagnostic report details and message text (excluding your email address, identity, or any Strava-derived data) are tracked in private GitHub issues for issue resolution.
Access, support, and requests
Your imported activities are available inside your authenticated account. For access, correction, privacy, or deletion requests, use the in-app controls or email privacy@scezka.com. For technical support, email support@scezka.com or submit an in-app . Do not include OAuth tokens or other secrets in a support request.
Strava usage monitoring
Strava may monitor and collect usage data relating to Ściežka's access to the Strava API and may use that usage data as described in the Strava API Policy.