PusherHub
Get started

Privacy Policy

Last updated 21 October 2026

This policy explains what personal data PusherHub collects, why, and what you can do about it. It covers the hosted PusherHub service at this website — the website, the dashboard, the REST API and the SDKs. It doesn't cover copies of PusherHub that other people host on their own servers.

PusherHub is operated by its developer ("we", "us"), who is responsible for your personal data under India's Digital Personal Data Protection Act, 2023.

Two kinds of data

  • Your account data is about you, as a PusherHub customer. We decide how it's used, and this policy explains how.
  • Your app users' data is about the people who use the apps you connect to PusherHub. You decide what's collected and why; we store and process it only to deliver your notifications and messages, on your instructions. If you're one of those app users, the app's own privacy policy applies, and the app's developer is the right person to contact first.

What we collect about you

  • Account details — your name, email address and password. Passwords are stored only as a secure hash; we can't see them.
  • Phone number — only if you choose to give one, when you sign up or in Settings › Profile, with the country code you pick. It's optional, and you can remove it at any time.
  • Messages you send us — if you use the form on our Contact Us page: your name, email address, topic and message, the phone number and website if you give them, and your IP address and the country we work out from it. We use them only to answer you.
  • Your currency — rupees or US dollars, set from the country we work out from your IP address when you sign up. We keep the currency, not the IP address.
  • Google sign-in — if you sign in with Google, we receive your name, email address, Google account ID and profile picture. We don't get your Google password or access to anything else in your Google account.
  • Signed-in devices — for each place you're signed in: the IP address, the browser and device, an approximate location worked out from the IP address, and when it was last used. You can see this list, and sign devices out, in Settings › Profile. Each entry is removed once that sign-in has expired.
  • Sign-in and reset codes — the IP address used to ask for a code. The codes themselves are stored only as a hash and deleted once they expire.
  • Payments — the plan you bought, the amount and currency, the date and status, the Razorpay order and payment IDs, how much came from your affiliate wallet, and your invoices. Your card, UPI or bank details go straight to Razorpay; we never receive or store them.
  • Billing details — what you enter at checkout for your invoices: your name, billing address and country, and, if you're buying for a business, its name and tax ID (such as a GSTIN). We print them on your invoices, with your email address, and keep them on your account so your next checkout is filled in for you.
  • Affiliate program — your referral code, who referred you and whom you referred, and your wallet's rewards and spending. When you ask to withdraw, the payout details you enter: a UPI ID, or a bank account holder's name, account number and IFSC, or a PayPal email address, and your PAN where we ask for it. Bank account numbers and PANs are stored encrypted.
  • What you set up in PusherHub — your apps, the Firebase service account you connect, API keys, notifications, templates, segments, in-app messages, webhook addresses and app backups. Firebase service accounts and API secret keys are stored encrypted, and backups are encrypted with a password only you know.
  • Server logs — like most websites, our servers record requests (IP address, time, page and browser) for security and troubleshooting.

What PusherHub stores about your app users

When your app registers a device with PusherHub, through our SDK or API, we store:

  • the device's Firebase messaging token, platform, brand and model, app version, language and timezone;
  • whether the user has allowed notifications, when the device was last active, and whether the app looks uninstalled;
  • a user ID: your app's own ID for the user once it signs them in, or otherwise a random ID the SDK makes for that installation;
  • an approximate location — country, state and city — worked out from the device's IP address. The IP address itself isn't stored with the device;
  • what happened to each notification and in-app message: delivered, opened, clicked, shown or dismissed.

How we use data

  • To run the Service: sign you in, send your notifications and messages, and show your analytics.
  • To apply your plan's limits and features, to process your payments, and to run the affiliate program and pay out withdrawals.
  • To email you sign-in codes, password-reset codes, and important messages about your account, your payments, your withdrawals or the Service.
  • If you gave us a phone number: only to contact you about your account, support or payments, by phone or WhatsApp. We never use it for marketing.
  • To keep PusherHub secure: block abuse, limit repeated sign-in attempts and investigate problems.
  • To meet our legal, tax and accounting obligations.

We don't sell personal data, we don't show ads, and we don't use your app users' data for any purpose of our own.

Cookies

We only use the cookies the site needs to work:

  • a session cookie that keeps you signed in;
  • a security token (XSRF-TOKEN) that protects forms against cross-site request forgery;
  • a "remember me" cookie, only if you tick that box when you sign in;
  • a referral cookie, only if you follow someone's affiliate link. It remembers who invited you for 30 days, so they're credited when you sign up. Visitors from the EU, the EEA, the UK and Switzerland are asked first, and it's set only if they agree;
  • a cookie choice cookie, which remembers for six months whether you allowed the optional cookies below — only if you were asked.

On our public website pages — not the dashboard, the sign-in pages or checkout — we may also use analytics and advertising tools, such as Google Analytics, Google Ads or Meta, to understand how people find PusherHub and to measure our own advertising. These tools may set their own cookies and receive your IP address and details about your browser and visit. Visitors from the EU, the EEA, the UK and Switzerland are asked first, and these tools load only if they agree; Cookie choices at the bottom of the page lets them change their answer.

Some pages also load services from other companies, which may set their own cookies or see your IP address: Google Sign-In on the sign-in page, and Razorpay Checkout when you pay.

Who we share data with

We share personal data only with the service providers that help us run PusherHub, and only what they need:

  • Google (Firebase Cloud Messaging) — to deliver push notifications, through the Firebase project you connect;
  • Google (Sign-In) — if you choose to sign in with Google;
  • Razorpay — to process payments and refunds, and, if you gave us a phone number, to fill it in on the checkout form for you;
  • PayPal, or your bank through UPI or a bank transfer — only when we pay out an affiliate withdrawal to you;
  • Cloudflare, which protects the website and passes its traffic on to our servers;
  • analytics and advertising providers (such as Google or Meta), only on our public website pages — and for visitors from the EU, the EEA, the UK and Switzerland, only if they agree;
  • our hosting provider, which runs the servers PusherHub is on, and our email provider, which delivers our emails.

Locations are worked out from IP addresses with a database kept on our own servers, so IP addresses aren't sent anywhere for that.

We may also disclose data where the law requires it — for example, a valid order from a court or government authority — or where it's needed to protect the rights, property or safety of our users or the public. Some providers, such as Google, Cloudflare and PayPal, may process data outside India under their own privacy and security commitments.

How long we keep data

  • Account data — for as long as you have an account. When you ask us to delete your account, we delete your account data together with the apps, devices and messages in it, as our Data Deletion Policy explains.
  • Payment, invoice and withdrawal records — for as long as Indian tax and accounting law requires, even after your account is deleted.
  • Sign-in and reset codes — deleted once they expire. Signed-in devices — removed once the sign-in has expired.
  • App backups — deleted from our servers 24 hours after they're made. Copies you download are yours to keep or delete.
  • Contact form messages — kept while we need them to answer you and follow up, then deleted.
  • App users' devices — until you delete the device or the app, or, if you've turned on automatic clean-up, once the device has been inactive for the period you set. When a device is deleted, its delivery records stay only as anonymous counts by app, platform and country.
  • Delivery and engagement records — kept while your account exists, so your analytics keep working. If message clean-up is switched on, the per-device records of notifications and in-app messages older than its number of days are deleted, and only their totals are kept — by app, day, platform and country. You can switch it off for your account in Settings.
  • Server logs — kept only as long as they're needed for security and troubleshooting.

How we protect data

Passwords and sign-in codes are hashed. Firebase service accounts, API secret keys, bank account numbers and PANs are encrypted. Each customer can see only their own apps and data, and sign-in attempts are rate-limited. Changing or resetting your password signs you out everywhere else. No system is perfectly secure, but if a breach affects your personal data, we'll tell you and the authorities as the law requires.

Your rights

Under India's Digital Personal Data Protection Act, 2023, you can:

  • ask for a summary of the personal data we hold about you and how we use it;
  • ask us to correct, complete or update it;
  • ask us to delete it, unless the law requires us to keep it — see our Data Deletion Policy;
  • withdraw your consent — which may mean closing your account;
  • nominate someone to exercise these rights for you if you die or can't act yourself;
  • raise a grievance with us and, if you're not satisfied with our answer, complain to the Data Protection Board of India.

You can change your name, phone number and password in Settings › Profile, and your billing details at your next checkout. You can reset your password with Forgot password? on the sign-in page. For anything else, contact our Grievance Officer below.

Children

PusherHub is a service for businesses and developers, and isn't meant for anyone under 18. If you believe a child has created an account, contact us and we'll delete it.

Changes to this policy

When we change this policy, we update the date at the top. If a change is significant, we'll tell you by email or in the dashboard before it takes effect.

Contact and Grievance Officer

For questions, requests or complaints about your personal data:

We'll acknowledge your request and respond within the time limits set by Indian law.