Privacy Policy

Radha Naam Jap Counter: Sadhna

Introduction

Radha Naam Jap Counter: Sadhna (“the app”, “we”, “our”, or “us”) is operated by Infinite Swipe Labs. We are committed to protecting your privacy and providing a peaceful, secure and respectful devotional experience.

This Privacy Policy explains what information may be collected, stored, processed, shared and used when you use the app, including its japa-counting, Mini Jap, cloud synchronisation, Group Sadhna, Naam Sathi, Bhakti Essentials, notification and advertising features.

By downloading, accessing or using the app, you acknowledge the practices described in this Privacy Policy. If you do not agree with this Privacy Policy, please do not use the app.

For privacy-related questions or requests, contact:

Infinite Swipe Labs
Email: infiniteswipelabs@gmail.com

1. Information Stored Locally on Your Device

The app stores certain information locally on your device to provide its core features.

This information may include:

Daily japa count
Current round count
Mala count
Total japa and mala progress
Current and longest streaks
Practice history
Grace-day or streak-saving status
Daily japa goal
Days practiced
Weekly and monthly progress
Reminder settings, reminder time and reminder message
Notification preferences
Selected devotional or display name
Selected japa mode
Private Mode and Private Mode (No Count) preferences
Mini Jap session status and temporarily pending counts
Selected background for the Japa Counter screen
Sound and vibration preferences
Mood or devotional-feeling selections
App theme and appearance settings
Tutorial and prompt-completion status
Journey, level and achievement progress
Temporary unsynchronised Group Sadhna contributions
Temporary synchronisation and recovery information
Bhakti Essentials visibility and feature-prompt status
Other app preferences and settings

This information is used to provide features such as:

Japa counting
Mala tracking
Mini Jap
Progress tracking
Streaks
Reminders
Goals
Achievements and levels
Private display modes
Background personalisation
Theme preferences
Group Sadhna contribution recovery
App tutorials and feature prompts

Private Mode and Private Mode (No Count) are display options. They do not provide anonymous use of the app and do not prevent account-linked information from being stored or synchronised where another app feature requires it.

Background selection is used to personalise the Japa Counter screen and is stored as an app preference.

Local information generally remains on your device unless it is:

Deleted or reset through an applicable app feature
Synchronised to your account where applicable
Replaced during normal app operation
Cleared through your device settings
Removed when the app is uninstalled

Uninstalling the app removes local information from that device but does not necessarily delete information already stored in Firebase or otherwise associated with your account.

2. Mini Jap and Picture-in-Picture Mode

Mini Jap allows you to continue using a small japa counter while navigating outside the app.

Mini Jap uses Android’s Picture-in-Picture functionality to display a compact version of the counter in a floating system window.

When you use Mini Jap:

Your japa count may be stored locally.
Your japa may update the same daily, lifetime, progress and cloud-linked records used by regular japa sessions.
The app may temporarily store whether a Mini Jap session is active.
Temporarily pending counts may be stored until they can be safely processed or synchronised.
Mini Jap usage may be recorded as a feature interaction or japa-session event in Firebase Analytics.
Session details may be included in account-linked daily-japa statistics where applicable.

Mini Jap does not give the app access to the content of other apps.

We do not use Mini Jap to:

Read what you type in another app
Capture the screen of another app
Record another app’s audio
Access another app’s messages or private content
Monitor which content you view in another app
Collect information from another app merely because Mini Jap is visible

Picture-in-Picture is an Android display mode that allows supported app content to remain visible in a small window while another app or screen is being used.

You can close Mini Jap using the controls made available by Android or return to the app where applicable.

3. Google Sign-In and Firebase Authentication

The current version of the app requires Google Sign-In to access its main features.

Google Sign-In and Firebase Authentication may provide or process:

Your Google display name
Your email address
Your Google profile picture or profile-picture URL
A unique Firebase user identifier
Authentication tokens
Account-session information
Information required to maintain your authenticated session

We use this information to:

Create and identify your app account
Keep you signed in securely
Associate cloud backups with your account
Synchronise supported progress across devices
Enable Group Sadhna and Naam Sathi features
Store account-linked japa statistics
Record Bhakti Essentials interest where you choose to express it
Manage account-related requests
Process account and data-deletion requests
Protect account-specific information from unauthorised access

Your email address is not displayed publicly to Group Sadhna members.

Other users may see your chosen display name and the Group Sadhna or Naam Sathi information described in this Privacy Policy.

Google Sign-In and Firebase Authentication are provided by Google and are also subject to Google’s own terms and privacy policies.

4. Cloud Backup and Synchronisation

The app uses Firebase Cloud Firestore to store and synchronise certain account-linked information.

Cloud backup or synchronisation information may include:

Daily and lifetime japa totals
Mala totals
Current and longest streaks
Days practiced
Weekly and monthly progress
Daily-goal information
Journey, level and achievement progress
Relevant app progress
Backup and synchronisation timestamps
Account and profile information required for synchronisation
Information required to recover or reconcile pending Group Sadhna contributions

The app may perform automatic backups and may also provide a manual synchronisation option such as “Sync Now”.

Cloud synchronisation is intended to help protect your progress and make supported information available after signing in on another supported device.

Synchronisation may require an internet connection.

Information stored locally and information stored in the cloud may not always update at exactly the same time, particularly when:

The device is offline
A network connection is unstable
A japa session has not yet been completed
A contribution is waiting to be synchronised
Firebase services are temporarily unavailable

We cannot guarantee that every local action will be synchronised immediately or that all information can be recovered in every circumstance.

5. Account-Linked Daily Japa Statistics

The app may store account-linked information about completed japa sessions in Firebase Cloud Firestore.

This may include:

Date or date key
Session identifier
Firebase user identifier
Display name
Email address
Japa count
Mala count
Session duration
Japa mode, including Mini Jap where applicable
Session-completion reason
Completion timestamp
Number of sessions completed on a particular day
Total japa completed on a particular day
Total duration of completed sessions on a particular day
First and most recent japa time for that day
Information about the most recently completed session

We may use this information to:

Understand genuine daily app usage
Measure the number and size of completed japa sessions
Understand which japa modes are used
Improve session reliability
Investigate counting or synchronisation issues
Understand app engagement
Make product and feature decisions
Maintain private operational statistics

These records are separate from Firebase Analytics events and may be directly associated with your Firebase account.

They are not displayed to other ordinary app users merely because they use the app.

Information that becomes visible through Group Sadhna is described separately below.

6. Anonymous or Aggregated Daily Japa Information

The app may contribute completed japa amounts to a private daily aggregate used to understand the collective amount of japa performed through the app.

This aggregate may contain information such as:

Date
Collective japa total
Number of aggregate updates
Most recent update time
General contribution source

This private aggregate is designed not to contain:

Your name
Your email address
Your Google profile picture
Your individual Firebase user identifier
Your individual lifetime japa total
Your individual Group Sadhna membership

The aggregate is intended for internal operational and product understanding and is not intended to identify individual users.

7. Group Sadhna Information

The Group Sadhna feature allows users to create or join a shared devotional japa goal.

The following information may be stored in Firebase Cloud Firestore:

Group name
Group identifier
Invite code
Group creator identifier
Administrator identifiers
Administrator display information
Target japa count
Current group total
Duration
Start and end time
Group status
Group visibility
Joining policy
Maximum member capacity
Active member count
Group membership
Member display names
Individual member contributions
Member roles
Join and leave timestamps
Rejoin information
Join requests
Join-request status
Join-request review information
Group invitations
Invitation status
Group-completion or expiry records
Group-card summary information
Weekly Group Sadhna creator statistics and recognition information
Relevant creation, update and activity timestamps

Information visible to Group Sadhna members

While a user remains part of a Group Sadhna, other active members may see:

The user’s display name
The user’s contribution to that group
The group’s overall progress
Membership status
Administrator or member role
Information required to show the group’s active membership

This visibility helps members understand the progress of the shared sankalp and support one another in completing it.

Personal japa performed outside Group Sadhna is not displayed to other Group Sadhna members merely because they are members of the same group.

Information visible to group administrators

When a user requests to join an open Group Sadhna, the group administrator may see information intended to help review the request, including:

Display name
Current devotional level
Total japa
Total malas
Days practiced
Current streak
Approximate daily average japa
Join-request message, if provided
Request time and status

By submitting a request to join an open Group Sadhna, the user understands that this information may be shown to the group administrator.

Weekly Sadhna Sevaks recognition

The app may use Group Sadhna activity to recognise users who help create successful Group Sadhnas. For this purpose, a successful Group Sadhna means a Group Sadhna created by the user that becomes active during the applicable weekly period.

For this feature, the app may process or store information such as:

Firebase user identifier of the original Group Sadhna creator
Creator display name
Number of qualifying Group Sadhnas created by that user during the applicable week
Group activation timestamps
Weekly ranking or recognition position
Week identifier and related calculation information

A limited weekly celebration may display to other signed-in app users:

The recognised creator’s display name
Their weekly recognition position
The number of qualifying Group Sadhnas they created

This feature is intended as community appreciation for helping devotees come together through Group Sadhna. Email addresses, individual personal japa totals and other private account information are not displayed as part of the weekly celebration.

Weekly recognition may be calculated automatically by backend systems using qualifying Group Sadhna activity.

Open Group Sadhna request records

To display request status efficiently, the app may store an account-specific copy or summary of an open-group join request.

This may include:

Group identifier
Group name
User identifier
Request status
Request and review timestamps
Reviewing administrator identifier
Group target
Group duration
Group-creation time
Most recent update time

These records are used to display statuses such as pending, approved, rejected, cancelled or ready to join.

Members who leave a group

A member who leaves a Group Sadhna may be marked as having left and will no longer be treated as an active member.

The user’s previous contribution may remain as part of the group’s historical total so that the group record and contributions of other members are not made inaccurate.

Completion and expiry notifications are intended only for users who remained members until the Group Sadhna was completed or concluded. Users who left before that event are not intended to receive those final notifications.

Abandoned, expired and cancelled groups

The app may use automated backend processes to:

Delete certain empty abandoned groups
Remove related request or invitation records
Clear stale user-group references
Mark non-empty abandoned groups as expired
Preserve historical contributions where deleting them would make records inaccurate

These processes are used for data maintenance, reliability and prevention of stale or unusable groups.

8. Naam Sathis

The Naam Sathi feature allows users to connect with devotional friends and invite them to Group Sadhnas.

Information stored for this feature may include:

User identifiers
Display names
Naam Sathi request status
Relationship status
Request timestamps
Response timestamps
Removal information where applicable
Group Sadhna invitations
Invitation status
Relevant group information
Information indicating whether an invited person is currently part of a Group Sadhna

Naam Sathi information is used to provide:

Devotional connections
Friend-request functionality
Relationship status
Group Sadhna invitations
Invitation availability
Related account-specific notifications

Your Naam Sathi list is not intended to be publicly visible to all app users.

9. Bhakti Essentials Interest Test

The app may include a feature called Bhakti Essentials.

Bhakti Essentials is currently intended to help us understand user interest in devotional items and related features.

At this stage, Bhakti Essentials may be an interest-testing or product-research feature rather than a complete online shop.

Bhakti Essentials page activity

When you open or explore the Bhakti Essentials page, the app may store:

Firebase user identifier
Display name
Email address
Visit or exploration identifier
Date
Source of the page visit
Total number of times the page has been explored
First exploration time
Most recent exploration time
Most recently used source
Most recent visit identifier

We may use this information to:

Understand whether users are interested in Bhakti Essentials
Measure feature engagement
Understand repeat usage
Decide whether to continue, change or discontinue the feature
Plan possible future devotional offerings
Improve page design and item selection

“I am interested” selections

When you select “I am interested” or another equivalent interest button, the app may store:

Firebase user identifier
Display name
Email address
Selected item identifier
Selected item name
Date and time of the interest selection
Source of the selection

The app may also update an aggregate interest count for the selected item.

Selecting an interest button indicates that you are interested in the item or concept. It does not necessarily create a purchase, reservation, order or legal obligation to buy.

Current purchasing status

Unless the app clearly presents an active purchase and checkout process:

Bhakti Essentials does not process a payment.
It does not create a confirmed order.
It does not collect a delivery address for an order.
It does not collect debit-card, credit-card, bank-account or UPI details.
It does not guarantee that a displayed item will become available for sale.
Expressing interest does not guarantee price, availability, delivery or future contact.

When purchasing functionality is introduced in the future, this Privacy Policy and any applicable terms may be updated before or when that functionality becomes available.

10. In-App Notifications

The app may store account-specific in-app notifications in Firebase Cloud Firestore.

These notifications may relate to:

Group Sadhna join requests
Join-request approvals
Group Sadhna invitations
Naam Sathi requests
New members joining a group
Group Sadhna completion
Group Sadhna expiry or conclusion
Other account-related Group Sadhna activity
Relevant service or account information

An in-app notification may include:

Notification identifier
Notification type
Related group identifier
Related group name
Sender identifier
Sender display name
Notification title
Notification message
Creation time

These notifications are displayed only to the intended user or users, subject to the app’s access controls.

Users may dismiss supported in-app notifications.

11. Firebase Cloud Messaging

The app uses Firebase Cloud Messaging, a service provided by Google, to deliver notifications such as:

Festival messages
Special devotional messages
Important app announcements
Relevant service or feature updates
Group Sadhna updates where supported

Firebase Cloud Messaging may generate or process:

App-instance registration token
Firebase installation identifier
Device and app information needed for delivery
Notification-delivery information
Similar technical identifiers

The app may store an FCM token with information such as:

Firebase user identifier
Platform
Whether notifications are enabled
App version
App version code
Device Android version or SDK level
Token-update time

Notification permission may be requested on supported Android versions.

You can allow or deny this permission and can later control it through your device settings.

Firebase Cloud Messaging is not used by us for personalised advertising.

12. Local Notifications and Reminders

The app may schedule local notifications to support your devotional practice.

These may include:

Daily japa reminders
Grace-day reminders
Streak-saving reminders
Reminder prompts based on practice activity
Other locally scheduled devotional reminders

Reminder settings, reminder time and reminder messages are generally stored locally on your device.

Grace-day and streak-related reminders may use locally stored information such as:

Practice history
Current streak
Last practiced date
Whether you have practiced on a particular day
Reminder preferences

These local reminders do not require your personal japa information to be sent to an advertising service.

You can disable reminders in the app where available and can control notification permission through your device settings.

13. Firebase Analytics

We use Firebase Analytics to understand how users interact with the app and to improve its features, performance and reliability.

Firebase Analytics may process information such as:

App opens
Screen views
Feature interactions
Japa-session starts and completions
Selected japa mode
Mini Jap usage
First-mala completion
Daily-goal completion
Reminder interactions
Rate-us interactions
Support interactions
Journey interactions
Settings interactions
Group Sadhna interactions
Bhakti Essentials page interactions
Bhakti Essentials interest-button interactions
Instagram or external-link interactions
App version
Device type
Operating-system information
App-instance identifiers
General technical and usage information
Approximate engagement information provided by Firebase

We use this information to:

Understand which features are used
Measure general app engagement
Diagnose broad product issues
Improve app navigation and performance
Decide which features to improve or discontinue
Understand the effectiveness of prompts and onboarding
Make product and design decisions

We do not intentionally use custom Firebase Analytics event data such as personal japa activity, Group Sadhna activity, Naam Sathi activity or Bhakti Essentials interest selections as direct inputs for personalised advertising. Advertising is provided separately through Google AdMob / the Google Mobile Ads SDK as described below.

We do not intentionally send the following as custom Firebase Analytics event content:

Personal devotional notes
Contact lists
Photos
Videos
Audio files
Documents
Financial information
Exact location
Passwords
The content of private communications

Google may process technical, device, app-instance and usage information according to its own Firebase and privacy policies.

14. Firebase Crashlytics and Diagnostic Information

The app may use Firebase Crashlytics to identify, diagnose and fix crashes, errors and stability problems.

Firebase Crashlytics may process information such as:

Crash reports
Stack traces
Error details
App version
Device model
Android version
Device state associated with a crash
Firebase installation identifiers
Crashlytics installation identifiers
Technical logs or diagnostic information
Information about app activity leading to a crash where provided by Firebase or the app

We use this information to:

Identify crashes
Understand how frequently a crash occurs
Determine which devices or app versions are affected
Investigate reliability problems
Improve app stability

Crashlytics information is not intended to be used for personalised advertising.

We do not intentionally include passwords, private devotional messages or payment information in Crashlytics logs.

Diagnostic information may be retained by Firebase according to Google’s applicable service settings and retention practices.

15. Firebase Remote Config

We use Firebase Remote Config to manage certain app settings without requiring a separate app release.

It may be used for purposes such as:

Checking whether an app update is required
Displaying information about a new version
Controlling supported app configuration values
Changing selected app behaviour or text remotely
Enabling, disabling or testing selected app experiences
Supporting gradual feature changes

Remote Config is not used to display third-party advertisements.

It does not give other Group Sadhna users access to your private information.

Firebase may process technical app-instance information required to deliver the applicable configuration.

16. External Links

The app may contain links to external services, including our Instagram profile, Google Play pages or other relevant websites.

When you open an external link:

You leave the app.
The external service’s own terms and privacy policy apply.
The external service may collect information according to its own practices.
We do not control how that external service processes your information.

The app may record that an external link was selected as an Analytics event.

We do not receive all information that an external service may collect after you leave the app.

17. How We Use Information

We use information for the following purposes.

App functionality

To provide:

Japa counting
Mini Jap
Mala tracking
Progress tracking
Goals and streaks
Reminders
Achievements and levels
Private display modes
Background personalisation
Cloud backup and synchronisation
Daily-japa statistics
Group Sadhna
Naam Sathis
Bhakti Essentials
In-app notifications

Account management

To:

Authenticate users
Maintain account sessions
Associate data with the correct user
Synchronise supported progress
Process account requests
Process data-deletion requests
Protect access to account-linked information

App improvement

To:

Understand feature usage
Measure engagement
Improve performance and reliability
Diagnose crashes and technical problems
Improve the user experience
Make product, feature and design decisions
Evaluate interest in possible future features or offerings

Notifications

To deliver:

Local reminders
Festival messages
Devotional updates
Important app announcements
Feature and service updates
Group Sadhna-related notifications

Security and maintenance

To:

Protect account-linked information
Apply authentication and access controls
Investigate technical or security problems
Prevent misuse
Remove abandoned or stale data
Maintain accurate Group Sadhna records
Detect or address harmful, fraudulent or abusive activity

Advertising and ad measurement

To:

Display a limited number of advertisements
Support keeping the app available and maintained
Measure ad delivery and ad performance
Detect invalid traffic, fraud and abuse
Comply with advertising, consent and privacy requirements

Bhakti Essentials research

To:

Understand interest in devotional items
Measure page exploration
Evaluate item demand
Decide whether to build or offer related functionality
Improve the selection and presentation of possible future offerings

18. Data Sharing and Visibility

We do not sell your personal information.

The app uses Google AdMob / the Google Mobile Ads SDK to display advertisements.

As part of ad serving, Google and its advertising partners may automatically collect, process or share technical and usage information such as:

IP address, which may be used to estimate a device’s general location
App and advertisement interactions, such as app launches, ad views or taps
Diagnostic and performance information
Device and account identifiers, including the Android advertising ID, app set ID and, where applicable, other identifiers associated with the device

Google states that these types of data may be used for advertising, analytics, ad measurement, fraud prevention, security and compliance purposes.

Depending on your region, consent choices, Google account or device settings, and applicable law, advertisements may be personalised or non-personalised. Where required, the app may display a privacy or consent message before requesting advertisements.

We do not intentionally provide Google AdMob with your name, email address, personal japa counts, private devotional information, Group Sadhna contributions, Naam Sathi relationships or Bhakti Essentials interest selections as custom ad-targeting information.

Information may be processed by Google and Firebase services that are necessary to operate the app, including:

Google Play Services
Google Sign-In
Firebase Authentication
Firebase Cloud Firestore
Firebase Analytics
Firebase Cloud Messaging
Firebase Remote Config
Firebase Crashlytics

These providers may process account, technical, device, diagnostic, usage and app-instance information according to their own terms and privacy policies.

Information may also be disclosed:

When required by applicable law
To respond to a valid legal request
To protect users, the app or our legal rights
To investigate fraud, abuse or security concerns
To enforce applicable app rules or protect the service
In connection with a business reorganisation, transfer or legal succession, subject to applicable law and appropriate protection

Certain Group Sadhna and Naam Sathi information is visible to other users as described in this Privacy Policy. This visibility is required for those collaborative features to function.

Weekly Sadhna Sevaks recognition may display a recognised creator’s display name, weekly position and number of qualifying Group Sadhnas to other signed-in app users, as described in Section 7.

Information entered into an open-group join request may be visible to the applicable group administrator.

Bhakti Essentials interest information is used internally by Infinite Swipe Labs and service providers required to operate the feature. It is not publicly displayed to ordinary app users.

19. Data Security

We take reasonable technical and organisational measures to protect information.

These measures may include:

Firebase Authentication
Firestore Security Rules
Account-specific document paths
Access restrictions
Transactional updates
Backend validation
Limited user-to-user visibility
Secure communication provided by Firebase and Android services
Automated maintenance of stale Group Sadhna information

However, no electronic storage or internet-transmission method can be guaranteed to be completely secure.

We cannot guarantee that:

Information will never be accessed improperly
A service will never experience an outage
Every synchronisation will succeed
Every technical error can be prevented
Data can always be recovered after deletion, corruption or device loss

You are responsible for maintaining the security of:

Your Google account
Your device
Your device lock
Your email account
Any access credentials associated with your Google account

Please contact us if you believe your app account or information has been accessed improperly.

20. Data Retention

Local information

Local information generally remains on your device until:

You use an applicable reset option
You clear the app’s storage through device settings
You uninstall the app
The app replaces or removes the information during normal operation

Cloud backup and account information

Account-linked cloud information may remain until:

It is replaced during synchronisation
You reset the relevant information
You request account deletion
It is no longer reasonably required to provide or improve the app
Retention is required for security, fraud prevention, dispute resolution or legal compliance

Daily-japa statistics

Account-linked daily-japa session and summary records may be retained for:

Usage understanding
Reliability analysis
Product measurement
Technical investigation
Historical app statistics

These records may be deleted or anonymised when they are no longer reasonably required, subject to technical, legal and operational requirements.

Bhakti Essentials information

Bhakti Essentials exploration and interest information may be retained while it is reasonably required to:

Evaluate user interest
Analyse feature demand
Plan future functionality
Maintain accurate aggregate counts
Respond to privacy or account requests

It may later be deleted, anonymised or aggregated where appropriate.

Group Sadhna information

Shared Group Sadhna records may remain in limited form when necessary to preserve:

Group history
Group totals
Contributions made by remaining members
Completion or expiry records
Accurate records for other participants

A user who leaves a Group Sadhna may no longer be treated as an active member, but their previous contribution may remain included in historical group totals.

Certain empty abandoned groups may be deleted automatically.

Groups containing contributed japa may be preserved as completed or expired history rather than deleted.

Firebase service information

Firebase Analytics, Firebase Cloud Messaging, Firebase Crashlytics and other Google-service information may be retained according to Google’s applicable service settings, retention periods and policies.

Legal and security retention

We may retain limited information when reasonably necessary to:

Comply with applicable law
Respond to legal requests
Resolve disputes
Enforce agreements
Investigate fraud or abuse
Protect users or the app
Maintain security records

21. Reset All Japa

The Reset All Japa option is intended to delete your personal japa progress and related information covered by that reset, including the associated cloud backup where supported.

Reset All Japa may remove information such as:

Daily japa count
Lifetime japa total
Mala progress
Streaks
Days practiced
Weekly and monthly progress
Goals
Journey progress
Achievements and levels
Related cloud backup information where supported

Reset All Japa is not the same as deleting your complete account.

It may not automatically delete:

Firebase Authentication account
Google Sign-In identity
Group Sadhna records
Naam Sathi relationships
Account-specific notifications
Daily-japa operational statistics
Bhakti Essentials interest or exploration records
Firebase Analytics data
Crashlytics diagnostic information
Information that must remain to preserve another user’s shared Group Sadhna record

Information connected with Group Sadhna, Naam Sathis, authentication or account administration may require separate deletion or a complete account-deletion request.

Before confirming a reset, review the warning shown in the app because deleted progress may not be recoverable.

22. Account and Data Deletion

Users may request account deletion through the account-deletion option provided in the app or by contacting:

infiniteswipelabs@gmail.com

An account-deletion request may cover information under our control, including:

Firebase Authentication account information
Google profile information stored by the app
Personal cloud backup
Account-linked preferences
Account-linked daily-japa statistics
Naam Sathi information
Account-specific invitations and requests
Account-specific notifications
Bhakti Essentials exploration records
Bhakti Essentials interest records
FCM tokens
Other account-linked information under our control

We aim to complete valid account-deletion requests within seven days after receiving sufficient information to identify and verify the account.

We may contact you to:

Confirm the request
Verify ownership of the account
Clarify the requested deletion
Explain information that cannot immediately be removed

Some information may remain temporarily in:

Backups
Security logs
Diagnostic systems
Firebase service systems
Systems where immediate deletion is not technically possible

Information already included in shared Group Sadhna records may need to remain in limited, historical, aggregated or non-identifying form so that:

Group totals remain accurate
The records of other members are not damaged
Completed or expired group history remains meaningful
Fraud, abuse or disputes can be investigated

Aggregate statistics that do not identify you may remain after account deletion.

Firebase Analytics or Crashlytics information that cannot reasonably be linked back to your account by us may be retained according to Google’s applicable settings and policies.

Deleting your account is separate from uninstalling the app.

Uninstalling the app removes local app information from that device but does not necessarily delete cloud information associated with your account.

23. Your Choices and Rights

Depending on applicable law, you may request:

Access to information associated with your account
Correction of inaccurate account information
Deletion of your account and account-linked information
Information about how your information is used
Withdrawal of consent where processing is based on consent
Restriction or objection where provided by applicable law
A copy of eligible information where technically and legally applicable

You can also:

Disable local reminders
Deny or revoke notification permission
Close Mini Jap
Reset applicable japa progress
Dismiss supported in-app notifications
Leave a Group Sadhna
Remove supported Naam Sathi relationships
Sign out of the app
Use privacy or consent choices shown in the app where available
Manage, reset or delete the Android advertising ID through supported device settings
Request account deletion
Contact us with a privacy question or concern

The current app version requires Google Sign-In to access the app’s main features.

Some features may not function when:

You are signed out
Notification permission is denied
Internet access is unavailable
Required device functionality is unavailable
Your account is deleted

To exercise an applicable privacy right, contact:

infiniteswipelabs@gmail.com

We may need to verify your identity before fulfilling a request.

24. Children’s Privacy

The app is intended for general devotional and spiritual use and is not specifically directed towards children.

We do not knowingly seek to collect personal information from children without the consent required by applicable law.

Parents or guardians should supervise a child’s use of the app where required.

Where applicable, advertising may be subject to age-related restrictions, consent requirements and child-directed treatment required by law or Google advertising policies.

Because the app requires Google Sign-In and includes collaborative features, parents or guardians should review:

The child’s Google account settings
Group Sadhna participation
Display-name visibility
Naam Sathi connections
Notifications
Bhakti Essentials interactions

If you believe a child has provided personal information without appropriate permission, contact us at:

infiniteswipelabs@gmail.com

We will review the request and take appropriate action.

25. Third-Party Services Used

The app currently uses or may use the following services.

Google Play Services and Google Sign-In

Used to support:

Google account selection
Authentication
Account sessions
Related Android services

Firebase Authentication

Used to:

Authenticate users
Maintain account identity
Restrict access to account-linked information

Firebase Cloud Firestore

Used for:

Cloud backup
Synchronisation
Daily-japa statistics
Group Sadhna
Naam Sathis
Invitations
Requests
Group records
Bhakti Essentials
Account-specific in-app notifications
Operational data maintenance

Firebase Analytics

Used to:

Understand app usage
Measure feature engagement
Improve the app experience
Support product decisions

Firebase Cloud Messaging

Used to deliver:

Festival messages
Devotional updates
Important announcements
Relevant service or feature notifications

Firebase Remote Config

Used to manage:

Selected app configuration values
Force-update requirements
What’s New information
Supported remote feature behaviour

Firebase Crashlytics

Used to:

Detect crashes
Diagnose errors
Understand stability problems
Improve app reliability

Google AdMob / Google Mobile Ads SDK

Used to:

Display App Open and banner advertisements
Measure ad delivery and performance
Support advertising-related analytics
Detect invalid traffic, fraud and abuse
Support advertising security and compliance requirements

The Google Mobile Ads SDK may automatically collect or share information such as:

IP address, which may be used to estimate general location
App and advertisement interactions
Diagnostic and performance information
Android advertising ID
App set ID
Other device or account identifiers where applicable

Advertising may be personalised or non-personalised depending on consent, region, device or Google account settings, and applicable law.

Google User Messaging Platform (UMP)

Used where applicable to:

Present privacy and consent choices relating to advertising
Record or communicate advertising-consent choices to Google’s advertising services
Support compliance with applicable privacy requirements

Android Picture-in-Picture

Used to display Mini Jap in a compact floating system window while you use another app or screen.

The current Bhakti Essentials interest test does not use third-party payment processing.

Google and Android services process information according to their own applicable terms and privacy policies.

For more information about how Google uses information from apps that use Google services, see:
https://policies.google.com/technologies/partner-sites

26. No Sale of Personal Information and Advertising Practices

We do not sell or rent your personal information.

The app displays third-party advertisements through Google AdMob / the Google Mobile Ads SDK.

Google and its advertising partners may process technical, device, identifier, diagnostic and ad-interaction information as described in this Privacy Policy and under Google’s own terms and privacy policies.

Depending on consent, region, account settings, device settings and applicable law, advertisements may be personalised or non-personalised.

We do not intentionally:

Provide advertisers with your name or email address as ad-targeting information
Use your personal japa count or private devotional activity as custom ad-targeting information
Use Group Sadhna contributions or membership to create an advertising profile
Use Naam Sathi relationships to create an advertising profile
Sell Bhakti Essentials interest information to advertisers

Advertising data may still be processed by Google and participating advertising partners for purposes such as ad delivery, ad measurement, analytics, fraud prevention, security and compliance.

This does not prevent us from using aggregated or non-identifying information to understand app usage, feature demand or general product performance.

27. International Processing

Google and Firebase services may process or store information using systems located in India or other countries.

The laws and data-protection standards of another country may differ from those of your location.

Where required, information is processed subject to the protections, contractual terms and security measures made available by the relevant service provider and applicable law.

By using the app, you understand that the technical operation of cloud, authentication, analytics, notification and diagnostic services may involve processing across different locations.

28. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect:

Changes to the app
New features
Changes to data handling
Changes to Google or Firebase services
Security or operational changes
Legal or regulatory requirements
Feedback from users or authorities

Changes will be reflected by updating the “Last Updated” date below.

Where an update materially changes how personal information is collected, used or shared, we may provide additional notice through:

The app
An update notice
Google Play
Email where appropriate
Another reasonable method

You should review this Privacy Policy periodically.

Continued use of the app after an updated policy becomes effective means that the updated policy applies to your continued use, subject to applicable law.

29. Contact Us

For privacy-related questions, access requests, correction requests, account-deletion requests or other privacy concerns, contact:

Infinite Swipe Labs
Email: infiniteswipelabs@gmail.com

When contacting us, please provide enough information to identify the relevant app account and understand your request.

Do not send us:

Your Google password
Your device password
One-time passwords
Financial account passwords
App-signing keys
Keystore passwords
Other sensitive access credentials

Effective Date

April 2026

Last Updated

August 28, 2026

Page updated

Google Sites

Report abuse