Cookie and Storage Policy

The difference between these things

These terms get used interchangeably, so to be precise about what actually happens:

• Cookies are small files sent back to a server with every request. Our own code sets none and never reads one. If you accept analytics, tags loaded through Google Tag Manager may set their own cookies; that is described below.
• Session storage lives in your browser, is readable only by pipeit.ai, is never transmitted automatically, and is erased when you close the tab.
• Local storage persists until it is explicitly cleared. We use it for exactly one thing: remembering your answer to the consent banner, so we do not ask again on every page. Nothing else, on either the website or the application.
• Third-party requests are resources your browser fetches from another domain. They are not storage, but they do reveal your IP address to that domain, so we list ours below.

Analytics, and how we ask

We use Google Tag Manager to load analytics so we can understand which pages are useful and where people get stuck. It is not on by default.

Until you press Accept on the consent banner, the Google Tag Manager container is never requested, no dataLayer is created, and no Google cookie is set. Declining is a single click, the same size and in the same place as accepting. Closing or ignoring the banner counts as a refusal, and nothing loads. We record only your decision, and we do not ask again unless this policy changes materially.

We do not load Meta Pixel, the LinkedIn Insight Tag, advertising pixels or session recording tools. We do not set cookies for advertising, we do not build behavioural profiles, and we do not sell or share browsing behaviour with advertising networks.

Change your cookie choice

What we do store

Your consent choice (local storage, first-party)

When you answer the consent banner we store your decision in your browser's local storage under the key pipeit_consent, together with the date and the version of this policy you were shown. This is what stops us asking on every page, and it is the record that proves we honoured your answer. It is strictly necessary for the consent mechanism itself, so it is set whether you accept or decline. It contains no identifier and is readable only by pipeit.ai. Clearing it makes the banner reappear.

Analytics (only if you accept)

If, and only if, you accept, we load Google Tag Manager from www.googletagmanager.com and the tags inside it may set their own cookies to measure page views and navigation. These are set by Google, not by us. If you decline, none of this happens. If you accept and later change your mind using the button above, we clear your decision and reload the page so the container is no longer running; you may also want to clear cookies for pipeit.ai to remove any Google cookies already set.

Campaign attribution (session storage, first-party)

If you arrive through a link that carries campaign parameters (for example utm_source or utm_campaign), we keep those parameters in your browser's session storage under the key pipeit_attr. This lets us record how you found us if you join the waitlist on a later page. It is cleared automatically when you close the tab, it is readable only by pipeit.ai, and it is never used to follow you across other websites.

Pipeit application storage (the product, not this website)

The Pipeit application at /prototype/ is access-controlled and stores a small amount of data in your browser so the app works:

• pipeit_auth (session storage) - records that you have signed in, so you are not asked again on every page. Cleared when you close the tab or sign out.
• pipeit_demo_mode (session storage) - records that you are in the demo workspace, which uses fictional data and blocks writes to external systems.
• pipeit_analysis_cache (session storage) - caches analysis results so the app does not repeat the same work within a session. Cleared when you close the tab.

All three are session storage, cleared automatically when you close the tab. The application sets no cookies and no local storage of its own. These entries are strictly necessary for the application to function; blocking them means the product will not work.

Cookies set by our infrastructure

This website is delivered through Cloudflare. Cloudflare may set strictly necessary cookies for security and bot protection when it needs to verify that a request is legitimate. These are set by the delivery layer rather than by us, they are not used for advertising or profiling, and we do not read them.

Third-party requests

These are the only domains outside pipeit.ai that this website contacts:

• Google Fonts (fonts.googleapis.com, fonts.gstatic.com) - loads the Inter typeface on every page. Google does not set cookies through this font service, but the request itself, including your IP address, is visible to Google. Browser extensions that block third-party font loading will not break the site.
• Our own backend (pipeority-production.up.railway.app) - contacted only at the moment you submit the waitlist form, and only to deliver what you typed. Nothing is sent in the background.
• Google Tag Manager (www.googletagmanager.com, and the analytics endpoints it loads) - only if you accept analytics. If you decline, or have not answered, this request is never made and Google never sees your visit.

No other external domain is contacted. No advertising, avatar, embed or widget service is loaded on any page.

How to control browser storage

The quickest way to change your analytics decision is the button above. Beyond that, every major browser lets you view, block and clear cookies and site storage from its settings. Clearing storage for pipeit.ai will remove everything described above, including your consent record, so the banner will ask you again. Blocking storage will not prevent you from reading this website, but it will prevent the Pipeit application from working, it will mean we cannot record how you found us, and it will mean we cannot remember that you declined.

Changes

If we start using anything that is not strictly necessary and not already described here, we will update this page and ask for consent before those tools load. If the change is material we will bump the consent version, which asks everyone again rather than assuming an old answer still applies.

Last updated: 22 August 2026. Questions: [email protected]. See also our Privacy Policy.