Terms of service

Last updated: October 13, 2026

These terms govern your use of VoxGuard API. By creating an account or using the API you agree to them.

1. The service

VoxGuard API provides programmatic profanity detection over user-supplied text using a deterministic word-list engine. Detection results are probabilistic in the colloquial sense: the service does not guarantee that every offensive message is caught, nor that every flagged message is offensive in context. You are responsible for reviewing edge cases for your use case.

2. Accounts and keys

• You must provide accurate registration information and keep your password secret.
• API keys are credentials for your account. Treat them like passwords: never commit them to source control or expose them in client-side code.
• You are responsible for all activity that occurs through your keys.
• Revoked or expired keys stop working immediately.

3. Acceptable use

• Do not attempt to circumvent rate limits, access another user's data, or probe, scan or overload the service.
• Do not submit content you are not authorised to process.
• Do not use the service for unlawful purposes or to harass others.

4. Rate limits and availability

Requests are limited per key (per minute and per day). Exceeding a quota returns HTTP 429. Creating additional keys does not remove platform-level capacity limits. The service is provided "as is" without warranty of uninterrupted availability.

5. Data

Message text is processed in memory and is not persisted; only request metadata and detection verdicts are logged. See the privacy policy for details.

6. Third-party components

This application integrates the open-source library profanity_php (CC0-1.0), whose word lists are derived from a public list of bad words. Attribution notices are retained in lib/profanity_php/.

7. Changes

The operator may update these terms; continued use after changes constitutes acceptance.