Acceptable Use Policy

Meet Buddy points a link at the public and puts strangers in a room together. Both halves can be misused, and this page says how they may not be.

Do not use it to harm people, to deceive them, to mail them things they did not ask for, or to record them without their agreement. Do not attack the service or try to reach data that is not yours. Everything below is that sentence with the specifics attached.

This policy is part of the terms, and it applies to hosts. If somebody is misusing a booking page or a meeting room, see reporting something.

• No harassment. Do not use a booking page, a meeting room, in-room chat or a workflow email to threaten, stalk, abuse or intimidate somebody. Repeatedly booking time with a person who has asked you to stop is harassment carried out with a scheduling tool.
• No recording without the consent the law requires. The indicator in the room is notice, not consent, and in a good part of the world notice is not enough. The distinction, and the rule that works everywhere, is on the recording and consent page.
• No sexual content involving minors, ever, and no using this to contact a child in a way you are not entitled to. Anything of this kind is reported, not warned about.
• No non-consensual intimate imagery, and no distributing a recording of somebody in order to humiliate or extort them.

A booking page is a small piece of the open web with your name on it, and a workspace name is the front of every link you publish. Both are usable for pretending to be somebody else, so both are covered.

• Do not represent yourself as a person, company or public body you are not, including by choosing a workspace name that reads as theirs.
• Do not run phishing through a booking page, a confirmation email or a meeting invitation. A calendar entry from a real scheduling product is an unusually convincing wrapper for a bad link, which is exactly why this is a firing offence rather than a warning.
• Do not use a booking form to collect credentials, card numbers or government identifiers under a pretext. Note that Meet Buddy’s own forms are not built for payment or health data even when you have a legitimate reason to want them.

Meet Buddy sends email on your behalf — confirmations, reminders, follow-ups, cancellation notices, and whatever your workflows are configured to send. That is a real outbound-mail capability aimed at addresses you choose, and it is treated as one.

• Booking notifications are transactional, not a mailing list. Do not use reminders or follow-ups to market to people who booked something else.
• No importing a list of addresses and generating bookings or workflow emails to reach them. Whatever that is, it is not scheduling.
• Follow the mail law that applies to you — accurate sender details, a way to stop hearing from you, and no pretending a promotion is a notification.
• Do not use the service to send malware, or links to it.

• Do not publish, transmit or store content you have no right to — somebody else’s copyrighted material, trade secrets, or personal data you were not entitled to collect.
• Do not use Meet Buddy for anything unlawful where you are, or where the people you are meeting are.
• If you are handling health information, financial data or anything else with its own regime, that is your obligation to meet. Nothing in this product is certified for it and no clause here says otherwise.

• Do not try to reach another workspace’s data, another person’s account, or any part of the system you were not given access to — including by guessing meeting codes or replaying a signed link that was not sent to you.
• Do not probe, scan or attack the service, and do not run automated traffic designed to exhaust it. Testing your own workspace at a reasonable rate is fine; that is not what this is about.
• Do not use webhooks or integrations to reach networks you do not own. Outbound webhook destinations are checked and private and loopback addresses are refused, so this is a rule the product also enforces — do not spend your afternoon looking for a way around it.
• Do not scrape booking pages at volume, and do not resell access without an agreement.
• If you find a security problem, report it to [contact address for legal notices] rather than exploiting it. Looking responsibly and telling us is welcome.

The response is meant to be proportionate. A misjudged reminder schedule is not the same thing as phishing, and treating them alike would only teach people not to report either.

We ask you to stop

The usual first step, for anything that looks like a mistake.

We disable something

A booking page, a workflow, an integration or an API key — the narrowest thing that ends the problem.

We suspend the account or the workspace

For serious or repeated breaches. A suspended account stops working on its next request, not when its session eventually expires.

We remove it

For the categories where there is nothing to discuss — content involving minors, non-consensual intimate imagery, phishing at scale. Deleting a workspace also schedules the removal of everything it stored.

What we generally will not do

We do not read your meetings or your recordings looking for breaches, and we cannot: Meet Buddy does not transcribe, and a recording is a file in your workspace’s storage. Enforcement is reactive — we act on reports, on legal process, and on abuse of the infrastructure that we can see from the outside.

Write to [contact address for legal notices]. Include the booking link, the meeting code or the workspace name, what happened, and roughly when. Those three things are what make a report actionable; without them there is usually nothing to look at.

If somebody recorded you without your agreement, start with the recording and consent page — it explains what the host can do, which is usually faster than anything we can do.

If you are reporting an emergency or a threat to someone’s safety, contact your local emergency services first. We are not a substitute for them and we cannot respond at that speed.