Legal information

Terms of Service

Rules for accessing and using MarketBase.club, its public profiles, integrations and paid features.

Last updated: September 30, 2026

1. Service and identification

MarketBase.club is the name of a service for discovering, benchmarking and understanding data about internet businesses and SaaS products. The service may provide public profiles, rankings, metrics, comparisons, optional integrations and reports.

The repository identifies the service through its domain and contact addresses. The operator’s legal name, legal form, full address, registration details and legal hosting information still need to be supplied in the production configuration. Those details are displayed in the legal notice when available.

2. Definitions

  • User: anyone who visits the site, creates an account or uses a feature.
  • Account: the space associated with an email address and an authenticated session.
  • Business or project: the activity, product or website listed in MarketBase.
  • Profile: the description and benchmark signals associated with a business.
  • Content: any information, description, logo, domain or data submitted to MarketBase.
  • Verified data: data obtained or checked through an identified provenance mechanism; it is not an audit or certification.
  • Declared data: data supplied by a user or representative without an established external check.
  • Integration: an authorised connection to a third-party service, including Google Search Console or Stripe.
  • Service: the site, interfaces, APIs, background processing and MarketBase features.
  • Report: content or analysis unlocked for a project, for free or after a one-time payment.
  • Subscription: recurring paid access to a MarketBase offer.
  • Free or paid feature: a feature available without payment or for the price shown before use.

3. Account and authentication

The currently available sign-in flow uses Google OAuth. The User must provide accurate information when it is supplied by the authentication provider, protect access credentials and report unauthorised use to [email protected].

An account is personal. The User remains responsible for activity performed through the session unless it results from a failure attributable to MarketBase. MarketBase may refuse, limit or suspend access where necessary for security, abuse prevention, a breach of these terms or a legal obligation.

4. Listing a business and domain

A User may list a business only where they have the rights, permission or sufficient legitimate interest to present it. Information must be fair and must not impersonate a company or suggest representation without authorisation.

Entering a hostname alone does not prove ownership. MarketBase may request proof and use available signals such as a Search Console property, DNS signal, meta tag, file or manual review when those mechanisms are enabled. The service may correct, hide or remove content when a request is supported by verifiable evidence or a legal obligation.

5. Verified, declared and calculated data

A metric status describes the provenance known at collection time. Data obtained through an authorised integration may be `verified`; a formula output may be `calculated`; a projection may be `estimated`; user-supplied data may be `self_reported`; and demonstration data may be `public`.

Verification is limited to the checked signal and scope. It does not guarantee completeness, permanence, the truth of every business statement, accounting quality, solvency, absence of fraud or future performance. Metrics, periods, formulas and rankings may change with the source, synchronisation or methodology version.

6. Google Search Console

When the integration is available and selected by the User, MarketBase requests the read-only scope `https://www.googleapis.com/auth/webmasters.readonly`. It is used to identify a property matching the project domain and import Search Analytics metrics, including clicks, impressions, CTR, positions, queries and top pages.

Queries and pages remain private in the dashboard. An aggregate for a public feature may be exposed only within the project’s public scope when the project is public. MarketBase does not sell Google data and does not use it for advertising or ad targeting. The User can remove the authorisation in their Google account; the current repository does not yet provide an internal disconnect or revocation control, which remains an audit action.

7. Stripe and Stripe Connect

Stripe is used in two separate ways. Stripe Checkout processes MarketBase subscriptions and one-time payments. Stripe Connect may, when enabled, authorise MarketBase to read signals from a business’s Stripe account in order to calculate benchmark metrics.

The Connect flow is designed for limited reading: the account identifier, subscriptions, paid invoices, customers and amounts needed for calculations may be accessed according to the granted authorisation. MarketBase stores identifiers and service aggregates; the observed schema does not store payment methods or complete customer contact details. MarketBase does not hold funds for the connected account, make payments for that account or replace Stripe. The Stripe application type and the exact `read_only` scope must be confirmed in production.

Stripe processes MarketBase payments under its own terms. MarketBase receives the events needed to reconcile a payment, activate access or record a purchased report.

8. Content, rights and moderation

The User retains rights in submitted content. The User grants MarketBase a non-exclusive permission, for the period needed to provide the service and meet obligations, to host, reproduce, technically adapt, analyse and display that content in the selected spaces, including a public profile.

The User warrants that they have the necessary rights in submitted text, logos, domains and data. They must not publish unlawful, defamatory, misleading, confidential, infringing or third-party-rights-violating content. MarketBase may disable or remove reported content; doing so does not decide the parties’ legal liability.

9. Acceptable use

  • bypass authentication, rate limits, access controls or security measures;
  • probe, attack, disrupt or exploit a vulnerability in the service or its dependencies;
  • abusively scrape the service, create accounts at scale or automate requests without a legitimate need;
  • impersonate a business, user, domain or data source;
  • forge, manipulate or present a metric as verified when it is not;
  • reverse engineer a part of the service where the law does not permit it;
  • use data to harass, discriminate, defraud, evade an obligation or make an automated financial decision about an individual.

11. Availability and dependencies

MarketBase may be interrupted for maintenance, updates, security, backups, migrations, infrastructure incidents or third-party failures. Synchronisations are asynchronous and depend on the worker and production configuration. Google, Stripe, OpenAI, email, network, DNS or hosting failures may limit or delay a feature.

12. Suspension and termination

MarketBase may suspend an account, project, integration or content where necessary for security, abuse prevention, third-party protection, non-payment, breach of these terms or legal compliance. Where circumstances allow, the User is informed of the reason and may request a review at [email protected].

Ending a subscription does not automatically delete data in the current implementation. Deletion requests are handled under the Privacy Policy, legal obligations and the technical limits described in the audit.

13. MarketBase intellectual property

The structure, software, design, original text, marks and databases of MarketBase belong to their owner or licensors. Unless permitted, the User may not reproduce, resell, substantially extract, distribute or commercially exploit them.

14. Liability and limitations

MarketBase is an information and comparison tool. Data may be incomplete, delayed, misclassified, unavailable or changed by its source. Users must verify important information before making a commercial, financial, legal or investment decision.

To the extent permitted by applicable law, MarketBase does not guarantee revenue, growth, a ranking position, a commercial result or continuous availability. No limitation applies to liability that cannot legally be excluded.

16. Changes

MarketBase may change the service and these terms. A material change will be communicated by an appropriate means and the update date will be displayed. Continued use after the effective date may constitute acceptance where the law permits; mandatory User rights remain protected.

17. Governing law and disputes

The current absence of a configured governing law and jurisdiction is a missing fact, not a waiver of legal rights.

The repository does not contain enough information to choose a specific governing law or jurisdiction honestly. This page therefore does not create an arbitrary choice-of-law clause. Mandatory rules applicable in the User’s place of residence continue to apply; the operator identity and governing-law clause must be finalised before commercial operation.

For a question about this document or your data, email [email protected].