CADENZ · Virzy Guns Production

Privacy Policy

This policy describes the current CADENZ app data flows and privacy controls, including how users can request account and associated-data deletion.

Effective September 27, 2026

Operator and scope

CADENZ is a running and cycling cadence-music app by Virzy Guns Production, operated by PT KREASI VIRZY NUSANTARA, Indonesia.

This policy covers the CADENZ mobile app and its account, workout, subscription, and app-service data flows.

Information CADENZ processes

  • Account information such as email address and authentication credentials handled through Supabase Auth.
  • Optional profile information such as name, location text, birth date, weight, height, and running experience.
  • Run information such as time, distance, pace, cadence, music history, GPS quality, and an optional mapped route.
  • Precise location during an optional mapped run, where permission has been granted.
  • Motion and step data for optional running AUTO cadence. Cycling V1 does not treat phone steps or motion as pedal RPM.
  • Subscription and entitlement status from the app stores, RevenueCat, and CADENZ backend services.
  • Crash and diagnostic information needed for reliability and support.
  • Technical network information processed by service providers to operate and protect online services.

How information is used

  • Authenticate accounts and support password recovery.
  • Provide cadence-based music, workout tracking, maps, recovery, history, and training features.
  • Synchronize eligible completed workouts when the signed-in user has granted the required route-sync consent and sync is enabled.
  • Verify subscriptions and control Premium access.
  • Diagnose crashes, protect the service, and improve reliability.

Location, route data, and consent

Precise location is used only when the user chooses mapped running and grants the required device permission. Accepted GPS points are processed locally during the workout. CADENZ does not use route data as advertising analytics.

Completed route synchronization is account-specific and consent-controlled. Withdrawing route-sync consent prevents future queued precise-route uploads from proceeding. A withdrawal does not by itself represent a promise that a route already synchronized to the account has been deleted.

Service providers

  • Supabase for authentication, database services, and signed backend requests.
  • Google Maps SDK for Android for map display where the feature is used.
  • RevenueCat for subscription management.
  • Apple App Store and Google Play for payment processing.
  • Sentry for crash and diagnostic reporting when configured for the release.
  • Amazon S3 and Amazon CloudFront for private audio delivery; Supabase Storage may be used as an alternative delivery path.

Private audio is delivered through Amazon CloudFront backed by AWS S3 when selected by server configuration; Supabase Storage is available as a configured fallback. Audio is authorized server-side with short-lived signed URLs.

Your controls

  • Update supported profile information in the app.
  • Delete individual workouts from history.
  • Revoke route-sync consent from Settings for future eligible route synchronization.
  • Revoke location, background-location, or motion permission in device settings.
  • Delete your CADENZ account from Settings. Local finalization may retry if an interrupted cleanup cannot complete immediately.
  • Request deletion of your CADENZ account and associated account data at the CADENZ account deletion page. This request can be sent without signing in to or reinstalling the app.
  • Contact the owner using the email shown below for other privacy or data requests.

Retention and security

Active-workout GPS points are retained locally only as needed to operate and recover the workout. Completed local workout information remains until the user deletes it, while synchronized account data is subject to deletion and provider backup-retention processes.

CADENZ uses HTTPS/TLS in transit, short-lived signed URLs for private audio delivery, server-side entitlement checks for Premium access, authenticated owner boundaries for account data, and platform-level authentication controls.

Children and policy updates

CADENZ is not designed or marketed as a service for children. This policy does not set an age threshold. Follow age requirements that apply under local law or in the store where you access CADENZ.

This page may be updated as CADENZ data flows, service providers, or applicable requirements change. Material updates will be reflected here with a revised effective date.

Owner contact

Virzy Guns Production is operated by Virzy Guns. Questions, privacy requests, and data deletion requests may be sent to founder@virzyguns.com.