Kumsing is built to work offline and to collect as little as possible. This policy explains exactly what data the app touches and why.
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. This is the first feature in Kumsing that sends something you supply off the device, so please read it.
What changed on 7 August 2026: Kumsing now 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.
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. Kumsing uses the free tier of Google's Gemini service. Under Google's terms for that tier, Google may use content sent to it to improve Google's products, and human reviewers may read it. 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.
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.
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 ID, 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 import (optional): if you use "Import events" and grant the calendar permission, Kumsing reads your device calendar once to copy the events you select into its own planner. It never modifies or deletes anything in your phone calendar, and the permission is used for nothing else.
Signing in with Google is optional. If you do, 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 (backup and sign-in) and Google AdMob (advertising, described above), we use no other third-party services.
This section explains how to delete your Kumsing account (developer: Kangla Labs) and the data associated with it.
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 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