Usage policy

AbyssGuard Usage Policy

Last updated: June 6, 2026

1. Allowed use

Use AbyssGuard to review repositories, codebases, and applications that you own, operate, or are explicitly authorized to assess. The product is meant to help builders find risky code patterns and make safer shipping decisions.

2. Repository permission

Do not scan private repositories, customer projects, employer code, client code, or third-party projects unless you have permission to use AbyssGuard for that work.

3. Prohibited use

Do not use AbyssGuard to attack systems, steal secrets, bypass access controls, scrape private code, harass targets, overload GitHub or our infrastructure, or generate instructions for exploitation against systems you are not authorized to test.

4. Sensitive data

Avoid submitting secrets, production credentials, personal data, health data, financial data, or confidential customer information. If a repository contains sensitive material, remove it or confirm you have permission before scanning.

5. Rate limits and abuse controls

Free scans, public quick checks, private scans, AI repair drafts, and fix-verification checks may be limited by plan, account, repository, device, IP address, or other abuse-prevention signals.

6. Enforcement

We may block scans, suspend access, remove reports, or contact users if usage appears abusive, unsafe, unauthorized, or harmful to the product or third-party services.

7. Contact

Questions about allowed use can be sent through support@abyssguard.app.