Terms of Service
The agreement for using Meet Buddy — accounts, workspaces, who owns what, and how either side ends it.
No effective date — draft
This document was drafted from what the Meet Buddy code actually does. No lawyer has reviewed it, it has no effective date, and nobody has agreed to it. Do not rely on it, and do not publish it without a review that covers your jurisdiction and your deployment.
4 facts are still missing and appear in the text as marked gaps: operator's legal name, contact address for legal notices, governing law and venue, liability cap.
Plain language, and short where it can be. Two sections are worth reading even if you skip the rest: invitees and guests, because the people who book with you have not agreed to any of this, and meetings, rooms and recording, because pressing record is a legal act.
01Who this agreement is between
These terms are between you and [operator's legal name], who operates this Meet Buddy deployment (“we”, “us”). They apply when you create an account, when you use a workspace, and when you host a meeting here.
They do not apply to somebody who merely books a meeting with one of our customers. An invitee has no account and has agreed to nothing here; the relationship is between them and the workspace that published the booking page. See invitees and guests.
02Your account
- One account, one person. Accounts are not shared; if two people need access to the same work, that is what a workspace with two members is for.
- Keep the credentials to yourself, and tell us if you think somebody else has them. Anything done with your account is treated as done by you.
- You must be old enough to enter a contract where you live, and you must not use Meet Buddy on behalf of somebody who has been barred from it.
Suspension
We can disable an account that is breaking the acceptable use policy, that is being used to attack the service, or that we are required to disable. A disabled account stops working on its next request — the account record is checked every time, not only when a session is issued — so suspension is immediate rather than eventual. Where we can give notice first, we will.
03Workspaces, roles, and who is in charge
Everything in Meet Buddy belongs to a workspace: event types, availability, bookings, meetings, recordings, integrations. A person can belong to several, and switching between them changes what they can see.
- Owner
- Everything an admin can do, plus the terminal acts — transferring ownership and deleting the workspace.
- Admin
- Changes the workspace: other people’s event types, workflows, integrations, API keys, invitations.
- Member
- Owns their own scheduling surface — their event types, their availability, their bookings — and hosts their own rooms.
- Viewer
- Reads. Sees the calendar, the bookings and the attendance reports, and publishes nothing.
The workspace, not the individual, is our customer for the content in it. Its owners and admins can read, change and delete what other members have created there, can remove members, and can delete the whole thing. If you are a member of somebody else’s workspace, that is the arrangement you are joining — take it up with them, not with us.
Your booking link
A workspace picks a short name that becomes the first part of every booking link it publishes. Names that would collide with parts of the product are unavailable, we can reclaim one that is being used to impersonate somebody, and we do not guarantee that a name is available in the future because you had it once. Changing it breaks every link already sitting in somebody’s calendar, which is your decision to make and your consequence to manage.
04Your content stays yours
You keep every right you have in what you put here: your event descriptions, your questions, the answers your invitees give, your chat, your recordings.
You give us only the permission needed to run the service for you — storing your content, moving it between our systems, showing it to the people you have shared it with, and putting it back in front of you. That permission is limited to operating Meet Buddy for you, it lasts only as long as we hold the content, and it does not include using your meetings to train anything.
You confirm you are allowed to put the content here in the first place — including anyone else’s material in it, and including the voices and faces in a recording.
05Invitees and guests
The people who book time with you are not our customers. They arrive through a link, give you their name, their email address and whatever your form asks, and turn up to a room. They have not read these terms and we do not ask them to.
That makes you responsible for them in three specific ways:
- What you ask for. Your booking questions are yours. Asking an invitee for a national identifier, a card number or health information is your decision and your legal exposure, not ours.
- What you tell them. Where the law requires an invitee to be told how their data will be used, telling them is your job — you are the one collecting it.
- What happens in the room. Especially recording. See recording, consent and attendance.
06Meetings, rooms and recording
A confirmed booking mints a meeting room before anybody joins, which is why the confirmation email and the calendar entry carry a join link that works. Cancelling the booking closes the room; rescheduling keeps the same link.
Recording is optional, host-controlled, always indicated in the room, and may not be available on this deployment at all. Everything about it — what the law generally asks for, what Meet Buddy does technically, what it deliberately does not do — is on the recording and consent page, and that page is part of these terms.
You are responsible for having whatever consent applies where your participants are. We provide the indicator and the notice; we cannot obtain consent for you, and we do not check whether you did.
07Availability, changes and the parts we do not run
The service is provided as it is. We do not promise a level of uptime in this document, and we will change features, add them and remove them.
The parts that are not ours
Meet Buddy depends on things outside it, and it is honest about which:
- Video runs on a media server. If it is not configured or is unreachable, rooms cannot be joined — but bookings still work, because nothing on the booking path depends on it.
- Recording additionally needs object storage and a separate recording worker. Without them the control is disabled and says so.
- Calendar connectionsare Google’s and Microsoft’s services. When one of them is down or a grant is revoked, Meet Buddy stops treating that calendar as readable rather than treating you as free — being shown as busy when you are not is an inconvenience; being double-booked is a failure.
- Emailgoes out through a mail provider. Delivery to an invitee’s inbox is not something anyone can guarantee.
08Fees
Meet Buddy itself contains no billing. There is no payment code, no plan, no metering and no invoice anywhere in it — which is a statement about this software, not a promise that using this deployment is free.
If [operator's legal name] charges for access, the price, the billing cycle, the refund position and what happens when a payment fails come from a separate agreement with them. Nothing in this document sets or limits those terms.
09How you may use it
The acceptable use policyis part of these terms. In summary: do not use a booking page or a meeting room to break the law, to harass people, to impersonate somebody, to send bulk unsolicited mail, or to record people who have not agreed to it. Do not attack the service or try to reach another workspace’s data.
Breaking it can cost you a booking page, a workspace or an account, depending on what happened and how deliberate it was.
10Ending it, and what happens to your data
You can stop using Meet Buddy at any time. An owner can delete a workspace, which is the act that actually removes things.
Deleting a workspace removes its records and its files. The rows go, and the removal of everything the workspace stored — its recordings and any other objects — is scheduled in the same database transaction as the deletion, so a crash cannot leave a workspace’s video sitting in storage with nothing left to point at it. Backups age out on their own cycle.
We may end your access if you break these terms, if we are required to, or if we stop running this deployment. Where we are shutting the service down we will give what notice we reasonably can so you can export what you need.
11Liability
To the extent the law allows, we are not liable for lost profits, lost business, lost data or indirect losses, and our total liability is capped at [liability cap].
Nothing here limits liability that cannot be limited — for death or personal injury caused by negligence, for fraud, or anything else your local consumer law protects. Where you are a consumer, your statutory rights survive this section.
You are responsible for claims arising out of what you do here: what your booking page collects, what is said in your rooms, what you record and who you record it from.
12Governing law, and changes to these terms
These terms are governed by [governing law and venue].
We can change them. For a change that materially affects you we will give notice through the product or by email before it takes effect, and continuing to use Meet Buddy afterwards is how you accept it. If you do not, stop using it and delete your workspace.
For anything about this document, contact [contact address for legal notices].