AgenticCLISign in

Privacy Policy

Last updated: 2026-11-05

agenticcli.dev (“we”, “us”, “our”) makes ShipGuard — a CLI release gate for AI-built apps distributed on npm. This policy explains what data we collect, why, and how to exercise your rights. Questions: [email protected].

Your code never leaves your machine. ShipGuard scans run locally. No file contents, file paths, or source code are ever uploaded — not on the free tier and not on paid plans. A signed-in CLI downloads the rulebook from us on every plan; your code stays local. The full list of what the CLI sends is in the network-call table.

Data we collect

Account data. When you create an account, WorkOS AuthKit collects and manages your email address and authentication credentials on our behalf. We receive a user identifier and email from WorkOS after successful sign-in.

Email preferences. If you tick “Send me the top security alerts for AI-built apps” on your dashboard or in Settings, we store that choice in our application database (Convex) with the date and where you made it, and we store the date when you switch it off. You can switch it off in Settings any time.

Waitlist data. If you join our waitlist, we store your email address in our application database (Convex) to notify you when access is available. We do not share waitlist emails with third parties.

Usage and analytics data (website). We use PostHog, our analytics processor, to understand how the website is used. What it does depends on your choice on the cookie banner (the banner controls PostHog only, not Google Analytics below):

Google Analytics (every visit to our public pages). We also use Google Analytics 4 to count visits and see which pages are read. It runs on every visit to our public pages, for every visitor, whatever you choose on the cookie banner and even if your browser sends Do Not Track or Global Privacy Control. It records the pages you view, the page or site you came from, your browser and device type, and an approximate location that Google works out from your IP address, using _ga cookies with a random id. Google processes this data for us as our processor, and says Google Analytics 4 does not log or store IP addresses. Google signals and ad personalisation are switched off. It never runs on the dashboard, sign-in or CLI login pages. You can opt out with Google's Google Analytics Opt-out Browser Add-on. Like everything else on this page, it never sees your source code.

We do not sell or share this data with advertisers. See our Cookie Policy for the mechanics.

Product events for signed-in accounts. If you have an account, we record what you do in the product — signing in, checkout, purchases, CLI login and scans — as part of running the service. This does not depend on the cookie banner. These events go to PostHog, named here as our processor. We do not send your email address or name to PostHog; events are tied to an internal account id.

Billing and payment data. Payment processing is handled by Dodo Payments as merchant of record. We do not store or receive your full card number or CVV. We receive subscription status, plan tier, and billing cycle information from Dodo Payments.

Local CLI scans and CLI usage ping. Your code never leaves your machine. When you run shipguard scan, your source code is read and analysed entirely on your machine; no file contents, file paths or code are sent. Published builds (0.10.0 and later) send three kinds of small pseudonymous usage ping: one after each scan, one the first time ShipGuard runs on an install (never in CI), and one after a successful shipguard login. A ping carries a random ping id, a random install id (none in CI), the CLI version, whether the build is published or a dev build, and a CI true/false flag; a scan ping also carries the verdict, a coarse duration range, which coding agent runs it (or none), whether the output is a terminal, and the output kind (json, human or sarif). From version 0.12, pings go to agenticcli.dev. An optional traffic label (“test” or “internal”) is added only if you set SHIPGUARD_TRAFFIC to one of those values, to keep your own testing apart from real usage; any other value is ignored. It never carries file contents, file paths, repo names, branches, commits, secrets or your identity. Any one of these turns off all three kinds: SHIPGUARD_TELEMETRY=0 or DO_NOT_TRACK=1 or shipguard telemetry disable, or telemetry: { enabled: false } in your policy file. The install id is random and is not linked to your account. Pseudonymous means it is not your name, but it is still one id per install, so we treat it as personal data and you can ask us to delete it.

How we use your data

We do not sell your data to third parties, use it for advertising, or use scan results for model training.

Sub-processors

The following third parties process data on our behalf:

Cookies

We use a strictly-necessary cookie for authentication (WorkOS session) and a first-party consent cookie that records your analytics choice. If you accept, PostHog also stores a random id in your browser's local storage; if you decline, it stores nothing. Google Analytics sets _ga cookies on every visit to our public pages, whatever you choose on the banner. See our Cookie Policy for details and opt-out instructions.

Sign-in helper cookies. After you sign in we set sg_seen (value 1, HttpOnly, one year) so the sign-in page can say “Welcome back”. When you start signing in we set sg_rt (the page you were heading to, HttpOnly, 10 minutes, sent only to the sign-in callback) so we can bring you back if sign-in fails. Neither holds your name, email or any personal data.

Data retention

Session recordings are kept for 30 days. Our own copy of analytics data, used for reports, is kept for 400 days and then deleted. PostHog keeps event data for the period set by our PostHog plan, until we delete it. Google Analytics keeps data for the period set in our Google Analytics settings. To have your account events or your CLI install id deleted sooner, email us.

We retain account data for as long as your account is active. If you delete your account, we will delete or anonymise your personal data within 30 days, except where we are required by law to retain it longer. Waitlist data is deleted once you convert to an account or on request.

Your rights

Depending on where you are located, you may have the right to:

To exercise any of these rights, email [email protected]. We will respond within 30 days.

Security

We apply reasonable technical and organisational measures to protect the personal data we hold. Sensitive operations (authentication, billing) are delegated to specialist sub-processors. However, no transmission over the internet is completely secure, and we cannot guarantee absolute security. If you believe your data has been compromised, contact [email protected] promptly.

Children

ShipGuard is intended for developers aged 13 and over. We do not knowingly collect personal data from children under 13. If you believe a child under 13 has provided us with personal data, please contact us and we will delete it promptly.

Governing law

This policy is governed by applicable law in the jurisdiction where agenticcli.dev operates. Where applicable, GDPR (EU/EEA users) and CCPA (California residents) also apply.

Changes to this policy

We may update this policy as our practices evolve. Material changes will be noted on this page with an updated “Last updated” date. Continued use of the service after changes constitutes acceptance of the updated policy.

Questions? Email [email protected].