What we read and what we can write
SeedQ requests the GitHub permissions its features need. Scans read your repository through the GitHub API and never clone it. SeedQ writes your application code only where an admin has chosen to have SeedQ build an app’s tasks. What it can write on the Guardian plan is listed in full in our Terms. Scans use short-lived installation tokens, never your personal GitHub token, and only for the repositories you choose. The optional hand-off to GitHub Copilot uses a personal token only if you add one.
Encryption
All traffic to SeedQ is encrypted in transit over HTTPS. Sensitive credentials you entrust to us — the read-only integration tokens you connect — are encrypted at rest with AES-256-GCM. Payment-card details are handled entirely by Stripe and never reach our servers.
Verified events & sessions
Every GitHub webhook is verified by HMAC signature before we act on it, and scheduled jobs are authenticated by a secret. Sign-in sessions are server-side and revocable, carried by a signed, HTTP-only cookie, and the sign-in flow is protected against CSRF. Access to your installation is gated by role-based membership checks on every request.
Auditability
Governance changes — connector credentials, members, routines and other settings — are recorded in append-only audit logs that capture who made each change and when.
Reporting a vulnerability
If you believe you’ve found a security issue, please tell us privately — don’t open a public issue. Email security@seedq.dev. Email is the only channel. We aim to acknowledge reports within 3 business days and ask that you give us a reasonable window (typically 90 days) to remediate before any public disclosure.
If you act in good faith and follow this policy, we will not bring legal action or file a criminal complaint against you for your research. This covers only SeedQ’s own systems listed in scope. We can’t give permission for systems we don’t own, including our customers’ apps and repositories and the services we use. If you come across personal data, stop, tell us, and don’t keep or share it.
Our machine-readable contact is published at /.well-known/security.txt.
Related
See our Privacy Policy for what data we process and your rights, and our Terms for the advisory nature of scan findings. The plain-language version of these answers — what SeedQ stores, how secrets are kept, how to delete your account — lives in the product guide.