Ente Cash policies

Privacy Policy

How information is used when you visit or use Ente Cash.

Last updated: 18 October 2026

Who this notice covers

This notice covers the Ente Cash website and application from Discernmax. For privacy questions or requests, email support@ente.cash.

Information you provide

Account information includes your name, email address, authentication provider and, for Google signup, your Google account identifier. Local-login passwords are stored as password hashes. The application stores the ledgers, balances, transaction amounts, categories, dates, notes, recurring settings and other financial records you enter. It also stores your selected countries, currency settings, time zone and any relevant agent association.

Contact enquiries

If you use our contact form, we store your name, email address, selected topic, message, submission time and a hashed network address for abuse prevention. Administrators use this information to review and respond to your enquiry. Please do not include passwords, one-time codes or payment-card details in your message.

Device and browser information

Sessions and optional remember-me cookies support authentication. A theme cookie stores display preferences. The website uses your browser time zone to suggest India or NRI pricing without requesting precise GPS location. This suggestion runs in your browser; your selected public pricing currency is saved in local storage on that device. You can change it with the pricing selector or clear it through browser settings. If you enable browser push, the application stores a notification token and device information, including the browser's device description, to send alerts to that device. Web servers may also record technical request and error logs.

Notifications, reminders and email

Ente Cash uses your calendar reminders, transaction dates, expected payments, loan schedules, budgets and account time zone to determine when an account alert is due. We store your notification choices, selected reminder times and generated in-app notifications, including their title, message, related page, read or attended state and delivery status. Some alerts may mention a transaction, bill, loan or budget category you entered.

App / push choices for personal reminders, bill reminders, budget alerts and monthly reports start on; the daily summary and optional daily log reminder start off. The daily log reminder suggests 9:00 PM during first setup and sends only when no income or expense has been recorded for that day. Email is off for each notification type until you enable it. Browser push also requires permission on each device. You can change the types and times in Settings > Notifications after signing in.

When browser push is enabled, Google Firebase Cloud Messaging handles the device token and the notification title, message and destination needed to deliver the alert. If you enable email for a notification type, we use your account name and verified email address to send its title, message and link through our hosting mail service. A notification may be visible in your device's notification area or email inbox, including on a shared or locked device. Account verification, password reset, welcome and other service emails are separate from optional notification emails.

Optional website analytics

With your permission, Microsoft Clarity helps us understand how visitors use public marketing pages through usage analytics and session recordings. The Clarity script loads only after you accept analytics cookies. It is not installed on signed-in financial pages. Authentication dialogs are masked in recordings. We store your choice in this browser's local storage. If you decline, you can revisit the choice using “Analytics settings” on a public marketing page. After accepting, you can reset your choice by clearing this site's local storage in your browser. We do not grant Clarity advertising storage consent.

Ask EC AI guide

When you use Ask EC, the question, recent chat messages needed for context and the reply are processed through OpenAI's API to answer you. Ask EC uses a guide to Ente Cash features; it does not read your account records, balances or transactions, and it cannot create or change entries. If you choose voice input, your recording is sent for transcription and the resulting text is shown for you to check before sending. If you choose spoken replies, the reply text is sent for speech generation. Avoid sharing passwords, OTPs, payment credentials or sensitive information you do not need for your question.

Ask EC saves recent chat messages in this browser's local storage for your convenience. Choose “Exit & clear” in Ask EC, or clear this site's browser storage, to remove that local history. Ente Cash does not save a separate Ask EC transcript in your account database. Requests may still be handled by OpenAI under its own data controls and retention practices, and technical error or security logs may be kept.

Receipt scanning

If you choose Scan receipt, a photo or selected image is sent through our server to OpenAI's API to read details such as the merchant, date, amount, currency and possible expense category. The image is processed temporarily and is not attached to your saved transaction. The extracted details are placed in an expense draft; only the entry you review and save becomes part of your financial records. Check every field before saving because scans can be incomplete or inaccurate. OpenAI may handle the image under its own data controls and retention practices.

UPI QR scanning

For an eligible expense, you can save the entry and then scan a UPI QR code. The camera reads the QR code in your browser and opens a UPI payment link on your device. The QR image and scanned payment address are not saved with the transaction or sent to Ente Cash for QR processing. Your saved expense details remain in your financial records. A UPI app or payment provider may process the payment link and payment information under its own privacy policy. Ente Cash does not receive confirmation from this scan that a payment succeeded.

Why we use information

We process information to create and authenticate accounts, organise financial records, generate reports, apply your settings, provide account alerts according to your notification choices, support you and investigate errors or misuse. Public pricing preferences control only the prices displayed; they do not establish residence or subscription eligibility.

Storage and protection

Account and financial records are stored in the application database. Authentication, password hashing and account-level access checks help restrict access. No storage or transmission method can be guaranteed completely secure. Protect your devices and credentials, and report suspected access problems promptly. Do not place passwords, card credentials or unnecessary identity documents in ledger names or transaction notes.

Service providers and external sites

OpenAI processes the questions, voice content, reply text or receipt images you choose to submit to AI features. Google processes information when you choose Google sign-in and, through Firebase Cloud Messaging, push notification tokens and alert content as described above. Our hosting mail service handles notification and account emails. Fonts, scripts and other website resources served by third-party providers may expose technical request information, such as an IP address, to those providers. Following an external link is also subject to that provider's policies. Information may be processed where the relevant providers operate. We may disclose information when required by law or to address fraud, security incidents or legal claims.

Payments and payouts

For payments and payouts, use only the payment provider's secure interface to enter the credentials it requests. Do not send bank credentials, card details, UPI PINs or OTPs to Ente Cash support. Payment providers process information under their own privacy policies. Transaction references, amounts and status may be retained for accounting, reward verification and support.

Retention and account deletion

We keep account information while needed to provide the service and handle support, security or applicable legal obligations. Notification history and delivery records can remain in the account after you read an item or switch off a delivery channel. Previously delivered push notifications or emails may remain on your devices or with your email provider. Contact support to request deletion or an explanation of retained records. Deletion may not immediately remove information from backups or records required for legal claims. A minimal email-linked trial-eligibility record may be retained after deletion to distinguish returning accounts and prevent repeated full trials, subject to applicable retention and deletion requirements.

Your choices and requests

You can update available account settings, switch individual App / push and Email notification types on or off, change reminder times and control browser notification permissions. Turning a channel off stops future alerts through that channel but does not remove older in-app notifications or emails already sent. Contact support to request access, correction or deletion of your information, withdraw applicable consent, or raise a privacy complaint. We may need to verify your identity before fulfilling a request. Withdrawing information needed to operate the account may prevent continued use of the affected features. You retain any rights and complaint channels provided by applicable law.

Updates to this notice

We will update this page when information practices change and provide additional notice where required. The updated date appears at the top of the page.



Welcome back

Sign in or create your user account to continue.

Forgot password?
Login