Privacy
Last updated 28 October 2026. Security and sub-processor details are on the Security page.
What we collect
- Your GitHub profile when you sign in: username, name, email address and avatar. We don't receive access to your repositories, and we don't keep the GitHub access token.
- Your answers about yourself, asked once after you sign in: what you do; if you study, your field, year and the areas you want to work in; otherwise the areas you work in and are strongest in and how long you've been writing software; and the languages you use most. We use them, counted together, to decide what to build, and you can change them in Settings.
- Autopilot on your computer (Team plan, desktop app) looks for git repositories in the folders you choose and analyses them on your computer. Their paths and results stay there; none of it is sent to us.
- Sign-in records: when you sign in and out, your IP address, the approximate location derived from it (country, region, city) and your browser and operating system. We use these to protect accounts, investigate abuse and show you where your account is signed in.
- Visits to dagsec.net, app.dagsec.net and docs.dagsec.net: the page, the site that linked to it, any campaign tags in the link, your IP address, the approximate location derived from it (country, region, city) and your browser, operating system and device type. We use these to understand how people find dagsec. No cookies are used for this, and these records are deleted after 30 days.
- Scans you start in the dashboard: the repository URL and the report.
- GitHub Action and GitLab CI runs: the repository or project name, time, and the runner's IP address and country, to apply your plan's limits.
- GitHub App scans: when you install the dagsec-security app, pull requests in the repositories you select are cloned to the dagsec server, scanned and deleted as soon as the scan ends. Only the report is kept: it goes to the pull request, not to our database.
- Package versions your repositories use, taken from the lockfiles of each scan, so we can email you when a new critical or high vulnerability affects one of them. Turn these alerts off on the Integrations page or with the link in any alert.
- Code Guard: the desktop app checks the code your AI agent writes on your computer. For each problem it finds or sees fixed, it sends us only the rule (such as
c-gets), the language, the AI tool and the time, for your Code Guard page. Never the code, file names or paths. Kept for 90 days. - Team audit log: for members of a team, the packages their AI agents tried to install, when, and whether dagsec allowed them. Only the team owner sees it; it's kept for 90 days.
- AI agent checks: the package names and versions your agent asks about, and install commands such as
npm install axiosseen by the Claude Code plugin. With the Cursor and Gemini CLI hooks, every shell command the agent runs is sent for checking, because those agents can't filter them first; commands that install nothing are ignored. Only the time, IP address and country of each check are stored, to apply your plan's limits; the packages and commands are not.
What we don't collect
- Your source code. The GitHub Action, GitLab CI, Code Guard and the AI agent plugins never upload it; the GitHub App and dashboard scans hold it only while a scan runs.
- Full secrets. Reports keep only a masked value such as
AKIA********. - Tracking or advertising cookies. The only cookie keeps you signed in.
- Personal data about visitors of this site who don't sign in. Visits are counted anonymously.
How long we keep it
- Sign-in records and Code Guard events: 90 days.
- Sessions: until you sign out, or 30 days.
- Action run records: 400 days, for usage and billing questions.
- Your account and scans: until you ask us to delete them.
- Database backups: 14 days, after which deleted data is gone from backups too.
Your rights
You can ask for a copy of your data, a correction, or deletion of your account at any time by writing to hello@dagsec.net. We don't sell personal data or share it with third parties except the infrastructure providers that run dagsec (Cloudflare, Hetzner, and Resend for alert emails) and Paddle, which processes payments for paid plans as our reseller. Paddle collects your billing details itself; dagsec never sees or stores your card number.