Terms of Service

1. The service

BrewPage is a free, no-signup publishing service for HTML, Markdown, multi-file sites, JSON documents, key-value entries and arbitrary files. It is provided by the individual maintainer named on the project's GitHub repository, as a best-effort community project — not as a commercial service with an SLA.

2. No warranty, no liability

The service is provided AS IS, without warranty of any kind, express or implied. We do not warrant that the service will be uninterrupted, error-free, virus-free, secure, or fit for any particular purpose.

To the maximum extent permitted by law, the maintainers are not liable for any direct, indirect, incidental, special, consequential, punitive or exemplary damages, including loss of data, profits, goodwill or business interruption, arising from your use of — or inability to use — the service. You use BrewPage at your own risk.

3. Your content and your responsibility

You keep all rights in the content you publish. By publishing you grant us the minimal non-exclusive licence we need to host, serve and back up the content while it lives on the service. That licence ends when the content is deleted (by you, by TTL expiry or by takedown).

You are solely responsible for what you publish. You affirm that you have the right to publish it and that doing so does not violate law, regulation or third-party rights.

4. Prohibited content and behaviour

You must not use BrewPage to publish, store, link to or deliver:

• Illegal content under any jurisdiction you or we operate in.
• CSAM or any content that sexually exploits minors.
• Phishing pages, malware, botnet C2, cryptojacking scripts, or any other attack infrastructure.
• Spam, mass unsolicited advertising, SEO doorway pages, affiliate cloaks.
• Content that infringes copyright, trademark, patent or trade secret rights.
• Harassment, threats, doxxing, targeted abuse, non-consensual intimate imagery.
• Hate speech or incitement to violence against protected groups.
• Personal data of other people without their consent; secrets or credentials.
• Content intended to circumvent rate limits, evade takedowns, or fingerprint / attack other users.

You must not scrape the service beyond the published rate limits (60 uploads / hour / IP, 300 reads / minute / IP), probe for vulnerabilities without prior written permission, or use the service to amplify denial-of-service attacks.

5. Owner Token — your responsibility

Every publish returns an Owner Token. It is the only way to edit or delete the resource. We do not have a backup, cannot reset it, and cannot recover it. Keep it safe. If you lose it, your resource will auto-delete at TTL expiry (default 15 days, max 30 days).

Do not share your Owner Token with anyone you do not trust with full edit/delete access to that resource.

6. Service limits

• HTML / Markdown: up to 5 MB per page.
• Files: up to 5 MB generic / 20 MB video / 5 MB audio.
• Multi-file site: up to 20 MB total / 100 files / 5 MB per file.
• KV value: up to 1 MB; 1000 keys per namespace.
• JSON document: up to 1 MB; 10 000 documents per collection.
• TTL: default 15 days, max 30 days. No extensions.
• Rate limits: 60 uploads / hour / IP, 300 reads / minute / IP.

Limits can change without notice. We do not owe refunds — the service is free.

7. Removal, suspension and termination

We can remove any resource and block any IP, namespace or user without prior notice if we reasonably believe it breaches these terms, breaks the law, or endangers the service or its users. We can discontinue the whole service at any time. We'll try to give reasonable advance notice for a planned shutdown, but cannot guarantee it.

If you want to stop using BrewPage, delete your resources via the Owner Token (see /advanced) or wait for TTL expiry.

8. Abuse reports and takedowns

Report abuse through /report-abuse. We review each report and take the action we think is appropriate, typically: remove the content, notify the publisher (where we have a way to), and log the event.

For copyright complaints (DMCA / equivalent), include: identification of the work, the URL of the infringing copy on BrewPage, your contact details, a good-faith statement that the use is not authorised, and a statement under penalty of perjury that the information is accurate and you are authorised to act for the rights holder.

9. AI training and machine-readable data mining

Unless the publisher explicitly grants permission, content published on BrewPage must not be used to train, fine-tune or otherwise improve machine-learning or generative-AI models. This includes large language models, image/video/audio generators, retrieval-augmented systems whose index is later used for training, and any commercial or research pipeline whose output is model weights.

For the purposes of Article 4 of the EU Directive on Copyright in the Digital Single Market (TDM opt-out) and analogous rights in other jurisdictions, publishers of BrewPage content are deemed to have reserved the rights to text and data mining unless they explicitly state otherwise in the page they publish.

Crawling the service for traditional search-engine indexing (displaying a snippet and linking to the original URL) is permitted within the rate limits and subject to /robots.txt.

10. Third-party services

BrewPage integrates analytics (Google Analytics 4, Yandex Metrika), webmaster tools, font CDNs and a container registry. Using BrewPage implies acceptance of those providers' terms; see Privacy for the list.

11. Changes to these terms

Material changes are announced on the homepage's New panel and on the project's GitHub releases page. The effective date above is updated whenever this text changes. Continuing to use BrewPage after a change means you accept the new terms.

12. Governing law

These terms are governed by the law of the operator's country of residence (as listed on the GitHub repository) to the extent permitted, without regard to conflict-of-laws principles. Mandatory consumer-protection provisions of your local law still apply.

13. Contact

Open an issue at github.com/kochetkov-ma/brewpage-openapi, or file a report via /report-abuse.