Terms of Service

1. Acceptance of these Terms

These Terms of Service govern your access to and use of RevenueBug, including its public startup directory, revenue profiles, leaderboards, dashboards, generated images, and sharing tools (the “Service”). By accessing or using the Service, you agree to these Terms. If you do not agree, do not use the Service.

You must be legally capable of entering into these Terms and authorized to act for any business or payment-provider account you connect.

2. The Service

RevenueBug connects to supported payment providers, including Stripe, Lemon Squeezy, Dodo Payments, Polar, RevenueCat, and Whop, to calculate and display revenue activity in USD. Features may include daily revenue graphs, trailing revenue, lifetime revenue, growth estimates, public profiles, rankings, embeds, and social preview images.

RevenueBug is an informational publishing and visualization service. It is not an accounting, audit, tax, investment, or financial-advisory service.

3. Accounts and management access

You are responsible for providing an accurate account email and safeguarding access to that email account. Magic links authenticate access to listings associated with your account. You are responsible for actions performed through your account and must notify us if you believe it has been compromised.

4. Payment-provider credentials

To import revenue, you provide a payment-provider API key. Stripe supports a restricted, read-only key. Lemon Squeezy keys are full-access credentials and may expire; RevenueBug nevertheless uses them only for documented read requests. Dodo Payments supports keys with write access disabled. Polar supports Organization Access Tokens limited to organization, order, and refund read scopes. RevenueCat requires a v2 secret key with read access to projects, apps, products, chart overview, and charts. Whop supports Account API keys with configurable read permissions. RevenueBug uses credentials to inspect provider accounts and retrieve records required to calculate revenue metrics.

• Credentials are encrypted at rest and are not displayed after submission.
• The Service does not use the credential to create charges, issue refunds, or move funds.
• Where provider permissions are configurable, grant only those identified by RevenueBug.
• You may rotate or disconnect the credential from your dashboard or provider account.

You represent that you are authorized to provide the credential and permit RevenueBug to access the associated data.

5. Data processed by RevenueBug

The Service may process provider account information, transaction-level balance records, currencies, transaction dates and categories, source identifiers, descriptions, and derived revenue metrics. Non-USD amounts are converted to USD using available historical reference rates.

RevenueBug does not request payment card numbers or bank login credentials. Provider responses may nevertheless contain identifiers, metadata, or descriptions supplied by you or your provider. You must not place sensitive personal information in fields that RevenueBug is permitted to retrieve.

6. Public listings and privacy choices

Successful submissions are public by default. Public information may appear in the directory, leaderboards, startup profiles, embeds, downloaded images, Open Graph previews, search results, and other sharing surfaces.

If you enable “Hide product identity,” RevenueBug omits the product name, website, logo, and description from its public output. Revenue metrics, category, and any founder name or X handle you submit remain public. Information already copied or cached by third parties may remain available after you change a privacy setting.

6A. For sale listings

An eligible public listing may display a “For sale” badge, asking price, and seller contact email. RevenueBug does not verify the asking price, broker a transaction, provide legal or financial advice, hold funds in escrow, or guarantee that a sale will occur. Buyers and sellers deal directly and are responsible for their own diligence.

During a launch offer, RevenueBug may waive the future $19.99 USD one-time sale-listing fee. A launch entitlement remains attached to that listing after paid activation begins. When billing is enabled, the badge activates only after payment confirmation. Fees are non-refundable except where required by law; a refunded or reversed fee may revoke the paid entitlement.

Sale listings cannot hide product identity. The seller’s account email is not displayed publicly. RevenueBug relays buyer inquiries to that address, and the buyer’s submitted contact details and message are shared with the seller.

7. Product attribution and your representations

A payment-provider account may receive revenue for multiple products. Unless RevenueBug expressly offers and applies product-level filtering, displayed metrics reflect the connected provider account and are not proof that every payment was generated by the website or product named in a listing.

RevenueCat does not provide a reliable public website URL for its apps. A RevenueCat account owner therefore manually links exactly one selected store/app to the verified website. RevenueBug includes all active products from that app that RevenueCat exposes in its revenue chart product filter.

Polar listings are scoped to the organization identified by the submitted Organization Access Token. RevenueBug aggregates orders and refunds across every product in that organization. The displayed revenue is account-wide and is not proof that every payment came from the website named in the listing.

Whop listings are scoped to the business identified by the submitted Account API key. RevenueBug aggregates revenue across every product in that business. When a business sells multiple products, the displayed revenue is account-wide and is not proof that every payment came from the website named in the listing.

You represent and warrant that:

• You own or are authorized to manage the submitted listing and connected account.
• Your product identity, founder information, and social links are accurate.
• Your listing does not misleadingly attribute unrelated revenue to a product.
• You have all rights and permissions needed to publish the submitted information.

We may suspend, anonymize, or remove a listing that appears misleading, unauthorized, unlawful, or harmful.

8. Revenue calculations and accuracy

Metrics are calculated from available provider data using RevenueBug’s classification, date-range, currency-conversion, refund, and dispute rules. Labels such as trailing-30-day revenue, lifetime revenue, growth, and verified revenue are platform calculations and may differ from your accounting records, tax returns, provider reports, or generally accepted accounting principles.

“Verified” means that RevenueBug successfully retrieved data using a connected credential. It is not an audit, certification of ownership, product-level attribution, or guarantee of accuracy. You are responsible for independently checking all metrics before relying on or sharing them.

RevenueCat metrics use production-only Charts data and product filters scoped to the selected store/app. RevenueBug resolves that app's current active products on every full sync, imports daily USD revenue net of estimated taxes and before store commission, then fully rescans history because chart adjustments can change prior periods. Charts data cannot independently distinguish refunds from chargebacks and does not represent payout accounting. The displayed trailing-30-day revenue is RevenueBug’s 30-day sum rather than RevenueCat’s native subscription MRR metric.

Polar metrics use paid order revenue after discounts and before tax, minus successful pre-tax refunds and final lost-dispute adjustments. RevenueBug fully rescans Polar history because order, refund, and dispute states can change.

Whop metrics use all payments and linked adjustment records from the connected business. RevenueBug reports successful pre-tax payment principal minus successful refunds and final lost disputes, before provider and payout fees, and fully rescans history because adjustment states can change.

9. Acceptable use

You must not:

• Submit a credential, business, domain, or listing you are not authorized to manage.
• Misrepresent revenue, ownership, identity, verification, or metric freshness.
• Attempt to identify an anonymous listing or expose information hidden by another user.
• Scrape, bulk-copy, republish, sell, or reconstruct the Service or its directory.
• Probe security controls, introduce malicious code, overload the Service, or evade limits.
• Use the Service for fraud, harassment, spam, unlawful activity, or rights infringement.

10. Third-party services

RevenueBug relies on services such as Stripe, Lemon Squeezy, Polar, Whop, email providers, hosting providers, and foreign-exchange data providers. Your use of third-party services is governed by their terms. We do not control and are not responsible for their availability, security, accuracy, or practices.

11. Your content and RevenueBug materials

You retain ownership of content you submit. You grant RevenueBug a worldwide, non-exclusive, royalty-free license to host, process, reproduce, format, and publicly display that content as necessary to operate and promote your listing and the Service. This license ends when the content is deleted from our systems, subject to legal, security, backup, and third-party caching requirements.

RevenueBug and its software, design, branding, and original content are protected by applicable intellectual-property laws. These Terms do not grant permission to copy or create a substitute for the Service.

12. Suspension and termination

You may stop using the Service and disconnect a provider credential at any time. We may limit, suspend, or terminate access, remove content, or disable a listing when reasonably necessary to protect the Service, users, third parties, or comply with law.

13. Disclaimers

The Service is provided “as is” and “as available.” To the maximum extent permitted by law, RevenueBug disclaims all warranties, express or implied, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, availability, and uninterrupted operation.

14. Limitation of liability

To the maximum extent permitted by law, RevenueBug and its operators will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenue, data, goodwill, or business opportunities arising from the Service, provider integrations, displayed metrics, downtime, or reliance on user content.

Some jurisdictions do not allow certain warranty exclusions or liability limitations, so parts of this section may not apply to you.

15. Indemnification

You agree to defend, indemnify, and hold harmless RevenueBug and its operators from claims, liabilities, damages, losses, and reasonable costs arising from your use of the Service, your content or credentials, your breach of these Terms, or your violation of another person’s rights or applicable law.

16. Changes to these Terms

We may update these Terms from time to time. The updated version becomes effective when posted with a revised “Last updated” date. Continued use of the Service after an update means you accept the revised Terms.

17. Contact

Questions about these Terms or requests for support may be sent to [email protected].