Privacy Policy

Effective date: 10 August 2026

AppSight is designed to help you follow App Store and Google Play performance, not to build a profile about you. Your developer keys and store history stay on your device. This policy explains the limited data needed for anonymous accounts, optional daily reports, optional notifications, purchases, and product reliability.

1. Who we are

AppSight (the “App”) is developed by Aryeh Naar (“we”, “us”, or “our”). We respect your privacy and limit data processing to what is needed to operate the App.

2. No name, email, or registration

AppSight does not require you to create a named account, sign in with email, or provide your name, phone number, or location in order to use the App.

To own server-side rows (reports, push delivery, and subscription status), AppSight signs you in anonymously through Supabase Auth and stores the session in your device keychain. We create a random identifier. We do not ask for, and do not hold, your name, email address, phone number, or password.

That identifier is what lets your reports and your subscription belong to you. It is not linked to any identity we can look up, which also means we cannot restore your data if you delete the App and its keychain entry.

Your device timezone is stored on your anonymous profile so daily reports and reminders can fire at a sensible local hour. You can change the device timezone in system settings; the App refreshes the stored value when it next syncs the profile.

3. What stays on your device

  • App Store Connect .p8 keys, Google Play service-account JSON files, and any RevenueCat v2 secret key you choose to connect for subscription activity.
  • Every daily figure imported with those keys: downloads, redownloads, proceeds, subscriptions, refunds, reviews, and their history.
  • Public listing observations, chart ranks, activity you have seen, your app groupings, and your preferences.

All of it lives in a SQLCipher-encrypted database. The 256-bit key is generated on the device and held by the iOS Keychain or Android Keystore with this-device-only handling; Android backup is off, and AppSight will not fall back to an unencrypted database if secure storage fails.

Your developer and RevenueCat keys are never uploaded to us. They are used on the device to sign requests directly to Apple, Google, or RevenueCat.

4. Requests AppSight makes to Apple, Google, and RevenueCat

Following or refreshing a public listing asks Apple’s public lookup service about that app in up to 184 App Store storefronts, one request per storefront, so pricing and availability can be compared worldwide. Google Play listings are read from the public product page.

App icons and screenshots are loaded straight from Apple and Google content networks rather than copied through our servers. That means Apple and Google can see your device’s IP address, approximate location, and network metadata for every listing shown, and they handle that under their own privacy policies, not this one.

When you connect a developer key, AppSight calls App Store Connect and the Google Play Developer API directly from your device, signing each request locally. That may include sales reports, catalogue metadata, customer reviews, and review replies you choose to send.

When you connect your own RevenueCat secret key, AppSight reads subscription overview and recent customer events from RevenueCat’s API on your device so Activity can show subscription movement for apps you already follow. We do not receive that key.

5. Chart data on our servers

Public chart rankings are collected on a schedule into a shared Supabase warehouse. The warehouse stores public rankings for storefronts, not information that identifies you.

When you follow an App Store app, or refresh charts, AppSight sends that app’s public App Store identifier — and only that — so the warehouse can collect the overall chart and the genres that app belongs to. No account, device, or anonymous user id is attached to that list by default. Entries that no device has confirmed for 30 days are removed.

If you turn on chart notifications, AppSight also stores those same public app identifiers against your anonymous account so the server can decide who to notify when a ranking changes. That link exists only while chart notifications are on; turning them off deletes it. An App Store ID does not establish that you own or use that application.

When you check whether an app is charting, the app identifier you asked about is sent to that service so it can answer. We do not build a profile from those lookups.

6. Notifications

Push notifications are off until you turn a kind on in Settings. When they are on, AppSight stores an Expo push token for your device so Apple or Google can deliver alerts through Expo’s push service. The token does not reveal your name, email address, or Apple or Google account to us.

Chart alerts name the app and chart. Report alerts name the report date. Activity alerts summarise a review, release, or subscription event. Notification bodies do not include your revenue figures or developer keys.

Unread report reminders stop once you open the report in the App. You can turn notifications off at any time in your device settings or in AppSight; when they are disabled, AppSight will no longer use the push token to send you those alerts.

7. Daily reports, and what they send

Written daily reports are off until you turn them on. The consent screen names every recipient before anything is uploaded, and nothing is sent from a device that has not consented.

  • A daily summary for the date in question: total downloads, proceeds and currency, new subscribers, refunds, and the day-over-day change for downloads and proceeds.
  • A per-app breakdown of the same figures, which includes your app names.
  • Signals worth writing about, such as a new version going live or a notable move in the charts.

That summary is stored in Supabase against your anonymous identifier, and is then sent to OpenAI, which writes the report text and returns it. Under OpenAI’s API terms, content sent through the API is not used to train their models.

We do not upload raw store reports, per-transaction records, customer information, or your developer keys. Withdrawing consent in Settings deletes the summaries and the written reports we hold and stops any further upload.

8. Purchases and subscriptions

AppSight may offer auto-renewable subscriptions and a one-time lifetime purchase. All purchases, billing, renewals, cancellations, and refunds are processed by Apple or Google through the App Store or Google Play.

We do not receive or store your payment-card number, billing address, or other payment details. We use RevenueCat to check and remember whether a purchase or subscription is active so that paid features can be available to you.

RevenueCat receives your anonymous AppSight identifier, the store receipt for the purchase, and device and platform details needed to validate it. RevenueCat then tells our server whether your entitlement is active, which is the only purchase detail we store.

Because Apple or Google is the payment processor, we cannot issue refunds or access your payment records. To request a refund, use the store’s refund tools or contact Apple or Google Support. Refund eligibility and decisions are determined by them.

9. Product analytics and reliability

To understand whether the App is working and which features people use, AppSight uses PostHog for product analytics and Sentry for crash and error reporting. These tools are not advertising SDKs and are not used to sell your data or to build an advertising profile about you.

PostHog receives your anonymous AppSight identifier and product events such as following an app, connecting a store, viewing the paywall, completing a purchase, enabling notifications, or deleting data. Screen views are not autocaptured. PostHog may also receive device and app metadata needed to attribute those events, and can capture uncaught errors.

Sentry receives crash reports, error events, and related device and app diagnostics. Session Replay may record a sample of sessions (and a higher share of sessions that hit an error) so we can see what went wrong in the interface. Replay is used only to fix reliability problems.

Neither PostHog nor Sentry receives your developer keys, RevenueCat secret keys, raw store reports, or the daily revenue figures you may upload for written reports. We do not sell, rent, or share personal information for advertising.

10. Third-party services

AppSight uses the following services to provide the App’s functionality:

  • Supabase — anonymous authentication, profiles, reports, push tokens, chart watches, and the public chart warehouse.
  • Expo — push-notification delivery to Apple and Google.
  • OpenAI — writing consented daily reports.
  • RevenueCat — validating AppSight purchases and entitlements.
  • PostHog — product analytics and error signals.
  • Sentry — crash reporting and Session Replay for reliability.
  • Apple and Google — store listings, developer APIs you connect, push delivery, and in-app purchases.

Those providers process data under their own terms and privacy policies. We do not use third-party advertising SDKs or marketing trackers.

11. What we do not do

  • No advertising, no ad identifiers, and no cross-app advertising tracking.
  • No selling or renting of personal information.
  • No use of your store figures to train any model of ours.
  • No upload of developer keys or RevenueCat secret keys to our servers.

12. How long anything is kept

On-device data stays until you remove a followed app, disconnect a key, choose “Delete all AppSight data”, or uninstall the App.

Server-side, daily summaries and written reports stay until you withdraw consent or delete your account, at which point they are deleted. Push tokens and chart watches stay while those features are enabled. Subscription status is kept while the entitlement exists and for as long as store and tax records require.

Public chart warehouse rows are not tied to you; watched app identifiers that no device has confirmed for 30 days are removed. Analytics and error events are retained according to our PostHog and Sentry project settings, only as long as needed to operate and improve the App.

13. Your choices

  • Turn daily reports off at any time in Settings, which also deletes what was uploaded.
  • Turn notification kinds off in Settings or in your device settings.
  • Delete all local data, including your keys and imported history, from Settings.
  • Delete your account, which removes the server-side rows tied to your anonymous identifier (including push tokens, chart watches, uploaded day facts, reports, and entitlement status we store).
  • Ask us for a copy of what we hold, or ask us to correct or delete it, by writing to appsight@byaryeh.xyz.

Where the GDPR or UK GDPR applies, our basis for processing on-device data you asked us to fetch and for operating anonymous accounts, purchases, notifications, and reliability tooling is the performance of our contract with you (and, where needed, our legitimate interests in keeping the App reliable). Our basis for sending daily figures to OpenAI is your consent, which you can withdraw at any time without affecting what happened before you did.

14. Where your data is processed

Supabase hosts our database and functions in Asia Pacific (Sydney). OpenAI, RevenueCat, PostHog, Sentry, and Expo may process data in the United States and other regions where they operate. Transfers out of the UK and EEA rely on the standard contractual clauses or other lawful transfer mechanisms in our agreements with those providers.

15. Security

We use reasonable technical measures to protect the limited information held on our servers. Your keys and store history remain on your device in an encrypted database, or travel only to Apple, Google, or RevenueCat when you ask the App to call those services.

16. Children

AppSight is a tool for app publishers and is not directed at children. Because we do not collect account registration details or knowingly identify users by name, we do not knowingly collect personal information from children under 13 (or the equivalent minimum age where you live).

17. Changes to this policy

We may update this Privacy Policy as the App evolves or when required by law. Any changes will be posted on this page, with the effective date revised accordingly.

If we change what leaves your device for daily reports, we will say so in the App before the change takes effect, and any new upload will ask for consent again rather than inherit the old one.

18. Contact us

If you have questions or concerns about this Privacy Policy, email us at appsight@byaryeh.xyz.