WALLETWATCH · PRACTICAL MONEY RECORDS

Privacy and your records

How WalletWatch stores records and measures public website use.

Last updated: 23 October 2026. WalletWatch is operated by Bhaumik Dhameliya in Surat, Gujarat, India. Privacy questions: privacy@naame.in. Support: support@naame.in.

Your financial records

WalletWatch stores financial records and settings in IndexedDB in your current browser. It has no customer account, bank connection or cloud sync. We do not receive these records through ordinary app use. Clearing site data or losing access to this browser can erase them. Export a JSON backup regularly. An exported file belongs to you and anyone you choose to share it with.

Optional reminder notifications

Reminders remain off until you enable them after a repeating setup. Enabling sends this browser's notification endpoint and encryption keys, time zone, chosen reminder time, and upcoming due dates to our reminder service. A random device credential protects changes. Its hash is stored on the server. Amounts, categories, notes, card details, transaction history, and recurring series IDs remain on your device.

The service sends generic notifications through the push provider for your browser, such as Apple, Google, Mozilla, or Microsoft. That provider processes delivery information and encrypted push messages. A notification asks you to open WalletWatch. It never logs a transaction automatically.

Turning reminders off removes the server subscription after a successful connection. Otherwise, subscriptions expire after 90 days without synchronization. Hashed revocation markers remain for 90 days to prevent late updates from enabling reminders again. Offline changes reach the service when you reconnect. Browser permissions and Focus settings can delay or suppress delivery. Reminder credentials stay out of exported backups and do not transfer to another device.

The public calculators run in your browser. They do not store or send their inputs. Templates and video demos contain fictional records.

Website measurement and optional cookies

Google Analytics 4 uses advanced consent mode. Before you accept cookies, and after you choose No cookies, Google receives limited cookieless visit signals without reading or writing analytics cookies. These signals can include page addresses, campaign labels, referrers, browser information and a random number for each page load. Ordinary network communication also exposes your IP address to Google.

If you choose Allow cookies, first-party cookies, including _ga, help estimate new and returning visits. Cookieless signals do not provide the same recognition of returning browsers. Google signals and advertising personalization remain disabled. Advertising consent remains denied. The privacy page does not initialize Google Analytics.

Our fixed-label events count app opens, guide views, calculator use, app-link clicks and template downloads. They contain no amounts, categories, comments, card details, imported files or calculator inputs. Google explains how it processes information and how consent mode works.

Your cookie choices

Open You, then Guides & privacy, then Analytics cookie settings to change your choice in the app. Public pages have the same link in their footer. No cookies removes accessible Google Analytics cookies and updates the tag to cookieless measurement. It does not delete information that Google already received. A saved acceptance or rejection stops the small reminder. Changing this setting does not reload the app or erase financial records.

A local-storage value remembers your choice in this browser. The choice does not sync across devices or between WalletWatch and Naame. Browser blockers and browser settings can prevent Google Analytics requests.

Hosting and support

Hostinger hosts this website. Web requests expose technical information such as IP addresses, request paths, browser information and request times to the hosting service. Server logs support delivery, security and fault investigation. Email providers process messages you send to support. Google and other providers can process information outside your country of residence.

Advertising

Display ads are not enabled in this release. A Google AdSense ownership meta tag and an ads.txt file identify the publisher for site review. They do not load ads or read your financial records. Before ads start, this notice will describe the advertising services and consent choices. Google-certified advertising consent controls will be configured where required. Financial records will not be sent as advertising parameters.

Requests and security

Contact privacy@naame.in for questions or requests about information we hold. We respond within 30 days, or sooner where applicable law requires it. We cannot recover or erase records that exist only in your browser. You can remove local records through the app or clear site data through your browser.

WalletWatch is intended for adults. HTTPS protects the website connection. Local record security depends on your device and browser. Anyone with access to the same browser profile can potentially access those records. We update this notice when the product or its data practices change.

Open WalletWatch