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
On this page
- Who this is between
- What Slate does, and what it is not
- Your account and your people
- What it costs
- The booking fee you pay us
- Starting on Free
- If a payment fails, or you stop paying
- Your guests are yours, and so is what you owe them
- What you may not do with Slate
- Who owns what
- The providers you connect
- What we do not promise
- How far our liability goes
- Ending it, and what happens to your data
- How these terms change
- Which law applies
- How to reach us
In effect from
21 September 2026. These terms are in effect. Creating an organization in Slate means accepting them, and you are asked to at signup. They were written in-house.
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 do not set what you charge, and we never hold your takings. What your guest pays is your price and, where they pay by card through Slate and you have chosen “Guest pays the fee”, Slate’s disclosed booking fee on top of it. If you have chosen “Business pays the fee”, the booking fee comes out of what Stripe settles to you instead. section 5 sets out exactly how that works.
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 8 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. The second one is refused as it is made, rather than caught afterwards by a tidy-up job — so the same boat is never sold twice and then untangled over the phone. That is a description of how Slate behaves, not a warranty; Section 12 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 17 and a person will act on it.
What it costs
Slate charges no monthly subscription. It is not per location, not per member of staff and not a flat fee of any kind. Boats, rooms, chairs, gear, locations and staff are unlimited — nothing you switch on changes what you owe, because the only thing you owe is the booking fee below, on bookings you actually take.
| Plan | Active resources | Per month | Booking fee |
|---|---|---|---|
| Free | Unlimited | $0 | 3% |
The monthly price is not the whole of what you pay us, and the last column is in the same table so that nobody reads one without the other. It is Slate’s share of a card payment Stripe settles for you. If you have chosen “Guest pays the fee”, it is added to your guest’s total as a separate, disclosed line; if you have chosen “Business pays the fee”, it is taken out of what settles to you. It is nothing at all on a booking paid any other way. Section 5 is the clause for it, and it is worth reading before you switch card payments on.
Prices are in US dollars and exclude any tax that applies. Nothing you switch on moves you onto a paid plan: there is only one plan, it is unlimited, so there is no allowance to exceed, and Slate cannot move you onto a more expensive plan and bill you for it unless you choose it. Where an older plan does still carry a ceiling, the new resource is refused and you are told which plan admits it — you are never quietly moved onto that plan and billed for it.
The booking fee you pay us
Slate's booking fee is charged on card bookings we process, it is never refunded, and whether it comes out of your payout or is added to your guest's total is a setting on your organization.
When a guest pays by card through Slate, the charge is made on the business's own Stripe account and the business is the merchant of record for the whole of it. Stripe splits the booking fee off to Slate at the moment of the charge; Slate never holds the business's takings and never invoices anyone for the fee afterwards. Which side of the price the fee sits on is a setting on the business's organization. The setting is captured when checkout begins, and that checkout keeps the terms it started with even if the organization's setting changes later. On 'customer', the fee is ADDED to the guest's total as its own disclosed line: a $100 trip is charged as $103, the business receives its $100, and Slate receives $3. On 'operator', nothing is added to the guest's total: the same trip is charged as $100, Slate receives $3 out of it, and $97 settles to the business. The rate is the same either way; only who carries it differs.
The fee is charged on the amount Stripe actually settles, and on nothing else. Money taken on arrival, cash, a bank transfer, a gift card redeemed against a booking, or anything a guest pays the business outside Slate carries no fee at all. Slate never invoices a business for it and never asks for it afterwards — if Stripe settled nothing, there is nothing to split, and no debt comes into existence.
The rate is a property of your plan rather than of any one booking, and the plan table in these terms carries it beside the monthly price. Every place it appears — the pricing page, this contract, your billing screen — is rendered from the same catalog row the database charges from, so none of them can quote a rate the product is not actually using. Grandfathered organizations are charged nothing, in the same way they are charged nothing for the subscription.
Slate's booking fee is not refundable. If a booking is refunded, in whole or in part, Stripe returns the business's own price to the guest and Slate keeps the fee it was paid on the original charge. This is decided by how the booking was taken, not by any setting changed afterwards, so altering the setting never changes what an existing booking refunds. Two consequences, and they fall on different people. Where the fee came out of the business's payout, a full refund debits the business the whole price although it only ever received the price less our fee — on a $100 booking the business is $3 down on a trip that did not happen. Where the fee was added to the guest's total, the guest is returned the business's price and not the fee they paid on top — on the same booking they are refunded $100 of the $103 they paid. Bookings that carried no fee carry none back: cash, payment on arrival, a bank transfer or a gift card were never split, so there is nothing to keep and nothing to return.
If the business passes the fee to its guests, the business must tell them, before they pay, both that the fee is charged and that it is not refundable. The booking is between the business and its guest, so the obligation to disclose is the business's and not Slate's. Slate's booking page draws the fee as its own line before the guest pays — its name, its rate, and that it is not refunded — so a guest who paid online was shown it on the screen where they decided to pay. That line is a courtesy to the business, not a transfer of the obligation: a business taking a card at a counter, or quoting a price by phone, is still the one who must say it. A business that would rather not carry that obligation can set its organization to take the fee out of its own payout instead, in which case the guest is charged the business's price and nothing more and there is nothing about our fee for a guest to be told.
A booking fee: Guest pays the fee or Business pays the fee
A guest still has no agreement with Slate. They do not see this document and they are not asked to accept anything of ours; the booking they make is with the business. That does not stop a business choosing to pass our fee on, but it decides who has to explain it. If the business's organization is set to 'customer', the fee appears on the guest's total, and the guest's contract for that amount is with the business — so the business is the one who must disclose it before the guest pays, and the business is the one a guest will ask about it. Slate shows the amount as its own line at checkout so it is never mistaken for the business's price, but Slate is not a party to that conversation.
We are telling you this in your agreement rather than in a help article because your organization’s setting decides who carries the fee. On a Stripe Connect direct charge you are the merchant of record for the whole of what your guest pays, and Stripe splits our share off that charge before the rest reaches your balance. If you have chosen “Guest pays the fee”, the fee is added to your guest’s total as a separate, disclosed line and you must tell them before they pay. If you have chosen “Business pays the fee”, nothing is added to your guest’s total and the fee comes out of what settles to you. What it costs is the rate beside your plan in section 4, on card payments and on nothing else, and it is not returned when you refund a booking. If that does not work for the margins you run on, say so before you switch card payments on, because that is a conversation and not a setting.
The figures in this clause were checked against Slate’s own records on 7 September 2026.
Starting on Free
A new organization starts on Free, and stays there until it chooses otherwise. There is no trial period and no expiry: Free is a plan, not a countdown, and nothing about your account changes on its own after any number of days. If a paid plan later lapses without a payment method, the console goes into a restricted state — see section 7 — and, as always, your public booking page keeps taking bookings.
There is no self-serve way to start or cancel a subscription today, because there is no paid subscription to start: the one plan is free. Write to us and a person will sort anything else 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 a paid plan. 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. There is no setting anywhere in Slate that can close your booking page: a closed state is not something the system will accept at all, a second safeguard stops that being undone without anyone noticing, and everything the first two cannot reach is checked on its own. 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.
Neither plan caps what you can run, so there is no ceiling here for you to cross. Where a plan does cap something, nothing of yours is ever removed for crossing it: existing resources stay exactly as they are, even if there are more of them than that 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 a 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 9 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.
If your business needs a separate data processing agreement, write to us and we will provide one.
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. Every organization is walled off from every other one underneath Slate itself, not merely by the screens you can see, so this is likely to fail — trying 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 7 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.
Your website content, including every photo and its alt text, stays yours. You promise that you own it or have every right and permission needed for Slate to copy, resize, store and publish it, including any permission the law requires from people shown in a photo. You give Slate permission to do those things only to run and host your Slate website or booking page.
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. You are the merchant of record and the money goes to you; Slate never holds your takings. The one amount that reaches Slate from a booking is the booking fee in section 5, which Stripe splits off your charge at the moment it is made. If you have chosen “Guest pays the fee”, it is added to your guest’s total as a separate, disclosed line; if you have chosen “Business pays the fee”, it comes out of what settles to you. 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 1 of the 11 — the fact that it has 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 is best effort. Slate’s email works and is what carries confirmations, sign-in links and account messages, but no message is guaranteed to arrive, and a guest’s spam filter is not ours to control. Check what actually reaches your guests before you rely on it.
- Text messages from Slate are governed by the text-message terms and go only to people who opted in.
- Card payments run on your own Stripe account, connected from the console; until an account is connected, bookings that require prepayment cannot be taken.
- 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 1,000 US dollars.
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, stop using Slate 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 record of a guest’s email address, kept for two hours so one person cannot hammer your booking page, and then removed. That is it.
Deletion happens when an owner asks for it
An owner can ask us to erase the organization. Everything held under it goes with it — bookings, customers, payments, sessions, staff, resources, and the records that nothing in the console can edit or remove: the audit log, the message log, signatures. It is done by hand, by a person here, 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 deletion covers
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 own systems. Records your payment processor holds stay with your payment processor, and a Google calendar connection is revoked at Google’s end — you disconnect those with the provider directly, and we will tell you what to do. The company that hosts our data keeps its own backups on its own schedule, and a deleted record ages out of those backups on that schedule.
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.
The date on this page is the record. Slate can now reach the address on your account by email, but there is no announcement list and no in-app notice, so nothing here promises that a change will find you. 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.
If a change is one you cannot live with, stop using Slate and ask us to delete your organization under section 14.
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 run through Slate.
For anything that has to be served formally, the postal address is 10200 Gandy Blvd N, Apt 601, St. Petersburg, FL 33702.