The verification boundary
RevenueBug verifies attribution to a connected payment-provider account. A valid, scoped credential lets RevenueBug import provider-reported payments without relying on screenshots or manually typed revenue. Credentials are encrypted and never exposed on public pages.
Verification does not prove profitability, ownership of every product in an account, customer satisfaction, or that an asking price is fair. Buyers and investors should still perform independent diligence.
Trailing-30-day revenue versus MRR
RevenueBug uses a trailing-30-day revenue window as its cross-provider headline metric. This makes stores, payment processors, and app-revenue sources more comparable, but it is not always subscription MRR. One-time sales, usage charges, and annual payments can all appear in trailing revenue.
True subscription MRR normalizes active recurring contracts into a monthly amount. Use the label shown on each RevenueBug surface and avoid treating trailing revenue as contracted recurring revenue without checking the underlying business model.
The headline sum covers the current UTC date and the previous 29 dates. The displayed 30-day change compares it with the 30 dates immediately before that. These are comparisons of recorded revenue, not changes in a subscription base.
Normalization, refunds, and currencies
Each provider adapter maps its source records into daily revenue events. Qualifying refunds and disputes reduce revenue according to provider capabilities. RevenueBug converts non-USD amounts using historical rates and stores normalized minor-unit amounts to avoid floating-point currency errors.
Freshness and historical changes
Imports run asynchronously. A new listing can briefly show zero while its first import is running. Reconciliation jobs may revise historical days when a provider reports a refund, dispute, or correction after the original payment.
Privacy
Listings are public by default. A founder can hide product identity while keeping revenue public, except when the listing is marked for sale. Hidden names, domains, descriptions, and logos are removed at the server-side public-data boundary.
Read the Terms of Service for the complete platform terms.