Aarambh Privacy Policy

Effective date: November 19, 2026

Aarambh: Gita & Morning Ritual (Android package com.zrf.aarambh) is operated by Atharv Kumar. This policy explains how the released app handles information when you use its morning alarms, breathing practices, Gita teachings, quizzes, downloads and notifications.

Information stored on your device

Alarm settings, tasks, reflections, quiz answers and history, learning progress, saved teachings, downloaded audio and app preferences are stored locally. Personal task and reflection text and individual quiz answers are not uploaded by the notification system. Android backup or device-transfer settings may affect whether local app data is backed up by your device provider.

Information processed by our online services

No name, email or password is required to use the app. Its notification service uses Firebase Anonymous Authentication to create a persistent installation identifier. When the app connects to that service, it may transmit:

Requests for teachings and audio include the requested dates or files. Google/Firebase infrastructure may process IP addresses, request metadata and operational logs. The content service temporarily uses a hashed IP address to limit excessive requests.

How we use information

We use this information to deliver content, send announcements according to your preferences, select relevant notification audiences using language and activity summaries, avoid duplicate notifications, measure announcement delivery and openings, troubleshoot failures and protect our services.

Permissions

Notification permission enables reminders and announcements. Alarm, full-screen presentation and background-related settings support timely morning alarms and their lock-screen presentation. Audio playback and vibration support the ritual experience. These permissions do not grant us access to your contacts, photos or precise location.

Service providers and sharing

We use Google Firebase and Google Cloud for authentication, messaging, content storage, databases and server operations. They process information needed to provide these services; see Google's Privacy Policy. Authorized app administrators can access notification installation records and activity summaries for these purposes. We do not sell user information or use it for third-party advertising. We may disclose information when required by law or necessary to protect users and our services.

The current production release does not enable subscriptions or initialize RevenueCat purchases. If a future release changes these practices, we will update this policy.

Retention and security

Local information remains until you remove it using available app controls or clear app storage. Server-side installation identifiers and notification preferences remain until the operator removes them; uninstalling the app does not automatically delete these records. Notification delivery details and recipient snapshots are scheduled for deletion after 90 days from campaign expiry, and administrative audit records after 90 days. Aggregate campaign counts may remain. Infrastructure logs follow the service's configured retention.

Connections to the production services use HTTPS. Backend access controls restrict notification records and administrative operations. No storage or transmission method is completely secure.

Your choices and deletion requests

You can disable announcements in the app or revoke notification permission in Android settings. Changes made offline reach our servers when the app next connects; previously submitted notifications may still arrive. Clearing Android app storage removes local information but does not automatically remove server records.

To request deletion of server-side information, email webifyit.in@gmail.com with the subject “Aarambh data deletion” and your app user code, if available. If you cannot find the code, contact us for help identifying the installation. We may request information needed to verify the request. Relevant legal or security obligations may require limited retention.

YouTube Reels

Spiritual Reels uses YouTube's embedded player. Video files stream directly from YouTube; we do not download or store them on our servers. Loading the player, including autoplay, connects your device to YouTube and may share playback and device information with Google. YouTube may use cookies or similar technologies and display advertising under its own policies. See YouTube's Terms of Service and Google's Privacy Policy. Reel bookmarks are stored on your current device and are not synced to an account. Remove individual bookmarks in Reels or clear app storage to delete them.

Children and changes to this policy

If a parent or guardian believes a child has provided information through the app, contact us to request review and deletion. We will update this page when our data practices change and revise the effective date.