Legal

Cookies are small text files placed on your device when you visit a website. Similar technologies include local storage and session storage, which a browser uses to keep information for a site. Cookies may be “first-party” (set by the site you are visiting) or “third-party” (set by another domain), and “session” (deleted when you close your browser) or “persistent” (kept until they expire or you delete them).

We use the cookies and storage needed to operate our website and application, plus two advertising tags — the Meta pixel on the marketing website and a Google Ads tag on the sign-up, sign-in and install pages of the web application — which have their own section below. The categories below describe how we use them. We do not maintain a fabricated cookie inventory; the descriptions reflect actual current usage.

Strictly necessary

These are required for the website and application to function and cannot be switched off in our systems. In the ChargePilot web application, we use essential cookies and local storage to keep you signed in, maintain your session, and provide secure authentication. On the marketing website, strictly necessary cookies are limited to infrastructure cookies that our hosting provider (Vercel) may set for security and reliable delivery.

Preferences

Where applicable, we use local storage to remember choices you make (such as interface preferences) so we can provide a more consistent experience.

Analytics / statistics

We do not load third-party analytics or statistics scripts on our marketing website. The one third-party script we do load is the Meta pixel, described in section 3; our website’s content-security policy allows that script and no other third-party script.

Marketing / advertising

We use two advertising technologies, described in section 3: the Meta pixel on our marketing website and a Google Ads tag on the sign-up, sign-in and install pages of the web application. They set the advertising cookies _fbp and _gcl_au and send Meta and Google page views — and, for the pixel, the button clicks listed there — so that each can tell us whether our ads led to them, and so that Google can show our ads again to people who reached those pages. We treat this as “sharing” personal information for cross-context behavioral advertising under California law; the Global Privacy Control signal is your opt-out for both, and we honor it (section 4). We do not sell personal information.

Our marketing website (chargepilot.ai) loads the Meta pixel, a small script from Meta Platforms, Inc. Five pages of the ChargePilot web application at app.chargepilot.ai — /install, /shopify/install, /login, /signup and /stripe-install — load a Google Ads tag (AW-17919321174), a script from Google LLC. The pixel is not loaded in the application, the Google tag is not loaded on any other page of it, and neither is loaded at all if your browser sends the Global Privacy Control signal.

The Meta pixel — what it collects

A cookie named _fbp, set by the pixel on our domain, which identifies your browser to Meta. The pages you view on the website, including their titles. Whether you click five specific buttons: Get Started, See How It Works, Install on Stripe, Install on Shopify, and the Download on the App Store badge. With each of these, Meta also receives your IP address and browser details, as with any request made to Meta. We never send it your name, email address, or account details, and it sees nothing from inside the ChargePilot application.

The Google Ads tag — what it collects

A cookie named _gcl_au, set by the tag on the app.chargepilot.ai domain, which lets Google connect a page load to an ad click. The page you loaded, including its title. With each of these, Google also receives your IP address and browser details, as with any request made to Google. We never send it your name, email address, or account details, and it is loaded only on those five pages, never on the dashboard.

What they are for

Advertising measurement. The pixel tells us whether our ads on Meta’s platforms led to those visits and clicks. The Google tag tells us whether our Google ads led to a sign-up or install, and lets Google show our ads again to people who reached those pages (remarketing). Meta and Google also process this data under their own privacy policies.

Global Privacy Control

If your browser sends the Global Privacy Control signal, neither tag runs: no _fbp or _gcl_au cookie is set and nothing is sent to Meta or Google from our pages. Most browsers and privacy extensions let you turn this signal on.

Our website does not present a cookie-consent banner. The only cookies we set that are not needed to run the site or the application are the two advertising cookies in section 3 — _fbp on the website and _gcl_au on the application’s sign-up, sign-in and install pages; turning on the Global Privacy Control signal in your browser stops both tags entirely. You can also control cookies through your browser settings — most browsers let you block or delete cookies and clear local storage. Blocking strictly necessary cookies may prevent parts of the application, including sign-in, from working.

We honor the Global Privacy Control (GPC) and similar browser opt-out signals as a request to opt out of any “sale” or “sharing” of personal information where applicable: when your browser sends the signal, neither the Meta pixel nor the Google Ads tag runs and nothing is shared with Meta or Google. As described in our Privacy Policy, ChargePilot does not sell personal data. If we introduce any other non-essential or third-party cookies, we will update this Policy and add any consent mechanism required by law before those cookies are set.

We may update this Cookie Policy from time to time and will revise the “Last updated” date when we do. Questions can be sent to privacy@chargepilot.ai.