Privacy policy

TapRev is an iPhone app published by Yazeed Al Oyoun. This policy describes what the app does with data, in the order a technical reader will want it. The short version: there is no TapRev server that holds your data. The one relay, for Instant Alerts, keeps your phone’s push token, its alert settings and a few timestamps, never a sale, a customer or a key. The website, taprev.app, is different: it measures visits and is used for TapRev’s advertising (your choices).

1. What the app stores, and where

2. What the app sends, and to whom

Payment platforms

When you connect a platform, the app sends your API key to that platform’s API over HTTPS, from your phone, and reads back your data. Every request is a read; the app contains no code that writes to a platform. The platforms are Stripe, Paddle, Lemon Squeezy, Polar, Gumroad, FastSpring, Dodo Payments, Creem, RevenueCat, Superwall and Square, and each one’s own privacy policy governs what it does with the request.

RevenueCat (subscription verification)

The app includes one third-party SDK, RevenueCat’s purchase SDK, to handle the Pro subscription through the App Store. On launch and when the app returns to the foreground it contacts api.revenuecat.com with your App Store transaction information, a random per-install identifier, the device’s vendor identifier (IDFV, not the advertising identifier), and device model, OS version, locale and storefront. RevenueCat uses this to confirm whether you have an active subscription. It is not linked to your name or email, and it is not used to track you across apps or sites. RevenueCat’s handling of that data is described in RevenueCat’s privacy policy.

Product analytics (PostHog)

The app sends anonymous, non-financial usage events — which onboarding screen was reached, which platform was picked, whether a sync or a notification permission succeeded, which paywall moment was shown, and the optional onboarding answers (what you sell, where you are on the journey and what you are expecting from TapRev, each as fixed words from a short list, which then ride on later events so we can learn which kinds of sellers the app serves well) — to PostHog, hosted in the United States. Each event also carries what PostHog’s SDK attaches by default: the app version, the iOS version, the device model, the locale, the screen size, whether the build came from TestFlight, and whether the phone was on Wi-Fi or cellular. Every event carries a random id generated on your device, never your name, email, API keys, or any revenue figure. Nothing about your transactions, customers, or connected platforms is ever included. From version 1.1, if the app crashes, a crash report is sent to PostHog the next time it opens: the kind of crash, the stack trace of the app’s own code at that moment, and the same device details, under the same random id; it helps us find and fix crashes. PostHog is configured to discard the connection’s IP address on arrival and to derive no location from it. Turn analytics off anytime in Settings → Preferences → Share anonymous usage data, and both the usage events and the crash reports stop immediately. Delete All Data also gives the app a new random id, and the app replaces it on its own every 13 months.

The website

taprev.app counts visits with Google Analytics 4, separately from the app’s analytics. It records which page was viewed, how far down it you scrolled, and which link out of the site you tapped (the App Store among them), with what the browser sends: the page address and the referring page, both without anything after the “?” except campaign tags (utm_…), the browser and screen size, and a rough location Google works out from the connection; nothing you type anywhere. A card someone shares from the app carries its figures after the “?” in its link; they are drawn on the page in your browser and never sent.

Unlike the app, the website is used for advertising. Outside the European Economic Area, the United Kingdom and Switzerland, Google’s cookies (such as _ga) tell a returning visitor from a new one, and Google may use the visit, with Google signals, to measure TapRev’s ads and to show TapRev’s ads to people who visited (remarketing). Under California law, sharing a visit with Google for that is a “sale” or “sharing” of personal information: an online identifier (the cookie), what you did on the site, and a rough location. In the European Economic Area, the United Kingdom and Switzerland the site sets no cookie, stores nothing in your browser and uses nothing for ads. Google handles the data under its own policy for partner sites. No other script runs on the site, and nobody under 16 is knowingly included.

Your choices on the website

Do Not Sell or Share My Personal Information: a browser that sends Global Privacy Control or Do Not Track is opted out already, and nothing from it is used for ads. Otherwise, choose here; the choice holds in this browser. You can also stop the site counting your visits at all, install Google’s opt-out browser add-on, or block cookies from taprev.app. To ask what we hold or to have it deleted, write to [email protected]; the site holds nothing that names you, and Google deletes visit data after 14 months.

Nobody else

The app has no account system and no advertising. Standard notifications are generated on the device and never pass through a push server. The app’s privacy manifest declares no tracking and no tracking domains.

The one relay

Instant Alerts (Pro) use one relay, hooks.taprev.app, whose only job is to wake your phone when a platform reports a sale. For each phone that turns them on, it stores the phone’s push token; a one-way hash of the secret in its webhook links; whether the phone runs a development or App Store build, and whether it asked for silent or visible alerts; when it registered and was last seen; and, for each platform, when that platform’s webhook last arrived, which the app reads to show a link as working. A platform’s webhook can carry an amount or a customer’s email: the relay never reads it, keeps it or passes it on, and it never receives an API key. Your phone then fetches what changed with its own key, as it always does. The relay’s logs hold the first six characters of a push token, never more, and the address a phone registers from is counted in memory for an hour to stop abuse, never written down. Turn Instant Alerts off and the relay forgets the phone.

3. The App Store privacy label

The label declares five data types, none linked to your identity and none used for tracking. Purchase History, for app functionality: the RevenueCat subscription check described above. Device ID, for app functionality: the vendor identifier RevenueCat receives with that check. Product Interaction and Other Usage Data, for analytics: the anonymous usage events, the onboarding answers and the device details described above. Crash Data, for app functionality: the crash reports described above (from version 1.1). Nothing about your revenue, customers or keys is collected by us, because none of it leaves the device.

4. Deleting your data

• Settings → Delete All Data in the app removes every cached record and every API key from the Keychain.
• Deleting the app removes the local database and the widget container, but iOS keeps Keychain items after an app is deleted. Use Delete All Data first if you want the keys gone too, or revoke each key in the platform’s own dashboard, which stops any further reads regardless.
• Data held by a platform or by RevenueCat is subject to their policies and deletion processes.

5. Children

The app is for business use and is not directed at children under 16.

6. Changes

If what the app does changes, this page changes first and the date at the top moves. The current version always lives at taprev.app/privacy.

7. Contact

Questions: [email protected], @yazeedaloyoun on X, or the support page.