Draft — not yet reviewed by a lawyer.

What this page says about data, retention and subprocessors is taken from how the software actually behaves and is accurate. The clauses that create legal obligations are marked as outstanding and have not been drafted.

Terms of service

Last updated 15 September 2026

These terms are between Lazavee by Krafftd ("we") and the business using Lazavee ("you").

What the service is

Lazavee is booking software. You configure your services, your staff and your opening hours; we compute what times are available and take bookings on your behalf, through a widget you install on your own website or through your dashboard.

We are a tool you use to run your business. We are not a party to the appointment you make with your customer, we do not take payment for it, and we do not market your business.

Your account

  • You are responsible for what is done under your logins, including by your staff.
  • Each person with access should have their own login. Shared credentials make the audit log useless, which costs you the answer to "who cancelled this booking?".
  • Tell us promptly if you believe an account has been compromised.

Your customers' data

This is the obligation that is most often overlooked and matters most.

When somebody books with you, their details are yours, not ours. You decide what to ask for, what to keep and how long. In data-protection terms you are the controller and we are the processor. That means:

  • You need a lawful basis for collecting what you collect, and your own privacy notice describing it.
  • If you add custom questions to your booking form, you are responsible for what you ask. A field that collects health information carries obligations that an ordinary one does not.
  • Requests from your customers to see, correct or delete their data come to you. We will help you act on them; we will not act on them without you.

What we do with that data on your behalf, and who else touches it, is set out in the privacy notice and the subprocessor list.

The embed key

The key that installs your widget is public by design — it sits in the source of your own website, and we assume anybody can read it. It permits three things and nothing else: reading your public booking configuration, reading which times are free, and creating a booking within rate limits.

It is restricted to the website addresses you register against it. Keep that list accurate. A key you no longer use should be revoked, and revocation takes effect within a minute.

Acceptable use

  • Do not use the service to take bookings for anything unlawful.
  • Do not use it to send people messages they did not ask for. Confirmations and reminders relate to a booking somebody actually made; the product is not a mailing list.
  • Do not attempt to reach another business's data, or to get around the rate limits.
  • Do not resell access without our agreement.

Security testing against your own account is welcome and we would like to hear what you find: see /.well-known/security.txt. Testing against another business's data is not.

Availability

We will try to keep the service running and will not pretend it never breaks. Two honest notes on how it behaves when something does go wrong:

  • If email delivery fails, your booking is still made. The failure is shown on the booking itself rather than hidden in a log.
  • Where the software cannot be certain which business a request belongs to, it refuses the request rather than guessing. Occasionally that means an error where you expected a page. It is deliberate, and it is the behaviour that keeps one business's data away from another.

Outstanding: any uptime commitment, planned-maintenance terms, and what happens if we do not meet them.

Ending the arrangement

You can stop using the service at any time. Your bookings and customer records are your records, and you should be able to take them with you.

Outstanding: notice periods, what happens to data after an account closes and for how long it remains recoverable, suspension for non-payment, and the export mechanism itself, which is not built.

The clauses a lawyer has to write

Not drafted, deliberately. The sections above describe how the software behaves and are accurate. The following create legal obligations, cannot be derived from the code, and are not guessed at here:

  • Fees, billing, taxes and price changes
  • Warranties and disclaimers
  • Limitation of liability
  • Indemnities
  • Intellectual property and licence grant
  • Confidentiality
  • A data-processing agreement, with standard contractual clauses where data crosses borders
  • Governing law, jurisdiction and dispute resolution
  • How these terms may change, and what notice you get

Contact

[email protected]