Skip to main content
Last updated: March 09, 2026
Note: If these Terms, Policies, or Agreements are available in multiple languages, and any discrepancies exist between translations, the English version shall prevail.

1. Plan model

BabySea currently offers a free plan and paid plans named Starter, Pro, Scale, and Enterprise. Paid plans are offered in monthly and yearly variants in the current billing configuration. Customers manage subscriptions and billing details from the Billing area of the dashboard.

2. Credits

BabySea uses a credit-denominated balance for generation usage.
  • In the current product, 1 credit maps to 1 USD of balance.
  • The balance supports three decimal places.
  • BabySea records reserve, charge, refund, and add events in a credit ledger for account-level auditability. Credit-ledger retention windows are described in Data lifecycle.

3. Welcome credits

In the current product, each new user receives a one-time welcome credit allocation of $1.00. This is a per-user onboarding benefit, not a recurring reward for every new team or account created by the same user.

4. Credit packs

The dashboard currently offers one-time credit packs on top of paid subscriptions. In the current self-serve workflow:
  • the account must already have an active subscription;
  • the purchase UI is available from Billing;
  • only the Primary Owner can purchase credit packs in the current product; and
  • credit packs are add-on purchases and do not replace the underlying subscription plan.

5. Automatic reserve, charge, and refund behavior

BabySea uses a staged credit flow for generation requests.
  • Credits are reserved when a generation request is accepted for processing.
  • The reserved amount is finalized as a charge when the generation succeeds.
  • If the generation fails, BabySea may return the reserved amount as a refund.
  • If a customer cancels an eligible in-flight generation before completion, BabySea may refund the reserved amount when the cancellation is successfully applied.
Because generation jobs can complete while cancellation is still in progress, not every cancel request results in a refund. The cancel flow and race-condition handling are described further in API and inference.

6. Billing authority in team accounts

In team accounts, the current dashboard separates billing visibility from billing purchasing authority. The team role model is described further in Account and workspace.
  • Team members can view the Billing page in the current product.
  • Subscription changes, payment methods, and credit-pack purchases are reserved to the Primary Owner.
  • Owners may operate most other administrative areas without receiving the same billing purchase rights.

7. Rate limits by plan

Plan level also affects usage controls. The current account-level limits are described in API and inference.

8. Refund boundaries

Unless required by law or separately agreed in writing:
  • BabySea does not promise discretionary cash refunds for completed successful generations;
  • automatically applied credit refunds are limited to service-side failure and successful cancellation conditions enforced by the product logic; and
  • billing disputes, payment issues, and account-specific refund requests are reviewed through BabySea support channels.

9. Changes to pricing and plan features

BabySea may change plan names, prices, included limits, retention windows, or add-on availability from time to time. Retention details are described in Data lifecycle. If BabySea makes a change to an existing subscription offering, the change will apply according to the billing workflow, renewal timing, and any notice process required by law or by a separate written agreement.