Privacy policy

No ads. No sign-up. Your camera feed and workout history stay on your device. CINDY has no analytics and does not track you across apps or websites.

Last updated: 14 October 2026

Camera

CINDY needs camera access to count reps. Camera images are processed on your device and are never sent to a server.

You can revoke camera access in Settings. Rep counting requires this permission.

History and recordings

Workout history and optional profile names are stored on your device. You can delete workouts in History.

Optional video and debug recording are off by default. Recordings stay on your device until you delete them. Exporting or sharing creates a separate copy at the destination you choose. Deleting the original does not delete those copies.

Ordinary workouts and recordings remain local. Optional public challenges use the separate publication choice described below.

Apple Health

Apple Health is optional. With your permission, CINDY saves completed workouts to Health and checks its own saved workouts to avoid duplicates. Apple manages Health storage and syncing.

You can change Health permissions in Settings. Deleting a workout from CINDY’s history does not delete its copy in Health. You can manage those copies in the Health app.

Optional public challenges

Challenges are optional and need a network connection. Creating a challenge sends its title, visibility, duration and retention choice. Browsing a board retrieves its public rules and leaderboard. Ordinary workouts remain offline and local.

Only when you choose Publish does CINDY send your nickname, selected score, challenge code and scoring metadata, including attempt timing, app/rules/measurement versions and the continuous clock choice. Camera images, photos, video, pose data, Apple Health data and your workout history are not uploaded.

Published nicknames and scores are visible to anyone who opens the challenge link. Public challenges also appear in the directory. Unlisted means anyone with the link can view the board; it does not mean private. Challenge QR codes contain only the public link, and are generated locally.

The challenge service uses Cloudflare Workers and a private D1 database. App Attest and private participant credentials protect changes; these are not shown on the public board. No analytics or request-body/token logging is added. Network providers process connection information to deliver requests.

The organiser chooses 7, 30 or 90 days of leaderboard retention after the 24-hour submission grace period. Expiry removes participant scores and attempt metadata and permanently reserves the code. Withdrawing in the app removes all your attempts from that board. An optional private recovery code can restore challenge participation; it is not a public profile or proof of one human. Losing it can prevent recovery. Local workout history stays on your device.

Feedback and contact

CINDY is developed by Velislav Gerov. For privacy questions, contact velislav@gerov.dev.

TestFlight feedback is optional. Apple and the developer receive the information you submit, which may include messages, screenshots and diagnostics. The developer uses it to answer questions and improve the app. Share only what is needed to explain the issue.

Policy updates

This policy will be updated if the app’s data handling changes.