Who runs Lapivo
CRYOSS, an independent app studio in Warsaw, Poland, operates Lapivo. Contact lapivo@cryoss.com for privacy and support.
What we process
Guest runs stay on your device. With an account, we store your email, display name, declared age band and country, document acceptance versions, and the runs you sync: GPS route, timestamps, pace, elevation and heart rate when recorded. Team membership, results, reports, preferences and credit history support the features you use.
Purpose and visibility
We use these data to sign you in, sync runs, calculate results, maintain private teams, provide support and protect the service. Team members see profile and result summaries; raw routes and heart rate stay private. There is no public profile search or direct messaging.
Your choices
You control location and health permissions on your devices. Signing in enables sync for account runs; earlier guest runs are imported only when selected. Advertising privacy choices are managed separately. Accepting the terms or reading this notice does not grant advertising consent.
Providers
OVH hosts the API and database; home.pl delivers sign-in emails. MapLibre renders maps using OpenFreeMap by default: tile requests reveal your IP and the viewed map area to that provider. Google AdMob/UMP handles optional rewarded videos for eligible adults, and banners on Today, History and Profile under the age protections described below, plus consent and device/ad signals. Ads are not loaded or shown during active or paused runs, recording recovery or saving. Apple Watch and Wear OS are ad-free. We do not pass GPS routes, heart rate or pace to advertising providers. Their processing may occur outside your country.
Young runners
Lapivo is for ages 13+. Age is self-declared. Users aged 13–17, guests and users whose age is unknown may see non-personalized banners with child age treatment and a G content limit. Rewarded videos still require an eligible adult account. Under-18 runners must declare that they have a parent or legal guardian’s permission. This self-declaration allows private team participation; it does not verify the parent’s identity. Revoked permission blocks team access. There is no identity-document upload to Lapivo.
Retention and security
Account data remain until you delete them or the account. HTTPS protects transfers; access is restricted. Local server backups run daily and keep up to seven daily copies; an offsite backup is not yet in operation. Deleted data can remain in those copies until rotation. Minimal deletion and reward transaction identifiers help reject delayed reuploads and duplicate rewards. Support messages are kept as needed to resolve requests and meet applicable obligations. When you use seasons, we also store journey selections, XP grants, achievement awards and cosmetic ownership. Deleting a run removes its route data and links to running-signature artwork, but already-earned XP, achievements and cosmetics remain. Until account deletion, we retain minimal award records, rule versions, activity timing and keyed activity fingerprints to prevent duplicate grants. These fingerprints are not public. Account deletion removes your season records.
Access, export and deletion
Use Profile to export your account data or delete runs/account. You can also request account deletion at the link below. Email us to request correction, restriction or other applicable rights, withdraw optional choices, or raise a complaint. You may contact your local data protection authority. Material notice changes will be identified by a new version.