Privacy Policy

Who we are

This policy applies to the MyJar app, published as com.myjar.app on Google Play and com.myjar.myjar on the App Store.

MyJar is developed and published by Sandip Pandey, Kalanki, Kathmandu 44600, Bagmati Province, Nepal, who is the party responsible for the information described here.

Privacy questions: sandipvai4456@gmail.com. Use of the app is also covered by the Terms of Use.

Information stored on your device

MyJar stores jar names, target and saved amounts, deadlines, status, deposits, withdrawals, and app preferences locally. Cached exchange rates and optional weather display data may also be stored locally.

This information is not uploaded to a MyJar account or server, because MyJar has no account or cloud-storage service. It is not sent to Firebase, RevenueCat, or any other service named in this policy.

Usage analytics

MyJar uses Google Firebase Analytics to understand how the app is used in aggregate — for example which screens people open, and whether a release is being adopted.

MyJar records screen views. It does not send any custom event containing your savings information: no jar names, no amounts, no deadlines, no transaction history.

Firebase Analytics automatically collects some technical information of its own, including a randomly generated app-instance identifier, device model, operating system version, app version, language, session and first-open timestamps, and an approximate region derived from your IP address. This identifier is specific to this app on this device.

MyJar contains no advertising SDK, does not use the device advertising identifier (IDFA or Android Advertising ID), and does not track you across other companies' apps or websites.

Crash reporting

MyJar uses Firebase Crashlytics so that crashes and unhandled errors can be found and fixed. When the app fails, a report is sent containing the error and stack trace, the device model and operating system version, the app version, and general device state such as available memory.

Crash reports describe the code that failed. They are not designed to carry your savings data, and MyJar does not attach jar names or amounts to them.

Push notifications

MyJar uses Firebase Cloud Messaging to send occasional announcements, such as news about a new feature. To deliver these, your device is issued a registration token by Apple or Google and that token is held by Firebase.

A token identifies a device installation, not you. MyJar does not attach your savings information to it and does not send savings details through a notification server. Push messages are separate from savings reminders, which are described in section 07.

Purchases and MyJar Pro

MyJar Pro is sold through the App Store or Google Play. Your payment details are handled entirely by Apple or Google — MyJar never sees or stores your card number.

MyJar uses RevenueCat to check whether a purchase is active. RevenueCat receives the purchase receipt and transaction information from the store, the store country, and basic device information, and issues a randomly generated anonymous identifier for the installation.

MyJar does not send RevenueCat your name, email address, or any savings information, and does not link purchases to a MyJar account, because there is no account to link them to.

Savings reminders

MyJar may request permission for optional reminders. These are scheduled and shown entirely on your device by the operating system. Their contents are not sent anywhere.

Approximate location and weather

If you enable Location Weather, MyJar requests approximate foreground location. Coordinates rounded to two decimal places are sent to OpenWeatherMap to retrieve current weather for the decorative app window.

MyJar does not request background location, create a location history, use location for advertising, or sell location data. You can decline or revoke permission at any time.

Exchange rates

MyJar requests public currency rates from ExchangeRate-API for converted totals. Requests do not include jar names, savings amounts, or transaction history. External services may receive normal network data such as IP address and request time.

Biometric authentication

If biometric lock is enabled, your device performs the authentication — Face ID or Touch ID on iOS, the biometric prompt on Android. MyJar receives only the result and does not receive, store, or transmit biometric templates.

Third-party services

MyJar does not sell personal information and contains no advertising SDK. The services below receive only what their entry describes.

Where information is processed

Firebase is operated by Google and RevenueCat by RevenueCat, Inc. Both process data on servers outside your country, including in the United States. Where required, transfers rely on the safeguards those providers publish, such as the European Commission's standard contractual clauses.

Their own policies apply to what they receive: Firebase and RevenueCat.

Your choices

• Location. Turn off Settings → Privacy → Location weather in MyJar, or revoke the permission in your device settings.
• Notifications. Turn reminders off in MyJar, or revoke the notification permission in your device settings. Revoking it also stops announcements.
• Biometric lock. Turn it off under Settings → Privacy in MyJar.
• Local data. Use Settings → Your data → Clear all MyJar data, or uninstall the app.
• Analytics and crash reporting. MyJar does not currently offer an in-app switch for these. Uninstalling the app stops all further collection.

Depending on where you live, you may have rights to access, correct, delete, or object to the processing of personal information. Savings data is local, so you exercise those rights on your own device. For anything held by the services above, contact sandipvai4456@gmail.com.

Security

Core savings information stays in private local app storage. Online requests use HTTPS. Optional biometric lock adds device-level protection. No storage or transmission method can be guaranteed completely secure.

Retention and deletion

Local data remains until you delete it. Use Settings → Your data → Clear all MyJar data, or uninstall MyJar. Device backup or device-management settings may operate outside MyJar's control.

Analytics and crash data are retained by Firebase under Google's retention settings and deleted on their schedule. Purchase records are retained by RevenueCat and by Apple or Google for as long as their own policies and tax obligations require. MyJar has no cloud account data to delete.

Children's privacy

MyJar is a general-audience savings utility and is not directed to children under 13. It does not knowingly collect personal information from children.

Policy changes

This policy may be updated when features, data practices, or legal obligations change. The revised policy will show a new "Last updated" date.

August 12, 2026: updated to describe the analytics, crash reporting, push notifications, and paid subscriptions introduced in MyJar 2.0, and to cover the iOS release alongside Android.

Contact

For privacy questions, or to exercise any right described in section 13, contact: