1. Acceptance
By creating an account, generating an API key, or otherwise using the meetbot.dev API or dashboard, you agree to these terms. If you're agreeing on behalf of an organization, you confirm that you have the authority to bind it. If you do not agree, do not use the service. Continued use after a material change to these terms (notified per Section 13) is acceptance of the change.
2. Acceptable use
You may use meetbot to record meetings only where you have the legal authority to do so. Recording-consent law varies sharply by jurisdiction — you, not we, are responsible for being on the right side of it. Specifically: 12 US states (California, Connecticut, Delaware, Florida, Hawaii in some cases, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Oregon, Pennsylvania, Vermont, Washington — non-exhaustive, list-as-of-2026 — please verify current law) require all-party consent; the EU's GDPR + national-level wiretap statutes typically require informed consent of every meeting participant. You agree not to: (a) record people without legally-sufficient consent; (b) record attorney-client privileged communications without authorisation from the privilege holder; (c) record medical consultations except under a HIPAA-compliant deployment configuration (see /samples/doctor-soap warning); (d) use meetbot for harassment, surveillance of intimate partners, or any purpose that violates applicable criminal law; (e) use meetbot to circumvent the participant-disclosure expectations of meeting platforms (e.g., disguising the bot's name to look like a human attendee). We may suspend or terminate accounts we reasonably believe to be violating this section.
3. Account
You must be at least 16 years old to create an account, or older if your jurisdiction sets a higher digital-services age (e.g., GDPR Art. 8). Account information you provide must be accurate and kept current. You are responsible for keeping your magic-link email box and your API keys secret, and for all activity under your account — including any actions taken by sub-users you grant access to via the organization plugin. Notify privacy@meetbot.dev within 24 hours of suspected key compromise; we will rotate keys on request. You may not resell, sublicense, or relabel meetbot under a different brand without a separate written agreement.
4. Fees and billing
Pricing is published on /pricing and at the time of this draft is $0.30 per meeting hour, billed monthly in arrears through Stripe. Each account receives 10 free meeting-hours per calendar month, refreshing on the 1st UTC of each month and not rolling over. We bill in per-minute increments — a 17-minute call is 8.5 cents. Failed payments: we retry per Stripe's smart-retry schedule for 14 days, then suspend the account. You can dispute a usage charge within 30 days of the invoice being issued; we will credit the disputed amount if our duration timestamps disagree by more than 5% with what you can verify from your own webhook log. We do not auto-renew anything other than the metered subscription; there are no annual contracts at the published self-serve tier.
5. Customer data
You retain all right, title, and interest in your recordings, transcripts, manifests, and any other data you cause meetbot to capture (your "Customer Data"). We claim no ownership over Customer Data and we will not use it to train models, market other services to you, or share it with anyone other than the sub-processors listed on /privacy. For the purposes of GDPR, you are the controller and meetbot is a processor with respect to Customer Data. Our Data Processing Addendum (DPA template at /dpa-template.pdf, pending counsel-finalised) governs this relationship; the DPA is incorporated into these terms by reference for any customer that has executed it.
6. Service availability
We operate the service on a best-effort basis. Our targets — published once we have 90 days of /uptime history — are 99.5% on the orchestrator API and 99.9% on the dashboard. Until that history exists we are explicit that we do not commit to a contractual SLA. You should not deploy meetbot to a mission-critical path that has no fallback path of its own until you have independently validated reliability for your workload. Planned maintenance windows are announced at least 72 hours in advance via /uptime.
7. Suspension
We may suspend the service to your account if (a) payment is past due by more than 14 days; (b) your usage materially threatens the security, integrity, or stability of the platform (for example, sustained bursts that overwhelm the queue or the bot fleet); or (c) we reasonably believe your usage is in breach of Section 2 (Acceptable use). Where practicable we will notify you before suspending; in cases of imminent harm we may suspend first and notify after.
8. Termination
You may terminate at any time by closing your account in the dashboard at /account/danger. We may terminate for material breach of these terms with 7 days' written notice and a chance for you to cure the breach within that window. We may terminate immediately for breach of Section 2 (Acceptable use) where in our reasonable judgement the breach is unsuited to a cure period (e.g., illegal recording). On termination we will delete your account data within 30 days, except where retention is required by law (Section 5 of /privacy lists those exceptions). API keys are revoked at termination.
9. Warranty disclaimer
Except as expressly set out in these terms, the service is provided 'as is' and 'as available' without warranty of any kind, express or implied, including without limitation any implied warranties of merchantability, fitness for a particular purpose, non-infringement, or that the service will be uninterrupted, secure, error-free, or that defects will be corrected. This is standard infra-SaaS language and counsel will adjust on review.
10. Limitation of liability
To the maximum extent permitted by applicable law, neither party will be liable to the other for any indirect, incidental, consequential, special, exemplary, or punitive damages, or for any loss of profits, revenue, data, or business opportunities, arising out of or relating to these terms or the service, even if advised of the possibility. Our aggregate liability for any and all claims arising out of or relating to these terms or the service is capped at the greater of (a) the fees actually paid by you to us in the 12 months immediately preceding the claim or (b) one hundred euros. Nothing in these terms limits liability for fraud, gross negligence, wilful misconduct, or any liability that cannot be limited by applicable law (including, in the EU, certain statutory consumer rights).
11. Indemnification
You will indemnify, defend, and hold harmless meetbot, its officers, employees, and agents from and against any third-party claim arising out of (a) your use of the service in breach of Section 2 (Acceptable use), (b) Customer Data you cause meetbot to capture without legally-sufficient consent from the participants, or (c) infringement of any third-party intellectual-property right by Customer Data you supply to the service. We will indemnify you on an analogous basis for any third-party claim that the service as provided by us infringes that third party's intellectual-property rights, subject to standard IP-indemnity carve-outs (combinations, modifications, use outside the documentation) that counsel will set on final review.
12. Governing law
These terms are governed by the laws of the Federal Republic of Germany, excluding its conflict-of-laws rules and excluding the UN Convention on Contracts for the International Sale of Goods. If you are a consumer based in another EU member state, your local mandatory consumer-protection law continues to apply where it is more protective.
13. Dispute resolution
Before bringing a claim, the parties will attempt in good faith to resolve any dispute by reasonable senior-level negotiation for at least 30 days after written notice of the dispute. If negotiation fails, the courts of Berlin, Germany have exclusive jurisdiction (subject to mandatory consumer jurisdiction rules where applicable).
14. Changes
We may update these terms. Material changes will be notified at least 30 days in advance via email to your account-holder address and a banner on /terms; non-material changes (typos, link rewrites) are made silently and reflected in the "Last updated" date at the top of this page. Continued use of the service after a material change takes effect is acceptance of it; if you do not accept, terminate the account before the effective date.
15. Contact
Legal inquiries, contract questions, and DPA requests: legal@meetbot.dev. Privacy: privacy@meetbot.dev. Security disclosures: security@meetbot.dev. Operating entity: meetbot UG (i.G.), Berlin, Germany — full register details published on the imprint page once UG formation completes.