WalletLoop
Features Guide Why track Privacy FAQ Get early access
Legal · Privacy

Privacy Policy

LAST UPDATED · NOVEMBER 6, 2026 VERSION 2.16 DPDP ACT, 2023
On this page
  • 1. Introduction
  • 2. Information We Collect
  • 3. How We Use Your Information
  • 4. Data Storage and Security
  • 5. Service Providers
  • 6. Data Retention
  • 7. Your Rights and Choices
  • 8. Children's Privacy
  • 9. Compliance with Indian Laws
  • 10. International Data Transfers
  • 11. Changes to This Policy
  • 12. Contact Us
  • 13. Grievance Redressal
Related: Terms of Service · Delete account

1. Introduction

WalletLoop ("we," "our," or "us") is committed to protecting your privacy. Our promise is simple: privacy-first money tracking — no ads, no data sold, no loans pushed. This Privacy Policy explains exactly what we collect, what we don't, and what we do with it.

WalletLoop is designed to help you track personal expenses across multiple digital payment platforms. We understand that financial information is sensitive, and we treat it accordingly.

The honest summary. Your transactions are stored on our servers (encrypted) so they sync across your devices and survive a phone reset. But we never see your bank account numbers, card numbers, or CVVs — we don't collect them, even masked. One exception, kept by the app on your phone: Precise matching (on by default) remembers the last 4 digits your bank texts show for each of your accounts and cards, so every payment lands on the right one. Those digits are never sent to or stored on our servers and never synced; they reach a new phone only inside your phone's own end-to-end-encrypted backup or a direct phone-to-phone copy, which we cannot read. You can delete them anytime. We never read your raw SMS — it's parsed entirely on your device. We never sell your data. We never show ads. We never push loans or financial products. We charge users directly through Pro subscriptions, and that's our only revenue.

2. Information We Collect

2.1 Information You Provide Directly

  • Authentication Data: Phone number for OTP-based login, email address (if you choose email authentication), and Google Account information (if you use Google Sign-in).
  • Linked Email & Product Updates (optional): If you signed up by phone, you can add an email address from Settings. We verify it with a sign-in link before it is saved, and it then also works as a backup sign-in method. Separately — and only if you switch on “Product updates” — we may send occasional emails about new WalletLoop features. This is off by default, you can turn it off anytime in Settings, and update emails are never sold, never shared, and never used for third-party marketing.
  • Financial Profile: Monthly income and savings goals (optional, used only for budget calculations and insights).
  • Transaction Data: Expense entries you manually create, including amount, category, merchant/platform name, date, and optional notes.
  • Profile Information: Your name and profile preferences.
  • Organization Data: Budgets, custom categories, accounts, trips (Yatra), savings goals, and recurring bills you create to organize your money.

2.2 SMS Data (Special Handling)

With your explicit permission, WalletLoop requests access to your SMS messages to detect and parse financial transaction notifications from banks and UPI applications. SMS data is processed entirely on your device and never transmitted to our servers in raw form.

  • What we do: We use regex patterns to identify transaction SMS from Indian banks (SBI, HDFC, ICICI, Axis, Kotak, etc.) and UPI providers (Google Pay, PhonePe, Paytm, etc.).
  • What we keep from a bank text: the amount, and the date and time; the merchant or payee as the text names it — a shop’s name, or a person’s name, UPI ID or phone number; the bank and the reference number; whether money went out or came in, how it was paid (UPI, card or bank transfer), and the kind of account or card; a foreign spend’s currency and amount; a prepaid card’s balance; and, when you track or apply a card statement, its bill amount, minimum due, due date and statement day. Never the message itself, and never account or card digits.
  • What we send: What we keep from a text reaches our servers when the payment is saved — by you, or by Auto-add if you turn it on. A few things about your texts leave your phone even when no payment is saved, and none of them is a message: if a new text matches one of your merchant rules, that rule’s “Used” count goes up by one and its last-used time is updated, in your account; usage events (Section 2.5) can record that the app showed a payment it could read only roughly, with the amount as a band and whether money went out or came in; and a crash or error report (Section 5) can include how many texts the app’s queue on your phone had to drop while WalletLoop was closed — a number, nothing else. Raw SMS content never leaves your device.
  • You control it: Each parsed transaction waits for your approval — unless you turn on Auto-add in Settings (off by default). Auto-add saves the payments WalletLoop is sure of without asking, usually with a notification that says so, and you can remove any of them. During setup, your recent transaction SMS are assembled into a review screen. Nothing is imported until you tap to add it, and anything you skip is never re-asked. You can revoke SMS access permission at any time through your device settings.

RCS messages (optional, off by default): Some banks now deliver transaction alerts as RCS chat messages inside your messaging app instead of SMS. If you turn on “Catch RCS bank messages” in Settings, WalletLoop reads your messaging app’s notifications (using Android’s Notification access permission) to catch those bank alerts. All of it happens on your phone. The app keeps a short queue of those notifications (up to 50) in its private storage until it has checked them. It keeps only the ones it identifies as bank payments, and discards the rest — personal conversations included — without sending them anywhere. While the app restarts, it can briefly receive other apps’ notifications as well; it discards them the same way. A payment it finds is saved like one from an SMS: when you approve it, or by Auto-add if you turned that on. Turning the toggle off (or revoking Notification access in your device settings) stops it immediately.

2.3 Debt and Financial Tracking Data

If you use WalletLoop's debt tracking features, you may optionally enter:

  • Loan Details: Loan amounts, interest rates, EMI amounts, tenure, disbursement dates, and bank/institution names.
  • Credit Card Details: Card name, credit limit, outstanding balance, due dates. We never collect card numbers, CVVs, or other card credentials.
  • Pay Later Balances: Outstanding amounts for services like Simpl, LazyPay, Slice, etc.
  • Personal Debts: Amounts owed to or by other people, including their names.

This data is stored on our servers and used only for calculating amortization schedules, EMI reminders, and debt-free date projections within the app.

Precise matching (on by default, Settings → Privacy & Data): the app remembers the last 4 digits shown in your bank texts, or that you type for a card, and which of your accounts and cards they belong to, so every payment lands on the right one. They are stored on your phone and never sent to or stored on our servers, or included in sync. They are included in your phone's own Google backup only when that backup is end-to-end encrypted with your screen lock, and in a direct phone-to-phone copy when you move to a new phone, so the new phone can restore them — we cannot read either. A new phone starts with Precise matching on, even if you had switched it off on the old one. You can forget an account's or card's digits from its screen, and switching Precise matching off deletes them all; your phone's next backup then carries none. Our servers never keep account or card digits, masked or partial.

2.4 People You Track (Khata, Splits, and Personal Debts)

If you use the split expense, Khata (people ledger), or personal-debt features, you may enter details about other people: their names and — for Khata — optionally the UPI IDs or phone numbers you already pay them at, so their payments group under one person. This information is stored with your account data and used only to organize your own records. We never contact the people you name, never share their details with anyone, and never use them to build profiles of those individuals. Khata's “settle up” option composes a plain-text summary on your phone that you choose to share; WalletLoop itself never messages anyone and never moves money. You can unlink an identity or delete a person at any time, and all of it is deleted with your account.

2.5 Device Information

  • Device Identifiers: Random IDs the app’s services create when it is installed (Section 5), the operating system type and version, and the app version. WalletLoop uses no advertising ID.
  • Usage events: Which screens and features you use and when, with a random session ID. They go to our own server from the first time you open the app — without an account ID before you sign in, and with it after. Amounts are recorded only as bands (for example ₹2,000–₹10,000), never as figures. When you delete your account, the events are unlinked from it, and every event is deleted 90 days after it was recorded. Crash and error reports: Section 5.
  • Location: We do not collect GPS location data. However, your IP address may be logged for security and abuse-prevention purposes (rate limiting, audit logs, our CDN provider's standard request logs).

2.6 Universal Merchant Categorization (On by Default)

WalletLoop maintains a community-built database of merchant categorizations so the app can recognize new merchants without an update. When you add a payment WalletLoop detected from a bank text, with its category — the one we suggested or one you picked, for example "Local Cafe" as Food — that merchant and its category can be shared with our database to help other users. This sharing is on by default, and you can turn it off at any time in Settings > Privacy & Data > "Help improve categorization." What is shared never includes amounts, dates, accounts, or anything that identifies you.

What we receive while sharing is on:

  • The merchant’s name as your bank’s text gives it (e.g. "Local Cafe") — for some businesses, their payment ID instead, such as a shop’s UPI ID on a payment gateway
  • The category you picked (e.g. Food)
  • An anonymous proof token used only to prevent the same device from counting the same merchant more than once in the same week. The proof token is a cryptographic hash that the server cannot link back to your device or account.

What we never receive, whether sharing is on or off:

  • Transaction amounts, dates, or account information.
  • A person’s UPI ID or phone number, or any account or card number.
  • Your name, phone number or email. Your account ID does reach us with the request: it is used only to limit how many merchants one account can share in a day, and is never stored with what you share.
  • Merchant names that look like personal payments (e.g. firstname.lastname@bank), phone numbers, or sensitive categories (clinics, therapy, legal services, pharmacies). These are filtered out on your device by an on-device classifier and never sent to our servers.

When a merchant joins the shared list: once it has been shared three times and we have checked it. A device counts at most once for a merchant each week, so the three can come from one device over three weeks — it is the filters above and our check, not the count, that keep personal payments and sensitive places out. A name that does not look like a shop’s — a link, an email address, a long run of digits — is refused.

How long we keep this data: The anonymous proof tokens used for duplicate-prevention expire automatically after four weeks. After that, we retain only an aggregate count of how many times each merchant was shared — these counts are not linked to any device or account.

Your control: You can turn the toggle off in Settings > Privacy & Data at any time. Turning it off stops new merchants from being shared and clears any pending ones that haven't yet been sent. Merchants already shared are anonymous and cannot be traced back to you, so they cannot be individually withdrawn.

The database itself is universal — every WalletLoop user benefits from what everyone who leaves sharing on has shared, including users who have turned it off for themselves. Approved entries are made available to all users via an anonymous public read.

2.7 SMS Format Reports (“Send It to Us” — You-Initiated)

If WalletLoop couldn't read one of your bank's texts, or read one wrong, you can choose to send us a scrubbed copy of that text so a later version of WalletLoop can read texts like it — from the Review & import screen (“A payment that isn't here?”, or “Send it to us” on a text). This happens only when you explicitly tap Send, never automatically.

  • Scrubbed on your device first: Before anything is sent, amounts are replaced with placeholders; account and card digits are masked; UPI IDs, phone numbers, email addresses, reference numbers, and payee names are removed or masked. The app shows you the exact scrubbed text before you send it, and you can hide any other word yourself.
  • Re-scrubbed on the server: The same scrubbing runs again server-side as a second safety net.
  • What we receive: The scrubbed text, the SMS sender header (e.g. "AD-HDFCBK"), what you told us went wrong (for example “Wrong amount”), your app version, and OS. OTPs and personal messages are rejected before the form even opens.
  • What it's used for: Improving how WalletLoop reads bank texts — nothing else.
  • A copy to our support inbox: A copy of the report may also be emailed to our own support inbox through our email provider (Section 5), so we can read it. That copy carries no account ID, phone number or email address.
  • After you send: If a later version of WalletLoop reads a text you sent, the app tells you. That check runs on your phone, against the text in your inbox — nothing about it is sent to us.
  • Retention: Format reports are linked to your account only so they can be deleted with it; deleting your account deletes them.

This is the only case where the text of a message reaches our servers — a scrubbed copy you reviewed and chose to send, never the raw message.

2.8 Website Visitors & the Early-Access Waitlist

Our website, walletloop.in, uses no cookies, no analytics service, and no third-party trackers. It is served by our website host, whose standard request logs (IP address, request path, user-agent) apply as described in Section 5. If you arrive through a link in one of our own ads, the campaign tags in that link (its source, medium and campaign name) are kept in your browser tab’s session storage until the tab closes, and reach us only if you join the waitlist.

If you join the early-access waitlist on the website, we collect the email address you enter, your platform choice (Android or iPhone), coarse request context (approximate country and browser user-agent), the page you joined from and when, and, if you came through one of our ads, that ad’s campaign tags. This is stored in our website host’s key-value storage and used for two purposes only: sending you the early-access invite and launch updates, and counting which of our ads bring sign-ups. Waitlist emails are never sold, never shared, and never used for any other marketing. They are deleted once the early-access rollout concludes — or earlier, on request to support@walletloop.in.

Early-access codes. If you are among the first 1,000 on the waitlist, your invite carries a one-time code for a free year of WalletLoop Pro. To send it, we copy your email address, sign-up time and platform into a private list that we keep ourselves, beside the code made for you; that list is deleted with the waitlist. We also give some codes directly to people who are not on the waitlist; those codes work the same way. Our server stores only a one-way scrambled form of each code — never your email address — and, once a code is used, which account used it and when, so that it works only once. That lets us match your waitlist email to the account that used your code, which we do only to give you the free year and to answer you if you write to us. If you delete your account, its link to the code is erased; the record that the code was used stays, so it cannot be used again.

2.9 Referrals (If You Invite Someone)

WalletLoop has a referral feature: you can share a personal invite code, and if someone signs up with it, both of you receive free Pro days. Using it creates a record linking the two accounts — who invited whom, the code used, when it was redeemed, and whether the reward has been granted. We store that record so the reward can be granted once and not repeatedly, and so we can investigate abuse (for example, one person creating many accounts to farm rewards).

  • What the person who invited you sees: that a referral was redeemed and that their reward moved. They do not see your name, phone number, email, transactions, or anything else about your account.
  • What you see: that your code was applied. Nothing about their account.
  • If you never use the feature, no such record exists for you.
  • Retention: the referral record is kept when either account is deleted — the two account IDs, the code, and whether the reward was granted — so a reward cannot be claimed twice (Section 6). It holds no name, phone number, email or financial data.

2.10 Feedback You Send Us (You-Initiated)

If you choose “Send feedback” in the app, we receive what you wrote and what it is about, linked to your account so we can look into it. Unless you switch it off, the app adds your app version and update, your phone’s maker and model, its Android version, whether sync is on and when it last synced, and the screen you started from. If you report a payment, we receive which payment it is, and we may look at that payment in your account to find what went wrong. Long numbers you type, such as card or account numbers, are hidden before your message is stored; please never include an OTP or PIN. If you allow it, we may reply to you by email. Feedback is used only to fix problems and improve WalletLoop. It is sent only when you tap Send, and it is deleted with your account. A copy may be emailed to our own support inbox through our email provider (Section 5), without your account ID, phone number or email address.

3. How We Use Your Information

3.1 To Provide the Service

  • Authenticate you securely using phone number, email, or Google account.
  • Store and display your transaction history.
  • Generate spending analytics, reports, and insights.
  • Create and track budgets and spending goals.
  • Calculate recurring expenses and provide notifications.
  • Parse SMS to auto-import transactions (on-device).
  • Track debts, loans, credit cards, and EMI schedules.
  • Calculate split expenses between friends or family.

3.2 To Improve the Service

  • Analyze how features are used, from usage events linked to your account ID (Section 2.5).
  • Identify and fix bugs and performance issues.
  • Develop new features based on user needs.
  • Improve SMS parsing accuracy for better transaction detection.
  • Add new bank SMS formats to the app, and fix the ones it reads wrong, from the scrubbed texts you explicitly choose to send (Section 2.7).

3.3 To Communicate With You

  • Remind you of bills, budgets and EMIs with notifications your phone schedules itself — our servers send no push notifications.
  • Tell you about important app updates or security issues, in the app or by email.
  • Respond to your support requests and inquiries.

3.4 Legal and Safety

  • Comply with applicable laws and regulations.
  • Detect and prevent fraud or unauthorized access.
  • Enforce our Terms of Service and other agreements.

3.5 What We Do NOT Use Your Data For

  • Selling your personal information or transaction data to third parties.
  • Targeted advertising or behavioral tracking.
  • Sharing with advertisers or marketing partners.
  • Profiling for credit decisions (we don't share with credit bureaus).

4. Data Storage and Security

4.1 How Your Data is Stored

  • Database: Transaction data, categories, budgets, debts, and user profiles are stored in our database, hosted by our cloud database provider.
  • API Server: Our backend API runs on our cloud hosting provider’s servers, behind a network service that provides DDoS protection and TLS termination.
  • Device-Side: Raw SMS content, your 4-digit PIN (in your phone’s secure storage), offline transaction queue, theme preference, and SMS dedup memory are stored locally on your device only. The app also keeps a local-first database of your own transactions on your device (protected by your OS’s encryption), so WalletLoop works fully offline and syncs when you are back online.
  • Authentication: Our sign-in provider handles phone numbers, email addresses, and Google sign-in credentials. We do not store passwords.
  • Sync Service: The database on your phone and our main database are kept in step by our sync service, which keeps a copy of your synced records — your transactions, accounts, categories, budgets, debts and cards, bills, splits, Khata, trips and merchant rules, and your profile (name, phone number, email, income, savings goal and plan). It is operated for us by our sync provider (Section 5). When we move the sync service to a new provider, the old one keeps its copy until the move is complete, and we then delete that copy.

4.2 Security Measures

  • Encryption in Transit: All data transmitted between your device and our servers uses TLS 1.2+ encryption (HTTPS).
  • Encryption at Rest: Your device data is encrypted by your operating system. Server data is encrypted at the database level by our database host.
  • Authentication: We use phone OTP, email magic-link, and optional Google Sign-in, through our sign-in provider.
  • App Lock: A 4-digit PIN protects in-app access. The PIN is hashed and stored exclusively on your device — we never receive it.
  • Access Control: Only the founder has access to production server data, and access is logged.
  • Rate Limiting: API endpoints are protected with rate limiting to prevent abuse.
  • Log Redaction: Authorization headers, cookies, tokens, and PIN hashes are stripped from all server logs before they leave our infrastructure.
  • No Raw SMS Storage: Raw SMS content is never stored on our servers, eliminating exposure of sensitive banking data. The one message text we store is the scrubbed format sample you explicitly choose to send (Section 2.7) — scrubbed on your device and again on the server, so it contains no amounts or account details, the payee names we can find are masked, and you can hide any other word before you send it.

4.3 Security Limitations

While we implement industry-standard security measures, no method of transmission over the internet or electronic storage is 100% secure. We cannot guarantee absolute security of your data, but we maintain reasonable and appropriate safeguards.

5. Service Providers

WalletLoop uses a small number of service providers to run the app. Each one receives only what its part of the service needs — listed below by the job it does for us. To know which company does a job, write to support@walletloop.in.

  • Signing you in: Your phone number, email address, or Google account information (when you choose Google Sign-In), to verify that it is you.
  • Storing your records: The structured data you save in WalletLoop (transactions, debts, budgets, profile), in our database.
  • Keeping your phone in step: A copy of your synced records (Section 4.1), held by our sync provider.
  • Running our server: Our API server runs on our cloud hosting provider’s servers: the provider hosts the machines and carries traffic in transit, while WalletLoop data on them is managed by our own software.
  • Protecting our servers and serving our website: Standard request metadata (IP address, request path, response status, user-agent), for routing and abuse prevention. The same provider serves walletloop.in and stores early-access waitlist signups (Section 2.8).
  • Crash reports and server logs: From the first time you open the app: error stack traces, your account ID (once you sign in), a random per-install ID, device type, OS version, app version, a session record each time the app starts, the screens and request paths before an error, how many texts the app’s queue on your phone dropped while it was closed (a number, if any), and (on the server) the URL path and status code of the request that failed; and server request logs (method, URL path, response status, latency). No financial data, SMS content, authentication tokens, or PIN data is sent — our redaction filter strips them first — and request and response bodies are never sent.
  • App updates: Small over-the-air updates — bug fixes and improvements that do not need a new Play Store release — are delivered by an app-update service. When the app checks for an update it sends the technical details needed to answer that question: your device’s IP address, a random per-install ID, your platform, the app’s runtime version, update channel and update IDs, and — after an update fails to load — the error it reported. No account data, transactions, SMS content, or anything you track in WalletLoop is involved — the check happens before and independently of anything you have entered.
  • Email to our support inbox: When you send us an SMS format report (Section 2.7) or feedback (Section 2.10), a copy may be emailed to our own support inbox so we can read it. Our email provider receives only that email — for a format report, the scrubbed text, the sender header, what you told us went wrong, and your app version and OS; for feedback, what you wrote, what it is about and the app details described in Section 2.10 — never your account ID, phone number or email address.
  • Sending you email: The waitlist invite and launch updates (Section 2.8) go through our email provider, which receives your email address and the message, including your code if you have one.
  • App stores and purchases: When you download the app from Google Play or the Apple App Store, those stores may collect and process your usage data under their own privacy policies. When WalletLoop Pro purchases launch, billing happens through the store — we never receive your payment-method details. To know reliably whether a purchase succeeded, renewed, or expired, a subscription-management service receives your WalletLoop account ID — a random string, not your name, phone, or email — and the purchase and subscription state from the store (the product bought, purchase and expiry timestamps, renewal state, and the store's country and currency for that transaction), and tells our server whether your subscription is active, so your Pro status stays correct across your devices. It never receives your transactions, SMS data, or anything you track in WalletLoop. If you never open the Pro screen or make a purchase, the app does not talk to it at all.
  • Merchant logos (earlier versions only): Since version 1.4.764 the app shows its own letter badges and asks no one for logos. Earlier versions — and a new install’s first session, until the app has updated itself — may ask Google’s public logo (favicon) service for a known brand’s website domain (e.g., "swiggy.com"), a merchant from your transactions. Like any web request, it carries your device’s IP address. No account or financial data is sent.

Services that never receive your data, such as our uptime monitor, are not listed.

6. Data Retention

6.1 How Long We Keep Your Data

  • Transaction Data: Retained while your account is active. You can delete individual transactions at any time.
  • Account Data: Retained while your account is active. When you delete your account from inside the app, your profile and every record you built in WalletLoop are erased from our database immediately — not queued for a 30-day window. Our server also deletes your sign-in record with our sign-in provider, and the app does too; if that cannot be completed, write to support@walletloop.in and we will remove it. Our sync provider’s copy of your records (Section 4.1) follows within a day: the deletion reaches it at once, and its automatic daily clean-up removes the history it keeps. Three kinds of record outlive the account, and none of them holds financial data or can rebuild your ledger: anonymised usage analytics (Section 2.5 — your account id is erased from them at once, and the rows are deleted 90 days after they were recorded); if you used or gave a referral code, the referral record (the two account ids, the code, and whether the reward was paid), so a referral reward cannot be claimed twice; and a deletion safeguard token derived from your phone number or email — described below — which is what stops the free Pro period being claimed over and over. If you ever subscribed to Pro, the identifiers of the billing events our payment provider sent us are also kept as the record that each was processed once, and where tax and accounting law requires it. Deleted data can remain in backup copies of our database — our database provider’s daily backups, and any copy we take before maintenance — for up to 7 days, until they are overwritten or deleted. Our deletion page lists all of this in full.
  • Device Data: Cached data on your device is deleted when you uninstall the app or manually clear the app cache.
  • SMS Data: Raw SMS content never persists on our servers. Extracted transaction data (amounts, merchants, dates) follows the same retention as manually-entered transactions.
  • Debt Data: Loan, credit card, and pay-later data is retained while your account is active. You can delete individual debt entries at any time.
  • Server Logs: HTTP access logs and error reports are retained by our crash-report and log providers for up to 90 days, then automatically deleted.
  • Usage Analytics: The in-app usage events described in Section 2.5 are held on our own server for 90 days and then deleted automatically by a scheduled job — not kept indefinitely, and not exported anywhere.
  • Merchant-sharing Proof Tokens (while sharing is on): Anonymous proof tokens used for duplicate-prevention expire automatically after 4 weeks.
  • SMS Format Reports (you-initiated only): Scrubbed format samples (Section 2.7) are retained to improve parsing and are permanently deleted when you delete your account. A copy emailed to our support inbox (Section 2.7) is not linked to your account — it carries no account ID, phone number or email address.
  • Feedback (you-initiated only): What you send us from Send feedback (Section 2.10) is kept with your account so we can look into it, and is permanently deleted when you delete your account. A copy emailed to our support inbox (Section 2.10) is not linked to your account — it carries no account ID, phone number or email address.
  • Deletion Safeguard Token: When you delete your account we keep one non-reversible token derived from your phone number or email — never the number or the address itself, and it cannot be turned back into either. It records only that this phone number or email has had an account before, whether that account had already received the free Pro period, and whether it had used a referral code. It exists so that an account cannot be deleted and recreated over and over to claim the free Pro period or a referral reward again. It cannot be used to identify you, to contact you, or to recover anything you deleted, and it is erased automatically 12 months after your most recent deletion. If you sign up again within that period you get a fresh account; what you do not get is a second free trial.

7. Your Rights and Choices

7.1 Access and Data Portability

You have the right to access all your personal data stored in WalletLoop. You can:

  • View your profile and all transaction data within the app.
  • Export your transactions as an Excel or CSV file, or a PDF report, from Money > Export data; or everything in your account as a JSON file, from Settings > Privacy & Data > Export all data.
  • Request a complete, machine-readable export of everything we hold about you — your DPDP data-portability right — at support@walletloop.in. We answer it from the same export endpoint the app uses, so it is the whole account, not a summary.

7.2 Correction and Deletion

  • You can edit or delete any transaction you created.
  • You can update your profile information at any time.
  • You can delete your account directly from the app (Settings > Privacy & Data > Delete account) or by contacting us at support@walletloop.in. Deleting from inside the app is immediate and irreversible: your profile, transactions, debts, budgets, accounts, custom categories and subcategories, merchant rules, Khata entries, trips, splits, goals and streaks are erased from our database as soon as the request is processed — and from our sync provider’s copy within a day (Section 6). A request made by email is completed within 30 days, usually much sooner. Section 6 lists the few records retained afterwards, and why.
  • Erasure does not extend to the deletion safeguard described in Section 6: it holds no phone number, no email address and no name, it cannot be linked back to you, and it exists only to keep the free Pro period and referral rewards from being claimed over and over. It expires by itself 12 months after your most recent deletion.

7.3 SMS Permission Control

  • You can revoke SMS read permission at any time through your device's Settings > Apps > WalletLoop > Permissions.
  • Without this permission, SMS auto-detection will not work — but you can continue using the app by adding transactions manually, and every other feature works as before.

7.4 Notifications

WalletLoop’s reminders (bills, budgets, EMIs) are scheduled on your phone; turn them off in your phone’s notification settings for WalletLoop.

7.5 Universal Merchant Categorization (Sharing Toggle)

Settings > Privacy & Data > "Help improve categorization" controls the sharing described in Section 2.6. On by default. Turning it off stops new merchants from being shared, clears any that are queued but unsent, and prevents future ones.

8. Children's Privacy

WalletLoop is not intended for children under the age of 18. Under India's Digital Personal Data Protection Act (DPDPA), 2023, a "child" is any individual below 18 years of age. We do not knowingly collect personal information from children under 18 without verifiable parental consent. If we become aware that a child under 18 has provided us with personal information without parental consent, we will take steps to delete such information and terminate the child's account. Please contact us at support@walletloop.in if you have concerns.

9. Compliance with Indian Laws

9.1 Digital Personal Data Protection Act, 2023

WalletLoop complies with India's Digital Personal Data Protection Act (DPDPA), 2023. Under DPDPA:

  • You have the right to access, correct, and erase your personal data.
  • From the first time you open the app — before you sign in — WalletLoop sends crash reports, usage events and update checks (Sections 2.5 and 5). Everything else is processed only after you sign in and accept this policy, which you can re-read in Settings at any time.
  • We implement reasonable data security measures and follow purpose-limitation.
  • We retain data only as long as necessary for the service or as required by law.
  • You can withdraw consent at any time by deleting your account from Settings > Privacy & Data > Delete account.
  • You have the right to nominate, in the event of death or incapacity, another individual to exercise your rights.

9.2 Information Technology Act, 2000

We maintain appropriate physical, electronic, and procedural safeguards as required under the Information Technology Act, 2000 (Section 43A and Rule 8).

10. International Data Transfers

WalletLoop is operated from India. Your data is stored and processed on servers run by our service providers (Section 5), in India and in other countries. Early-access waitlist emails (Section 2.8) are stored on our website host’s global network. Our service providers process data in accordance with their own policies. Where data is transferred outside India, we rely on the recipient's standard contractual safeguards and ensure compliance with India's Digital Personal Data Protection Act, 2023.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. We will notify you of significant changes by updating the "Last Updated" date and posting the revised policy in the app. Your continued use of WalletLoop after changes constitutes your acceptance of the updated Privacy Policy.

12. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or our data handling practices, please contact us:

WalletLoop Support

Email: support@walletloop.in

We typically respond to privacy inquiries within 7 business days.

13. Grievance Redressal

Grievance Officer: Phanindra Kanakamedala, Founder, WalletLoop.
Email: support@walletloop.in

Write to the address above with any question or complaint about how your personal data is handled — access, correction, deletion, portability, withdrawing a consent, or anything else in this policy. We acknowledge every grievance within 2 business days and aim to resolve it within 30 days. Tell us what happened and, if you can, the phone number or email your account uses, so we can find it.

If you believe your personal data has been processed in violation of the Digital Personal Data Protection Act, 2023, you also have the right to lodge a complaint with the Data Protection Board of India. You may raise it with us first, but you are not required to.

Summary: WalletLoop is designed to respect your privacy. Your raw SMS content is never stored on our servers — only the details of the payments you save (or let Auto-add save), and a scrubbed text if you choose to send us one. Your financial data is encrypted in transit and at rest. We do not sell your data. We do not show ads. We do not push loans. You have full control over your information and can delete your account at any time from within the app.
WalletLoop
Features Guide Why track Compare Privacy Terms Delete account Contact

© 2026 WalletLoop · Privacy Policy v2.16 · Built in India · Raw SMS is parsed on your phone and never uploaded unless you choose to send us one; only the details read from it sync to your account.