Privacy Policy

Last Updated: 11 September 2026

This Privacy Policy explains how the Aavak Javak mobile application and its referral website (together, the “Services”, “App”, “we”, “our”, or “us”) access, process, store, back up, restore, export, and share information on Android, iOS, and iPadOS. Aavak Javak is a bookkeeping and record-management tool for income, expenses, accounts, categories, balance transfers, Customer Ledger, Milk Account, Notes & Reminder, reports, backups, and related personal or business records. It does not provide banking, lending, investment, payment-processing, or financial-advisory services.

1. Bookkeeping Information Entered by the User

The App may process information voluntarily entered or created by the user, including:

• Income and expense records, amounts, dates, categories, notes, and transaction details
• Accounts, opening balances, account order, default account, and balance transfers
• Custom categories and category icons
• Customer names, optional mobile or WhatsApp numbers, addresses, notes, reference numbers, linked accounts, and Customer Ledger entries
• Credit, payment, Jama, Udhar, Aavak, Javak, and balance records
• Milk quantity, Gram or Liter unit, rate, morning/evening entries, payments, and related records
• Notes & Reminder titles, descriptions, selected dates and times, Reminder ON/OFF status, Once/Daily/Weekly/Monthly/Yearly repeat rule, Completed/Pending status, creation/update times, and local notification identifiers
• Shop name, shop mobile number, address, and business details
• Language, currency, filters, display, reminder, security, backup, and other supported settings

This information normally remains on the device unless the user chooses Google Drive Backup, manual backup, export, sharing, or voluntarily sends information to us for support. Never enter or send: Google or Apple passwords, bank passwords, UPI PINs, card PINs, OTPs, complete card details, authentication tokens, or similar sensitive credentials.

2. Customer and Third-Party Information

Users are responsible for ensuring that customer or third-party information is collected, stored, used, backed up, exported, and shared lawfully. Users should obtain any permission or consent required before storing or sharing another person’s information.

3. Phone Contacts and Customer Import

Android: When the user deliberately selects “Add Contact”, the App may open the Android system Contact Picker. Only the selected contact’s available display name and phone number are returned for review. The App does not automatically scan or upload the complete address book and does not request broad Contacts permission for this picker flow. iOS/iPadOS: The current App version does not access the Contacts database or provide contact import. Customer details are entered manually. After the user saves a selected contact in Customer Ledger, it becomes local App data and may be included in a user-initiated backup or export. Changing or deleting the original phone contact does not automatically change or delete the saved customer in Aavak Javak.

4. Local Data Storage

Bookkeeping records, Notes & Reminder records, and many App preferences are stored in the local device database and local preferences. Notes search, calendar markings, Day/Month/Year/Upcoming/Completed filters, and completion calculations are performed locally. Local records remain until the user edits or deletes them, clears App storage, restores different data, resets local data, or deletes/uninstalls the App, subject to platform and device behavior. The current Android configuration disables automatic Android App backup for Aavak Javak. Device-manufacturer transfer or operating-system behavior may still vary. Search text is processed locally and is not uploaded as a separate search-history record. Notes & Reminder notifications: When the user turns a note reminder ON, the App provides the note title and, where entered, its description to the device’s local notification system and schedules it for the selected date/time and repeat rule. The notification contains an internal note reference so tapping it can open the related note. Depending on the user’s device and lock-screen settings, the title or description may be visible to anyone who can view notifications on that device. Users can turn Reminder OFF, mark the note completed, delete the note, disable App notifications, or hide notification previews in device settings. These are local notifications; Aavak Javak does not send note content to its referral backend for notification delivery.

5. Sign-In and Firebase Account Information

The App uses Firebase Authentication with Google Sign-In and may offer Sign in with Apple on Apple platforms. Sign-in supports account features including purchase verification/restoration, Google Drive Backup eligibility, and Refer & Earn. Depending on the provider, we may process the display name, email or Apple private-relay email, profile-photo URL, Firebase user identifier, login provider, email-verification status, and session-related information. We do not receive or store the user’s Google or Apple password.

6. Firebase and Purchase-Entitlement Information

Firebase and the App backend may process limited account and one-time purchase information, including:

• Firebase user identifier, name, email, profile-photo URL, and login provider
• Product identifier and entitlement/restoration status
• Order, transaction, purchase, or verification reference
• Purchase token, receipt-related information, or a cryptographic hash where applicable
• Purchase, acknowledgement, refund/reversal, and verification timestamps or status
• Security, fraud-prevention, and entitlement-ownership records

Android purchases are processed by Google Play. iOS/iPadOS purchases are processed by Apple through StoreKit/App Store. We do not receive or store complete card, UPI, bank-account, Apple Pay, or Google Play payment credentials. Income, expense, account, category, balance-transfer, Customer Ledger, selected-contact, Milk Account, Notes & Reminder content, and backup contents are not uploaded to Firebase as bookkeeping records.

7. Google Drive Backup

Google Drive Backup is optional and available only when the App recognizes the required signed-in account and purchase entitlement. It uses the limited drive.appdata scope and stores backups in the hidden App Data folder of the user’s own Google Drive account. This folder is not displayed in the normal My Drive file list and is intended to be accessible only by this App. The selected Drive account must match the current App/Firebase login email. A one-way email hash may be stored in backup metadata for account matching. The developer does not receive or keep the Drive backup in the developer’s Firebase database or referral server.

8. Auto Backup, Manual Backup, and Restore

Google Drive Auto Backup is off by default. If enabled, the App may create an initial backup and later create one monthly backup when a new month begins and the App is opened or becomes active, subject to internet access, authorization, account matching, and entitlement verification. The App cannot guarantee an exact backup time while fully closed. Eligible users may also select Backup Now or Restore from Google Drive. Turning Auto Backup off stops future automatic backups but does not delete existing Drive backups.

9. Information Included in Backups

A complete Google Drive or manual JSON backup may include supported transactions, accounts, balances, account order, categories, Customer Ledger data, selected phone numbers, addresses, transaction/customer notes, shop details, Milk Account data, Notes & Reminder titles and descriptions, dates/times, Reminder ON/OFF status, repeat rules, Completed/Pending status, local notification identifiers, language, currency, supported settings, a one-way PIN hash, creation time, source version, record counts, and an integrity digest. Restoring a backup that contains Notes & Reminder data may recreate enabled local reminders, subject to notification permission and platform scheduling rules. The actual App PIN is not included. The current implementation may keep the latest 12 Aavak Javak backups and delete older App backups after a successful Drive upload.

10. Backup Security

Backup data is transmitted over HTTPS. Hidden App Data storage is not the same as end-to-end encryption. The current JSON backup uses an integrity digest to detect incomplete or modified data; the digest is not encryption. The backup is not encrypted with a separate App-specific password or end-to-end encryption key.

11. Manual JSON Backup and Restore

Users may create and restore a manual JSON backup. The user controls the save location. If the user stores or shares it through Drive outside the App, iCloud, WhatsApp, email, or another service, that service’s privacy practices apply. Restore may replace local data; users should create a current backup before restoring older data.

12. Excel Export and External Sharing

At the user’s request, the App may create an Excel workbook containing Aavak Javak entries, Accounts, Milk Account, Customer Ledger, and a Notes Reminder sheet. The Notes Reminder sheet may include note title, description, date, time, Reminder ON/OFF status, repeat rule, and Completed/Pending status. Exported files are handled by the storage location, receiving application, service, recipient, and user after they leave the App. When the user chooses WhatsApp or another share option, the App prepares content and opens the selected external application. Messages are not sent automatically; the user must review and send them.

13. Advertising and Ad Privacy

The free version may display banner, interstitial, and voluntarily viewed rewarded advertisements through Google AdMob. Depending on consent, platform settings, SDK behavior, and applicable permissions, Google Mobile Ads may process IP address, approximate location inferred from technical data, advertising or installation identifiers, App/product interactions, ad interactions, consent status, diagnostic/performance information, and fraud-prevention signals. On Android, the App declares Advertising ID access for supported advertising. Users may reset or delete the Advertising ID through Android settings where available. On iOS/iPadOS, the current App does not intentionally request IDFA access through App Tracking Transparency. If tracking practices change, the App, this policy, and store disclosures will be updated before tracking that requires permission is used. Bookkeeping records, Customer Ledger data, selected contacts, and backup contents are not provided by us to AdMob for advertising personalization.

14. Rewarded Ads Free Feature

The user may voluntarily watch one rewarded ad to hide eligible advertisements for the remainder of that day. The reward status may be stored locally. Watching a rewarded ad does not create a Lifetime entitlement or Google Drive Backup eligibility.

15. Lifetime Ads Free Purchase

The App may offer a one-time Lifetime Ads Free purchase that removes eligible advertisements and unlocks Google Drive Backup while the entitlement remains valid under the applicable App and store conditions. Payment and independent store transaction history are controlled by Google Play or Apple.

16. Refer & Earn Account and Wallet Information

Refer & Earn is optional and requires sign-in. The App may send limited information over HTTPS to the Aavak Javak referral backend, including:

• Firebase user identifier, name, email, verification status, and platform
• User referral code, applied code, referral relationship, attribution date, and status
• A hash of a randomly generated App installation identifier
• IP-derived security hashes, request timing, rate-limit records, and fraud/risk flags
• Verified purchase, order/transaction reference, purchase-token hash, amount, currency, purchase/refund status, and Approve Period information
• Welcome Bonus, reward, pending/available/paid/cancelled commission, immutable wallet entries, and withdrawal history
• Withdrawal amount, selected method, payout details, and mandatory WhatsApp number

The Firebase ID token is sent so the backend can verify the signed-in user. Database credentials and private administration keys are not included in the public App or website. Referral data is used for program operation, purchase/refund verification, payouts, support, security, fraud prevention, payment reconciliation, and legal/accounting needs; it is not sold or used to build advertising profiles.

17. Three-Day Qualifying Activity Proof

When a referred user saves an eligible income or expense entry, the App may send the referral backend a random one-time event identifier and the general entry type (income or expense). The App does not send the entry amount, category, note, user-entered date/time, account, customer, local row identifier, or other bookkeeping content for this activity check. The backend records its own server-received time and uses server time—not the phone’s clock—to determine the configured activity sequence. Under the current rule, an event less than 24 hours after the previous valid event is too early; an event at or after 48 hours begins a new Day 1 sequence. The qualifying-day count, cycle/reset count, completion status, and reward record may be stored for referral administration and fraud prevention.

18. Referral Website, Login, and Security Logs

A public referral link may open https://www.aavakjavak.com/r/ followed by a referral code. The page may display the public referral code, referrer display name, current offer information, and download links. Google or Apple sign-in may be offered through Firebase; manual password/account creation is not offered on that referral page. For referral attribution and security, the website/backend may process the referral code, click token, short-lived web-flow token, selected login provider, Firebase identity information, browser/device platform, user-agent information, request time, and an IP-derived security hash. The raw database password, service credential, and administration key are not exposed in the page.

19. A4 Referral Poster, QR Code, PDF, and Video

A signed-in user may open the public referral page and download a Color or Black & White A4 referral poster. The poster is generated in the browser and may contain the referrer’s display name, public referral code/link, QR code, current promotional amounts or rules, and App Store/Google Play information. The QR code contains the public referral URL. It does not contain the Firebase user identifier, email address, ID token, database credentials, wallet balance, or administration key. The downloaded PDF is saved or shared only through the user’s browser/device actions. Copies printed, downloaded, or shared by the user remain under the user’s or recipient’s control. The App may retrieve language-specific Home or Refer & Earn PDF links and an information-video link selected through the Aavak Javak Admin Panel. Supported PDF pages may be displayed from Google Drive, Google Docs, or an Aavak Javak domain. Supported videos may be embedded from YouTube or YouTube’s privacy-enhanced domain, with the administrator-selected 9:16 or 16:9 display ratio. These settings are public App configuration and do not include the user’s local bookkeeping or note content. Opening an embedded or external PDF, video, store listing, privacy page, deletion page, WhatsApp link, or other third-party destination may allow that provider to process the user’s IP address, browser/WebView information, cookies, account status, viewing interaction, and other technical information under its own privacy policy. Aavak Javak does not intentionally send local transactions, customer records, Milk Account data, backup contents, or Notes & Reminder content with these media requests.

20. Automatically Processed Technical Information

The App, referral website, and integrated providers may process device type, operating-system and App version, package/bundle information, installation information, network/IP information, authentication status, Drive request status, advertisement interactions, purchase/restoration status, error/diagnostic information, rate-limit data, and security/fraud signals as needed to operate and protect the Services.

21. Permissions and Device Access

Depending on the platform, version, and feature selected, the App may use:

• Internet and network-state access
• Google or Apple authentication
• Google Drive App Data authorization
• Android system Contact Picker for a deliberately selected contact
• System file/photo pickers for user-selected backup, restore, export, or image items
• In-App browser/WebView, external browser, WhatsApp, or share-sheet opening for user-selected links and media
• Local notification permission on supported platforms; Android may additionally use exact-alarm scheduling, boot rescheduling, wake, and vibration capabilities for enabled reminders
• Biometric/device authentication when the user enables it
• Google Play Billing or Apple StoreKit
• Android Advertising ID access for supported AdMob functionality

Biometric templates are handled by the operating system. Aavak Javak receives only the authentication result and does not receive or store fingerprint or Face ID templates. Local reminder scheduling does not require normal remote push-notification delivery. Reminder title/description content is passed locally to the operating system so it can display the user-requested notification.

22. How Information Is Used

Information is used only as reasonably necessary to provide App features, authenticate users, calculate local totals, create backups/exports, verify or restore purchases, display ads, operate Refer & Earn, calculate server-time activity eligibility, process withdrawals, prevent fraud/abuse, maintain security, diagnose errors, meet legal/accounting obligations, and respond to support/privacy requests.

23. Service Providers and Data Sharing

We do not sell or rent user data. Limited information may be processed by Google Firebase, Google Sign-In, Google Play, Google Drive/Docs, Google AdMob, YouTube, Apple Sign in with Apple/App Store/StoreKit, the Aavak Javak hosting and database provider, system notification/file/contact pickers, and user-selected sharing/storage services. Information may also be disclosed when required by applicable law or a valid legal request. Third-party services process information under their own terms and privacy practices. Useful references include Google Privacy Policy, Firebase Privacy and Security, and Apple Privacy Policy.

24. Data Security, APKs, External Links, QR Codes, and Fraud

We use reasonable technical and administrative safeguards for information under our control, including HTTPS, authentication, server-side token verification, access controls, rate limits, input validation, unique/idempotent transaction protection, and fraud review where applicable. No device, application, storage method, cloud account, or internet transmission can be guaranteed completely secure. To the fullest extent permitted by applicable law, the Aavak Javak developer/administrator is not responsible for malware, fraud, payment loss, credential theft, data loss, device damage, unauthorized account access, misleading content, or other harm caused by installing an unofficial, modified, repackaged, cloned, or third-party APK/App; bypassing platform security warnings; opening or sharing an external link; scanning or paying through a third-party, altered, substituted, or unverified QR code; or providing credentials or money to another person or service. External websites and services are not controlled by Aavak Javak merely because a user can open them from the App. This limitation does not exclude any responsibility that cannot lawfully be excluded and does not reduce our obligation to use reasonable safeguards for systems and links under our direct control. Users should report a suspicious Aavak Javak link, QR code, APK, payment request, or impersonation attempt to the contact address below.

25. Data Retention

Local information remains until the user removes it as described above. Drive backups remain until deleted by backup cleanup, the user, or Google. Login, purchase, referral, activity-proof, wallet, withdrawal, payout, rate-limit, audit, and fraud records may remain while an account/program is active and afterwards only as reasonably required for purchase restoration, refunds, payout reconciliation, security, fraud prevention, disputes, tax/accounting, or legal compliance. Manual backups, Excel files (including Notes Reminder sheets), screenshots, printed posters, QR posters, shared messages, and copies stored by external media/services remain wherever the user or recipient/provider stores them. Local scheduled reminder data remains until the note/reminder is disabled or deleted, the relevant App data is cleared/restored, or the App is deleted, subject to platform behavior. Google Play, Apple, Google/YouTube, and other providers may maintain independent records under their own retention policies.

26. Account and Data Deletion

Users may initiate account and data deletion through the Data Deletion option in the App or through the public page below without reinstalling the App:

Request Account and Data Deletion

A valid request may delete or anonymize eligible Firebase, login-profile, purchase-entitlement, referral-profile, attribution, activity-proof, wallet, withdrawal, payout-detail, and related online records under our control. Limited information may be retained when legally required or reasonably necessary for security, fraud prevention, refund/payout reconciliation, disputes, tax/accounting, or purchase verification. Deleting the online account does not automatically delete local App data, Notes & Reminder records, scheduled or already displayed local notifications, Drive App Data backups, manual backups, exported files, messages, printed/downloaded posters, recipient copies, external-provider records, or Google/Apple transaction history.

27. Children’s Privacy

Aavak Javak is a general bookkeeping and business utility and is not directed specifically to children. We do not knowingly request children to provide personal information. Contact us if you believe a child has provided personal information through the Services.

28. User Rights and Choices

Depending on applicable law and available features, users may access, correct, export, or delete local information; create, edit, complete, disable, or delete Notes & Reminder records; control notification permission and lock-screen previews in device settings; choose sign-in, backup, purchase, advertising privacy, contact picker, sharing, reminder, and biometric options; revoke Google/Apple authorization through account settings; and request access, correction, deletion, or anonymization of eligible online records under our control.

29. Changes to This Policy

We may update this policy when features, service providers, data practices, platform rules, or legal requirements change. The revised version will be posted with a new “Last Updated” date.

30. Contact Us

App: Aavak Javak Platforms: Android, iOS, and iPadOS Android Package / Apple Bundle ID: com.bindi.aavakjavak Email: vijyacrafto@gmail.com Data Deletion Page: https://birthdaymitra.com/aavak-javak-data-deletion/

---

© 2026 Aavak Javak. All rights reserved.