தீபம்·Deepam

Privacy Policy

Effective •Applies to the Deepam Android app (me.kartdroid.kaalathuli)

Deepam (formerly Kaalathuli) is a Tamil Panchangam (lunisolar calendar) app. This page explains, plainly, what data the app touches and why. It's an independent, single-developer app — there's no company and no user account behind it. Small banner ads from Google AdMob keep it free.

At a glance

App usageWhich screens you open (Daily, Monthly, Yearly, Settings), via Firebase Analytics — helps us see what's actually used.
Crash reportsIf the app crashes, Firebase Crashlytics sends a diagnostic report so we can fix it — device model, OS version, and the stack trace.
Banner adsOne small banner on some screens, from Google AdMob, limited to ads suitable for a general audience. Google's ad SDK uses your device's advertising ID, IP address and ad taps to choose and count ads.
Panchangam dataCalculated entirely on your device from a bundled dataset. Your selected city never leaves the app.

Not collected, ever: your name, email, phone number, contacts, photos, GPS location, or anything you'd consider personal. There's no sign-up, no login, and no user-generated content to store.

1. Information we collect

The app itself asks for nothing — no location permission, no camera, no contacts. Two Google Firebase services and Google's ad SDK run in the background and collect the following, standard to how those services work:

Firebase Analytics

DataWhat it's used for
Screen views (screen_view events — e.g. "Daily", "Monthly")Understanding which parts of the app people actually use
App version, device model, OS version, language, countryPrioritizing device/OS support
Advertising ID (Google Play services identifier)Part of Firebase Analytics' default behavior.

Firebase Crashlytics

DataWhat it's used for
Crash stack traces and exception detailsFinding and fixing the bug that caused the crash
Device diagnostics at crash time (model, OS version, free memory/disk)Reproducing crashes tied to specific devices
Recent screen-view breadcrumbs leading up to a crashUnderstanding what you were doing right before a crash

Google AdMob (banner ads)

The app shows at most one small banner per screen — never on a notification or the widget, and never a full-screen or video ad. Ads are limited to Google's general-audience content ratings, and categories such as gambling, dating and alcohol are blocked. Google's ad SDK collects, as Google itself describes it:

DataWhat it's used for
IP addressMay be used to estimate your general location, to choose ads for your area
Advertising ID and app set IDChoosing and measuring ads, and limiting how often one is shown
Ad interactions — that an ad was shown or tappedCounting ads and detecting fraudulent clicks
Diagnostic information about the ad SDK's performanceKeeping the ad SDK working well

All of it is encrypted in transit. In the European Economic Area, the UK and Switzerland, the app asks for your consent through Google's own form before any ad is requested, and Settings → Ad privacy choices in the app lets you change your answer at any time.

2. Panchangam data — what stays on your device

Every date's Tamil month, thithi, nakshatra, yogam, karanam, Naalvar Kaalam timings, and fasting-observance calculations are computed locally from a dataset bundled inside the app. Your selected city (used only to pick the right sunrise/sunset times) is stored in the app's local settings and is never transmitted anywhere — there is no server call involved in showing you a day's Panchangam.

3. Who this data is shared with

Analytics and crash data goes to Google Firebase, and ad data to Google AdMob — both operated by Google LLC, the only third party this app uses. Google's handling of that data is governed by Google's Privacy Policy and described in How Google uses information from apps that use its services. We don't sell data, and we don't share it with anyone beyond this.

4. Data retention

Analytics and Crashlytics data is retained according to Firebase's own default retention windows (Google Analytics data is retained for a fixed period before automatic deletion; Crashlytics reports are retained per Firebase's standard policy). We don't independently store or back up this data ourselves.

5. Children's privacy

Deepam isn't directed at children under 13, and we don't knowingly collect data from anyone in that age group. If you believe a child has provided data through this app, contact us using the details below and we'll address it.

6. Your choices

Since there's no account, there's no data tied to an identity you could log in and manage. You can limit what's collected at the device level: Settings → Google → Ads lets you reset or delete the advertising ID used by Firebase Analytics and by ads (ads then stop being chosen by it), and Settings → Apps → Deepam → Permissions shows everything the app has (and hasn't) asked for.

7. Changes to this policy

If what the app collects changes — for example, if a future version adds a feature that needs a new permission — this page will be updated first, with the effective date at the top revised accordingly.

8. Contact

Questions about this policy or your data: kartdroid.me@gmail.com