Legal
Privacy Policy
This Privacy Policy explains how cronoWiz handles user data. cronoWiz is designed as a local-first fitness app: no account is required, no advertising is used, and your training data is intended to stay on your device unless you choose to export, share, or connect it.
- App
- cronoWiz
- Developer
- YPT
- Effective date
- June 10, 2026
- Privacy contact
- https://ypt.ai/
Scope
This policy applies to the cronoWiz app, including the PWA at app.cronowiz.com , any Android app or Trusted Web Activity that points to cronoWiz, and the public website at cronowiz.com .
Data processed locally by the app
cronoWiz may access or process the following data to provide its fitness, training, readiness, route, sensor, camera, backup, sharing, and coaching features. This app data is stored locally in your browser or app storage, such as IndexedDB, OPFS, Cache Storage, and related local storage areas.
Training and fitness data
workouts, exercises, sets, reps, rest times, routes, diary entries, training load, readiness, RPE, pain notes, weight log, hydration, goals, preferences, achievements, levels, streaks, stickers, and similar app records.
Health and sensor-related data
heart-rate readings from compatible Bluetooth sensors, HRV measurements, estimated heart rate, cadence, step count, treadmill or bike FTMS values, calories, pace, speed, distance, altitude, and related session metrics.
Profile values you choose to enter
for example age, sex, height, weight, fitness level, equipment, limitations, goals, preferred training days, session length, nickname, coach persona, and language.
Location data
GPS/location data is used for outdoor cardio tracking, route planning, repeat-track, ghost runs, maps, distance, pace, and elevation-related features. cronoWiz does not collect location in the background when you are not using a location-based feature.
Camera data
camera frames may be processed on your device for pose detection, form checks, and camera-based HRV/PPG measurements. Camera frames are not uploaded to cronoWiz servers.
Local AI coach data
the on-device coach may read your local profile, recent sessions, training load, active plan, readiness, and chat thread to generate coaching explanations locally on your device.
Data collected by cronoWiz
cronoWiz does not operate a user-account backend and does not receive your workout diary, routes, health metrics, camera frames, profile, AI coach conversation, or encrypted backup contents as part of normal app use.
Like most websites and web apps, cronoWiz servers process limited technical data when they serve the website or app. This may include:
- IP address, user-agent, request URL, timestamp, status code, referrer, and similar standard web-server log fields generated when your browser loads cronowiz.com or app.cronowiz.com.
- On cronowiz.com, privacy-friendly first-party beacon events such as page view, click target, outbound host, scroll-depth bucket, dwell-time bucket, page path, language, screen-size bucket, and referrer host.
- No cookies, no localStorage identifiers, no advertising identifiers, and no third-party analytics SDKs are used for this website analytics system.
This technical data is used for security, abuse prevention, debugging, reliability, and aggregate traffic analytics. cronoWiz does not use it for advertising or cross-site tracking. The website beacon honors Do Not Track and Global Privacy Control signals when supported by the browser.
How data is used
cronoWiz uses data to run the features you choose to use: recording workouts, showing live metrics, estimating training load and readiness, supporting maps and routes, detecting cadence, reading compatible Bluetooth sensors, controlling compatible fitness equipment, processing camera-based form checks or HRV readings, generating local AI coaching responses, saving preferences, importing/exporting files, pairing devices, and providing security and reliability for the website and app.
Sharing and third parties
cronoWiz does not sell personal or sensitive user data. cronoWiz does not use ads and does not include third-party analytics SDKs.
Data can leave your device when you choose to make it leave your device, for example:
- Encrypted .cwbackup files that you export through the operating-system share sheet.
- .cwshare, .cwchallenge, GPX, route, workout, or session files that you choose to create, import, or send.
- Peer-to-peer or paired-device features such as TV Hub, LiveRoom, session transfer, and library exchange, when you intentionally connect another device or person.
- External services you choose to open or use from the app, such as YouTube, web radio streams, cloud drives, messaging apps, email apps, file managers, or other share targets.
Infrastructure providers that host or deliver cronowiz.com and app.cronowiz.com may process standard technical request data, such as IP address and user-agent, as necessary to provide the service, security, and logging described above.
Security
cronoWiz is served over HTTPS. App data is stored locally on your device. Encrypted backups are encrypted on your device with the passphrase you choose before they are handed to the operating-system share flow. cronoWiz does not receive or store your backup passphrase and cannot recover an encrypted backup if you forget it.
Browser and operating-system permissions, such as location, camera, Bluetooth, and motion-sensor access, are requested only when a feature needs them. You can revoke those permissions through your browser, operating system, or device settings.
Retention and deletion
Because cronoWiz does not require an account, there is no cronoWiz account to delete. Your app data remains on your device until you delete it in the app, uninstall the app, clear the site's browser/app storage, reset your browser profile, or delete the files you exported.
Files that you export or share, including backups, challenges, routes, GPX files, and share files, are under your control. To delete them, remove them from the location or third-party service where you saved or sent them.
Raw web-server logs are retained for the server log-rotation period, typically about 14 days. Aggregated traffic statistics may be retained for longer to understand usage and keep the service reliable, but they are not used for advertising or cross-site tracking.
Children
cronoWiz is not directed to children under 13. If you believe that a child has provided personal data through cronoWiz, contact us so we can review and respond.
Contact and requests
For privacy questions or requests, contact the developer through https://ypt.ai/ . Because cronoWiz stores app data locally and does not maintain user accounts, some requests can only be completed on your own device by deleting local app data or exported files.
Changes to this policy
This Privacy Policy may be updated when cronoWiz changes its features or data practices. The effective date at the top of the page will be updated when the policy changes.