ŚCIEŽKA TRUST CENTER
Trust, Privacy, and Resilience
Effective November 4, 2026
Ściežka is an active pre-commercial product. The current service is free and paid billing is not enabled. This page describes controls present in the reviewed source tree and clearly identified limits; deployed operation requires separate evidence. It is not a security certification or uptime guarantee.
Control of your route data
- Saved routes and precise location are private by default.
- Browser location is requested only after you activate the location control.
- Standard route formats can be imported and exported.
- Authenticated users can request an account export and full account deletion.
- Community Routes are opt-in, provenance-filtered, redacted, and published only after manual approval unless the author has an explicit, revocable fast-track grant.
No attention-market business model
Ściežka does not run ads, sell personal data, or use behavioural advertising. Optional AI Route Copilot requests process only the active route prompt and map waypoints you submit in that session; private saved routes are never used for model training. Connected Strava, Garmin Connect, Wahoo Fitness, COROS, and Suunto data is never used for AI, model training, advertising, analytics, public sharing, another user, or paid entitlements.
Provider boundaries
Server-only provider credentials stay out of client source; authenticated browser sessions necessarily use Firebase-issued tokens. Production routing and geocoding fail closed unless explicit endpoints are configured. The current pre-commercial deployment may use the existing public BRouter and Photon services under an owner-enabled exception; they provide no availability SLA, and contracted or self-hosted endpoints remain an external launch gate. Fonts are self-hosted, and map attribution remains visible. If billing launches, checkout will be provider-hosted: full card numbers and card security codes will be collected only by that provider, while Ściežka may receive a provider token, masked card metadata, and payment status.
Account lifecycle
Export jobs fail rather than silently returning incomplete archives. Account deletion is confirmed only after the deletion workflow has actually completed. Status tokens are sent in an authorization header and are not accepted in URLs.
Current limits
Ściežka does not claim a security certification, paid-country approval, global payment availability, or a service-level agreement. Community Routes use private media storage, malware scanning, manual moderation, reports, takedowns, and post-publication sampling for trusted authors. Community POIs, advertising, and paid checkout remain disabled.
Community operations
Community moderators and trust managers use a protected, non-indexed console. Access is capability-based and audited; ordinary users cannot list accounts or moderation queues. Staff access never bypasses route provenance checks, photo processing, reporting, withdrawal, or deletion controls.
Report a security issue
Send a private report to support@scezka.com with the subject “Security report”. Use synthetic data and do not include another person's information, real Strava data, credentials, or production records.