Acceptable Use Policy

最終更新: 2026-10-08

What you may not do with the Service. Short, specific, and enforced at the network edge.

本文書は当サイトの運営者が作成したものであり、法的助言ではありません。コンプライアンス判断の根拠とする場合は、あなたの法域の資格を持つ弁護士に確認してください。

この法的文書は英語版のみ提供しています。機械翻訳されたプライバシーポリシーは、利用者の法域に合わせて確認済みであると誤解させるおそれがあるため、訳文は公開しません。必要に応じてブラウザの翻訳機能をご利用ください。その訳文の責任はブラウザ側にあり、当方にはありません。

1. Purpose

The Service is free. Keeping it free requires that it not be used in ways that impose cost on us or risk on other users. This Policy states those limits specifically, so that enforcement is not arbitrary.

2. Prohibited use

You agree not to use the Service to:

Circumvent rate limits, including by rotating addresses, by using distributed clients, or by probing the limits to map them.

Attack or degrade the Service, including denial-of-service, resource exhaustion, or exploiting the client-side application to attack a third party.

Scrape or index at volume. Occasional personal use is the intended purpose; automated bulk generation is not. If you need programmatic access, contact us.

Reverse-engineer the rate-limiting or abuse-prevention mechanisms for the purpose of evading them. Security research conducted in good faith and disclosed to us is expressly permitted and welcomed.

Generate context for code you do not have the right to disclose. You are responsible for your own confidentiality obligations. Do not use the Service to prepare material for transmission to a third-party AI provider where doing so would breach an NDA, an employment agreement or a client contract.

Infringe intellectual-property rights, or to produce material intended to mislead about the provenance of code.

Any unlawful purpose, or in violation of any applicable law or regulation, including export-control, sanctions and data-protection law.

Interfere with another user's use of the Service.

Circumvent rate limits, including by rotating addresses, by using distributed clients, or by probing the limits to map them.
Attack or degrade the Service, including denial-of-service, resource exhaustion, or exploiting the client-side application to attack a third party.
Scrape or index at volume. Occasional personal use is the intended purpose; automated bulk generation is not. If you need programmatic access, contact us.
Reverse-engineer the rate-limiting or abuse-prevention mechanisms for the purpose of evading them. Security research conducted in good faith and disclosed to us is expressly permitted and welcomed.
Generate context for code you do not have the right to disclose. You are responsible for your own confidentiality obligations. Do not use the Service to prepare material for transmission to a third-party AI provider where doing so would breach an NDA, an employment agreement or a client contract.
Infringe intellectual-property rights, or to produce material intended to mislead about the provenance of code.
Any unlawful purpose, or in violation of any applicable law or regulation, including export-control, sanctions and data-protection law.
Interfere with another user's use of the Service.

3. Automated enforcement

Rate limits are applied automatically at the network edge and are keyed on a hashed form of your IP address and autonomous system number, as described in the Privacy Policy. Counters expire within 24 hours.

Exceeding a limit produces a visible message in the application and a standard HTTP 429 response. It is not a ban and does not create a record of you beyond the expiring counter.

Sustained or deliberate abuse may result in a longer block applied at the network level. Because there are no accounts, we have no other remedy, and we will normally prefer to contact you first if a contact route exists.

4. Reporting abuse

Report abuse, or a vulnerability you have found, to abuse@contextbridge.app. We aim to acknowledge reports within five business days.

We do not have a bug bounty and cannot offer a payment. We will credit you in the changelog if you would like to be named, and we will not pursue legal action against good-faith security research that does not damage the Service or its users.

5. Changes

We may update this Policy. The date at the top of the page reflects the current version. Material changes will be noted in the application's changelog.

← アプリに戻る