Skip to content

Draft — not reviewed by a lawyer

These documents were written in-house from the source code and the database, so the facts in them about how Slate behaves are accurate and checkable. The legal drafting is not. No lawyer prepared, reviewed or approved any part of this page, and it must be reviewed by qualified counsel before Slate relies on it or asks anyone else to.

Terms of Service

The agreement between us and your business.

This covers you — the business taking bookings. It does not cover your guests. Your booking terms, your cancellation window and your refunds are yours, and nothing on this page changes them.

Facts checked 14 August 2026

Slate ↔ the operator

In effect from

TODO — not in effectto confirm. These are drafts. No operator has been shown them at signup and nobody has agreed to them, so nothing here binds anyone yet.

Who this is between

“We”, “us” and “Slate” mean Calibrate Holdings LLC, a Florida limited liability company, which operates the Slate booking software.

“You” means the business that creates an organization in Slate and uses it to take bookings. If you are agreeing on behalf of a company, you are saying you are allowed to.

Your guests are not part of this agreement. When somebody books a trip with you through Slate, that booking is between them and you. We are not a party to it, we take no percentage of it, and we hold none of the money.

What Slate does, and what it is not

Slate is software that takes bookings on your behalf: a public booking page, a calendar that refuses to double-book a resource, a console for managing what comes in, and optional payment, messaging and calendar integrations.

Slate is not the seller of your trips, not your merchant of record, not your agent, and not a party to your bookings. We do not set your prices, your cancellation window, your refund policy, your safety rules or your waivers. Those are yours, and section 7 says so at more length because it is the part people get wrong.

How the calendar holds

Two bookings cannot overlap on the same resource. That is enforced by a database exclusion constraint — the second one is rejected at write time, not reconciled afterwards by a script. This is a description of how the software is built, not a warranty; Section 11 is the warranty section and it disclaims plenty.

Your account and your people

You get one organization. Inside it, people hold one of three roles — owner, admin or staff — and you decide who holds which. You are responsible for who you invite and for what they do with the access you gave them.

Staff records can name a person who has no Slate login at all, because a schedule needs names on it. If you put an employee’s name in Slate, you are the one who owes that employee an explanation of why.

Keep your login credentials to yourself. If you think an account has been taken over, write to us at the address in section 16 and a person will act on it.

What it costs

Slate is a flat monthly price. It is not per location, not per booking and not per member of staff — staff are unlimited on every plan. Which price you are on is decided by one number: how many bookable resources you have switched on. A resource is the thing that can only be in one place at a time — a boat, a room, a chair, a piece of gear.

Slate plans, by number of active bookable resources
PlanActive resourcesPer month
Starter1$199
Pro2–4$499
Scale5–9$999
Fleet10+$1,799

Prices are in US dollars and exclude any tax that applies to the subscription itself. If you switch on more resources than your band allows, Slate refuses the new one and tells you which plan covers it — it does not silently upgrade you and charge you more.

Where billing actually stands today

Slate has never charged anyone. No payment keys are configured on this deployment, so the subscribe flow returns an error rather than a payment page, and every organization on Slate today is grandfathered: full console, no plan limits, no invoice.

We are telling you this in the terms rather than in a footnote because it changes what the rest of this section means. Until billing is switched on, the price table above is what you would pay, not what you are paying.

The trial

Every plan has a 14-day trial. During it you have the plan you picked, in full. When it ends without a payment method, the console goes into a restricted state — see section 6 — and, as always, your public booking page keeps taking bookings.

There is no self-serve way to start or cancel a subscription today, because billing is not switched on. Write to us and a person will sort it out.

If a payment fails, or you stop paying

Here is the whole ladder, in the order it happens:

  • A payment fails. Your account is marked past due. The console still works in full; it carries a banner about it. You have 14 days.
  • Fourteen days pass with no payment. The account moves to unpaid. The console becomes restricted — you can see and run what you already have, but Slate stops provisioning anything new.
  • You cancel, or the trial lapses. Same restricted console. Nothing is switched off, deactivated or deleted.

What never happens: your booking page closing

There are ten billing states an account can be in. In every one of them, your public booking page stays open and your guests can book, reschedule and cancel. A guest is never shown a payment problem between you and us.

This is not a policy we could quietly change. The column that decides it cannot hold a “closed” value at all — a database constraint refuses to store one — a second trigger stops that constraint being dropped without anyone noticing, and a test covers the application layer that no database rule can see. Three layers, because a promise to the people who trusted you with a deposit should not depend on somebody remembering.

What we will refuse is more product: an eleventh boat, a fourth location, a new gift card. Refusing to provision is fine. Refusing a booking never is.

If you drop below your band — you deactivate boats for the winter — nothing of yours is removed. Existing resources stay exactly as they are, even if there are more of them than your plan covers, and the booking page keeps running on all of them. The one thing Slate refuses is turning a deactivated resource back on past your ceiling, because otherwise switching off and on again would be a way around the plan.

Your guests are yours, and so is what you owe them

This is the most important clause in the document for anyone who has never run software on someone else’s platform before.

You publish your own consumer-facing policies

Slate does not publish a cancellation policy, a refund policy or booking terms for your guests, and it never will. Your cancellation window is a setting in your own account — you can set it per organization and override it per experience, or leave it off entirely so a guest can cancel right up to departure. Slate shows a guest whatever you set. What that window means, whether money comes back, and on what terms, is your policy to write and yours to honour.

You are responsible for having the consumer terms, waivers, licences, insurance, safety rules and tax registrations your business needs where it operates. Slate has fields for some of these. Having a field is not the same as having complied with anything.

You are responsible for your guests’ data

Your guests’ names, email addresses and phone numbers are collected by you, through software we run. In the ordinary way of describing it, you decide what is collected and why, and we store and process it on your instruction. Section 8 of the Privacy Policy sets out what that means in practice, including the parts we cannot yet do automatically.

That means: you tell your guests what you collect and why. You answer their requests to see, correct or delete it — and where you need us to act, you ask and we act. You do not upload data you had no right to collect, and you do not use Slate to contact people who did not give it to you.

There is no data processing agreement yet

A proper arrangement between a business and its software vendor over customer data is normally written down in a separate agreement, with named obligations on both sides. Slate does not have one for you to sign. If you need one — and if you serve guests in the UK or the EU you probably do — say so before you rely on Slate, because we would be writing it from scratch.

What you may not do with Slate

  • Break the law with it, or help somebody else to.
  • Use it to collect personal information you have no right to collect, or to contact people who never gave you their details.
  • Try to reach another organization's data. Tenancy is enforced in the database rather than in the application, so this is likely to fail — probing it is still a breach of these terms and grounds for us to suspend the console.
  • Resell console access, or run other businesses' bookings through your organization as if they were yours.
  • Scrape, load-test, or automate against Slate at a volume that degrades it for other operators. Ask us first and we will usually say yes.
  • Upload malware, or content that is unlawful where you or your guests are.
  • Remove or obscure Slate's notices, or reverse engineer the software except where the law says you may regardless of what a contract says.

If something you are doing puts other operators or their guests at risk, we may restrict your console. Even then, the rule in section 6 holds: your booking page and your guests’ ability to manage what they already booked are the last things we touch, and we would rather deal with you directly than leave a guest stranded.

Who owns what

Ours. The Slate software, the name, the logo and everything we wrote stays ours. Using Slate does not give you a licence to any of it beyond using the product as it is meant to be used.

Yours. Your bookings, your customer records, your service catalogue, your logo and your brand colours stay yours. You give us permission to store, copy and process them for one purpose: running Slate for you, which includes handing what is necessary to the providers listed on the subprocessors page. We do not sell your data, we do not use it to advertise to anyone, and we do not use one operator’s bookings to do anything for another.

If you send us an idea for the product, we may build it, and we do not owe you anything for it. Say so plainly if you would rather not have that be true.

The providers you connect

Card payments run through Stripe, on your Stripe account, not ours. The money goes to you. Slate takes no percentage of a booking — the flat monthly fee is the whole commercial relationship. Calendar import runs through Google, with read-only permission; nothing Slate does can create or change an event in your calendar.

When you connect one of these, you are agreeing to that company’s terms as well as ours. What they do with what they receive is between you and them. The subprocessors page lists all of them, what each one can see, and — for 3 of the 6 — the fact that they have never been handed anything at all.

What we do not promise

Slate is provided as is. To the extent the law allows, we disclaim the implied warranties — merchantability, fitness for a particular purpose, non-infringement — and we make no promise that the software will be uninterrupted, error-free, or right for how your business works.

Rather than leave that as boilerplate, here are the specific things we are not promising, because they are true today and you should know them before you depend on us:

  • Email does not work. The mail provider rejects every request from this deployment, and no message has ever left Slate. Do not build your operation on the assumption that a guest gets a written confirmation from us — check what actually arrives before you rely on it.
  • Text messages are not switched on — no credentials, and the feature is off by default per organization regardless.
  • Card payments are not configured on this deployment. Bookings that require prepayment behave accordingly.
  • There is no uptime commitment, no service credit and no support response time in this document. If you need those, ask, and we will write down something we can actually keep.
  • Nothing here makes us responsible for a provider — if Stripe, Google or the hosting underneath us has a bad day, that is not a breach of this agreement.

How far our liability goes

Neither of us is liable to the other for indirect, incidental, special or consequential loss, or for lost profits, lost bookings, lost goodwill or lost data, even if we were told it might happen.

Our total liability arising out of this agreement is capped at the greater of the fees you paid us in the twelve months before the claim and TODO — a dollar floor for the liability capto confirm.

Read that cap with today's facts in mind

Slate has charged nobody. For every current operator, “fees paid in the last twelve months” is zero, so the floor is the entire cap — and the floor has not been decided yet. This is exactly the kind of clause that needs a lawyer and a commercial decision, not a template.

None of this limits anything that cannot be limited by law — including liability for fraud, or for death or personal injury caused by negligence. If the law where you are gives you rights this section tries to cut down, the law wins.

Ending it, and what happens to your data

You can stop using Slate whenever you like. We can end this agreement if you breach it and do not fix it after we have raised it with you, or if we stop offering the product — in which case we would give you as much warning as we practically can and help you get your data out.

Nothing is deleted automatically. Ever.

This is the part most software gets wrong in the friendly direction. Slate has no automatic deletion at all. If you cancel, churn, let a trial lapse or simply never pay, every booking, every customer record and your public booking page carry on existing indefinitely. Leaving Slate does not erase anything, and you should not assume it does.

There is exactly one thing in the whole product that deletes personal data on a timer: a short-lived rate-limiting table that holds an email address for two hours. That is it.

Deletion happens when an owner asks for it

An owner can ask us to erase the organization. Every table that belongs to an organization goes with it — bookings, customers, payments, sessions, staff, resources, and the append-only records nothing else can touch: the audit log, the message log, signatures. It is performed by hand, by a person with database access, because there is no button for it in the console. We will do it within 30 days of establishing that the request came from an owner.

What that deletion does not reach

An operator's own login is not part of their business. Deleting an organization takes the business with it — every booking, customer, payment, session and audit entry — and leaves the account the owner signs in with. The email address, the hashed password, the name on the profile and the record of each sign-in, including its IP address, belong to the person rather than to the organization, and nothing in the organization delete reaches them. Deleting the login is a second, separate request. Ask for it by name if you want it, and we will do it on the same 30-day footing — we would rather you knew that than assumed it was included.

It also clears our database and nothing beyond it. It does not reach into Stripe and delete the records your payment processor holds, and it does not revoke a Google calendar token at Google’s end — you disconnect those with the provider directly, and we will tell you what to do.

Our database host keeps its own backups on its own schedule. A deleted row can survive in those backups until they age out, and we do not control that schedule. Anyone who tells you a deletion is instant and total across every system has not thought about backups.

Getting your data out: an operator can export their own reports as CSV from the console today. If you need a fuller export, ask before you go.

How these terms change

We may update these terms. When we do, the changed version is published on this page with a new date at the top, and it applies from that date.

We have no reliable way to reach you about it. Slate’s email does not work, so there is no announcement list and no in-app notice that we can honestly promise will find you. The date on this page is the record. If a change matters to you, the practical answer is to check this page when your renewal comes round — and if that is not good enough for your business, tell us, because a mail channel that actually works is on the list of things to fix.

If a change is one you cannot live with, stop using Slate and ask us to delete your organization under section 13.

Which law applies

This agreement is governed by the law of the State of Florida, without regard to conflict-of-law rules, and disputes go to the courts of Pinellas County, Florida.

Both are confirmed: Calibrate Holdings LLC is a Florida limited liability company and its principal place of business is in Pinellas County. If your business is somewhere else, or your guests are, this is still one of the first clauses counsel will want to look at — a choice of law is only worth what a court in your jurisdiction will give it.

If a court finds part of this agreement unenforceable, the rest stays. Not enforcing something once does not mean giving it up.

How to reach us

One address, read by a person. It does not pass through Slate, which is why it works when Slate does not.

cooper@usecalibrate.io

For anything that has to be served formally, the postal address is 10200 Gandy Blvd N, Apt 601, St. Petersburg, FL 33702.