Privacy Policy

The application this policy covers

This policy applies to Amla Dharma Calendar, the Android application published under the package name com.findnsecure.amladharmacalendar. It does not apply to any other application.

The application is developed and published by Embarc Information Technology Pvt. Ltd., 39, Old Vijay Nagar Colony, Agra – 282 004, India. You can reach us at support@embarc.co.in or on +91-562-3511073.

The short version

Amla Dharma Calendar collects nothing about you.

It has no account, no server, and no analytics. It does not ask for the internet permission, so on Android it is not merely that the app chooses not to send anything — the operating system will not let it. Everything it shows is calculated on your own device.

Information we collect

None. We do not collect, store, transmit, sell or share any personal information. Specifically, the application does not collect:

• names, email addresses, phone numbers or any contact details
• accounts, usernames or passwords — there is nothing to sign in to
• device identifiers, advertising IDs or analytics identifiers
• location data
• photos, files, contacts, microphone or camera input
• crash reports or diagnostics sent to us
• the dates you look up, the place you select, or the results you are shown

What you enter stays on your device

To answer a question, the app needs a date, a place chosen from a built-in list, and a few optional details about what you are asking. These are used only to perform the calculation on your device, in memory, while the app is open.

They are not transmitted anywhere, because the application has no ability to transmit anything. They are also not saved: the app keeps no history. Close it and reopen it, and it starts again at today's date with no record of what you asked before.

Permissions

The application requests no Android permission that grants it access to your data or your device. In particular it does not request:

• INTERNET — not requested; the app cannot open a network connection
• ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION — not requested; location is chosen from a list inside the app, not read from the device
• CAMERA and RECORD_AUDIO — not requested
• READ_CONTACTS — not requested
• storage and media permissions — not requested
• POST_NOTIFICATIONS — not requested; the app sends no notifications

The one entry that does appear

A single permission entry appears in the application's manifest: com.findnsecure.amladharmacalendar.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION. It is added automatically by AndroidX, a standard Android support library, so that the library can register an internal event receiver safely.

It is declared at signature level and scoped to this application, meaning only a build signed with the same key could ever hold it. It grants access to nothing, reads no data of yours, and cannot open a network connection.

You can verify all of this yourself: on your device, under Settings → Apps → Amla Dharma Calendar → Permissions — and, once the application is published, on its store listing under App info → Permissions.

No network use

The application works entirely offline and is designed to. All of its content — the research material, the rules, and the astronomical routines used to calculate the pañcāṅga — is contained in the app itself. Nothing is downloaded at runtime, no content is fetched from any server, and no third-party service is contacted.

The application does display reference URLs for the traditional sources it cites, so that you can look them up yourself. These are shown as text. The app does not fetch them.

No cookies or stored data

The interface is built with web technology running inside the app, but it uses none of the storage that normally implies. There are no cookies, no localStorage, no sessionStorage, no IndexedDB and no web SQL database. No service worker is registered. The app stores no files.

Android's automatic cloud backup is explicitly disabled for this application, so nothing belonging to it is copied to any backup service.

No analytics, advertising or tracking

The application contains no analytics SDK, no crash-reporting service, no advertising library and no tracking of any kind. There are no advertisements and no in-app purchases. We do not profile users, because we have no information with which to do so.

Data deletion

There is nothing of yours for us to delete. The application has no account, collects nothing, and keeps no history: the date and place you enter are used for the calculation and are gone when you close the app. Nothing is transmitted to us, so we hold no record of you to erase on request.

To remove the application and everything it carries, uninstall it in the ordinary way. Because Android's automatic cloud backup is disabled for this application, uninstalling leaves no backup copy behind.

Security

The protection here is architectural rather than procedural: there is no data to protect. The application stores nothing and transmits nothing, and it holds no INTERNET permission, so it cannot open a network connection — there is no transmission to intercept and no server holding your information to breach. What you enter exists only in memory while the app is open.

No claim of encryption, security certification, independent security audit, or compliance with any security standard is made here, because no such thing has been carried out for this application.

Children

The application is suitable for general audiences. Because it collects no data at all, it collects no data from children either.

What this policy does not cover

This policy describes the application. It does not, and cannot, describe the behaviour of other parties:

• Google Play collects its own data when you find, install or update any app — for example download records and device information — under Google's own privacy terms. That is outside our control and is not covered here.
• Your device and operating system may collect diagnostics independently of any app, according to your own device settings.
• Websites you visit yourself after reading a source citation in the app are governed by their own policies.

How each claim can be verified

Every statement above is a description of how the application is built, and each is checkable in its source repository by automated audit rather than by assertion:

• No permission granting any access — the built artifact's permission list is inspected, and the audit fails on any android.permission entry
• Cannot use the network — INTERNET is absent from the merged manifest; on the device, the app's uid does not hold the kernel group that permits a socket call
• No analytics or crash reporting — no such dependency exists, and the audit fails if one is added
• No remote content — no configured server address, and nothing loadable from a third-party origin
• No cookies or stored data — the shipped bundle is scanned for cookie, localStorage, sessionStorage, IndexedDB, WebSocket, EventSource, sendBeacon, service worker and push APIs; none are present
• Backup disabled — allowBackup is set to false in the manifest

Changes to this policy

If this policy changes, the effective date above will change with it, and the revised policy will replace this one at the same address. Because the application collects nothing, we do not expect material changes unless the application itself gains a capability it does not have today.

Contact

Embarc Information Technology Pvt. Ltd., 39, Old Vijay Nagar Colony, Agra – 282 004, India.

Email support@embarc.co.in · Telephone +91-562-3511073 · https://www.embarc.co.in