Privacy Policy
Choghadiya is operated by Webdean Inc.
Effective date: November 8, 2026 · Owner-review draft
This English draft is provided for review by Webdean Inc. It is not legal advice or a certification of compliance. Certain provider, retention and jurisdiction-specific details still require confirmation before store release.
1. Scope and public access
This policy describes Choghadiya at choghadiya.net and the native app experience currently being prepared. The calendar is publicly usable without signup. There is no public account, payment or subscription workflow in the current app. It does not mean that no information is processed: online features and hosting receive data as described below.
Backend session support is present: if an existing session is available, it may be stored locally, refreshed and attached to server-function requests. Editor preview sessions can use the platform’s preview session handling; this is not a required public signup. Hosted account settings have not been independently verified.
2. Optional location and calendar calculations
You can select a city manually or choose “Use my location.” Location access is requested only after your action, and you can deny or revoke permission in browser or device settings. No background location tracking is implemented. Manual selection uses the listed city’s coordinates, not your physical position.
Automatic location uses the coordinates supplied by your browser or operating system. High-accuracy mode is not requested, but this is not a guarantee of approximate location: the returned coordinates may be precise and are stored without rounding. Native Android requests approximate foreground location; iOS precision follows your permission choice. The displayed place label or identifier may be rounded while the stored coordinates are not.
Time zone and nearest listed city are determined on your device using static place files downloaded from our host, not a runtime third-party geocoding service. Calendar and eclipse calculations ordinarily run on your device. Location can still leave your device for weather, when you submit an AI question, or when you explicitly enable native remote announcements or continuous reminders. Continuous reminders also send the relevant saved calculation preferences to our server so it can calculate them while the app is closed.
3. Device storage and your controls
Local storage holds your selected place and coordinates, favorites, language, calendar tradition, observance profile, weather units and, in the native app, category/time/lead-time choices, scheduling and remote-registration status, a random installation ID and a sessionless installation credential. Provider tokens are passed to the server during enabled registration but are not written into these local preferences. These choices can reveal location or religious preferences. They are not a public account or a cloud-synced favorites list. Browser and native app storage are separate.
You can remove individual favorites, choose another city, and change preferences in the app. To remove all saved choices, clear this site’s browser data or the native app’s data using your device controls. Local values have no automatic expiry in the app and remain until replaced, removed or storage is cleared by you or your device. Clearing local data does not erase information already processed by online providers.
A session-storage flag remembers that the Ideal Jodi promotion has been shown, so it does not reopen during navigation in the same session.
4. Weather processing
The weather card sends selected latitude, longitude and time zone to our server. When weather is configured and available, our server requests weather from Apple WeatherKit, rounding coordinates to four decimal places for Apple’s request and the cache key. This remains potentially precise location. Credentials and signed Apple tokens stay on the server.
The server coalesces duplicate weather requests and keeps a bounded in-memory cache, with freshness controlled by Apple’s expiry information and a fallback freshness limit when necessary. An IP-based limiter uses ten-minute counting windows in runtime memory to protect the service. That window is not a promise that all IP records or logs are deleted after ten minutes: expired entries are cleaned or replaced as the runtime operates. No permanent application weather database is implemented. Unavailable weather does not mean that hosting receives no request metadata.
5. AI questions
AI explanations are optional. After you explicitly agree to sharing with Lovable AI Gateway and OpenAI and press Ask, your question, selected city, coordinates, time zone, date, language and chosen calendar/observance settings go to our public explanation API. The server recalculates facts for that place and date, then sends your question, language and derived facts (including city, time zone, date, calendar choices, timings and observances) through Lovable AI Gateway to the configured OpenAI model provider. Raw latitude and longitude are used by our server for calculations but are not fields in the current model prompt; your own question can still contain location or other personal information.
This processing provides an explanation, not personal predictions. Avoid names, contact details, health information or other sensitive content in questions. Questions and answers are held in the current screen’s memory, not an app-managed conversation database. The app does not establish the gateway or model provider’s retention, training use or deletion timetable; these details require confirmation. Do not assume that closing the screen deletes provider records. Request limits use runtime IP counting; hosting may separately retain request metadata.
6. Optional notifications and installation records
Native remote announcements and continuous reminders are independent and off by default. Registration is enabled for the native release, but no Firebase module initialization, OS notification-permission request or provider-token collection occurs before your explicit opt-in to at least one remote category. This account-free installation uses a random installation UUID and a random sessionless credential; the server stores the credential only as a SHA-256 hash. No public Choghadiya account is created.
During registration and token rotation, our backend stores the installation UUID, selected city and its coordinates and IANA time zone, platform, recurring-transport choice, daily/festival/period/announcement consent choices, notification-permission and token status, app version, FCM provider token, credential hash, and creation/update/last-seen/token timestamps. If you separately choose Continuous reminders, it also stores the reminder HH:mm, language, explicit calendar tradition and observance profile, enabled calculated categories, selected Choghadiya period names and lead time, configuration revision, calculated occurrence content/local date/scheduled instant, and delivery status needed to calculate and send reminders while the app is closed. Administrator campaigns can additionally create audience, message, schedule, outbox, provider-message-ID and audit records. Raw provider tokens and credentials are not shown in the admin interface. Administrator sign-in is separate and uses server-side role checks.
Android uses Google Firebase Cloud Messaging; iOS uses Apple APNs through the same Choghadiya-owned Firebase project. They process the enabled installation’s token and notification payload. Provider acceptance does not establish device delivery or provider-log deletion. Turning off announcements does not revoke an enabled continuous-reminder registration, and turning off continuous delivery does not disable announcements. Only when every remote category is off does the app disable local token auto-init, request local token deletion and request atomic server revocation. The app shows an unconfirmed state and retries if server revocation fails. Switching between phone-local and continuous calculated reminders cancels only calculated local reminders after a confirmed handoff; private plan alerts remain separate.
Private plan titles/notes are always stored locally and are never uploaded for announcements or continuous reminders. Without Continuous reminders, calculated daily, festival and selected-period content remains on-device with a rolling local horizon. Continuous delivery requires internet-connected backend/provider operation and does not guarantee delivery; stale occurrences after an outage are skipped rather than sent as a late batch.
7. Hosting, analytics, diagnostics and other recipients
Lovable hosting and backend services, their infrastructure providers, and network delivery services process connection information such as IP address, request URL, time and browser/device metadata to deliver and protect the app. Weather coordinates appear in our request URL. Error handling can send diagnostic information to platform telemetry.
On the published website, Lovable’s visitor analytics and click tracking are enabled. For every visitor, they record pages visited, where visitors came from, their country, browser, operating system and device type, how long they stay, how fast pages load, errors, and button and link clicks. There is currently no cookie-consent banner connected to this analytics. Lovable’s analytics uses no cookies, stores nothing on the visitor’s device, doesn’t keep IP addresses and doesn’t identify visitors. Detailed data is kept for 90 days and daily summaries for a year. Lovable collects this data for us. Lovable’s privacy policy explains how it handles it.
Google Fonts receives network requests to load fonts. Apple receives requests when its weather attribution image or legal link is used. Apple WeatherKit, Google Firebase Cloud Messaging, Apple APNs and Lovable AI Gateway/OpenAI receive the feature data described above. No Firebase Analytics feature is used by the native app. If you email us, your message and contact details are processed through email services for support and privacy requests. Mailbox provider and retention practices are awaiting owner confirmation.
8. Ideal Jodi and future advertising
Ideal Jodi is our current direct house promotion: text, a ten-second countdown, immediate close control and a link to idealjodi.com. The promotion implementation does not send ad impressions or install an ad-network tracking SDK. Clicking the link opens an external website, which receives your connection information and follows its own privacy practices. In the prepared native app it opens outside the app’s trusted web view.
Other banner placements are currently disabled. Future ad-network/native-ad adapters are not connected and do not currently run network advertising code. Any future tracking integration requires separate configuration, appropriate consent and updated disclosures. These statements concern the promotion code, not the unverified hosting telemetry noted above.
9. Retention, security and international processing
Verified local-storage and runtime-cache behavior is described above. Remote opt-out clears the current server provider token and server category consents and marks the installation revoked, but retains the installation record; it does not establish deletion from provider logs or backups. No automatic server-side deletion timetable for installation records is currently implemented. Contact us to request review or deletion of an installation record. We have not verified production hosting/log retention, AI/FCM/APNs provider retention, email retention or a complete provider deletion process; this draft makes no fixed-duration promise for those records. Our current app code does not write favorites, location history, private plans or AI conversations to an application database.
The production app uses HTTPS, server-only credentials and restricted native external-link handling. No transmission, browser storage or security control is guaranteed to be completely secure. Hosting and service providers may process data internationally; exact processing countries, contractual safeguards and regional hosting arrangements have not been confirmed.
10. Children and privacy requests
Choghadiya is a general-audience calendar, not a child-directed service. No age-verification or parental-consent workflow is implemented. Children should use it with a parent or guardian and should not put personal information into AI questions or emails. If you believe a child’s personal information was submitted, contact us so we can assess the request and available removal options.
For access, correction, deletion or other privacy requests available under applicable law, contact hello@choghadiya.net. Describe your request without sending unnecessary sensitive information. We may need limited information to verify and handle it. Device-only preferences are best removed through your browser/device controls; provider-held information may need coordination with the relevant provider. This is not a guarantee of deletion from every provider or a fixed response time.
11. Updates and contact
We may update this policy when functionality or processing changes, and will change the effective date. Material changes will be identified on the updated page; new permissions or consent will be requested where needed. Privacy contact for Webdean Inc.: hello@choghadiya.net. Any required postal contact remains awaiting confirmation.