Legal · Production service

Terms of Service & Service Level Agreement

These terms govern use of Burgus Security (the “Service”) operated at burgus.ai, mcp.burgus.ai, and associated proxy hostnames under *.securellm.burgus.ai. By registering a tenant or routing traffic through the Service, you agree to these terms on behalf of your organisation.

Effective date: 18 July 2026 · Version: 1.0

1. Service description

Burgus Security is a managed AI security and audit platform for multi-agent workloads. The Service provides an LLM API proxy data plane, a Model Context Protocol (MCP) control plane, platform baseline alerts, optional custom content policy alerts, behavioral analysis on audit traffic, and compliance-oriented export tools. Alert matching is alert-only by default — the Service surfaces matches for your review; you retain responsibility for response actions unless a separate blocking agreement is signed.

2. Commercial package & pricing

• Trial: New commercial tenants receive one calendar month of full platform access at no charge. No credit card is required to start the trial.
• After trial: Usage is billed at USD 0.05 per million tokens processed through the Burgus proxy data plane (prompt + completion tokens counted from audit metadata returned by upstream providers).
• Upstream costs: You bring your own provider API keys. Fees charged by OpenAI, Anthropic, Groq, or other upstream vendors are separate and payable directly to those providers.
• Invoicing: Platform usage is invoiced monthly in arrears via Stripe. You may add a payment method at any time during or after the trial from the billing portal linked in your tenant profile.

3. Acceptable use

You agree not to:

• Use the Service to attack, probe, or disrupt third-party systems without authorisation.
• Attempt to bypass tenant isolation, authentication, or rate limits.
• Store or transmit unlawful content through the Service.
• Resell raw proxy access without a written reseller agreement.

We may suspend or terminate access that poses a security risk, violates law, or materially breaches these terms, with notice where practicable.

4. Data & privacy

By default the Service retains request metadata (timestamps, vendor, model, HTTP status, token counts, timing) — not full prompt or completion bodies. When you enable content policy rules, text is scanned ephemerally against approved rules; matched snippets may appear in alert records. See product documentation for audit data scope. You are the controller of data you send through the proxy; Burgus acts as processor for security and audit processing on your instructions via tenant configuration.

5. Intellectual property

Burgus retains all rights in the platform, rule catalogues, documentation, and branding. You retain all rights in your policies, keys, and application logic. Export bundles generated from your tenant data belong to you.

6. Warranties & liability

The Service is provided on an “as is” basis except where expressly stated in the SLA below. Burgus does not warrant that every security incident will be detected. To the maximum extent permitted by law, Burgus’s aggregate liability for claims arising from the Service in any twelve-month period is limited to the platform fees you paid in that period. Nothing in these terms excludes liability for death, personal injury caused by negligence, fraud, or other liability that cannot be excluded under applicable law.

7. Service Level Agreement (SLA)

This SLA applies to paying commercial tenants after the trial period unless otherwise agreed in writing.

7.1 Covered components

• Data plane: HTTPS proxy endpoints at https://{provider}.securellm.burgus.ai
• Control plane: MCP endpoint at https://app.burgus.ai/docs and registration at /register
• Audit ingest: Store ingest path used for tenant audit metadata

7.2 Availability commitment

Burgus targets 99.9% monthly uptime for covered components, measured as:

Uptime % = (Total minutes in month − Downtime minutes) / Total minutes in month × 100

Downtime means HTTP 5xx responses or complete unavailability of a covered component for more than five consecutive minutes, excluding scheduled maintenance (notified at least 48 hours in advance) and failures caused by upstream provider outages, your misconfiguration, or force majeure.

7.3 Support response targets (business days, UTC+1)

• Critical (production proxy or MCP unavailable): initial response within 4 hours
• High (degraded audit ingest or widespread alert pipeline failure): within 1 business day
• Normal (product questions, non-urgent issues): within 2 business days

Contact: [email protected] or the contact form at burgus.ai.

7.4 Service credits

If monthly uptime falls below 99.9%, eligible tenants may request a credit equal to:

• 99.0%–99.9%: 10% of that month’s platform usage fees
• 95.0%–98.9%: 25% of that month’s platform usage fees
• Below 95.0%: 50% of that month’s platform usage fees

Credits are applied to future invoices, are the sole remedy for SLA breaches, and must be requested within 30 days of the affected month. Credits do not apply during the free trial.

7.5 Trial period

During the one-month trial, the Service is provided with best-effort support and no SLA credits. We still aim for production-grade reliability — trial tenants use the same production infrastructure as paying customers.

8. Changes

We may update these terms with 30 days’ notice for material changes (email to your registered address or notice via MCP). Continued use after the effective date constitutes acceptance. Pricing changes apply from the next billing cycle after notice.

9. Governing law

These terms are governed by the laws of Belgium. Courts in Antwerp, Belgium have exclusive jurisdiction, without prejudice to mandatory consumer protections where applicable.