Security Policy

Last updated: March 26, 2026

What do we store?

We store the minimum necessary to operate the service:

That's it. We do not store agent data, prompts, telemetry, logs, or any user activity. Shoofly runs locally on your machine — nothing phones home.

Where is data stored?

Our backend runs on Railway. Data is encrypted in transit (TLS) and at rest on Railway's infrastructure.

Reporting a vulnerability

If you discover a security vulnerability, please report it responsibly:

Our commitment:

Note: security@shoofly.dev needs to be set up. Flag for Evan.

Safe harbor

We consider good-faith security research to be authorized conduct. If you act in good faith and in accordance with this policy, we will not pursue legal action against you. We ask that you:

Scope

In scope:

Out of scope:

CVE disclosure

For vulnerabilities that warrant a CVE, we will use GitHub Security Advisories to coordinate disclosure and publish advisories.

security.txt

The following content is also available at /.well-known/security.txt:

Contact: mailto:security@shoofly.dev Expires: 2027-03-26T00:00:00.000Z Preferred-Languages: en Canonical: https://shoofly.dev/.well-known/security.txt Policy: https://shoofly.dev/security

Contact

Security issues: security@shoofly.dev

General support: support@shoofly.dev