Corveil
CorvusWorkforceBuilderGovernance
Use CasesTry CorveilCompany
Log In ↗
Use CasesTry CorveilCompany
Try Corveil

Platform

CorvusWorkforceBuilderGovernance

Account

Log In ↗

Website

Privacy Policy

How this website handles visitor data.

Last updated: November 21, 2026

01

Scope

This policy covers corveil.com — the marketing website you are reading right now. That includes our documentation at /docs, which is built separately from the main site and loads a different set of third-party resources. Where they differ, this policy says so.

It does not describe the Corveil gateway product. Corveil is deployed inside your own environment or as managed SaaS, and the analytics described below are not part of it — the product does not load Google Analytics. For how the product handles customer data, including its subprocessors, see the Trust Center.

02

Website Analytics

We use Google Analytics 4 to measure how this website is used.

This site loads Google Analytics 4 (measurement ID G-2MHZK8EQLN) on the marketing pages: the rebuilt public pages (/, /corvus, /getting-started, and the rest of the product site), our campaign pages under /c/, this policy, and the Trust Center. We use it to understand which pages are working. We do not sell visitor data.

Our documentation at /docs does not load Google Analytics. It loads no external resources at all.

What Is SentWhenData Processed
Page viewsOn each marketing page you openThe page viewed and your navigation within the site, the referring URL, approximate location derived from your IP address, and device/browser characteristics reported by your browser.
Form submissionsWhen you submit the Try Corveil formAn event recording that a submission happened (waitlist_signup) and which page it came from. Your email address is not sent to Google.
Campaign page interactionsOn a campaign page under /c/, when it opens and as you use itEvents named campaign_view (the page opened), cta_click (a button was clicked, and which), plan_click (a plan was picked, and which), sim_used (an interactive demo was used), quiz_complete (a quiz was finished, with its score and tier, but not your answers), video_play (a video was started), form_start (you started filling in the signup form, and which form), lead_submit (the signup form was sent, with the plan picked), and details_submit (you sent the optional follow-up questions after signing up, and which form). Each carries the campaign’s name. Your email address and anything else you type are not sent to Google.
Tool-Call X-rayOn /x-ray, when it opens, when a scan finishes and as you use the resultsThe transcripts you pick are read and analyzed by your browser. They are never uploaded, stored or sent to us or to Google. Besides the page views described above, the page’s events record only that it was used and which of its buttons were clicked. The page sends the same campaign_view and cta_click events as a campaign page, plus sim_used (a scan finished), patch_copy and patch_download (you copied or downloaded the generated patch, and which one), ticket_copy (you copied a finding as a ticket), report_download (you downloaded the full report) and results_clear (you cleared the results). If you sign up, it sends the same form_start, lead_submit and details_submit events as a campaign page. None of these events carries anything about your files or results: no counts or totals, no coding agent, category or finding, and no secret or personal data, nor its type. No file names, folder or project names, commands or transcript text are sent. The report itself is built in your browser and saved to your device; it is not sent to us or to Google.

Loading Google Analytics means your browser contacts Google-operated hosts. The following are permitted by this site’s Content Security Policy for analytics:

  • www.googletagmanager.com
  • www.google-analytics.com
  • region1.google-analytics.com
  • analytics.google.com
  • www.google.com
  • stats.g.doubleclick.net

One of these, stats.g.doubleclick.net, belongs to Google’s advertising network rather than its measurement infrastructure. Your browser contacts it when Google Analytics’ advertising features are enabled on our property. The opt-out and blocking options below apply to it as they do to the rest.

Google processes this data as described in Google’s Privacy Policy. You can opt out of Google Analytics across all sites by installing the Google Analytics Opt-out Browser Add-on, or by blocking the hosts listed above with your browser or an extension. Blocking them does not affect your ability to use this website.

03

Fonts & Other Third-Party Content

Requests your browser makes to other companies while loading this site.

Google Fonts. The marketing pages load a stylesheet from fonts.googleapis.com and font files from fonts.gstatic.com. Both are operated by Google and are separate from Google Analytics: they receive your IP address and browser user agent when the page loads, before you interact with anything, and blocking Analytics does not stop them. This data is handled under Google’s Privacy Policy. Our documentation at /docs serves its fonts from our own servers and makes no request to Google.

Video. Videos on this site are served from our own servers. We do not currently embed a third-party video player, so no video provider receives your data.

Links to other sites. Some pages link out to services we do not run — for example, our demo booking page is hosted by Google Calendar. Those sites receive your data only if you choose to follow the link, and their own privacy policies apply once you do.

04

Information You Submit

What we store when you use a form on this site.

The Try Corveil form at /getting-started asks for your email address, name, and company. The signup form on a campaign page under /c/ asks for your email address, and may ask for your name, your company, and a few questions about your team. The Tool-Call X-ray at /x-ray asks for your email address before you download its full report or when you ask us to set up its daily team version, and may then ask for your company and whether you would like us to set up the daily team version. If you ran a scan, it also offers to include your scan summary with your signup; that is off unless you tick the box. When you submit any of these, we record the following:

DataWhy We Collect It
Email addressTo reply to you. For the Try Corveil form, also so the product waitlist on corveil.io has the same details.
Name and companySo we can consider the request. For the Try Corveil form, also so the product waitlist on corveil.io has the same details.
Which form you usedTo know whether the submission came from the Try Corveil page or a campaign page, and which campaign.
The plan you picked (campaign pages)To know which offer interested you.
Link details (campaign pages): the utm_source, utm_medium, utm_campaign, and utm_content values and the ref value in the address of the page, if presentTo know which ad, post, or email brought you to the page. A ref value identifies the email we sent you, so your signup can be matched to that conversation.
Your answers (campaign pages with a quiz, calculator, or application form, and the optional questions some campaign pages ask after you sign up)To follow up with what is relevant to you. Answers to the follow-up questions are added to your signup.
Which you signed up for: the full report or setting up the daily team version (Tool-Call X-ray signup only)To follow up with what you asked for.
Your scan summary, only if you choose to include it (Tool-Call X-ray signup only)To follow up with what is relevant to you. It is sent only if you tick “Include my scan summary” when you sign up, and the page shows you the values first. It holds rounded figures: which coding agent wrote the transcripts, how many files were scanned, the share and dollar amount found avoidable, the largest category, the team size you entered, and how many secrets, secret files or pieces of personal data were found, each as a range or a category. None of it is sent to Google. Without it, we receive your email and which you signed up for, and nothing from the scan. Either way, we do not receive your transcripts, the report, file, folder or project names, commands, findings, or any secret.
Submission timeTo order and de-duplicate submissions.

Form submissions are handled on our behalf by our internal customer relationship management system, which records your submission so we can follow up; by WorkOS, which holds the signup waitlist that gates access to the product at corveil.io and sends you the waitlist confirmation (Try Corveil submissions only; campaign page and Tool-Call X-ray signups are not sent to WorkOS); and by Resend, which notifies our team of the submission. Our customer relationship management system may in turn post a notification of your submission, including your email address, to our internal Slack workspace. We pass on the fields you typed (email, name, and company) plus which form you used and the submission time, and for a campaign page or the Tool-Call X-ray the details listed above. We do not store a copy of the submission on this website’s servers, and we do not sell this information or share it with advertisers.

Pre-orders. Some campaign pages offer a pre-order button. It takes you to a checkout page run by Stripe, which collects your payment details under its own privacy policy. We receive the contact details you enter at checkout, such as your name and email address, and whether the payment went through; we never see your full card number. Nothing from Stripe is loaded until you click the button.

How long we keep it. This website does not keep a local file of form submissions. WorkOS, our customer relationship management system, and the internal notification email retain what they receive under their own retention. If you want your information deleted, ask us using the address below and we will act on the request with those processors.

05

Cookies & Local Storage

On the marketing pages, Google Analytics sets two cookies to distinguish visitors and sessions: _ga and _ga_2MHZK8EQLN, each with roughly a two-year expiry. Blocking Analytics or installing the opt-out add-on prevents further collection but does not delete cookies already stored in your browser — you can clear those through your browser settings. Google describes both in its Analytics cookie usage documentation. We set no advertising cookies of our own. Google Fonts only serves static assets and does not set cookies through this site.

This site also uses your browser’s local storage for the two items below. Neither holds your email address or anything you typed, neither is transmitted to us, and both can be cleared through your browser settings:

  • vitepress-theme-appearance — on the documentation pages at /docs, remembers whether you chose the light or dark theme.
  • rookery-kit — on the Rookery campaign page at /c/rookery, remembers that you signed up from this browser, so the setup kit download is shown again when you come back.

06

Your Choices

  • Analytics: opt out using the browser add-on or host blocking described above. The site works normally either way.
  • Fonts: blocking Analytics does not stop the Google Fonts requests. You can block fonts.googleapis.com and fonts.gstatic.com separately; pages stay readable and fall back to your system fonts.
  • Forms: submitting a form is entirely optional — you can read every page on this site without giving us any information.
  • Access or deletion: to ask what we hold about you, or to have it deleted, email us at the address below and we will act on the request.

Privacy Questions

Questions about this policy, or requests to access or delete information we hold about you.

security@corveil.com
Corveil

Platform

CorvusWorkforceBuilderGovernance

Resources

Use CasesTry CorveilDocs

Company

CompanyTrust CenterPrivacy

© 2026 Corveil