ASCENDANCIFY / LEGAL
Privacy Policy
Last updated: October 1, 2026.
1. Introduction and information we process
This Privacy Policy explains how Ascendancify processes information when you use the Android app, our website, or contact support. The app includes training, movement, progression, leaderboard, and Bible-reading features. Depending on the features you use and whether you have an account, information may include account and sign-in details; profile and onboarding choices; training plans and selected activity records; movement summaries submitted for reward checks; progression and leaderboard records; diagnostic information; and support messages. Some detailed app information remains on your device, while selected account and reward information is sent to our backend.
2. Account and authentication information
Firebase Authentication handles your email address, password credential, Firebase account identifier (UID), sign-in state, and authentication/session credentials. The app obtains a Firebase ID token to authenticate requests to protected backend functions; the token is not displayed publicly. Firebase and Google may also process network and device/app information associated with authentication and operation of their services, such as IP address, client or SDK details, and app identifiers.
3. Profile and onboarding choices
If you complete onboarding while signed in, the app may send your username, goals, training preferences, selected exercises, unit preference, user type, and records of relevant agreements or acknowledgements to Ascendancify's backend. Depending on choices shown in the app, onboarding can also include a broad income range or content-creation preferences such as a topic or selected platforms. We do not receive your date of birth through the 18+ acknowledgement.
4. Training and fitness information
The app processes training plans, assigned exercises and targets, sets and reps, workout and exercise completion, training-day records, and progression. Detailed set logs and much of your personal workout history are stored locally. A serialized training plan and selected task or completion information may be backed up to Supabase when supported sync or reward features are used. Reward verification can receive limited evidence such as the assigned training day, completed exercise identifiers, and completed/required set counts; this is not a routine upload of every set you perform.
5. Movement information
On assigned Movement Quest days, Android activity or step sensing may be used to track a session. A reward request may send a session identifier, date, step count, duration, estimated distance, and sensor type to verify the activity. Distance is estimated from movement/step tracking and is not measured using GPS. Raw accelerometer samples are processed transiently by the app and are not intentionally uploaded as part of normal movement reward requests.
6. Progression, rewards, and analytics
The app keeps local progression and personal analytics such as streaks, workout history, consistency, missed days, and trends. Selected task and reward events, including relevant training-day completion evidence, and progression totals are also associated with your account in Supabase, including QRI balance and competitive progression values. These records support reward verification, account restoration, and leaderboard operation. In-app Analytics refers to progression summaries shown to you; the current app does not add third-party advertising analytics to those screens.
7. Leaderboard information
If you participate in the public leaderboard, other users and visitors may see your username, placement, Lifetime QRI, and badge or nameplate. Your email address, Firebase UID, authentication credentials, private profile information, and spendable QRI balance are not included in the public leaderboard projection.
8. Bible reading and device storage
The app uses SQLite and Android Preferences to keep app state on your device. Local information can include detailed workout and set history, personal analytics inputs, profile or plan caches, movement-session state, and Bible reading position, chapter progress, highlights, and bookmarks. Bible reading state is primarily local and is not promised to synchronize across accounts or devices. The app's Android configuration excludes app data from Android cloud backup and device transfer. Copies you create outside those Android features are outside the app's control.
9. Crash reports and diagnostics
Firebase Crashlytics is enabled to help identify app crashes and errors. It may process crash reports, stack traces, app version/build information, and technical app/device metadata such as device model and operating-system version. The app also sends limited diagnostic events and safe context tags. A shortened hash derived from the Firebase UID may be attached as a pseudonymous identifier to help relate diagnostic reports; it is not the UID itself. Custom non-fatal reports are constructed to avoid including exception messages or text you enter, but technical reports can contain diagnostic context generated by the software and device.
10. Support messages
The app contains a support form for a subject and message. Its current code attempts to submit the message with a Firebase-authenticated request. The prepared server function is designed to verify that request, associate it with the Firebase UID and account email, and send the message to ascendancifysupport@gmail.com through Resend, with the account email used for replies. The current app repository's deployment notes say this message-delivery function has not been deployed, so in-app delivery may fail; when it fails, the app tells you the message was not delivered and keeps the draft. The current function does not automatically attach your username; include it in your message only if needed. Email is the available contact route. We do not offer two-way in-app support chat.
11. How we use information
We use information to create and authenticate accounts, save selected profile and training information, provide supported restoration, calculate or verify progression rewards, operate the leaderboard, show your personal analytics, respond to requests when support delivery is available, diagnose crashes, and protect the service from abuse. The current app does not include advertising functionality.
12. Authentication and cloud services
Firebase Authentication manages account sign-in. Supabase database services and Edge Functions provide selected profile sync, onboarding, training-plan and task backup, reward verification, leaderboard, restoration, account deletion, and request protection. Protected functions verify Firebase authentication on the server. Not every app record is sent to Supabase, and a local record should not be assumed to have a cloud copy.
13. Service providers
The website is hosted with Firebase Hosting. The app uses Google Firebase Authentication and Firebase Crashlytics, Supabase database and Edge Function services, and Android platform features for local storage and movement sensing. Google/Firebase may process website connection and request information needed to serve and protect the site. Resend is the email provider in the prepared support-delivery code; the message-delivery function is not currently deployed according to the app repository's setup notes, so Resend should not be understood as currently receiving support messages through that route. We have not identified an active ad system or Advertising ID use in the current app implementation.
14. Security and abuse prevention
Backend functions verify Firebase tokens before processing account-protected requests and apply request limits. For abuse prevention, the backend may process account identifiers and request information such as IP address and user-agent details; rate-limit records can include account-based counters or a hashed request-origin identifier. Service providers may separately keep their own security and operational logs. No method of transmission or storage can be guaranteed completely secure.
15. Data retention
We retain account, training, reward, diagnostic, and support information for as long as reasonably needed for the purposes described here, service operation, security, and applicable requirements. The app does not publish one retention period covering every provider, log, or record. Provider backup and operational-log retention may follow that provider's systems and settings, which are not all controlled by the app.
16. Account deletion
You can start deletion in the app's account settings or request it by email using the public account-deletion page. The in-app flow sends an authenticated request to delete the account's supported records from active Ascendancify cloud tables and then requests Firebase account deletion. If recent sign-in is required, cloud records may already have been removed and you will need to sign in again and retry to finish deleting the Firebase account. Selected local database tables and account preferences are cleared after the cloud and Firebase steps complete; if a deletion step fails, local cleanup does not run. This flow does not establish that every legacy local preference, provider log, or backup is immediately erased. Signing out only ends the session and is not deletion.
17. Children and age requirements
Ascendancify is intended for adults who meet applicable age requirements. The app displays an 18+ acknowledgement, but does not perform government-ID age verification through that acknowledgement. Contact us if you believe a child has provided personal information through the service.
18. Your choices and rights
You can use device settings to control activity-recognition permission; restricting it may affect Movement Quest. You can request account deletion through the app or public deletion page and contact us about access, correction, or other privacy requests. Rights and available choices depend on your location. We may need to verify account ownership before acting on a request.
19. International processing and policy changes
Our service providers may process information in locations outside your country. We may revise this policy when the app or its data practices change. The date below identifies the current version; we will provide notice of material changes where appropriate or required.
20. Contact
For privacy questions or requests, email ascendancifysupport@gmail.com. For account-deletion steps, see the public deletion page.