Privacy Policy

Last updated: 21 November 2026

Template text. Please have it reviewed by a qualified legal professional and update company details before going live.

1. Information we collect

Name, Gmail address, an encrypted password hash (or your Google account identifier and profile picture if you use Continue with Google), your UPI ID, encrypted Gmail App Password, API keys (stored as hashes), and records of orders and payments (amount, order ID, UTR, payer name, timestamps).

2. How we use information

To run your merchant account, verify payments, send webhooks, provide support, prevent fraud and keep the service secure. Sign-in pages use Cloudflare Turnstile to detect bots.

3. Google sign-in

If you choose Continue with Google we receive your verified email, name and profile picture. If a password account already exists for the same email, you are signed in to that same account; no duplicate is created.

How payment verification works

MyFamGetway does not hold your money. Customers pay your UPI ID directly. We only confirm that a payment arrived, using the bank/UPI credit notification email that lands in your own Gmail.

  1. Connect Gmail. In Integrations you enter your Gmail address and a Google App Password. The App Password is encrypted at rest and is shown only as masked dots afterwards. You can revoke it any time from your Google account or disconnect it from Integrations.
  2. Create an order. Each payment link or API order gets an order ID starting with MFG and a unique payable amount (a few paise may be added so two customers never pay the exact same amount at the same time).
  3. Customer pays. The checkout page shows an amount-bound QR code. Your UPI ID is never displayed.
  4. We look for the notification. Right after an order is created and while the checkout page is open, our servers read your inbox (read-only) with a narrow search: emails from the platform-approved payment sender domain received in the last two days. All other emails are ignored. The same check also runs every minute in the background.
  5. We validate it. We check that the sender domain and email authentication results are trusted, then extract only the amount, UTR/transaction reference, payer name and time. The payment is matched to your order by order ID or exact payable amount, while the order is valid. Each email is processed once, and a UTR cannot be reused, so old or duplicate emails cannot confirm a new order.
  6. We mark it paid. The order becomes SUCCESS, the UTR, payer name and date are saved, the checkout page switches to the success screen automatically, and a signed webhook is sent to your server if you configured one.

What we store from emails: only the parsed fields above, the sender domain and the mailbox message ID used to avoid reprocessing. We do not store full email bodies. What we never do: send email from your account, delete mail, or read mail outside the narrow search.

Your responsibility: deliver goods or services only after the order shows SUCCESS. If notification emails are delayed or blocked by your bank or Gmail, confirmation is delayed too.

4. Sharing

We do not sell personal information. Data is shared only with infrastructure providers needed to run the service or when required by law.

5. Security and retention

Secrets are encrypted at rest and passwords are hashed. We keep records while your account is active and as required for legal and accounting purposes.

6. Your rights

You may request access, correction or deletion of your data by contacting us.

7. Contact

See the Contact page.