End user agreement

For the person using the product inside a company, as against the business that pays for it.

This document is not written yet, and nothing on it is in force.

The headings below are the shape it will take. Each one says what it needs before it can be published. It is not indexed by search engines while it says this.

Before anything else: should this document exist?

A separate end user agreement only earns its place if it says something the terms of service do not. In this product the candidate is the person a customer invites: they hold a role in somebody else company, their WhatsApp number can raise an invoice, and they never signed up or paid.

Copy owed. Nothing here is written yet.

  • A decision: keep this as a second document, or fold it into the terms of service and redirect this address there.
  • If it stays, who an end user is here, and what binds them to it.

1. Parties

Copy owed. Nothing here is written yet.

  • The registered legal name of the company.
  • Who the other party is: the invited person, the business, or both.

2. Eligibility and accounts

Copy owed. Nothing here is written yet.

  • The minimum age, and what a person has to be able to agree to.

3. What the service does

Copy owed. Nothing here is written yet.

  • How much is described here, as against in the terms of service.
  • That what a person can do depends on the role their company gave them.

4. Permitted use

Copy owed. Nothing here is written yet.

  • What a person may and may not do with a company figures.

5. WhatsApp, and a phone as a credential

A phone is linked to a person by a code issued in the app, and a linked phone can raise an invoice in that company books. Every message and every action is recorded against the person the phone was linked to.

Copy owed. Nothing here is written yet.

  • What a person agrees to by linking a phone, and what they must do if they lose it.
  • Whether messages to our number are described as recorded, and for how long they are kept.
  • Whether a shared or company phone is allowed, since the trail names the person it was linked to.

6. Third party connections

Copy owed. Nothing here is written yet.

  • What a person is agreeing to when they connect Zoho, QuickBooks or a payment gateway on a company behalf.
  • Whether an invited person may connect anything at all, or only an owner.

7. Fees

Copy owed. Nothing here is written yet.

  • That an invited person pays nothing, if that is the position, and who does.
  • What happens to their access when the company stops paying.

8. Intellectual property

Copy owed. Nothing here is written yet.

  • What is ours, and what a person may do with what they see.

9. Privacy

Copy owed. Nothing here is written yet.

  • How this points at the privacy policy, and anything true only of an invited person.
  • What their company can see about what they did. Every action is in the audit trail, and saying so here is honest.

10. Disclaimers

Copy owed. Nothing here is written yet.

  • The warranty position, as against this person rather than the business.

11. Limitation of liability

Copy owed. Nothing here is written yet.

  • The cap and the exclusions.

12. Indemnity

Copy owed. Nothing here is written yet.

  • Whether an individual is asked to indemnify anybody, and for what.

13. Term and ending it

Copy owed. Nothing here is written yet.

  • That a company can remove somebody at any time, and what happens to what they did.
  • How a person leaves of their own accord.

14. Governing law and disputes

Copy owed. Nothing here is written yet.

  • The governing law, and the courts or the arbitration seat.

15. Changes, and contact

Copy owed. Nothing here is written yet.

  • How a change is notified.
  • The effective date to print at the top, and who signs it off.
  • The address to write to.