Last Updated: 5 November 2026
Version scope: Updated for Android 1.0.33 (Build 76) and iOS/iPadOS 1.0.19 (Build 63), including optional bill photos, uploaded category icons, monthly category budgets, related backups and budget reports. Features described for a particular platform or supported build may not be available in an older installed version.
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, optional monthly budgets, bill photos, 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.
The App may process information voluntarily entered or created by the user, including:
This information, including selected images, 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.
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.
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:
Supported builds can open Apple’s contact picker after the user requests contact selection. The selected name and/or phone number is used to fill the relevant form for review. This flow does not automatically scan or upload the complete address book. Manual entry remains available.
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.
Adding a bill photo or a custom category icon is optional. A user can keep ordinary bookkeeping records without attaching photos or uploading an icon. A selected image may contain names, merchant details, addresses, purchase information or other personal information visible in the image. Add only images you are entitled to use, avoid unnecessary sensitive details, and obtain any required permission from other people.
Android: Selecting Camera opens an installed camera application for a user-requested still image. Selecting Gallery opens the system document/image picker for a selected image. This receipt feature does not scan the gallery, request unrestricted photo/video storage access, or record video or audio. The App grants limited temporary access to the camera output file needed for capture.
iOS/iPadOS: Gallery selection uses Apple’s system photo picker to return only the selected image, without requesting access to the whole Photos library for this feature. Camera capture asks for camera permission and opens the camera interface after the user requests it. The feature does not record video or audio and does not automatically save the processed copy into the user’s Photos library.
Processing and storage: The App reads the selected image, corrects its displayed orientation where supported, resizes/re-encodes it, and saves a working copy in App-private storage. The original selected gallery image is not edited or deleted. Receipt images are stored as JPEG and uploaded icons as PNG. File identifiers/checksums and references link images to entries or categories, detect corruption and avoid storing identical processed images repeatedly. These identifiers are not encryption or anonymization. This feature does not perform OCR, extract receipt text into transaction fields, identify faces, or derive a user’s location from an image.
Where images go: Photo selection alone does not send the image to the Aavak Javak referral backend, Firebase bookkeeping storage or AdMob. Referenced photos and custom icons are included if the user chooses a complete local ZIP backup or authorizes a Google Drive backup, including an enabled automatic backup schedule. The App reads and transfers these images for backup and restore; they are not merely files handled outside the App. The Google account and chosen backup settings determine the cloud destination.
Reward/Premium notice: Before each receipt Camera/Gallery attempt, supported builds show a notice advising users to add only necessary photos because large collections can affect storage, backup time and performance. Free users can choose a rewarded advertisement or open the Premium plan. A completed rewarded ad provides one picker opening; cancelling after the picker opens uses that opening. Premium users receive the notice and can continue without this ad gate. A failed operation or late earned-reward callback is handled through the reward-recovery mechanism. Watching an ad is not consent to send the bill image to the advertising provider.
Removing a photo: Removing a photo from an entry, deleting an entry, or replacing an icon removes or changes the reference. The current implementation does not immediately erase all unreferenced App-private image files. A selected image may remain in private storage even after a cancelled entry form. Older backups, separate cloud photo objects and external copies may also remain. See Sections 25 and 26 for retention and removal.
Users may optionally set a monthly limit for an expense category. The App stores the limit locally and calculates spending, remaining budget, excess spending and related status from bookkeeping records. A budget is not a bank limit and does not prevent the user from entering further expenses. Complete backups may include budget settings. Selected Budget sections in Excel/PDF reports may include category names, monthly limits, date periods, expenses, remaining/excess amounts, percentages, entry counts and status.
Budget reports compare expenses with the currently configured monthly limits, including when reporting an earlier month. The feature does not maintain historical budget-setting versions. A partial-month report does not prorate the monthly limit; its expenses use the selected dates. Report creation does not change the stored budget or transactions.
Bookkeeping records, Notes & Reminder records, monthly budget settings, image references, 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. On iOS/iPadOS, operating-system device backups or transfers may include App data and private image copies depending on the user’s Apple/iCloud and device settings. Those system-managed copies are separate from the App’s optional Google Drive backup and have their own removal and retention controls.
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.
Home filters and monthly reminders (Android): The App stores the supported Month/All display choice and selected month locally. A new-month prompt changes which records are displayed; it does not delete earlier months. Notes & Reminder supports choosing a calendar date for a monthly reminder, using the selected day of the month and time. If that day does not exist in a month, the reminder uses that month’s last day. The reminder list may be displayed in pages of 10 items; pagination does not remove notes.
Demo Account (Android): When a user saves an expense without any balance account, the App can create an internal Demo Account and a matching automatic income entry for that expense. This is local bookkeeping support, not a real deposit, bank account, loan, or payment. The Demo Account is available in account management and expense selection but hidden from Home account cards. It cannot be renamed or selected for manual income or incoming transfers. User-created accounts remain available for manual income. Account order is stored locally; income selection skips the internal Demo Account. The expense and its automatic funding remain linked when edited, deleted, or backed up. These restrictions use the internal account designation, not just its displayed name.
Existing records: Hiding an account, an automatic funding entry, or an older month in a particular view does not erase the stored record. The update does not intentionally remove earlier manual Demo entries or reset an already stored account name.
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.
Firebase and the App backend may process limited account and one-time purchase information, including:
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, bill photos, uploaded category icons, budgets and backup contents are not uploaded to Firebase as bookkeeping records.
Google Drive Backup is optional and requires the supported signed-in account and Drive authorization. In current supported builds, manual backup/restore can be accessed through a valid Premium entitlement or an earned single-use rewarded-ad benefit. Automatic backup schedules require the supported Premium entitlement. Availability depends on the installed version. 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.
Automatic Drive backups are opt-in and require the supported Premium entitlement. Supported Android and iOS/iPadOS builds offer separate Daily Auto Backup and Monthly Auto Backup settings. The App checks whether a backup is due when it opens, resumes, or remains active, subject to internet access, existing authorization, account matching, and entitlement verification. A daily and monthly backup due at the same time may share one snapshot. Automatic attempts use existing authorization; if renewed authorization is needed, backup may wait until the user reconnects through the backup controls. The App cannot guarantee an exact backup time or a daily backup while fully closed. Other platform versions may offer a different subset of these options.
Eligible users may also select Backup Now or Restore from Google Drive. In photo-enabled builds, complete backups include referenced bill photos and uploaded category icons. An optional Wi-Fi-only setting can restrict the start of photo-containing Drive backups; it is off by default. Turning it on does not remove copies already uploaded. Turning off a particular automatic backup setting stops that schedule but does not delete existing Drive backups. Where both Daily and Monthly options are enabled, turn both off to stop both schedules.
A complete Google Drive or manual backup (ZIP in current photo-enabled builds, JSON in older builds) 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.
Backups also retain the internal Demo Account designation, automatic funding records and their expense links, and supported local display preferences, monthly category budgets, photo references and the images needed to restore them so restored accounting data remains consistent. Hiding automatic funding from history, an Excel worksheet or a PDF report does not remove it from a complete backup.
The actual App PIN is not included. In supported Android and iOS/iPadOS builds, automatic cleanup keeps snapshots for the latest 31 successful daily backup dates, 12 successful monthly periods, and 12 manual Drive snapshots for the same account and backup-device identifier. One snapshot may satisfy more than one group. Cleanup applies only to recognized, matching backup metadata after a successful upload; legacy or unrecognized backups and other devices’ backups are protected from this cleanup. This is not a guarantee of exactly 55 files or 31 consecutive calendar days. Manual JSON/ZIP files saved elsewhere are not managed by this Drive cleanup. These retention limits apply to recognized backup snapshots, not to all photo objects: current photo-enabled builds store images separately in Drive and do not automatically delete those image objects when a snapshot is removed.
Drive backup metadata may include an account-matching email hash, a random backup-device identifier, backup date/month, snapshot type, source version, and integrity information. These support account matching, restore, duplicate prevention and safe retention cleanup.
Photo backup storage: Drive snapshots refer to separately stored image objects in the same App Data area. Matching processed images can be reused by several snapshots. Metadata can include image identifiers/checksums, size, type, Drive file references and an account-matching email hash. Referenced images are downloaded and verified during restore. A local ZIP includes its bookkeeping JSON and the referenced image files together.
Backup data is transmitted over HTTPS. Hidden App Data storage is not the same as end-to-end encryption. The bookkeeping JSON and photo-backup checks use integrity digests/checksums to detect incomplete or modified data; these checks are not encryption. JSON/ZIP backups and image files are not encrypted with a separate App-specific password or end-to-end encryption key.
Current photo-enabled builds create a complete local ZIP backup containing bookkeeping JSON, supported settings and referenced bill photos/category icons. Compatible older JSON backups can still be restored; an older backup does not contain photos or budget settings that it never recorded. The user chooses the save or share destination. If a selected system file provider is a cloud provider, that provider may upload the chosen backup even though the App calls it a local/manual backup.
Files saved through Drive outside the App, iCloud, WhatsApp, email or another destination are handled under that service’s privacy practices. Restore may replace local records and recreate reminders. Create a current backup before restoring different data. Full backups contain more information than a filtered report; review the destination and protect the file. A bookkeeping reset or a restored snapshot does not necessarily erase all previously stored image files or external backup copies.
At the user’s request, supported Android and iOS/iPadOS builds can create Excel workbooks and PDF reports from local App records. Available report sections include Aavak/Javak history, charts, Accounts, Milk Account, Customer Ledger, Notes Reminder and, in photo/budget-enabled builds, Budget. Depending on the sections included, a report may contain amounts, balances, dates, categories, account or customer details, shop information, notes, reminder titles and descriptions, reminder date/time, Reminder ON/OFF status, repeat rules, and Completed/Pending status.
Filters and section selection: Export controls support date/period and category choices, including multiple selected categories, and may use the current search text for transaction history. Category selection affects the Aavak/Javak history and related chart/summary calculations; category-filtered totals exclude previous balance. It does not automatically limit the Accounts, Milk Account, Customer Ledger, Notes Reminder or Budget sections to those categories. Those sections keep their own existing report scope. The Budget section includes all expense categories and is not narrowed by the transaction category/search filter; its expenses follow the selected dates. All report sections are initially selected in the current export dialog; users can deselect unwanted sections. Review every included sheet or PDF page before sharing, even when a category or date filter has been chosen. Changing filters or deselecting sections does not delete stored data.
Current standard Excel/PDF accounting reports do not embed attached bill photos or uploaded category icon images. Full local/Drive backups do include referenced images. Budget details are included only when the Budget report section is selected.
Local PDF generation and viewing: PDF report content is prepared on the device from the same report data used for Excel. Android uses the device’s WebView/print components; supported iOS/iPadOS builds use Apple’s WebKit/PDF/printing components for local layout, rendering and preview. Its accounting-report renderer blocks network loads and bundles the required Noto Latin, Gujarati and Devanagari fonts with their license notices; generating a report does not download these fonts from a font service or upload the report to an online PDF-conversion service. Other App features, including Premium verification, may still use the network. These locally generated reports are separate from administrator-linked PDFs or videos described in Section 19.
Supported PDF controls include preview, download, export/share, and Print/Save PDF. Reports can use Color or Black & White styling, selected sections, and A4 portrait or landscape layout with margins and bordered tables. Presentation choices do not anonymize the report or remove sensitive data from the selected sections.
Temporary copies: PDF generation may create temporary report-layout and PDF files in the App’s private cache. The App attempts to remove the temporary layout file when the operation finishes. Its PDF feature attempts to remove temporary report files older than 24 hours when a later PDF-generation operation starts; this is not a guaranteed deletion exactly 24 hours after creation. A preview, failed operation or interrupted App session may leave a temporary copy until later cleanup or device-managed cache removal. Downloaded, shared or printed copies are separate from this cache.
Sharing and printing: The user chooses where to save or share a report. Selecting WhatsApp or another share destination opens the receiving application or system share flow; the user reviews and confirms sending. Selecting Print opens the platform’s print controls, where the user chooses a printer, print service or Save as PDF destination. The selected service, printer, storage provider or recipient may process or retain the report under its own practices. We do not automatically send a generated accounting report to Firebase or the referral backend as bookkeeping content. Exported reports are not password-encrypted by this feature; protect them as financial and personal information.
Demo funding in Excel and PDF (supported builds): Aavak/Javak history omits linked automatic Demo funding income entries while keeping their expense entries. If included, the Accounts section retains the account information and funding in its totals. Applicable balance and summary calculations may still use the complete underlying data. Ordinary user-entered income is not excluded merely because its text or account name contains “Demo”. Full JSON/ZIP/Drive backups retain the Demo records and expense links needed for restoration. Excel and PDF reports are reports, not a replacement for a complete restorable JSON/ZIP/Drive backup.
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, bill photos, custom category icons, budget values, Notes & Reminder content, Customer Ledger data, selected contacts and backup contents are not provided by us to AdMob for advertising personalization. Advertising requests and reward events are separate from these local records.
Supported builds let free users voluntarily complete a rewarded ad for a single requested operation, such as an eligible Excel/PDF action, manual backup/restore or receipt camera/gallery opening. The confirmation identifies the operation. A successful use consumes that benefit; a new use requires a new reward unless a previously earned, unused benefit is available. Refer & Earn has its own separate rules.
The App stores reward identifiers, feature/account associations, pending earned benefits and used status in App-private storage to recover late callbacks, avoid duplicate use and preserve earned benefits after recoverable failures. Advertising providers process the technical/ad-interaction information described in Section 13. The local feature-reward record does not contain bill image bytes, receipt text, bookkeeping amounts or customer notes. App data removal can remove locally stored reward records.
Daily banner/interstitial pause: A separate rewarded-ad option switches off Banner and Interstitial Ads until midnight of the current device-local calendar day. It is not a rolling 24-hour period and does not switch off the separate rewarded-ad gates for feature use. This daily pause does not create Lifetime Premium or unlock automatic Drive backup.
The App may offer a one-time Lifetime Premium purchase, also called Lifetime Ads Free in earlier versions. Supported benefits include ad-free access to eligible exports, manual backup/restore and receipt picker use, plus supported automatic Drive backup. Both existing and new valid Premium entitlements use the same access checks. Receipt selection may still display an informational performance notice for Premium users. Benefits depend on the platform, installed version and valid entitlement. Payment, verification/restoration and independent store transaction history are controlled by Google Play or Apple and the entitlement services described above.
Refer & Earn is optional and requires sign-in. The App may send limited information over HTTPS to the Aavak Javak referral backend, including:
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.
When a referred user saves a new qualifying income, expense, Milk Account, Notes & Reminder, or Customer Ledger entry in a supported version, the App may send the referral backend a random one-time event identifier and the general activity type (income, expense, milk, note, or customer_ledger). Eligibility depends on the current program rules and backend support. The App does not send the amount, category, note title or description, reminder schedule, user-entered date/time, account, customer identity, milk quantity, local row identifier, or other record content for this check. Edits and backup imports do not count as new qualifying entries. Pending proofs may be stored locally and retried when online; their receipt and timing are evaluated by the server.
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.
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.
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.
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.
Supported Android builds use Firebase Cloud Messaging (FCM) to receive general App information and update news sent by the administrator. The App registers with Firebase and subscribes to a general Android announcement topic when initialized. This subscription is associated with an App installation and does not require a Refer & Earn login or Premium purchase.
Firebase processes installation identifiers and messaging registration tokens needed to route messages, along with related service technical data under Google’s policies. The current announcement backend sends topic messages rather than maintaining a list of users’ device tokens linked to their names, email addresses, or bookkeeping records. Local income/expense data, balances, customers, Milk Account data, Notes & Reminder content and backup files are not included in these announcement requests.
Our administration history records the announcement title/body, administrative sender reference, submission time, Firebase message reference when returned, and submission status/error information. “Accepted” means Firebase accepted the request; this history does not establish whether a particular person received or read the message. Delivery can be delayed or prevented by network conditions, notification settings, force-stop state or operating-system restrictions.
Users can control notification display through Android’s App notification settings and, where available, the App news & updates notification category. Disabling all App notifications may also silence user-created reminders. Turning notification display off does not itself delete Firebase installation identifiers or stop all SDK registration activity. Signing out or deleting the online App account does not automatically unsubscribe the installation. Delivered notifications and lock-screen previews are controlled by the device’s settings. Firebase’s handling of installation data is described in its Privacy and Security information.
Separately, supported Android builds may check Google Play for an available App update and show a dismissible update prompt. The App may store the last prompted version locally. Choosing Update starts the supported Google Play update flow; closing the prompt does not disable administrator announcements.
Depending on the platform, version, and feature selected, the App may use:
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.
Information is used only as reasonably necessary to provide App features, authenticate users, calculate local totals and budgets, attach/display selected photos and category icons, create backups/exports, verify or restore purchases, display ads, deliver App announcements and update notices, 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.
We do not sell or rent user data. Limited information may be processed by Google Firebase, including Firebase Authentication and Firebase Cloud Messaging, 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, Android print components, and user-selected printing/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.
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.
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 JSON/ZIP backups, original gallery/camera copies, Excel files and PDF reports (including any selected Notes Reminder information), saved PDF copies, printed accounting reports, screenshots, printed posters, QR posters, shared messages, and copies stored by external media/services remain wherever the user or recipient/provider stores them. Temporary PDF cache handling is described in Section 12; it does not delete saved files, printer/service copies or recipient copies. 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.
Messaging tokens and installation identifiers are handled by Firebase under its service lifecycle and retention rules; deleting an Aavak Javak login account is not the same as deleting a Firebase installation identifier. General announcement drafts and submission history are not a per-user delivery list. Deletion-request administration may retain the requester’s name, email, App user identifier, request scope, processing status, timestamps and results for verification, dispute handling and audit. The standard completed-request identity-retention setting is 365 days after completion, after which identifying fields are redacted when the retention cleanup runs. Limited non-identifying outcomes and security-related hashed identifiers may remain for the stated audit or abuse-prevention purpose.
Bill photos and custom icons: Removing an attachment, deleting its entry or changing an icon does not currently trigger automatic cleanup of all unreferenced private image files. Likewise, Drive snapshot retention does not remove separately stored image objects. These copies may remain until the relevant App storage or Drive App Data is removed. A previous local ZIP, cloud snapshot or external copy can retain an image after its current entry reference is deleted. The App does not promise immediate or per-photo erasure across existing backups.
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, bill photos, uploaded category icons, budget settings, 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.
Administrator push notifications are tied to the App installation rather than the login account. Online account deletion does not automatically stop these announcements or erase provider-held installation identifiers. Use device notification controls to stop display, and the device/file/provider controls explained on the deletion page to remove local data, backups, delivered notifications and external copies. Any retained deletion-request history is described in Section 25.
Removing photo copies: To remove the App’s private local image copies, use Android’s Clear storage/Clear data control or delete the iOS App and its data; offloading the iOS App is not the same as deleting its data. These actions also remove other local App records, so first preserve only the information you intend to keep. To remove cloud copies, stop automatic backups and remove Aavak Javak’s hidden App Data through Google Drive’s app-management controls where available. This removes that cloud backup data and can prevent restoration; it is not limited to one photo. Revoking authorization, signing out, deleting an online App account or deleting one snapshot is not the same as deleting every cloud image object.
Remove unwanted local ZIP/JSON files and shared/exported copies separately from the locations or services where they were saved. Original images in Photos/Gallery or the camera provider remain under the relevant device/provider controls. The developer cannot remotely erase a copy kept only on your device, in your personal Drive account or by an independent recipient; contact us for assistance with records under our control.
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.
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, photo attachment, category icon, budget, backup, purchase, advertising privacy, contact picker, sharing, reminder, camera permission and biometric options; revoke Google/Apple authorization through account settings; and request access, correction, deletion, or anonymization of eligible online records under our control.
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.
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.