# Acceptable Use Policy

This policy explains what you can and can't do with LogBrew. It is part of the Terms.

Updated October 28, 2026

Canonical: https://logbrew.co/en/acceptable-use
HTML: https://logbrew.co/en/acceptable-use
See also: https://logbrew.co/en/terms

## Who this policy covers

This policy applies to everyone who uses LogBrew, including people who use it for an organization. You are responsible for activity through your account, including activity through its API keys, the CLI, SDKs, and connected agents, unless applicable law states otherwise.

## Projects you can monitor

Use LogBrew only for projects, systems, accounts, and data that you own or are authorized to monitor. You are responsible for the notices, permissions, and lawful instructions that the data you send requires.

## Content and data in events

Do not send secrets, unlawful content, unnecessary sensitive personal data, or data that violates another person's rights in events, logs, traces, or other telemetry. Do not submit malicious code.

## Unlawful and harmful use

Do not use LogBrew for unlawful, deceptive, harmful, or rights-infringing activity. Never send child sexual abuse material, malware or phishing kits, spam or phishing data, content that promotes violence or terrorism, or data that you have no legal right to collect.

## API, ingest, and limits

Do not interfere with the service or overload it. Load and stress tests need prior written permission from LogBrew: write to support@logbrew.co with the dates, the expected volume, and the project. A test without permission counts as overloading the service. Do not evade rate, usage, or plan limits. Do not share access in a way that bypasses plan, security, or organization controls. LogBrew can apply reasonable technical or usage limits.

## Accounts

Do not create accounts automatically or in bulk. Do not use several Free accounts to get around plan limits. Each person or company can have one Free organization.

## Security research

Report vulnerabilities to support@logbrew.co. LogBrew welcomes good-faith security research that follows this policy and will not take action against it. Good faith means that you do not access other users' data, do not disrupt the service, and give LogBrew reasonable time to fix an issue before you publish it. Outside good-faith research, do not probe or bypass security controls. If you suspect unauthorized access to your account, report it promptly.

## Reselling and competing use

Do not resell access to LogBrew without written permission from LogBrew. Do not scrape or copy the service, its interface, or its documentation to build a competing product. You can benchmark LogBrew and publish honest comparisons.

## How LogBrew enforces this policy

LogBrew can restrict or suspend access when reasonably needed to protect the service, prevent harm, comply with law, or respond to a material breach. When practical, LogBrew gives notice and a chance to correct the issue. For serious or repeated abuse, LogBrew can suspend or end the service without notice and remove the offending data. Charges follow the billing section of the Terms.

## Report abuse

Anyone can report abuse, a security issue, or unauthorized access to support@logbrew.co, whether or not they use LogBrew. Say what happened and when, and name the affected project or account if you know it.

## Changes

This policy is part of the Terms and changes with them. The updated date shows the current version.