Privacy Policy — Suricode

Privacy Policy

What we keep.

This page says what Suricode stores so it can check your code and show you the results.

Your account

We store the email you sign in with and the name you give us. Sign-in uses a code we send to that email. There is no password.

The app keeps you signed in with a session cookie on app.suricode.ai. A separate signed-in flag on suricode.ai lets this site show Open the app instead of Start free.

The home page has a dark design and a light design, both at this site’s address. With no choice from you, this site follows the light or dark setting on your device. If you pick one, a cookie on suricode.ai loads that design next time.

Your projects

We store the repositories you connect: name, clone address, and the branch we check. For GitHub, Bitbucket, and Origin we keep the read-only connection that lets us list and clone. For a git address we keep the token or SSH key you gave us so we can clone again. If an Origin namespace only accepts clones from certain network addresses, those addresses have to include Suricode or the check cannot read the repository.

Each check fetches a private working copy onto our scanner. Tools and an AI reviewer read that copy to judge which findings are real. Nobody else has access to it.

Findings and keys

We store the findings, the plain explanations, scores, and the history of scans. If you create an agent key, we store a hash of it so the MCP server can recognise it. We show the secret once.

Mail

We email sign-in codes and, if you leave weekly mail on, a summary of what changed. We send mail through our mail provider.

Why we keep it

We use this data to run Suricode: to sign you in, to check the projects you added, and to show you the results. We do not sell it.

How the app is used

When you are signed in to the app, we may record which pages you open and what you click, so we can see where Suricode is hard to use. That can include click maps and, when we turn it on, a replay of the session. Form fields are hidden in a replay. Pages that show findings, source code, keys, or an agent prompt hide that text as well. A click is stored as which control it was, not the words on the page.

We tie that record to the id of your account. We do not send your email address with it unless we turn that on. If your browser sends Do Not Track, or Global Privacy Control, we do not load the click maps or the replay. The app looks for a cookie named suricode_analytics. Set it to 0 and the recording stays off. If we add a cookie notice, it uses that same switch.

We use PostHog for this, on their EU cloud or on a server we run. The marketing site does not use it. We also count that a repository was connected and that a scan started, finished, or failed. Those counts use the same account id, with no code and no findings. They are kept even when the browser asks not to be tracked, because they describe the check itself.

Ads

If you click Start free, we send Reddit Ads a click event. If you then add your email or enter the code on the app, we send those steps too, so we can tell which ads led to a sign-up. We do not send Reddit your email. We also load the Google tag on this site and the app so we can measure visits and ads. We do not send your email to Google from our pages. We load the Meta Pixel on this site and the app. It records a page view. When an account is created, the app records a Lead, and our server sends Meta the same event with a hash of the email address, not the address itself. The first page you land on can store advertising tags (UTM, gclid, fbclid) and the referring site for 30 days, and we save them on your account when you register so we can see which ads and sites brought you here.

Contact

Questions about this policy: hello@suricode.ai.