Skip to main content
Ascendancify
DiscoverTrainProgressCompeteCommunityBiblePlansGoogle Play
Discover→Train→Progress→Compete→Community→Bible→Plans→Google Play→

ASCENDANCIFY / LEGAL

Privacy Policy

Last updated: November 13, 2026.

ON THIS PAGE

  1. Introduction and information we process
  2. Account and authentication information
  3. Profile and onboarding choices
  4. Training and fitness information
  5. Movement information
  6. Progression, rewards, and analytics
  7. Older reward claims retained for review
  8. Leaderboard information
  9. Clubs and shared profile information
  10. Google Play subscriptions and purchase information
  11. Optional Discord community and roles
  12. Bible reading and device storage
  13. Crash reports and diagnostics
  14. Support messages
  15. Opening support from the app
  16. Website support cookies and browser storage
  17. Your website chat choices
  18. Reminders and optional promotional notifications
  19. How we use information
  20. Cloud services and service providers
  21. Other providers and device features
  22. Security and abuse prevention
  23. Data retention
  24. Account deletion
  25. Age requirements
  26. Your choices and rights
  27. International processing and policy changes
  28. Contact

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. Depending on the features you use, information may include account and sign-in details; profile and onboarding choices; training plans and activity summaries; QRI and reward records; public leaderboard information and optional Club membership; Pro or SPECIALS subscription records; crash diagnostics; and support messages. Some detailed information remains on your device, while selected account, training and reward information is sent to our service providers.

2. Account and authentication information

When you create or use an account, we process your email address, username, account identifier, sign-in status, and information needed to maintain account access. We also record legal acknowledgements and a last-username-change time to apply account rules, including the Free and Pro rename limits. Google/Firebase provides account authentication and may process technical connection and app or device information to operate and protect that service. You can choose Continue with Google where offered. Google and Firebase process sign-in credentials, your email address and provider account identifiers to authenticate your Ascendancify account. Information made available by Google, such as a display name or profile photo URL, may also populate your authentication profile. Your public app identity uses the Ascendancify username you choose; Google profile information is not automatically published as your leaderboard identity. Linking Google to an existing account requires verifying access to that account; a matching email address alone does not authorize a merge. Ascendancify does not ask for your Google password.

3. Profile and onboarding choices

If you complete onboarding, we process your username, profile selections, goals and training preferences to personalize the app. Current onboarding does not ask for your monthly income. Older versions may have collected broad income ranges or content interests if those choices were provided. Previously saved onboarding choices can still be synchronized when a pending save is retried; existing records remain subject to the retention and deletion limits below.

4. Training and fitness information

We process your training plan, assigned exercises and targets, workout or exercise completion, training history and progression. When your account training schedule is activated, we store the time zone configured on your device. That time zone remains fixed for reward-day calculations. Our server creates training assignments and uses its own clock to determine when each reward day starts and ends. We store schedule, assignment and progression-operation records to provide training and verify rewards. Some detailed workout information stays on your device; selected account-related training and progression information is processed by our cloud providers for restoration, verification and summaries. Not every workout detail is uploaded.

5. Movement information

On assigned Movement Quest days, the app may process activity or step information, session duration, and an estimated distance to record activity and verify progression rewards. Distance is estimated from movement or step tracking; it is not GPS-measured distance. Raw accelerometer samples are not intentionally uploaded as part of normal movement reward claims.

6. Progression, rewards, and analytics

The app provides progression analytics such as streaks, completed workouts, missed days, consistency, exercise trends, and QRI progression. Some details may stay on your device, while selected progression totals and reward records may be associated with your account to support the leaderboard, restoration, and reward features. In-app Analytics means summaries of your own progression; it is not a third-party advertising analytics feature.

7. Older reward claims retained for review

Older queued reward requests that cannot be verified against a server assignment may be retained for review. They can include your account identifier, the claimed day, completed exercise identifiers and set totals, or walking steps, estimated distance, duration and session or sensor summaries. These records do not automatically earn QRI. Active account deletion includes associated schedule, assignment, progression-operation and review records, subject to the backup, log, security and provider limitations described below.

8. Leaderboard information

If you participate in the public leaderboard, other users and visitors may see your username, placement, current QRI balance, and applicable badge, tag, or nameplate. When an active Pro entitlement is verified, a Pro badge or nameplate may be displayed as a cosmetic identity feature. This status comes from the subscription entitlement record. Private billing details, purchase tokens, subscription expiry information, email addresses, and account identifiers are not displayed publicly.

9. Clubs and shared profile information

Joining a Club is optional. We store the Club name and unique join code, membership, joining time and ownership information. A Club has up to 15 members. Members can see the Club name and code, and each member's username, Club position, current QRI and applicable badge, tag or nameplate. Someone with the code may join if space is available; a code is not a promise that the Club will remain private to its original members. Club responses do not display your email, account identifier or private billing details. Leaving or deleting your account removes your membership. If the owner leaves or deletes their account, ownership passes to a remaining member; an empty Club is removed.

10. Google Play subscriptions and purchase information

Pro and the RICH, ECOM and POOKIE SPECIALS tags are separate monthly Google Play subscriptions when offered to your account. Google Play processes payment credentials; Ascendancify does not receive or store your full card number or payment credentials. We process account-linked purchase history, product and base-plan identifiers, purchase tokens and token-derived identifiers, related or replacement purchase references, subscription and refund/void status, entitlement end times, auto-renewal and acknowledgement states, test-purchase status, and verification times. We also store your selected eligible nameplate. We use these records to verify, provide, restore and reconcile subscription benefits, and prevent replayed or cross-account purchase claims. We verify purchases with Google Play and Google APIs. In app versions with promotional reminders, the last confirmed Pro subscription status may also be used on your device to select or suppress messages about Pro. We do not use purchase history to build third-party advertising profiles. We retain them as needed for entitlement, support, security, disputes and applicable legal obligations. Account deletion removes associated active account subscription and appearance records through the deletion flow, subject to the retention limitations below. Deleting the app or account does not cancel any Google Play subscription: cancel each subscription through Google Play.

11. Optional Discord community and roles

Discord is an optional external platform with its own terms and privacy practices. Joining is not required to use training or Clubs. If you request a Pro or SPECIALS Subscriber role through Discord Tickets, we may process your Discord identity, ticket messages and the minimum account and subscription information needed to verify ownership, assign the correct role and review continued eligibility. This is handled manually; there is no automatic Discord account linking. Do not send passwords, verification codes or purchase tokens in tickets. Discord retains messages and account information under its own practices. Deleting your app account does not automatically delete Discord messages or your Discord account; contact support about related role or account-mapping records.

12. Bible reading and device storage

Your device stores detailed workout history, local progression summaries, and Bible reading position, chapter progress, highlights and bookmarks. Bible reading state is not intentionally uploaded for account-wide synchronization. Cached account information helps screens load and may remain on the device between visits. Signing out does not erase all stored history. Account-scoping and cleanup behavior can differ between app versions, so do not assume another sign-in or reinstall will restore or erase everything. Older unowned reading preferences may remain locally without being assigned to an account. The current Android configuration excludes app data from Android cloud backup and device transfer; this is not a guarantee about every device or older app version. Clear app storage when needed on a shared device, understanding that this removes local-only history and does not delete your cloud account.

13. Crash reports and diagnostics

Firebase Crashlytics helps us identify crashes and errors. Reports may include stack traces, app state, technical event logs, app version, device and operating-system information, installation or session identifiers and a shortened account-derived identifier when signed in. That identifier is not your email and is not a promise of anonymity. We use these reports to understand reliability, diagnose failures and improve the app. These diagnostics are separate from the personal training summaries shown on the Analytics screen.

14. Support messages

If you contact support, we process your messages and the contact information needed to respond, such as your name, username or email address when provided. Website chat is provided through GoDaddy Conversations using Re:amaze. These providers process messages, contact information and conversation identifiers to deliver messages and replies, maintain conversation history and operate the support service. They may also process technical information such as your IP address, browser or device information, time zone and page context. Depending on the contact information and chat settings, replies may be available through the website or email. Email at ascendancifysupport@gmail.com remains a direct support route. We do not promise live in-app chat, instant replies or continuous availability.

15. Opening support from the app

When you open Support from an authenticated app screen, the app may pass your username and email to our support website as URL parameters to pre-fill contact details. Signed-out support is available without those values. Prefilled details are editable convenience information, not authentication or proof that someone owns an account. The website removes the contact parameters from the visible URL before loading the chat provider, but this cannot erase the initial browser or hosting request and associated logs. Use the plain support page or the email fallback if you prefer not to use app prefill. Chat history follows the browser/provider session and is not guaranteed to be isolated by your app sign-in or restored across devices.

16. Website support cookies and browser storage

When website chat loads, it uses browser storage, including local storage and session storage, and may use cookies or similar technologies. This storage helps recognise your chat session, restore recent conversations, remember widget settings and maintain the support connection. Some storage remains between visits; session storage usually lasts for the current browser session. Storage duration depends on your browser settings and the provider's operation. We configure the integration for support and do not enable its optional Google Analytics event forwarding. Browser storage does not link a chat to your signed-in app account. We do not promise history restoration across devices, private browsing or cleared storage.

See the provider's Privacy Notice and Cookie Policy for information about its processing and browser technologies.

17. Your website chat choices

You can manage, block or clear cookies and site storage through your browser settings. Doing so may prevent chat from working or stop previous conversations from appearing; you can use the email fallback instead. On a shared browser, another person may be able to reopen your recent conversations, so avoid sharing sensitive information and clear site storage when appropriate. Clearing browser storage does not delete messages already held by the support provider. Website support conversations are managed separately from your app account; deleting your app account does not automatically erase those conversations. Contact us about access or deletion of support information so we can identify the relevant conversation and review the request.

18. Reminders and optional promotional notifications

If notifications are enabled, supported app versions can show streak reminders, occasional Pro and Clubs promotions, and encouragement after time away. On your device, the app stores the last-open time, reminder timing, account-scoping information, limited progress hints and the last confirmed subscription or Club status to select or suppress messages. It may refresh those statuses through existing account services while the app is open. This reminder implementation does not upload its local timing preferences or add a push provider. You can disable notifications or individual categories in Android settings. Notification behavior can differ between app versions. Android permissions, battery settings and app or device state can delay or prevent delivery; timing, delivery and immediate awareness of changes on other devices are not guaranteed.

19. How we use information

We use information to provide accounts and app features, personalize training, record progression, verify rewards and Google Play purchases, provide or restore subscription benefits, operate leaderboards and Clubs, fulfil optional community roles, respond to support, diagnose failures and protect against abuse. Supported app versions also use limited subscription and Club status to select or suppress optional promotions about our own app features. We do not use training summaries or purchase history to build third-party advertising profiles.

20. Cloud services and service providers

We use third-party cloud service providers to authenticate accounts, store account data, provide crash diagnostics, deliver support messages, and verify Google Play purchases. These providers include Google/Firebase and Google Play/Google APIs, Supabase, our email delivery provider, and GoDaddy Conversations/Re:amaze for website support. The website also relies on cloud hosting. Not every app record is stored in the cloud, and local information should not be assumed to have a cloud copy.

21. Other providers and device features

The app also uses Android device features for on-device storage, local notifications and movement sensing. Service providers may process information under their own privacy terms when providing services to Ascendancify. We do not use a third-party advertising SDK or Advertising ID for app advertising; optional notifications about our own Pro and Club features are described above.

22. Security and abuse prevention

We may process limited account, device, network, and request information to maintain service security, prevent abuse, investigate misuse, and enforce service limits. Our service providers may also maintain security and operational records. We use reasonable safeguards, but no online service can guarantee absolute security.

23. 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.

24. Account deletion

Start deletion in the app or request it through the public account-deletion page. Ownership verification and a fresh sign-in may be required. The flow removes the authentication account and associated active profile, onboarding, cloud training, reward, leaderboard, Club membership, subscription and appearance records. Interrupted or failed steps can leave the account pending deletion until you retry or contact support. Limited security records, including an account-derived deletion marker used to prevent accidental recreation during incomplete deletion, may remain, as may provider backups, operational logs or records required for legal/security purposes. Device-local or older unowned preferences may require separate cleanup. Website support conversations and Discord records are handled separately; contact support about those records. Deleting your app or account does not cancel Google Play subscriptions. Cancel each subscription in Google Play. Signing out is not deletion.

If re-authentication is required to complete deletion, some account data may remain temporarily until you sign back in and confirm the deletion. Instructions will be shown in the app.

25. Age requirements

Ascendancify is intended for users aged 18 and older. We do not request or store date-of-birth information for age verification. If we later obtain reliable information that an account does not meet our eligibility requirements, we may restrict access and take appropriate steps regarding the account and associated data in accordance with applicable law and our retention obligations.

26. Your choices and rights

You can use device settings to control activity-recognition permission; restricting it may affect Movement Quest. You can also turn notifications off or manage individual notification categories in Android settings. 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.

27. 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.

28. Contact

For privacy questions or requests, email ascendancifysupport@gmail.com. For account-deletion steps, see the public deletion page.

Email Ascendancify support · Account deletion instructions

Privacy PolicyTerms of ServiceAccount deletionSupport
Ascendancify

Ascendancify by zxqrify.

Train. Progress. Compete. Read.
Build lasting discipline.

Fitness trainingProgress analyticsBible readerCommunity feedbackPrivacy PolicyTerms of ServiceDelete AccountSupport

Support

ascendancifysupport@gmail.com
© 2026 AscendancifyBuilt for real development.