Security Policy

How to report a vulnerability to Seele Agency, what to expect, and what we'll do (and won't do) once we hear from you.

Contact

Primary security@seele.agency Backup (PGP-keyed) github.com/griptoad26/seele-agency-site/security/advisories/new PGP fingerprint Available on request. We will sign replies.

Encrypt sensitive reports. If you can't encrypt, mention "security disclosure" in the subject line so it routes past spam filters.

What we promise

Scope

In scope

Out of scope

Severity classification

Payouts come from the bug-bounty pool, funded from 3% of net revenue. The pool is $0 today (no revenue yet). When revenue materializes, payouts flow to researchers who report valid issues via security.txt. See /security/acknowledgments for the pool balance, and /docs/bounty/ for the full program policy.

Program status: designed, not yet activated. The policy, payout tiers, response SLAs and safe-harbor terms are published in full at /docs/bounty/. The funding is pending: the revenue source has no live payment keys yet, so there is no revenue, no 3% allocation and no pool balance. Reports are still accepted and still fixed — only the payout is pending.

Safe harbor

When you conduct security research and report it to us per this policy, we will:

What we won't do

Acknowledgments

Researchers who report valid issues (with consent) are listed on /security/acknowledgments. The bug-bounty pool accrues at 3% of net revenue and pays out per the severity table above when revenue exists.

Safe harbor does not depend on being paid: a report is covered even if it is out of scope, a duplicate, rejected as invalid, or the pool is empty. Full safe-harbor terms, scope, exclusions and the activation checklist are in /docs/bounty/.

Last reviewed: 2026-08-21 · Edit on GitHub