Kumsing is built to work offline and to collect as little as possible. This policy explains exactly what data the app touches and why. It covers both the Android and the iPhone versions, which offer the same features; where a platform differs, the difference is named.
What changed on 1 September 2026: the iPhone version caught up with the Android one. Where the iPhone app previously had no ads, no sign-in and no scanner, it now has all three, and this single policy replaces the separate iPhone one. Two things are specific to iPhone and are new here: the App Tracking Transparency prompt, described under Advertising, and Sign in with Apple, described under Signing in.
What changed on 13 August 2026: Kumsing can now read a holiday list for you. If — and only if — you choose "Scan a planner", the photo or PDF you pick is sent to Google to be read. The Scanning a planner section below says exactly what leaves your phone and what happens to it.
What changed on 7 August 2026: Kumsing shows a small number of advertisements, supplied by Google AdMob. The Advertising section below says exactly where they appear, what the ad network receives, and how to limit it.
Before the sections below, the plain fact: the calendar itself needs nothing. Every date, festival, tatnaba day, sunrise, moon phase and reading ships inside the app as a database and is read from your phone. With no account, no internet and every optional feature untouched, Kumsing is complete, and nothing about you leaves the device.
Planner → Scan a planner lets you photograph your office, school or club's yearly holiday list, or pick its PDF, and have the dates read into your planner.
What leaves your phone. The pages you choose, and nothing else. They are sent to Google's Gemini service (through Google's Firebase AI Logic), which reads the dates and names and sends them back as a list.
What we keep. Nothing. The pages are held only in memory for the one request — Kumsing never writes them to storage, never puts them in your cloud backup, and never sends them to us. Only the dates you then confirm are saved, as ordinary planner entries.
What Google may do with them. Since 18 September 2026 Kumsing uses the paid tier of Google's Gemini service. Under Google's terms for the paid tier, content sent through it is not used to train or improve Google's products, and it is not read by human reviewers for that purpose. Google may retain it briefly for abuse and security monitoring, under its own policy.
(Before that date Kumsing used the free tier, where Google was permitted to use submitted content to improve its products, with human review. If you scanned a page before 18 September 2026, that earlier tier applied.)
Even so, please do not scan a page that carries anything private. A printed holiday list is exactly what this is for; a page with names, addresses, phone numbers, or medical or financial details is not. The page still leaves your device to be read, and the safest page is one that would not matter if it did.
It is entirely your choice. The feature never runs on its own. It needs internet, it is never used anywhere else in the app, and nothing is added to your planner until you have reviewed every entry and confirmed it. If you never open it, nothing you own ever leaves your phone.
On iPhone, choosing pages uses Apple's own photo picker, which hands Kumsing only the pictures you tapped. The app never asks for, and never receives, access to your photo library.
Since 18 September 2026 Kumsing sends anonymous usage counts to Google Analytics for Firebase, and crash reports to Firebase Crashlytics. Both are Google services, used here to answer two questions: which parts of the app people actually use, and what broke.
What is counted. The name of a screen when it is opened; that a first-run step was reached or finished; that a plan, reminder or invitation was saved; that a scan started, succeeded or failed, and how many dates it found; that a theme or script was changed; that a rewarded video was offered, watched or closed; that a share card was sent, and through which app. Alongside these, a small number of settings are recorded so the counts can be grouped: which script you read in, which theme you wear, whether the calendar is pinned to Manipur days, and whether you are signed in.
What is never counted. The content of anything you make or hold. Not a plan's title, an invitation, a name, a date you typed, a note, a tarot entry, your rashi, your birth details, or any part of a page you scanned. When a scan fails, Kumsing records only why it failed as a fixed word such as “no network” — never the message, which can quote your document.
No location, ever. Google may derive a coarse country from the network connection, as it does for any internet request; Kumsing itself sends no location and asks for no location permission.
How to turn it off. Settings → Privacy → Help improve Kumsing. It is on by default and switching it off stops collection at the source, including the automatic session and first-open counts — not merely our own events. Nothing else about the app changes.
Where it goes. Google Analytics, under Google's privacy policy at policies.google.com/privacy. It is kept for 14 months, is not sold, and is never joined to advertising data.
Kumsing shows ads from Google AdMob (Google Ireland Limited / Google LLC). They pay for the app's development and keep it free.
Where ads appear. A small banner strip along the bottom edge of the app, below the navigation bar, and one under the filters on the Festivals screen. Never more than one banner on screen at a time. You may also choose to watch a short video ad to unlock a feature for a day; that never starts on its own.
What we will not do with them. No ad is ever placed over, inside or against a reading — the banner is a separate strip at the edge of the window, never mixed into the calendar, the day details, a festival entry, a tarot card or a rashiphal. No full-screen ad ever interrupts you. And no panchang, festival, tatnaba or calendar information is ever placed behind an ad: everything the calendar knows is free, in full, always. The rewarded videos unlock cosmetic and convenience extras only.
What Google receives. To serve and measure ads, Google may access your device's advertising identifier, along with technical information such as your device model, operating-system version, coarse region and IP address. This is standard for mobile advertising and is handled under Google's own privacy policy: policies.google.com/privacy — see also how Google uses data from apps that use its services.
Your control.
We do not operate an ad network, we do not run our own ad targeting, and we never hand your Kumsing content to an advertiser.
Everything you create in Kumsing lives in a private database on your phone: planner events, invitation cards and their photos, tarot journal entries, your chosen rashi, themes and settings. If you never sign in, none of it ever leaves your device. (The one thing that does travel is a page you hand to "Scan a planner" — and only at the moment you ask for it.)
Phone calendar (optional). Kumsing can do two things with your device calendar, and asks separately for each:
Signing in is optional, and everything in the app works without it. Its only purpose is to back up your data and carry it to a new phone.
On Android you may sign in with Google. On iPhone you may sign in with Google or with Sign in with Apple. If you use Sign in with Apple and choose Apple's "Hide My Email", Kumsing receives only the relay address Apple generates — we never see your real one, and the app works exactly the same.
From the identity provider Kumsing receives your name, your email address (or Apple's relay address) and an account identifier. It is used to show who is signed in and to identify your backup, and for nothing else. We never ask you to type any of it.
If you sign in, the following is stored in Google Firebase (Firestore, asia-south2/Delhi region) under your account, solely to back up your data and sync it between your devices:
This data is transmitted encrypted (HTTPS/TLS), is readable only by your authenticated account under Firebase security rules, and is never sold, shared, or used for advertising or profiling. Apart from Google Firebase (sign-in, backup, the Gemini scan, and an anti-abuse check that confirms requests come from a genuine copy of the app), Apple (Sign in with Apple, on iPhone only) and Google AdMob (advertising, described above), we use no other third-party services.
How to request deletion — two ways:
What is deleted: your Kumsing (Firebase) account and all of the cloud-backed data stored under it — your name and email taken from Google or Apple sign-in, and your synced planner events, invitation entries, tarot journal entries and chosen rashi. This removal is permanent and the data is not retained after deletion (server backups holding it roll off within 30 days).
What is kept: nothing on our servers. Any data stored only on your phone (the on-device copy of your planner, invitations, tarot notes and settings) stays on your device and is removed when you clear the app's data or uninstall Kumsing — it is never on our servers to begin with.
Signing out is different from deletion: it only stops syncing and leaves your data on your device and in your cloud backup.
Kumsing is a general-audience calendar app and does not knowingly collect personal data from children.
If this policy changes, the new version will be posted at this URL with an updated effective date.
Kangla Labs — kanglalabs@gmail.com