Security and data
Last updated 28 September 2026.
dagsec is built so that most customers never send us their code. This page is for security and procurement reviews. For anything it doesn't answer, write to hello@dagsec.net.
Where your code goes
| How you use dagsec | Where the scan runs | Does code reach dagsec? |
|---|---|---|
| GitHub Action, GitLab CI, command line | Your own runner | No. The runner downloads the scanner and scans locally. |
| GitHub App | dagsec server | Only while a scan runs. The pull request is cloned to a temporary directory and deleted when the scan ends. |
| Dashboard scan | dagsec server | Only while a scan runs, as above. The report is kept; the code is not. |
| AI agent plugin and hooks | Your machine | No. Only package names, versions and install commands are checked. |
Leaked credentials
- Reports show a masked value such as
AKIA********. The full secret is never written to a report, the database or logs. - When your own CI or the GitHub App finds a GitHub, Stripe or Slack credential, dagsec asks that provider, read-only, whether it still works, so the report can say which ones to revoke first. Turn this off with
--no-verify. Dashboard scans never do this, because anyone can scan any public repository there.
Where data is stored
- The application and its database run on a dedicated server at Hetzner in Germany (EU).
- The application listens only on the server's local interface. Visitors reach it through a Cloudflare tunnel, over HTTPS.
- Daily database copies are kept for 14 days, alongside the hosting provider's server backups.
What is stored, and for how long
| Data | Kept |
|---|---|
| Account: GitHub username, name, email, avatar | Until you ask us to delete it |
| Dashboard scan reports: repository URL, findings with masked secrets, dependency list | Until you ask us to delete them |
| Sign-in records: time, IP address, approximate location, browser | 90 days |
| Sessions | Until sign-out, at most 30 days |
| CI run records: repository name, time, runner IP and country | 400 days |
| Team audit log: packages members' AI agents tried to install | 90 days |
| Package versions your repositories use, for vulnerability alert emails | Until you turn alerts off or delete your account |
Sub-processors
| Provider | Purpose | Location |
|---|---|---|
| Hetzner Online | Server hosting and backups | Germany |
| Cloudflare | Network, TLS, website hosting, cookieless visit counts | Global edge network |
| Resend | Vulnerability alert emails | United States |
| Paddle | Payments for paid plans, as merchant of record | United Kingdom |
| GitHub | Sign-in and the GitHub App | United States |
Scans also query public services with package names and versions only, never code or personal data: OSV.dev (Google) for vulnerabilities, and the npm, PyPI, crates.io, Go, Maven Central, NuGet and Packagist registries.
How the service is protected
- HTTPS everywhere with HSTS, a strict Content Security Policy, and no framing by other sites.
- Sign-in only through GitHub. dagsec never sees a password and doesn't keep your GitHub access token.
- API keys and session tokens are stored as SHA-256 hashes, so a copy of the database can't be used to sign in.
- Requests that change data need a same-site header, which blocks cross-site request forgery.
- Per-IP rate limits, limits on repository size and scan time, and plan quotas.
- The admin area sits behind a separate Cloudflare Access login.
- Server errors and crashes are reported to the team by email within 15 minutes.
- Every change runs the full test suite in CI.
Compliance
- We process little personal data and keep it in the EU. We follow the GDPR, Qatar's Personal Data Privacy Protection Law (Law No. 13 of 2016) and Türkiye's KVKK (Law No. 6698): data is used only to run the service, kept for the periods above, and deleted on request.
- dagsec does not yet hold a SOC 2 or ISO 27001 certification. We answer security questionnaires on request.
- Business customers can sign a data processing agreement (DPA) covering the processing described on this page. Ask at hello@dagsec.net.
Reporting a vulnerability
Write to hello@dagsec.net with the details. We reply within two business days and don't take legal action against good-faith research. Contact details are also in security.txt.