Skip to content

Cookie Policy

This is the current version.

This Cookie Policy covers postcat.ai, the website of PostCat AI LLC ("PostCat AI", "we"): the cookies and similar browser storage it uses, what the cookie banner does, and how to block them. What we collect, and why, is in the Privacy Policy.

What we use

Some names below sit in local storage or session storage, not in a cookie. What sits in local storage stays until you clear it. We use no advertising cookies.

NameSet by, and what forWhere, and for how long
ph_<project key>_posthogPostHog: a random id for your browser, the id of the current visit, and your first page here with the site that sent youA cookie for postcat.ai and its subdomains, kept up to a year after your last visit, with a copy in local storage
Other names that start with ph_PostHog: working data for the current visit and tabLocal storage, and session storage until you close the tab
__ph_opt_in_out_<project key>PostHog: whether it may capture in this browserLocal storage
cookie_consentOur banner: that you answered it, so it asks only onceLocal storage
NEXT_LOCALEOur site: the language you read in, when it differs from your browser's, so the site keeps opening in itA cookie for this website, until your browser session ends
Names that start with crisp-clientCrisp, on our support page only: your chat session, so a conversation does not start over on every pageA cookie for postcat.ai and its subdomains, up to 6 months after your last visit
postcat:landing-utmOur waitlist: the campaign tags of the page you first opened, so a waitlist entry says which campaign brought youSession storage, until you close the tab

The project key is our PostHog project's public key. PostHog uses the id in its cookie to record the pages you open and leave, the links and buttons you press, and events such as a press on Start Free Trial. PostHog also records visits: the pages, scrolling, clicks and pointer movement, with what you type into fields hidden, kept for 30 days. Your browser sends these to PostHog's servers in the United States through an address of our own on postcat.ai.

Vercel, our host, counts visits and page speed with Vercel Web Analytics and Speed Insights. Neither sets a cookie: Vercel says it tells visitors apart by a hash of each request and discards it after 24 hours (vercel.com/docs/analytics/privacy-policy).

  • PostHog starts first. As the page loads, it sets its cookie and records the page view, before the banner appears.
  • The banner follows about a second later, as a small card at the bottom left. It closes through either of its buttons and then does not come back in this browser. Until you press one, it comes back on every visit.
  • Your answer stays in this browser, not in your other browsers or devices.
  • Wide screens only. In a window narrower than 640 pixels, as on a phone held upright, the banner does not appear, and PostHog runs all the same.
  • No storage, no banner. If your browser blocks local storage for the site, the banner stays hidden: it could not keep your answer.

What we do not use

  • No ad or retargeting tags, such as the LinkedIn Insight Tag, the Meta Pixel or Google's ad and analytics tags.
  • No heatmaps on postcat.ai.
  • We neither sell what these cookies collect nor share it with advertisers.

Other sites your browser contacts

  • Iconify. Your browser fetches the icons on our pages from api.iconify.design, a public icon service, or from its spare addresses api.simplesvg.com and api.unisvg.com. Each request carries your IP address and shows that it comes from postcat.ai. No cookie is set.
  • Stripe, once paid plans open: you pay on Stripe's own checkout page, under Stripe's cookie rules.
  • Crisp, on the support page only: your browser loads the chat from client.crisp.chat, and what you write in it goes to Crisp, a company in France.
  • Nothing else. Fonts and pictures load from postcat.ai itself, and LinkedIn appears only as plain links.

The companies that handle personal data for PostCat AI are on the Subprocessors page.

Our script on our customers' sites

A company that uses PostCat AI can add our script to its own website, to see which LinkedIn posts bring sign-ups and payments. A click on a tracked link adds a short id to the page address, and the script keeps that id on the company's own domain for 90 days, so a later sign-up or payment is matched to the link. The script never ties a visit to anyone's LinkedIn account. With Session replays on, it also records those visits, hiding typed text by default and passwords and card numbers always.

The company decides how its website uses the script: we run it on the company's behalf. It must name PostCat AI in its privacy policy and cookie banner, and ask for consent where the law requires it. For visitors in the European Economic Area and the United Kingdom, the script waits for that consent. Questions about such a site go to that site first. Our part is in the Terms of Service and their Data Processing Addendum.

How to block cookies

  • In your browser. Block cookies and site data for postcat.ai. PostHog then keeps no id between your visits, though it still counts page views. A private window deletes everything when you close it.
  • Browser signals. Do Not Track and Global Privacy Control change nothing on the site today.

Changes

We update this page before adding a cookie or a service your browser contacts. Each version keeps its own dated address on this site.

Contact

Questions about cookies on postcat.ai: meow@postcat.ai.

· · Questions about this page: meow@postcat.ai