Terms of Service
A draft skeleton. It sets out the structure a finished agreement will follow and is not in force. Do not rely on anything on this page.
Draft
This Terms of Service is a draft, not a published agreement
The sections below set out the structure a finished Terms of Service will follow. They are placeholders describing intended scope. Nothing on this page is a term, a commitment or a representation, and no part of it is currently in force.
A qualified legal professional must draft and review this document before EQ Books is offered commercially. Until that review is complete and a dated version is published here, do not rely on anything on this page.
Parties and acceptance
Will identify the legal entity providing EQ Books, the customer it contracts with, and the point at which the terms are accepted.
- Provider entity: [REGISTERED NAME AND NUMBER]
- Whether acceptance is by account creation, order form, or signature
- Who may bind a business, and what happens when an individual signs up on its behalf
The service provided
Will describe what EQ Books is and, more importantly, what it is not. The distinction matters for an accounting product.
- Bookkeeping, receivables and payables, banking and reconciliation, payroll, expenses and reporting
- An explicit statement that EQ Books is software, and does not provide accounting, tax, audit or legal advice
- That output produced by the AI CFO is informational and requires human review before it is relied on
- That the customer remains responsible for statutory filings and for the accuracy of what it records
Accounts, access and eligibility
Will cover who may hold an account and the customer’s obligations around access.
- Sign-in is handled by a third-party identity provider; credential security obligations follow from that
- Responsibility for the actions of users the customer invites into its company
- Age, jurisdiction and business-use eligibility
Customer data and ownership
Will state that the customer owns the financial records it enters, and what licence the provider needs to run the service on them.
- Ownership of ledger, payroll and document data
- The limited licence needed to host, process, back up and display that data
- Export on request and on termination, in what format and for how long
- Interaction with the ledger’s append-only design, where corrections are reversing entries rather than deletions
Acceptable use
Will list the conduct that terminates access, and how it is enforced.
- Unlawful use, including use to record or conceal fraudulent transactions
- Attempts to access another company’s data, probe, or overload the service
- Resale or provision of the service to third parties without agreement
Fees, billing and taxes
Cannot be drafted yet. EQ Books has no published pricing and no billing system, so every figure here is undetermined.
- Charges: [NOT SET]
- Billing period, currency, payment terms and late payment
- Taxes, withholding, and which party bears them
- Price changes and notice periods; renewal and cancellation
Third-party services
EQ Books depends on infrastructure and identity services it does not operate. The terms must say what that means for the customer.
- Named dependencies and their role
- That an outage or change at a dependency can affect the service
- Where a dependency’s own terms flow through to the customer
Availability, support and changes
Will set out what is promised operationally. Nothing is promised today.
- Availability target: [NONE COMMITTED]
- Support channels and response targets: [NOT SET]
- Planned maintenance, notice of it, and how breaking changes are communicated
Intellectual property
Will separate what the provider owns from what the customer owns, and cover feedback.
- Ownership of the software, interface and documentation
- That customer data is not thereby acquired
- Treatment of feedback and feature suggestions
Confidentiality
Financial records are commercially sensitive by nature, so mutual obligations are needed rather than one-way ones.
- Definition of confidential information and the standard usual exclusions
- Permitted disclosure to staff and sub-processors under equivalent obligations
- Compelled disclosure and notice
Warranties and disclaimers
Must be drafted by counsel. Disclaimer language is jurisdiction- specific and unenforceable if copied carelessly.
- What, if anything, is warranted about the service
- Disclaimers, and consumer-protection rules that override them
- An explicit statement that the customer must review its own books
Limitation of liability
The most consequential section of the document, and the one least suited to being drafted by anyone other than a lawyer.
- Liability cap and its basis: [TO BE ADVISED]
- Excluded categories of loss
- Liabilities that cannot lawfully be excluded in the governing jurisdiction
Term, suspension and termination
Will cover how the relationship ends and what survives it.
- Term, renewal and notice periods
- Grounds for suspension, and for termination for cause
- Data export window and deletion timetable after termination
Changes to these terms
Will state how amendments happen and how customers are told.
- Notice period for material changes
- Whether continued use constitutes acceptance
- Version history and effective dates
Governing law and disputes
Cannot be filled in until the provider entity and its seat are settled.
- Governing law: [JURISDICTION]
- Forum, and whether arbitration applies: [TO BE ADVISED]
- Escalation before formal proceedings
Notices and contact
Will state how formal notice is validly given by each party.
- Legal notices address: [ADDRESS]
- Notice email: [LEGAL EMAIL]
- When notice is deemed received