Draft framework · not in force

Terms of Service

A review framework for the commercial, operational, and risk decisions required by Bitfoo’s final customer agreement.

Review status: Awaiting legal review

1. Agreement and eligibility

Identify the contracting entity, when the agreement begins, who may create an account, and which related policies are incorporated.

Information required before approval:

  • Verified legal entity and governing agreement structure
  • Age, authority, and account-eligibility rules
  • Order form and policy precedence

2. Services and product boundaries

Describe the service categories and distinguish published specifications from variable or third-party elements.

Information required before approval:

  • Approved service descriptions and management boundaries
  • Provisioning, migration, support, and availability scope
  • Third-party registrar, certificate, or infrastructure dependencies

3. Customer responsibilities

Define account security, accurate information, lawful use, backups, software maintenance, and cooperation duties.

Information required before approval:

  • Credential and authorized-user responsibilities
  • Managed-hosting and unmanaged-VPS duty split
  • Customer content, licenses, and recovery obligations

4. Orders, billing, renewals, and taxes

Document actual charging, renewal, failed-payment, price-change, tax, and refund behavior.

Information required before approval:

  • Supported billing periods and renewal mechanics
  • Cancellation, refund, credit, and chargeback rules
  • Domain and certificate renewal exceptions

5. Service changes and availability

Set expectations for maintenance, product changes, migrations, resource limits, and any separately published service levels.

Information required before approval:

  • Maintenance and emergency-change process
  • Resource enforcement and upgrade behavior
  • Approved SLA, credit, and exclusion language if offered

6. Suspension and termination

Define grounds, notice, emergency action, data-access, and deletion behavior when service ends.

Information required before approval:

  • Nonpayment and policy-violation process
  • Security, abuse, and legal emergency authority
  • Data export, retention, and deletion windows

7. Warranties, liability, and indemnity

Allocate commercial risk using language appropriate to the business and applicable law.

Information required before approval:

  • Counsel-approved warranty disclaimers
  • Liability caps, exclusions, and essential-purpose language
  • Customer indemnity and claim-handling process

8. Governing law and disputes

Define the governing jurisdiction and approved dispute-resolution process.

Information required before approval:

  • Governing law and venue
  • Notice and informal-resolution steps
  • Arbitration or class-action terms only if specifically approved

9. Changes, notices, and contact

Set the policy-change process and official legal-notice routes.

Information required before approval:

  • Effective date and version history
  • Electronic and formal notice methods
  • Verified legal contact information