Draft — last updated 20 October 2026

Privacy policy

Perchpush is run by Neptechpal Pvt. Ltd., a company registered in Nepal (“we”). This policy covers two groups of people: customers who sign in to the Perchpush dashboard, and end users — the people who use our customers’ apps and websites and receive their messages.

1. Who is responsible

For dashboard accounts, billing and our own emails, we are the controller. For end-user data, the customer who connects their app is the controller and we act as their processor under our Data Processing Agreement. End users who want to exercise their rights should contact the app they use first; we help that customer respond.

2. Data about customers

• Account: email address, name and profile picture (from Google, if you sign in with Google), sign-in times, plan and paid-until date.
• Sign-in: with Google we receive your verified email, name and picture — never your Google password. With an emailed sign-in link we store a one-time token until it is used or expires.
• Teams: the apps you belong to, your role, and an audit log of changes you make (who, what, when).
• Payments: plan, amount, currency, status and the payment provider’s reference. Card details are entered on Stripe’s page and never reach our servers.
• Credentials you connect: Firebase service-account keys, APNs keys, SMTP and SMS gateway passwords, and optional Cloudflare AI keys. These are encrypted at rest (AES-256-GCM) and used only to send on your behalf.
• Usage: monthly send counts and daily AI-call counts, to enforce plan limits.

3. Data about end users (processed for customers)

When a customer’s app or website uses a Perchpush SDK or our API, we store what is needed to deliver and measure their messages:

• Device: push token or web-push subscription, platform, push channel, app version and build, SDK version, device model, OS version, locale, timezone and UTC offset, country, notification permission, subscription status, session count, last session and last seen time, tags the app sets, unsubscribed topics, and a learned best hour for delivery.
• Person (if the app identifies them): the app’s own user id, and — only when the app signs the request from its server — email address and phone number; attributes the app sets; opt-outs for push, email and SMS; and purchase revenue the app reports.
• Activity: messages sent and their delivery status, opens, custom events the app tracks, inbox messages, journey progress.
• Tracking links: when someone clicks a customer’s Perchpush link we store a hash of the IP address salted per day (so we can match an install made the same day, but cannot recover the IP), the platform and the browser’s user-agent.

We do not use end-user data for our own purposes, do not build cross-customer profiles, and do not sell it.

4. Why we use it (legal bases)

• To provide the service you signed up for — contract.
• To keep the service secure, prevent abuse and fix faults — legitimate interests.
• To keep payment records — legal obligation.
• To send service emails (sign-in links, receipts, team invites, plan and quota notices) — contract. We do not send marketing emails without asking.

5. Where data is kept and who helps us

Our servers and database are hosted by Hetzner in Germany (EU). A small number of providers process data for us; they are listed with their purpose and location on the sub-processors page. Push notifications go through the customer’s own Firebase project or Apple key, and email and SMS through the customer’s own SMTP server or gateway — those providers work for the customer, not for us.

Where data leaves the EU (for example to Nepal for support, or to US providers), we rely on the European Commission’s Standard Contractual Clauses or an equivalent safeguard.

6. How long we keep it

• Delivery logs, events and inbox messages: deleted automatically after each app’s retention window (90 days by default, set per app).
• Tracking-link clicks: 30 days. Webhook delivery logs: 14 days. Finished journey runs: 180 days.
• Devices and people: until the customer deletes them, deletes the app, or the app reports the device as uninstalled and the customer removes it.
• Deleting an app deletes all of its data at once.
• Database backups: 14 days on our server; encrypted off-site copies 30 days. Then deleted.
• Payment records: kept as long as accounting law requires, even after an account is deleted.

7. Deleting your account

You can delete your account from Account settings. Apps you own must be deleted or handed to another owner first. Deleting removes your memberships and anonymises your user record; payment records are kept, without your name, for accounting. Copies in backups expire within 30 days.

8. Cookies

The dashboard sets only the cookies sign-in needs (a session cookie and its security tokens). We use no advertising or analytics cookies. The web SDK on customers’ sites stores a device id in the browser so that the same visitor is not registered twice.

9. Security

Traffic is encrypted with TLS. Connected credentials are encrypted at rest. Access to production systems is limited to our staff who need it. Outgoing webhooks and gateway calls are restricted to public internet addresses. Each app’s data is isolated, and isolation is tested before every release.

10. Your rights

Depending on where you live (for example under the GDPR) you can ask to access, correct, delete or export your data, object to or restrict its use, and complain to your data-protection authority. Email info@neptechpal.com.np; we reply within 30 days. End users should contact the app that messages them; customers can delete or export any end user’s data from the dashboard.

11. Children

The dashboard is not for children under 16. Customers whose apps are used by children are responsible for the consents their laws require.

12. Changes

We will post changes here and email customers before any change that reduces their rights.

Neptechpal Pvt. Ltd., Nepal · info@neptechpal.com.np