Privacy Policy

Effective: 1 November 2026 (updated 11 November 2026) • Controller: COOLSOLVE LLP (India)
Summary: moneylanded is a technology service operated by COOLSOLVE LLP (India) that enables merchants to accept direct UPI payments into their own bank account. We do not hold money, we do not sell your data, we run no advertisements, and we include no third-party tracking or analytics SDKs. Contact us at bala@coolsolve.com.

1. Who This Policy Applies To

This privacy policy applies to:

2. What We Collect and Why

We collect and process only the information strictly necessary to provide the payment confirmation service:

3. Raw Message Handling and Storage

Server-side: We do not store raw SMS text or raw email bodies in our database. When a bank alert arrives on the server (from the Android app or via forwarded bank email), our backend parses the message body strictly in volatile memory to extract the payment facts (the 12-digit UPI reference number, amount, timestamp, masked bank account last-4 digits, and payer VPA/name). The raw message body is immediately dropped and discarded. It is never stored in our database, never written to server disk, and never included in error logs or alerts.

On the Android phone: When the Android app identifies an SMS matching the merchant bank's credit alert format, the matching alert's full text, sender ID, and timestamp are saved in the app's private local SQLite storage (the outbox) solely to ensure reliable transmission over intermittent mobile networks. Once the moneylanded server receives and acknowledges the alert, the message is immediately and permanently deleted from the phone's outbox database.

For Gmail forwarding setup, when Google sends a forwarding verification email, the system extracts only the confirmation token or verification link and stores it in the merchant row to display in the dashboard; the raw email message is immediately discarded.

4. Android App SMS Permissions and Access

The Android app (com.moneylanded.reporter) ships as two builds of the same app, and they do not ask for the same permissions.

The Google Play build requests no SMS permission — neither android.permission.RECEIVE_SMS nor android.permission.READ_SMS. If the merchant turns it on, it uses Android's notification access instead, to read the notifications that the phone's default messages app shows, only to find the merchant bank's credit alerts. It is off until the merchant taps Agree on an in-app disclosure and then allows notification access for moneylanded in Android settings. Notifications from other apps are ignored. A message from the default messages app is checked on the phone: if its sender matches the merchant bank's sender pattern and its text parses as a bank credit alert, the app sends that alert's full text, sender ID, and received time over HTTPS to the server, which handles it as described in section 3. Any other message is dropped on the phone and is not kept or sent. A matching alert's text stays in the app's local outbox only until the server confirms it has received it, and the app keeps a short one-way fingerprint of each alert it has already sent so that the same alert is not sent twice. Some Android versions hide the text of messages from apps. On a phone that does, the app cannot read the alert and says so in Settings, and the merchant confirms payments through email forwarding (section 3) or by placing the payment on an order by hand. The merchant can turn the feature off at any time in the app's Settings, which removes the phone's credentials, empties the outbox and stops all transmission, or in Android's notification access settings.

The direct build, downloaded from moneylanded.com, does read bank credit alerts on the phone and additionally requests android.permission.RECEIVE_SMS and android.permission.READ_SMS. Everything below to the end of this section describes the direct build only.

5. Storage and Third-Party Service Providers

We do not sell, rent, or monetize your data. Data is processed and hosted with the following infrastructure providers:

No Ads and No Trackers: moneylanded does not serve advertisements, does not use advertising networks, and embeds no third-party tracking, profiling, or analytics SDKs in the web application, APIs, or Android app. Cloudflare Turnstile, described above, is a bot check and is not used for advertising or analytics.

6. Data Retention and Backups

7. Account and Data Deletion

Merchants have the right to delete their account and all associated data at any time. When an account is deleted, everything belonging to the account is permanently deleted immediately from the live database, including all business profiles, payment links, products, orders, credit records, customer payer references, paired devices, API keys, webhook deliveries, feed diagnostics (ingest events), and sessions.

Merchants can delete their account through either of two paths:

Encrypted backups of deleted data age out completely within 30 days.

8. Security

All communication between apps, browsers, and our servers is encrypted in transit using modern TLS (HTTPS). Credentials — including API keys, device reporter tokens, session tokens, and sign-in codes — are stored strictly as SHA-256 cryptographic hashes and are never stored in plaintext.

9. Children's Privacy

moneylanded is a commercial payments technology service intended for businesses and merchants. It is not directed at or marketed to children under 18 years of age.

10. Changes to This Policy

If we make material changes to this privacy policy, we will update the effective date at the top of this page. Continued use of moneylanded after changes take effect constitutes acceptance of the updated policy.

11. Contact Us

If you have questions about this privacy policy, your personal data, or account deletion, please contact:

COOLSOLVE LLP
India
Email: bala@coolsolve.com
Support: support@moneylanded.com