Store connections

Your store data

Read-only. We never change your apps, listings, prices or reviews, and we never reply to anyone. Connect or disconnect in Account → Connections.

How it is handled

Your key is encrypted: Before it is stored, the key you upload is encrypted with a key of its own (AES-256-GCM), and that key is encrypted again by a separate key-encryption key — envelope encryption. It is decrypted only inside the sync worker, for the length of a sync. It is never written to a log, and never shown again: you see its last four characters and the day you uploaded it.
Only you see your figures: Your downloads, proceeds and reviews are shown to you and nobody else — unless you switch on “Show my actual numbers publicly as Verified” for an app.
Two consents per app, both off until you switch them on: “Help improve Appleak’s estimates (anonymous)” lets your app’s figures become calibration points: a chart position, a storefront, a category, a month and a monthly revenue rounded to two figures, filed under a random id instead of your app’s name or id. “Show my actual numbers publicly as Verified” puts your proceeds in place of Appleak’s estimate on your app’s public revenue figure. One is never the other, and every change to either is recorded with its time.
Withdrawing a consent: Switching “Help improve” off deletes the calibration points already taken from that app. Curves fitted on several apps together can’t be un-fitted; they are replaced at the next nightly refit, which no longer sees yours. Switching “Show my actual numbers” off takes your figures down within a minute.
Disconnecting: Deletes your key at once and stops every sync. You choose whether the figures and reviews synced so far are deleted now, or kept for 30 days — so reconnecting picks them back up — and then deleted. Calibration points already taken from an app with “Help improve” on are kept, and nothing links them to you or the app.
Delete all my store data: Deletes every connection, key, figure and review now. Two things stay: the anonymous calibration points you allowed, and the record of when you changed each consent, which holds no figures.
Currencies: Amounts are converted to US dollars at the rate of the day they were earned — the European Central Bank’s reference rates, and frankfurter.dev for the 14 currencies the ECB doesn’t publish. The original amount and currency are always kept beside the dollar figure.

App Store Connect

What Appleak reads: Your app list: names, bundle IDs and SKUs.
Daily sales reports: first-time downloads, redownloads, updates, refunds, proceeds and customer price, per storefront — the last 365 days, then every day.
Daily subscription reports: active subscriptions and trials, new subscriptions and cancellations — the last 90 days, then every day.
Monthly finance reports: what Apple actually paid, per storefront — the last 12 fiscal months.
Analytics reports: impressions, product page views and first-time downloads from the product page, which is how the conversion rate is worked out.
Customer reviews and your published responses.
The one thing Appleak asks Apple for: An “analytics report request” for each app you pick. It asks App Store Connect to start producing the analytics reports; it changes nothing about the app. It needs an Admin key once — without one, everything else still works.
Which key to create: Users and Access → Integrations → App Store Connect API → Team Keys. A Finance key reads sales, subscriptions, finance and analytics.
Reviews need Admin, App Manager, Customer Support, Developer or Marketing — Apple doesn’t let Finance or Sales keys see them. The test tells you which parts your key can read.
Apple lets you download the .p8 file only once, and doesn’t keep a copy.

Google Play Console

What Appleak reads: The statistics files in your reports bucket: first-time installs per user, updates, and store listing visitors and acquisitions, per storefront.
The estimated sales and monthly earnings files: what buyers were charged, and what Google paid you after its fee and taxes.
The monthly review files, and the last week’s reviews with your replies through the Play Developer API.
The permissions it needs: “View app information and download bulk reports (read-only)”, set at account level.
“View financial data, orders, and cancellation survey responses”, for revenue. Without it, downloads and reviews still import.
“Reply to reviews”, only if you want the last week’s reviews and replies. Google has no read-only permission for reviews; Appleak only reads them.
Google says permission changes can take up to 48 hours to reach the reports bucket.