Vedanta Yojana ("the app") is a reference app for Sri Vaishnava scripture, Divya Desam temple information, and daily Panchangam (Hindu calendar) details. This page explains what data the app uses, why, and how it is handled.
Location data
When you open the app's Home screen, it requests your device's approximate location to calculate today's Panchangam (tithi, nakshatram, upcoming Ekadashi) and Samkalpam for where you actually are, rather than a fixed city. This is the only use of location data in the app.
How it's used:
The Panchangam is calculated entirely on your device from your coordinates and configured timezone. They are not sent to any calendar service.
Your coordinates are also turned into the name of the place they fall in (“Chennai”), so the app can show which place the day's Panchangam and Sankalpam are calculated for instead of an unnamed “your location”. In the Android and iOS apps this lookup is done by your device's own operating-system geocoder; on the website it is done by BigDataCloud's public reverse-geocoding service (api.bigdatacloud.net), which receives the coordinates being named and nothing else — no account, no API key, and no identifier of any kind. The resolved name is cached on your device, so the lookup is not repeated for a place you have already been shown.
We do not use this data for advertising, analytics, or tracking, and it is never linked to your identity.
Instead of your location, you can choose any city for the Panchangam. The city list is part of the app and website, so searching it sends nothing anywhere; your choice is saved only on your device (or in your browser), and while a city is chosen your location is not used at all.
If you decline the location permission, the app shows that Panchangam data is unavailable until you choose a city — every other feature works normally. If the place name alone cannot be resolved, the Panchangam is still calculated from your coordinates and is simply shown without a place name — never under a guessed one.
Data stored only on your device
Your reading progress, bookmarks and appearance preferences are saved locally on your phone. Your selected language is also sent if you allow notifications, as described below:
Your reading progress (which chapter you last opened, per book)
Bookmarked chapters
Language, theme, and text-size preferences
Uninstalling the app removes all of this data. We have no server that stores or can access it.
Ekadasi reminders
After setup, the app asks once for your phone's notification permission. If you allow it, the app works out the coming Ekadasi dates on your phone, for the place its Panchangam uses, and schedules a reminder for 7 am the day before each one. This happens entirely on your phone: no location, token or other information is sent to us or anyone else for these reminders. To stop them, turn off the app's notifications in your phone's settings (on Android you can turn off just the Ekadasi reminders channel); the app then cancels the scheduled reminders.
Announcement notifications
In app versions that support push notifications, announcement notifications are on once you allow your phone's notification permission, which the app asks for once after setup. You can turn them off at any time with the switch in the app's Settings, or in your phone's settings. While they are on, we store an Expo push token, your app platform and selected language in our Cloudflare notification service. These are used only to send new announcements, in your language where a translation is available. Delivery uses Expo and Apple's or Google's push services. Tokens are not used for advertising or reading analytics, and we do not attach your name, location or reading history to them.
Turning notifications off in the app removes your subscription and queued notifications when the request succeeds. Turning notifications off in phone settings also stops display; the app removes the subscription when next opened online, and subscribes again if you later allow notifications there. Invalid tokens are removed when the push service reports them, and subscriptions not refreshed for 180 days expire. Uninstalling alone does not immediately notify our server. Cloudflare processes network addresses for security and rate limiting; we do not store them in the subscription database.
Aggregate counts, with no identifiers
Two things are counted in aggregate. Neither involves a cookie, an advertising identifier, a device identifier, or anything that could single you out or be linked to you.
The app's update and content checks. The app asks our website whether a newer version, new Library content or new What's New announcements are available — the same kind of check it has always made, and which is what tells you an update exists. Nothing about you is sent with it. Our website's network provider counts those requests and the country they came from, so we can see roughly how many people use the app and where. The count is of requests, not of people: we cannot tell one device from another, and we do not try to.
What is read in the Android app. The app reports which screen you open, the screen you opened it from, the language you are reading in, and roughly how far down a chapter you reach — counted as totals added up across everyone, so we can tell which books and chapters are worth writing more of. No identifier is sent and nothing is stored on your device for this, so one opening of the app cannot be joined to another, and each report knows only the screen immediately before it rather than a path through the app. A route taken by fewer than five readers is discarded rather than shown. The iOS app reports none of this.
Visits to our website. The website at vedantayojana.org records aggregate page views and the visitor's country using a cookieless measurement service. It also counts which pages are opened, which page is opened next, and roughly how far down a page readers reach — all as totals added up across everyone, so we can tell which writing is being read and what to write more of. No identifier of any kind is stored or sent, nothing is kept in your browser, we cannot tell one device from another, and a route taken by fewer than five readers is discarded rather than shown. It cannot follow you to any other site.
Neither source is used for advertising, sold, or shared for marketing purposes, and neither is ever linked to your identity.
App updates
The app checks Expo's update service (u.expo.dev) for updates to its content and fixes. Each check sends the app's platform, its version, and a random identifier the app generates when it is installed, which Expo uses to deliver updates. This identifier is not linked to your identity and is not used for advertising.
What the app does not do
No account or sign-in is required or offered.
No advertising or ad networks.
No analytics SDK, crash-reporting SDK, or usage-tracking service is built into the app, and no third party receives anything about your reading. The Android app counts which screens are opened and how far a chapter is read, as described above — as totals, with no identifier, and nothing kept on your device that could join one opening of the app to another.
No data is sold or shared for marketing purposes.
Children's privacy
The app is not directed at children and does not knowingly collect data from children.
Changes to this policy
If this policy changes, the update will be posted on this page with a revised date above.
Contact
Questions about this policy or the app's data practices can be sent to [email protected].