Privacy Policy

1. Introduction

LekhaVault is a personal finance management application developed and published by Japrinix Labs. It helps users organize financial records such as accounts, transactions, categories, budgets, recurring dues, savings plans, credit-card records, loan records, and reports.

This Privacy Policy describes the types of information handled by LekhaVault, how that information is used, how the production LekhaVault service API is involved, and how users can contact us with privacy questions.

2. Information We Collect

Depending on the features used, LekhaVault may process the following categories of information:

• Account/profile information, such as display name, selected currency, locale, app settings, credential metadata, and reminder preferences.
• Financial records entered or imported by users, including account names, account types, balances, transactions, income, expenses, transfers, categories, payees, tags, notes, budgets, subscriptions, recurring rules, credit-card tracking records, loans, EMIs, savings plans, and contribution records.
• Import, export, backup, restore, duplicate-detection, integrity-check, and audit-related metadata created when those workflows are used.
• Support communications, including any information a user chooses to send when contacting Japrinix Labs.
• Technical and application information needed to operate, protect, troubleshoot, and improve the LekhaVault service. The exact production logging categories are NOT VERIFIED in the reviewed repositories.

3. Financial Information

LekhaVault is designed to handle user-entered financial tracking records. These records may be sensitive because they can describe income, spending, balances, debts, budgets, savings goals, payees, and other personal finance activity.

The reviewed mobile application source supports finance tracking records such as account containers, transaction records, card statement information, loan schedules, savings plans, budgets, recurring rules, and exports/backups. The reviewed source did not show bank aggregation SDKs or fields for online banking passwords, ATM PINs, card PINs, or complete payment-card credentials. Do not enter those credentials into LekhaVault.

4. How We Use Information

We use information to provide and maintain LekhaVault, including to:

• Create, save, display, update, search, and organize financial records.
• Show dashboards, reports, balances, budgets, due dates, and summaries.
• Support reminders, recurring rules, import/export, backup, restore, and integrity workflows.
• Operate user account and application data services through the LekhaVault service infrastructure.
• Respond to support or privacy requests sent by users.
• Protect, troubleshoot, maintain, and improve the reliability of LekhaVault services.

5. Service API Processing and Storage

The production LekhaVault architecture uses the LekhaVault API at https://api.lekhavault.japrinixlabs.com for applicable application data processing and storage. This API is part of the LekhaVault service and is not described here as a third-party API.

The reviewed Japrinix Labs repository currently contains an API application scaffold and placeholder architecture documents. API-specific details such as authentication implementation, database schema, encryption at rest, backup retention, disaster recovery, exact logging categories, and exact deletion workflow are NOT VERIFIED in the reviewed repositories.

6. Data Security

We use reasonable administrative, technical, and organizational measures intended to protect information handled by LekhaVault. The reviewed mobile source includes mobile-side controls such as credential-based unlock, optional biometric unlock, screenshot blocking hooks, backup exclusions for sensitive Android domains, and cleartext-traffic restrictions.

No electronic storage, software, network, or service can be guaranteed to be completely secure. Users should protect their devices, credentials, exported files, and backup files. API-specific security certifications and compliance attestations are NOT VERIFIED in the reviewed repositories.

7. Data Sharing

We do not sell or rent personal information. LekhaVault may process information through the LekhaVault application and API services to provide the product features described in this policy.

Information may also be disclosed when a user directs us to do so, when needed to respond to a support request, or when required by applicable law, legal process, or a valid governmental request. Specific production infrastructure providers or data processors are NOT VERIFIED in the reviewed repositories.

8. Third-Party Services

The reviewed LekhaVault mobile source did not identify advertising SDKs, analytics SDKs, crash-reporting SDKs, Firebase, Sentry, Play Services, or bank-aggregation SDKs. App distribution, device operation, and platform-level services may involve providers such as the application store, Android, or the user's device manufacturer under their own privacy terms.

Production API hosting, database, monitoring, email, or support providers are NOT VERIFIED in the reviewed repositories.

9. Data Retention

We retain information for as long as needed to provide LekhaVault, comply with legal obligations, resolve disputes, enforce terms, maintain security, and support legitimate operational needs.

Exact production retention periods for API data, logs, backups, and deleted records are NOT VERIFIED in the reviewed repositories.

10. Data Deletion and User Choices

The reviewed mobile source supports management of records such as transactions, account archive/reactivation, budget archive states, data cleanup, restore validation, and backup-before-destructive-action controls. Some deletions are modeled as status changes or archived records so that financial history and balance rules remain consistent.

A self-service production server-account deletion workflow is NOT VERIFIED in the reviewed repositories. For API-backed data or privacy requests, contact us using the details below.

11. Permissions

LekhaVault may request permissions needed for selected mobile features. Reviewed Android sources include reminder-related notification and restart handling in the native Android module, and import/export workflows are designed around user-selected files. The reviewed sources did not identify contacts, location, SMS, phone, microphone, camera, or broad external-storage permissions.

Permission prompts and controls can vary by Android version and distribution channel. Users can review or change permissions in device settings.

12. Children's Privacy

LekhaVault is a general personal finance application and is not directed to children. We do not knowingly seek personal information from children. A parent or guardian who believes a child has provided information through LekhaVault may contact us.

13. International Users

Users may access LekhaVault from different regions. Information may be processed in locations where LekhaVault, its service infrastructure, or verified operational providers maintain systems. Specific production processing locations are NOT VERIFIED in the reviewed repositories.

14. Changes to This Privacy Policy

We may update this Privacy Policy as LekhaVault features, service architecture, legal requirements, or operational practices change. Updates will be posted on this page with a new Last Updated date.

15. Contact Us

For privacy questions, support requests, or data-related inquiries, contact:

Return to the LekhaVault home page.