Laxmii Privacy Policy

Publisher: TK Digital · Updated 3 November 2026

Laxmii helps you record and understand your income and expenses. This policy explains what stays on your device, what is sent online when you use accounts or voice, why we use that information, and the choices you have. “We”, “us” and “our” mean TK Digital, the publisher of Laxmii.

1. Privacy at a glance

Manual expense and income tracking works without an account or internet connection. Your transaction ledger is saved on your device. Signing in does not create a cloud backup of that ledger.

Voice is optional and needs internet access and an enabled account. When you use it, your recording, transcript and relevant financial context are processed online through Supabase, OpenAI and ElevenLabs. “Saved locally” does not mean that voice data never leaves your device.

We do not sell your personal information. This version has no advertising SDKs, targeted advertising or advertising profiles. It does not read your Gmail, SMS, contacts or bank account, and it does not request bank-login credentials.

2. Records and preferences on your device

The app saves the transactions you enter or ask it to create, including amounts, dates, income or expense type, labels, notes and record timestamps. It also saves budgets, reusable repeat transactions, label choices, notification preferences, text-size preferences and limited information needed to prevent duplicate actions or undo recent changes.

These records describe what you have recorded; they are not a bank connection or a guaranteed bank balance. The Android app does not include the desktop stock features.

Local records belong to the app installation, not to an online account. Signing out or signing in with a different account does not remove or separate records already on that device. Protect access to your phone, especially if you share it.

3. Accounts and sign-in

If you sign in, Supabase processes account information such as your email address, user ID, sign-in provider and authentication records. Google sign-in also involves Google and may provide basic profile information associated with the identity you select. If you choose email and password, Supabase processes the password for authentication; the app does not save a readable password in your ledger.

We use account information to identify you, protect voice access, manage service access and respond to account requests. The publisher can manage accounts and access through Supabase. Sign-in credentials and sessions are stored separately from financial records using device credential protection. They are excluded from local ledger backups.

Signing in does not synchronize transactions between phones or between the phone and desktop. It cannot recover records lost from a device without a backup.

4. What happens when you talk to Laxmii

Recording begins when you activate the microphone and grant microphone permission. Tap again to finish and send. During an active interaction, the app may open a short listening window for a clarification or confirmation. It does not continuously listen after you close the voice interface, and it stops recording when the app goes into the background.

The audio is sent through our Supabase gateway to ElevenLabs for transcription. The transcript and the context needed to understand your request are sent through that gateway to OpenAI. Context can include recent transactions, amounts, dates, labels, budgets, preferences, relevant search results and recent conversation turns. A question about older records can cause relevant older records or totals to be included. A note you dictate or ask the assistant to process can also be included.

The app validates proposed actions and calculates financial totals in application code. The reply text is sent through Supabase to ElevenLabs to generate spoken audio. That text may contain the amounts or financial details needed to answer you. The assistant uses a selected synthetic voice; the app does not create a clone of your voice or use your voice as a biometric sign-in method.

Recent conversation context is used during the interaction rather than provided as a cloud chat-history feature. Your resulting transactions and limited undo information are saved locally. Temporary Android recording files are removed when recording finishes or is cancelled; audio and transcripts may still be retained by the processing providers as explained below.

Voice can make mistakes. Review your records and correct unexpected changes. Avoid speaking passwords, PINs, payment-card details, government identification numbers or other information that is not needed for your money-tracking request.

5. Services involved in online processing

Supabase provides authentication, the voice gateway, access controls and service-usage storage. It also processes operational information needed to run those services, which can include network, request, security and authentication metadata.

OpenAI processes the text and relevant context used to interpret requests and prepare answers. We send Responses API requests with storage disabled (store:false). That setting does not guarantee zero retention: OpenAI states that API abuse-monitoring logs may contain customer content and are generally retained for up to 30 days, with exceptions. OpenAI states that API data is not used to train its models by default unless the customer opts in.

ElevenLabs processes recordings for speech recognition and reply text for speech generation. We do not claim that these requests have zero retention. ElevenLabs documents that its normal service retains data and that zero-retention options are limited to eligible arrangements and endpoints. Its applicable service terms, account settings and data-processing arrangements govern that processing.

Google processes information when you choose Google sign-in. The services may use their own infrastructure and subprocessors to provide, secure and maintain their services. The links below provide more information; they do not replace this policy or our responsibility for Laxmii.

6. Service access and usage records

Our Supabase database stores account-linked voice access settings, enabled status, safety limits and any access-expiry setting. For service operations it records a user ID, a random request ID, operation type and time. It can also record numerical timing measurements for authentication, access checks and provider response.

We use this metadata to enforce access and rate limits, prevent duplicate service requests, investigate failures and improve response speed. These usage-table records do not contain recordings, transcripts, transaction amounts, labels or notes. The gateway code does not intentionally write that content into its application logs. Infrastructure providers can keep operational and security logs under their own applicable arrangements.

This version shows a proposed Pro offer but does not process in-app purchases, collect payment-card details or activate a trial or purchased request balance. Access safety limits are not a purchased balance. We will update the relevant disclosures before enabling purchases.

7. How long information is kept

Local records and preferences remain until you remove them, clear the app data or uninstall the app. Removing a transaction may leave a temporary local undo copy until that undo history is replaced. Reset App Data removes local financial records, preferences and undo history after explicit confirmation, while keeping the account session and service configuration separate. It does not cancel a subscription or delete an account. Clearing app storage removes the installation’s records and undo history. Files you exported or backed up remain wherever you saved or shared them until you delete those copies.

Account and access information are retained while the account exists, unless removed earlier. Account-linked usage records currently have no automatic time-based deletion and are retained until removed by us or when the associated account is deleted. They are not erased after every voice command.

Provider processing, operational logs and provider backups follow the providers’ applicable retention arrangements. We do not promise that deleting an entry or account immediately removes every provider log or backup. Information required for security, a legal obligation or resolving a dispute may need to be retained for the relevant purpose.

9. Permissions and notifications

Microphone permission is used for voice recording. You can refuse or revoke it in Android settings and continue entering records manually. Internet access is used for sign-in and online voice processing.

Notification permission is used for optional recording reminders. You can change reminder preferences in Laxmii or disable notifications in Android settings. Reminders do not read your financial account or automatically add a transaction.

Exports and restores use the files or locations you select through the device’s file picker. The app does not need broad access to every file on your phone to use those features.

10. Security and your device

Online service requests use HTTPS. Provider API keys for the server version are kept in Supabase server secrets rather than embedded in the APK. Server-side access checks protect the voice service. Authentication sessions use Android Keystore-backed protection on the phone and Windows credential protection in the desktop preview.

The local ledger uses app-private storage protected by the operating system. We do not describe the ledger or exported backup files as end-to-end encrypted or password-protected. Use your device lock, keep the operating system updated and store exports and backups carefully. No storage or transmission system can be guaranteed completely secure.

11. Your choices, access and deletion requests

You can use manual tracking without signing in, choose not to use voice, edit or delete records, change settings, export transactions and save a backup. Turning off notifications or microphone permission does not delete existing records.

For account access, correction or deletion requests, email tamalkchandra@gmail.com. For account deletion, use the subject “Laxmii account deletion” and contact us from the registered email address where possible. We may verify ownership before changing or deleting account information. Do not send a password, API key or your complete ledger to prove ownership.

An account-deletion request covers the Laxmii authentication account and associated server-side access and usage records, except information that must be retained for a legitimate legal or security purpose. You can also ask about applicable provider-held information. We will explain any retention that affects your request.

Account deletion or sign-out does not automatically erase financial records or exports on your devices. Remove those separately by deleting entries, clearing Laxmii’s app storage in Android settings or uninstalling, and deleting any backup/export copies you no longer want. Depending on where you live, additional privacy rights may apply; contact us to make a request.

12. Backups and restoring records

Backup & Restore saves a local backup file containing records, labels, repeat templates, budgets and preferences. Authentication credentials and provider API keys are excluded. There is no automatic cloud backup of the financial ledger in this version.

Restoring a backup can recover the information included in that backup. We cannot recover a lost local ledger if no usable backup exists. If you choose a cloud drive as the backup destination, that is a copy stored with the service you chose and subject to its terms. Anyone who obtains an unprotected export or backup may be able to read it.

13. Children and information about others

Laxmii is a personal money-management tool and is not designed or marketed specifically for children. Do not submit someone else’s personal or sensitive information unless you have the right to do so. If you believe a child has provided personal information through the service, contact us so we can review the situation and take appropriate action.

14. Policy changes and contacting us

We may update this policy when features, service providers, data handling or applicable requirements change. The updated date identifies the version shown here. Material changes will be communicated through an appropriate in-app notice or other suitable channel.

Publisher: TK Digital. App: Laxmii. Privacy and support contact: tamalkchandra@gmail.com. Please describe your question or request without including unnecessary financial or sensitive details.