AppSight

Privacy Policy

Effective date: 24 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 daily store history stay on your device. This is a short read — most sections are a few lines.

1. Who we are

2. No name, email, or sign-up required

AppSight does not ask for your name, email address, phone number, or a password. To let your reports and subscription belong to you, we create an anonymous identifier (via Supabase Auth) and store the session in your device keychain — nothing more.

That identifier is not linked to any identity we can look up, so we cannot restore your data if you delete the App. Your device timezone is stored against it too, purely so daily reports and reminders land at a sensible local hour.

3. Website waitlist

Joining the waitlist sends your email to Loops, our email provider, after a bot check. It is not stored in our own database and does not create or attach to an AppSight account. Unsubscribe anytime via the link in those emails.

4. What stays on your device

  • App Store Connect keys, Google Play service-account files, and any RevenueCat key you connect.
  • Every daily figure those keys import: downloads, proceeds, subscriptions, refunds, reviews.
  • Public listing data, chart ranks, activity you have seen, groupings, and preferences.

All of it sits in a SQLCipher-encrypted database, keyed by iOS Keychain or Android Keystore, this-device-only. Your keys are never uploaded to us — they sign requests to Apple, Google, or RevenueCat directly from your device.

5. What we ask Apple, Google, and RevenueCat on your behalf

  • Following a public listing: a public lookup across App Store storefronts (or Google Play’s public page). Icons and screenshots load straight from Apple/Google’s own content networks, so they see your device IP for those requests, under their own privacy policies.
  • A connected developer key: calls to App Store Connect / Google Play Developer API, signed on-device — sales reports, catalogue data, reviews, and any replies you send.
  • A connected RevenueCat key: subscription overview and recent events, read on-device so Activity can show subscription movement.

We never receive any of those keys ourselves.

6. Chart data we hold server-side

Public chart rankings are collected on a schedule into a shared warehouse, keyed by App Store ID only — no account or device is attached by default. Rows unconfirmed for 30 days are removed.

Turning on chart notifications links those same public app IDs to your anonymous account, only for as long as the notification is on. Connecting App Store Connect also stores a small private history (app ID, name, version, App Store state) purely so the App can recognise a pre-order starting or ending — never your key, sales reports, or reviews.

Turning on Subscription activity notifications mints a separate webhook secret (not your RevenueCat key) that you paste into your own RevenueCat project; we store only its hash, plus which RevenueCat app IDs it may notify for. Turning the toggle off deletes both. This lets subscription alerts reach you while AppSight is closed without ever holding your RevenueCat key server-side.

7. Notifications

Off until you turn a kind on. When on, we store an Expo push token for delivery — it reveals nothing about your identity to us. Notification text names the app, chart, or report date; it never includes revenue figures or keys. Turn any kind off anytime in Settings or your device settings.

8. Daily reports

Off until you turn them on, and the consent screen names every recipient before anything uploads.

  • A daily summary — downloads, proceeds, subscribers, and refunds if you’ve connected a developer account; chart placements and rating movement if you’ve only followed public listings.
  • A per-app breakdown of the same figures, including app names.
  • Notable signals: a new release, a chart move, a rating change.

That summary goes to OpenAI, which writes the report and returns it. Content sent through OpenAI’s API is not used to train their models. We never upload raw store reports, customer records, or your keys. Turning reports off in Settings deletes what was uploaded and stops future uploads.

9. Purchases and subscriptions

Apple or Google handle all billing, renewals, cancellations, and refunds — we never see your payment details. RevenueCat validates purchases for us, receiving your anonymous identifier and the store receipt; it tells us only whether your entitlement is active. Refunds go through the store’s own tools, not us.

10. Analytics, reliability, and other services we use

PostHog (product analytics) and Sentry (crash reporting, with sampled Session Replay) help us see what’s working and fix what isn’t. Neither is an advertising SDK, and neither receives your keys, raw store reports, or revenue figures. Screen views aren’t autocaptured.

  • Supabase — accounts, reports, push tokens, chart data.
  • Expo — push delivery.
  • OpenAI — writing consented daily reports.
  • RevenueCat — purchase validation.
  • PostHog / Sentry — analytics and reliability.
  • Apple / Google — store listings, APIs you connect, payments.
  • Loops — waitlist emails.

Each processes data under its own terms. We use no advertising SDKs or marketing trackers.

11. What we don’t do

  • No advertising, ad identifiers, or cross-app tracking.
  • No selling or renting personal information.
  • No training any model of ours on your store figures.
  • No uploading developer or RevenueCat keys to our servers.

12. Retention and your choices

On-device data stays until you remove it, disconnect a key, or uninstall. Server-side: private history and reports stay until you delete your account or withdraw consent; push tokens and chart watches stay while those features are on; unconfirmed chart rows expire after 30 days.

  • Turn daily reports off — deletes what was uploaded.
  • Turn any notification kind off.
  • Delete all local data from Settings.
  • Delete your account — removes every server-side row tied to your identifier.
  • Unsubscribe from waitlist emails, or ask us to delete your address.
  • Ask us for a copy of what we hold, or to correct or delete it: appsight@byaryeh.xyz.

Where GDPR/UK GDPR applies: our basis for on-device fetches, accounts, purchases, and reliability tooling is performing our contract with you; for sending figures to OpenAI it’s your consent, withdrawable anytime.

13. Security, processing location, and children

We use reasonable technical measures to protect the limited data we hold. Supabase hosts our servers in Sydney; our other providers may process data in the US and elsewhere under standard contractual clauses or equivalent safeguards.

AppSight is a tool for app publishers, not directed at children, and we don’t knowingly collect data from anyone under 13 (or the local minimum age).

14. Apple Standard EULA

If you downloaded AppSight from the App Store, Apple’s Standard End User License Agreement also applies to your use of the iOS app — see our Terms of Use for the full reference.

15. Changes and contact

We’ll post any changes here with a revised effective date, and if what leaves your device for reports changes, we’ll ask for consent again rather than carry over the old one. Questions: appsight@byaryeh.xyz.