1. Essential account and device storage
FitVoya uses browser storage for the signed-in session and authentication tokens, language, install prompts and per-account journal-photo display preferences. Step-counting state may be stored on the device. This keeps the account usable and remembers presentation choices; it is not proof of consent. The exact authentication-cookie behavior can depend on the hosting/sign-in flow.
2. Analytics and outside services
Account-linked feature-usage events are stored on the server, even when they do not rely on analytics cookies. External sign-in and font services have their own data practices. No advertising-cookie or nonessential cookie-consent system is currently implemented. Before adding nonessential trackers, the operator must inventory them, disclose names/providers/purposes/duration and obtain any required prior consent with an equally accessible refusal and withdrawal option. This page is not a functioning cookie-consent banner.
3. Your controls
Sign-in offers a keep-me-signed-in choice, checked by default. Unchecking it stores the session only for the current browser session rather than persistent device storage; browser session restoration may retain it. You can sign out, clear site data in browser settings and change supported in-app preferences. Clearing device storage may remove the session and local settings but does not erase account records stored in the cloud. Blocking essential storage may prevent sign-in or other features. Device motion/health permissions are controlled separately in phone or browser settings.