Privacy policy

The app and this website, tithicalendar.in, are published by ACKPlus. We decide what the app does with the small amount of information described here, which makes us the data controller - the data fiduciary, in the words of India's Digital Personal Data Protection Act, 2023.

Anything you want to ask, correct, withdraw or complain about goes to contact@ackplus.com. A person reads that address. It is also the address for a grievance under the DPDP Act and for a request under the GDPR or any comparable law where you live.

• There is no account and no sign-in.
• There is no advertising, no advertising identifier, no ad personalisation and nothing sold or passed to a data broker.
• The app does send crash reports and basic usage statistics to Google Firebase - which screens are opened, and what broke. It has its own section below, and it never carries what you wrote, where you are, or anything you saved.
• This website counts visits with Google Analytics: which pages are opened and which of its buttons are used, never what you type into it. The pages the app opens inside itself are not counted.
• Your place, your events, your photos and your settings stay in the app's own storage on your device. We never receive them.
• Two things leave your device only when you press a button: a report that a date looks wrong, which is always anonymous, and feedback, where a name and an email address are optional fields you can leave empty.
• We do not sell your personal data, we do not share it with anyone for their own purposes, and we never use it for advertising.

Sunrise decides which day a tithi falls on, so the panchang depends on where you are. If you allow location access, the app reads your approximate (coarse) position and uses it to compute sunrise, sunset and the timings of the day. The coordinates are stored in the app's own database on your device and are never sent to us.

Location is optional. If you decline it, you can pick a city from a list instead and the app works exactly the same way. You can change the place, or switch from your live location to a chosen city, at any time in Settings.

To show the name of the place rather than a pair of numbers, the app asks the operating system's own geocoding service - Apple's on iOS, Google's on Android - to turn the coordinates into a town name. That request is made by the platform on your behalf and is handled under Apple's or Google's privacy policy. We do not receive it and we do not keep its result anywhere but your device.

Anything you save - an anniversary, a reminder, a note, a photo you attach to an event - is written to a database inside the app on your device. It is not backed up to us, not synced, and not readable by us.

The app asks for access to your photo library only at the moment you choose a picture for an event, and it reads only the picture you pick.

Export sends your events out through your phone's own share sheet, to wherever you choose to send them. That only happens when you ask for it, and the destination is yours, not ours.

Reminders are scheduled locally by your phone. No reminder is sent from a server, and we do not know which days you asked to be reminded about.

The app uses two Google Firebase services: Crashlytics, which tells us when the app has crashed, and Analytics, which tells us which screens people open. Both start when the app starts.

Crashlytics receives, when something goes wrong: what the code was doing at the moment it failed, your device model, your operating system version, and an identifier Firebase generates for the installation. Not your name, because it does not have one.

Analytics receives: the names of the screens you open, a short list of things you can do in the app - finishing the first-run setup, switching a festival calendar on, sending a report, sharing the app, being offered an update - and an identifier Firebase generates for this installation. Google also works out an approximate area from the internet address the request arrives on, the way any website can.

What neither of them receives: your place, your coordinates, your events, your notes, your photos, your reminders, anything you typed, or any name or email. The app has one file that talks to Firebase and it can only send the events listed above.

We use this to find crashes we cannot reproduce and to see which parts of the app people actually use. We do not use it for advertising, we have not switched on ad personalisation, and we do not combine it with data from anywhere else. Google processes it for us under their own terms.

The app has a feedback screen, and after you have had the app a couple of weeks it may ask you once whether you have anything to say. It asks once and does not ask again, whatever you answer. Everything about it is optional: you can ignore it, and you can send feedback without telling us who you are.

If you do send feedback, we receive what you wrote, an optional score out of five and - when the feedback is about a particular day or festival - which one. The screen shows you the technical details that go with it before you send: the app version and build, the platform, your chosen place and language, which festival calendars you have switched on, and which calendar data the app is carrying. You can read all of it on the screen, and nothing else about you or your device is included.

The name and email fields are optional and exist only so we can reply. Leave them empty and your feedback is anonymous. If you fill them in, we store them alongside your message so that a person can write back. We do not add you to a mailing list, we do not use the address for anything else, and we do not pass it to anyone. Ask us and we will delete your feedback and your details.

If you tell us a date looks wrong, that report is separate from feedback and is always anonymous. It carries no name, no email and no reply address at all - only the date, what your own almanac says, and how this build of the app computed it. There is no field in which to identify yourself, by design.

The app works fully offline. There are six things it can connect for, and nothing else. The first three happen on their own; the last three happen only when you open or send something yourself.

• Checking for, and downloading, an updated calendar database, so that new festival dates and corrections reach you.
• Downloading festival artwork that is not already bundled with the app.
• Asking the platform's own geocoder for the name of your place, described under Location above.
• Opening this policy, the terms or the help page from Settings, which loads that page from tithicalendar.in inside the app.
• A report that a date looks wrong, which carries no identity.
• Feedback, which carries a name and an email address only if you typed them.

The downloads are plain requests for a file, and the pages load the way any browser loads a page. None of them carries your location, your events, an account or an identifier for your device, and nothing about you is attached to them.

tithicalendar.in shows no advertising. In a browser it counts visits with Google Analytics, so that we know which pages are read and which need work: the address of each page opened (which never holds a date, a place or anything else you entered), the page you came from, your browser, device type, screen size and language, a country and city worked out by Google from your connection, and some of the site's own buttons when used - a store button, a Support us button and where on the site it was, the support page's pay button, the birth tithi form (that it was used, never the date or time you gave it) and the language you switched from and to. Google Analytics sets its own cookies, named _ga, to tell one visit from the next. Google Signals and ad personalisation are switched off, so none of this is joined to a Google account or used for advertising, and Google Analytics does not store your IP address.

The pages the app opens inside itself - help, this policy and the terms - carry no analytics, and neither does a visit leave anything beyond the ordinary server access log described below. To browse the website without being counted, block cookies for it or use Google's Analytics opt-out browser add-on.

Besides Google's, there are two cookies, and each holds one choice you made. The first is the language you chose, as en, gu or hi, set when you pick a language so that the site opens in it next time. The second is which festivals you chose to see, as the names of the traditions you kept, such as gujarati_hindu, set only if you change that choice. Each is read by this site alone, to decide what to show you. Neither is an identifier, nothing is counted with them, and they are not sent anywhere else. Clearing your browser's cookies for this site forgets both, and the site then opens in English with every festival until you choose again.

If you sign in, a third cookie, tc_session, keeps you signed in. It holds a random code that only our server can match to your account; scripts on the page cannot read it, and it is not sent to any other site. Signing out, or deleting your account, ends it, and it lapses after 180 days without a visit.

The app takes no payment. If you make a payment to us on this website, Razorpay processes it and asks for what it needs to do so; we never see your card or UPI details. Razorpay gives us your name, your email address or phone number, and the amount, and we keep them for our accounts for as long as Indian tax law requires. We use them for nothing else. Razorpay's checkout may set its own cookies, under Razorpay's privacy policy.

Signing in is optional: every calendar, festival and panchang page works without it. You can sign in on this website with Google, to ask the built-in AI about a day or a festival. Google tells us your Google account's name, email address and its identifier for you, and our own server keeps you signed in with a cookie of ours that only it can read. We keep those, your credits and their history in your account on our server.

When you ask a question, we send the AI company that answers it your question, the language you read in, and the app's own data for that day or festival (its panchang times and festival dates). We do not send your name or email address. We keep each question, the data it was sent with and the answer on our server, to run the feature, to check answers you report, to stop misuse, and to make the answers better.

Before your first question we ask whether we may also use your questions and answers to train our own AI. Both answers let you ask, and you can change it any time on your account page. Questions are used for training only if you said yes when you asked them, and never with your name or email.

You can delete your account on the account page. That deletes your name, email, sign-in identifier, credits and their history at once. The questions you asked are kept, but no longer linked to you or to any account.

We keep the number of other companies in this as small as we can manage, and none of them is an advertising company or a data broker.

• Our own server at tithicalendar.in, which serves the calendar database, the festival artwork and this website. As with any request to any website, the server that answers sees your device's IP address and the time. Those ordinary access logs are used to keep the service running; they are not linked to anything else about you, and neither the correction endpoint nor the feedback endpoint stores the address.
• Google Firebase, which receives the crash reports and usage statistics described above, and processes them for us.
• Google Sign-In, which confirms who you are to us when you choose to sign in with Google, as described above.
• The AI companies that answer questions, today Anthropic, which receive a question with the app's data for it, never your name or email, and answer it for us under their terms for businesses, which do not let them train on it.
• Google Analytics, which counts visits to this website as described above, and processes them for us.
• Apple and Google, whose geocoding services turn coordinates into a place name, as described above.
• Razorpay, which takes a payment made to support us, as described above, under its own privacy policy.
• The App Store and Google Play distribute the app and collect their own information about downloads under their own privacy policies. We see only the anonymous, aggregated statistics each store shows a developer.

We do not sell personal data and we do not share it for anyone else's purposes. If the app is ever transferred to a different publisher, this page changes before that happens and says so.

Everything the app holds about you lives on your device for as long as the app is installed, and uninstalling removes it.

Feedback you sent us is kept while we are still acting on it and for up to two years afterwards, so that a report of a wrong date can still be checked against the year it was about. If it carried your name or your email, ask us and we will delete it sooner. Correction reports carry no identity, so there is nothing in them to delete.

Your account is kept until you delete it. Questions and answers are kept for as long as the feature runs, and once your account is deleted they no longer name you.

Server access logs are kept for a short operational period, measured in weeks, and are then discarded. Crash reports are kept by Firebase for ninety days and usage statistics for fourteen months, which are Google's own retention periods for those services. Google Analytics keeps what it counts on this website for the period set in our account, which is at most fourteen months, the longest it allows.

Where India's DPDP Act applies, the basis is your consent: you choose to send feedback, and the name and email fields are yours to leave empty. Where the GDPR or a similar law applies, the basis for the optional name and email is likewise your consent, given by typing them in, and you can withdraw it at any time by asking us to delete them. The basis for the rest - answering you, and fixing a date that is wrong - is our legitimate interest in making the app correct, which is also the reason you wrote to us.

For the crash reports and usage statistics, the basis is our legitimate interest in knowing that the app works and where it does not. If you would rather not be counted, uninstalling stops it entirely, and you can ask us to delete what is held against your installation identifier. The same interest, in knowing which of the website's pages are read, is the basis for counting visits to it; blocking its cookies stops it.

There is no automated decision-making and no profiling anywhere in the app.

You can ask us for a copy of anything we hold about you, ask us to correct it, ask us to delete it, withdraw a consent you gave, or object to what we are doing with it. Write to contact@ackplus.com and we will answer within thirty days.

Almost always the honest answer will be that we hold nothing, because there is no account and nothing is uploaded. The exception is feedback you sent with your name or your email on it, and that we can find and delete.

If you are not satisfied with how we answer, you can complain. In India that is the Data Protection Board. In the EEA or the UK it is your national data protection authority.

The app is not directed at children, has no account, and asks for nothing about anyone. We do not knowingly collect personal data from a child. If a child has sent us feedback with a name or an email on it, write to us and we will delete it.

Everything the app keeps stays in its own private storage on your device, protected by the operating system in the same way as any other app's data. Every request the app makes uses HTTPS, so nothing it sends can be read or altered on the way. Access to the small amount of feedback we hold is limited to the people who work on the app.

No system is perfect. If something we hold is ever exposed, we will say so on this page and tell the relevant authority as the law requires.

We are in India and our server is operated from there. If you write to us from outside India, the message and anything in it is read in India. The only thing this can involve is feedback you chose to send.

• Approximate location - to compute the panchang for where you are. Optional; a city list does the same job.
• Notifications - to show the reminders you set. Optional.
• Alarms and reminders (Android) - so that a reminder arrives at the time you chose rather than whenever the system next wakes up.
• Photos - only when you attach a picture to one of your own events.

If the app ever starts doing something this page does not describe, this page changes first and the date at the top changes with it. If a change matters to you - anything that would mean us collecting something new - the app will tell you rather than leaving it here to be found.

Questions, requests and complaints about this policy or about anything we hold: contact@ackplus.com.

ACKPlus, tithicalendar.in.