Privacy
What data RevenueHog collects from your account, App Store Connect, notifications, SDKs and analytics, where it is stored, and how to remove all of it.
RevenueHog holds as little about you as the product needs, and only to run it for you. This page summarizes the privacy policy at revenuehog.dev/privacy, which covers the web app, the API and the iOS app.
Data RevenueHog holds
| Data | Source | Why |
|---|---|---|
| Email, name, hashed password | Signup | Your account. Google sign-in shares your basic profile (name, email, avatar); RevenueHog never sees your Google password. |
App Store Connect .p8, Issuer ID, Key ID | You | To call Apple on your behalf. Encrypted at rest and never shared. |
| Sales, proceeds and subscription reports | Apple, with your key | Your feed, metrics and customers. Other currencies are converted to USD with public daily reference rates. |
| Server notifications (purchases, renewals, cancellations, refunds, transaction IDs) | Apple, if you point notifications at RevenueHog | Real-time events and forwarding to your own server. |
| Push tokens | Your devices, if you enable alerts | Sending your alerts. Removed when a device stops responding or you turn alerts off. |
| Alerts subscription transaction | Apple | To know your alerts are active and when they renew. |
| App user IDs and attributes | Your app, only if you add an SDK | Tying purchases to users in Customers. Without an SDK, customers are anonymous transaction-derived records. |
| Usage analytics | Google Analytics 4 | Aggregate usage of the site and app. Analytics storage is denied by default in the EU, EEA and UK. |
First-touch cookie rh_ft | Marketing site | Remembers the landing page, referrer and campaign tags for 90 days; saved with your workspace if you sign up. |
RevenueHog does not receive your customers' payment details; Apple never shares card or bank information.
Who can see it
Your account belongs to a workspace. Every member of a workspace can see its data. MCP clients and feedback API keys you create can read or write only that workspace.
What RevenueHog does not do
- It does not sell your data or share it with advertisers or data brokers.
- It does not use your revenue data to train models.
- It does not use third-party advertising trackers.
- It forwards notifications only to URLs you set yourself.
Where it lives
RevenueHog runs on Cloudflare with a Neon PostgreSQL database, both in the United States. Sub-processors: Apple (reports, notifications, APNs), Google (Google sign-in, Google Analytics, Play data if connected, FCM), Cloudflare and Neon (hosting and database), and Cloudflare Email for verification and password-reset messages.
Retention and removal
Data is kept while your account is active. You can at any time:
- Remove credentials or forwarding endpoints in Settings.
- Turn off alerts to drop your push tokens.
- Delete your account. See Delete your account.
Questions or data requests: privacy@revenuehog.dev.
Related
Last updated on
Security
How RevenueHog encrypts your App Store Connect, Stripe, Google Play and Apple Ads credentials, the sign-in methods it supports, token handling and rate limits.
Delete your account
Delete your RevenueHog account from the web or the iOS app, what is removed immediately, what happens to shared workspaces, and why subscriptions continue.