Cookie Notice
Effective July 29, 2026 · last updated July 29, 2026
Every page of this website except one sets no cookies at all, and our analytics are cookieless. The exception is the booking page, where the calendar is provided by Cal.com and sets Cal.com’s cookies. This notice says precisely where that happens, and what the application itself stores to keep you signed in.
The website
Browsing this site sets no cookies, stores nothing in your browser, and does not follow you anywhere else. That is true of every page except the booking page, which is covered in §3 and is the only exception on the site.
We carry no consent banner. On every other page there is genuinely nothing to consent to, and a banner asking permission we do not need would be theater. On the booking page there is one third-party embed, and rather than put a banner in front of the whole site for it, we describe it plainly below and give you a way to book without it.
Analytics are provided by Vercel Web Analytics, which is cookieless by design. It counts page views and a small number of interactions, such as which call to action was used. Visitors are counted using a hash derived from the request, which is discarded within 24 hours, and results are stored as aggregates rather than against a person or an IP address. There is no cross-site tracking, no advertising network, no marketing pixel, no session recording and no data broker, on this site or in the product.
What you type is never sent to analytics. When the contact form is submitted we record only whether it succeeded or failed. Your name, email, company and message go to us by email and nowhere else.
The booking calendar
The demonstration booking calendar is provided by Cal.com and runs inside our page as an embedded frame. It loads with the page, and when it does, Cal.com sets its own cookies in your browser. That happens on the booking page only, and only on that page. It does not happen anywhere else on this site.
We had this behind a button for a while, so that nothing from Cal.com ran until you asked for it. It was better for privacy and worse for everyone trying to book a call: the calendar takes a few seconds to appear, so the page looked broken. We removed the button and are telling you here instead.
If you would rather not load it at all, do not open the booking page. Email privacy@dmcpilot.com or use the contact form, which sets nothing, and we will arrange a time by email. Your browser's third-party cookie blocking will also stop it, and the rest of the site is unaffected either way.
The calendar operates under Cal.com's own privacy policy as well as ours, and the name, email and answers you give when booking go to Cal.com and to us so that we can hold the meeting. To arrange a time without using it, email privacy@dmcpilot.com and we will arrange a time directly.
We record that a booking happened, for analytics. We never record who made it.
The application
The platform at app.dmcpilot.com is different: signing in requires remembering that you are signed in. These are strictly necessary cookies, exempt from consent requirements, and there are no others.
| Purpose | What it is | Lifetime |
|---|---|---|
| Authentication | Session and refresh tokens issued by our authentication provider, which keep you signed in across page loads and are required for every authorized request | Until you sign out or the session expires |
| Two-factor state | Records that a second factor has been satisfied for the current session, so you are not challenged on every page | The session |
| Support access | Set only when a member of our support team is accessing an organization with authorization. It is bound to the signed-in administrator, and every use is written to an audit log that deleting an account cannot remove | The support session |
| Interface preferences | Small values remembering things like whether the sidebar is collapsed | Until cleared |
The product contains no analytics cookie, no advertising cookie and no third-party tracker. Error monitoring runs without one, and its payloads are scrubbed of identity, credentials, cookies and sensitive fields before leaving the application.
Your control
You can block or delete cookies in your browser settings. Blocking them on the website costs you nothing, because it sets none. Blocking them for the application will prevent you from signing in, since the authentication cookies are what a signed-in session consists of.
Changes
If we ever introduce a cookie that is not strictly necessary, we will ask for your consent before setting it and update this notice first. Questions: privacy@dmcpilot.com.
Questions about this document: legal@dmcpilot.com. Privacy requests: privacy@dmcpilot.com. Security reports: security@dmcpilot.com.