How the connection works
During onboarding, you provide a read-only v2 project secret. RevenueBug validates the credential and derives or asks you to confirm a selected RevenueCat app. Nothing is published until the credential, website, and selected scope pass validation.
RevenueBug reads daily production revenue net of estimated taxes for every active product available in the selected app's Charts filter.
What appears on the public listing
The listing includes trailing-30-day revenue, lifetime revenue, growth, and a daily revenue plot. The source credential and transaction-level customer data remain private. Revenue can briefly show zero while the first historical import is running.
Scope and attribution
The selected scope is important: a selected RevenueCat app may contain revenue from more than one product. A verified connection proves the data came from that provider scope; it does not independently audit every product’s ownership or expenses.
Provider-specific limitation: Charts data is before store commission and does not separately classify refunds or chargebacks.
Credential safety
Create a dedicated read-only credential where possible, grant only documented permissions, and revoke it when you stop using the listing. RevenueBug encrypts stored provider credentials and does not expose them through public listing responses.