Skip to content

Privacy Policy

This is the current version.

This Privacy Policy explains what personal data PostCat AI LLC ("PostCat AI", "we", "us") collects, why we use it, who receives it, how long we keep it and what you can ask of us. It covers people who visit postcat.ai or join its waitlist, people who use the PostCat AI app, people whose LinkedIn account is connected to a workspace, Brand Ambassadors, and anyone who writes to us.

A company uses PostCat AI through its workspace. For account, billing, website, app usage, security and support data we decide how the data is used, so we are its controller. What a company puts into its workspace or receives in it, such as what LinkedIn returns for its connected accounts, what its own website sends us and what we read from its payment account about its visitors and buyers, and its Session replays, we process for that company and on its instructions, under the Data Processing Addendum, which is part of our Terms of Service. For that data the company is the controller, and its own privacy policy applies as well.

Who we are

PostCat AI LLC is a limited liability company in the United States. For anything in this policy, write to meow@postcat.ai.

What we collect

Most of it you give us yourself. To have an account you need a name and an email address; everything else you choose to add. Some of it comes from others: from LinkedIn through Zernio, from Google or LinkedIn when you sign in with them, from the company that invited you, and from a company's own website.

Your account

  • Your name, work email, photo, company and role in the workspace (owner, admin, member or guest).
  • How you sign in. If you continue with Google or LinkedIn, that provider sends us your name, email address and photo. We never ask for your LinkedIn password.
  • Your settings, such as notifications, language and appearance.
  • A record of what you agreed to: which versions of the Terms of Service and the Refund Policy you accepted, which version of this policy you were shown, when, and from which IP address and browser. It is our proof of the agreement if a payment is disputed.

Signing in with Google

If you sign in with Google, Google sends us your name, email address and profile photo, and nothing else from your Google account: we ask for no access to your Gmail, Drive, Calendar or contacts. We use them only to create and run your account: to sign you in, to show your name and photo in your workspace and to send you the emails the service needs. We keep them with your account and delete them with it, as How long we keep it describes. We do not sell them, use them for advertising or share them with anyone except the companies that run PostCat AI for us. PostCat AI's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

The waitlist

Until accounts open, you can join the waitlist on postcat.ai. We then receive your email address and the address of your LinkedIn profile; if you answer them, whether your company has paying customers and how big your team is; the page you joined from and the campaign tags in its address; and the IP address you joined from, the country and city it points to and your browser. Your entry arrives in our team's Slack, and in PostHog your email becomes the id of your visits to postcat.ai. We use it to tell you when your account can open and to learn which companies want PostCat AI.

Your workspace

  • What your team writes and uploads: briefs, chats with the agents, drafts, posts, replies to comments, tasks, calendar entries, routines, files and images.
  • What shapes each voice and the brand: posts and screenshots you paste, your company's logo, colors, fonts, facts and links, and what we read from your company's own website when you ask us to.
  • Your own LinkedIn data archive, if you choose to give it to us. We keep only its posts and your profile, and delete the rest of it once read, since the archive also holds your connections and messages.

LinkedIn

What LinkedIn's official API returns for each connected profile and company page: see Data from LinkedIn.

Payments

Stripe runs checkout and invoices and keeps the card details. We never see or store the full card number. We keep the plan, the amount, date and status of each payment, the billing contact, the company's name, address and tax number, and the id Stripe gives the customer.

Brand Ambassadors

If a company invites you as a Brand Ambassador: your name, email and connected LinkedIn account; your bank details for payouts, stored encrypted, with only their last 4 digits shown in the app; the tax details your invoices need; and your commissions, earnings and the invoices made in your name. The company that invited you sees your agent's chat, your posts, the comments under them and your earnings, as it would for its own employee, and you can see who reads your chat. For this data the company that invited you is the controller, and we process it for that company under the Data Processing Addendum; your own account, sign-in and the record of what you accepted are ours.

A connected revenue account

A workspace can connect its own Stripe, Polar or Dodo Payments account with a read-only key. We then read its payments, subscriptions and refunds to show revenue, count commissions and fill in revenue templates. A read-only key cannot move money, and we never ask for one that can.

Your customers' data

When a workspace adds the PostCat AI script to its own website: clicks on its tracked links, and the sign-ups and payments its site reports, as Tracked links and your customers' data and Session replays explain.

Messages to us

What you write to meow@postcat.ai or in the chat on our support page, and anything you attach. Our mailbox runs on Google Workspace, and the chat on Crisp, which also receives your IP address and browser and keeps a cookie so the conversation stays open from page to page.

Using the website and the app

Pages and screens opened, buttons pressed, your IP address, browser, device and the rough location your IP address points to, and technical logs of requests, errors and sign-ins that keep the service running and safe. Analytics and cookies on postcat.ai has the details.

Data from LinkedIn

PostCat AI works with LinkedIn only through LinkedIn's official API. The connection runs through Zernio (Zernio Software SL, a company in Spain), which handles it for us as our processor. Each person connects their own account on LinkedIn's own screen and can disconnect it at any time. We never see a LinkedIn password, and the token LinkedIn issues stays with Zernio.

What LinkedIn returns:

  • For a person's profile: their name, photo, headline and profile address; the posts made or added through PostCat AI and their numbers, such as impressions, reach, reactions, comments, shares, saves and sends; their follower count; and the comments under their own posts, with each commenter's name and photo.
  • For a company page: its posts and their numbers, the comments under them with each commenter's name and photo, its description, totals of followers and page views, and follower demographics in aggregate.
  • From the company's own LinkedIn ad account: a boost's spend and results, and LinkedIn's audience estimates, for boosts and for Your market in Stats.

What we never do:

  • We never scrape LinkedIn, and we fetch nothing from it beyond what the official API returns for the accounts connected to a workspace.
  • We never turn the people who comment on or react to a post into a list, a lead or a CRM record, and we never export followers or commenters.
  • PostCat AI sends no LinkedIn messages.

Links to other people's posts, pasted by your team into Tasks or the team chat, are kept as the address only, without the author's name, photo or the post's text, apart from what the address itself shows: LinkedIn's usual share address contains the author's profile name.

Posts, replies and boosts go to LinkedIn only on the workspace's instructions. Nothing is published from a person's profile without their consent: they approve the post, name someone who approves for them, or turn on a setting that publishes for them. Once something is on LinkedIn, LinkedIn's own terms and privacy policy govern it.

How long we keep data from LinkedIn, within the limits LinkedIn sets for apps:

  • profile data of other LinkedIn members, such as the name and photo of someone who commented: up to 24 hours;
  • other members' posts and comments: up to 48 hours;
  • a connected company page's own posts: up to 6 months;
  • a connected company page's details, such as its description: up to 8 weeks;
  • company page reporting data, such as page analytics and follower numbers: up to 1 year;
  • ad account data, such as a boost's results and LinkedIn's audience estimates: up to 1 year.

When a profile is disconnected, Zernio deletes that account's analytics, and its numbers are removed from PostCat AI. If a workspace stops paying, we disconnect its LinkedIn accounts in Zernio 10 days after its tracked links switch to the postcat.ai home page, and erase the data that came from LinkedIn (When a payment fails).

Zernio keeps what it needs to publish and report under its own data processing agreement with us.

How we use AI

PostCat AI is an AI-powered service. Language models write drafts, rewrites, replies and chat answers, and image models make pictures and covers. AI can get things wrong, so read what it writes before you approve it (AI features).

A model receives only what its task needs: the brief, the profile's posts and voice, the brand's facts, the comment being answered or the numbers being explained. These requests go through Vercel's AI Gateway to Anthropic for text and to OpenAI for images. The gateway keeps no prompts or outputs once a request is done.

When a person connects a profile, we tell them that AI models work with its posts and data to do this work, and they confirm it. This rests on the legal bases in Why we use it, and it ends when the profile is disconnected. Neither we nor our AI providers train models on your data.

We make no decisions about you by automated means that have legal or similarly significant effects.

Why we use it

  • To run the service your company signed up for: accounts, workspaces, connected profiles, drafts, publishing with consent, numbers, tracked links and support. Legal basis: our contract with your company, and our legitimate interest in serving the people who use PostCat AI on its behalf.
  • To bill and keep accounts. Legal basis: our contract, and the tax and accounting laws we must follow.
  • To keep PostCat AI safe: to stop abuse, fraud and attacks, fix errors and enforce our Terms of Service. Legal basis: legitimate interests.
  • To make the product better from how it is used, through analytics and your feedback. Legal basis: legitimate interests. The Cookie Policy lists the cookies this uses on postcat.ai.
  • To run the waitlist: to tell you when your account can open and to learn which companies sign up. Legal basis: the steps you asked us to take before an account, and our legitimate interests.
  • To write to you: the emails the service needs, and product news. Legal basis: our contract for the service emails; for product news, our legitimate interests within the email marketing rules, and consent from people who did not sign up themselves.
  • To follow the law: keeping records, answering lawful requests from authorities and handling legal claims. Legal basis: legal obligation and legitimate interests.

For data we process for a company, that company sets the purposes, and we use the data only to provide PostCat AI to it and, as it instructs in the Data Processing Addendum, to make totals that identify no one.

We never sell personal data, and we never share it for advertising.

A workspace's tracked links run on PostCat AI's short domain or on the company's own domain. For everything in this section we work for that company, under the Data Processing Addendum.

  • A click records when it happened, which link it was, the country and city its IP address points to, the kind of device, and the site the person came from. It carries no name, but the law still treats it as personal data, because it can be linked to the person who later signs up.
  • The short id. A click adds a short id to the address of the company's site. The company's PostCat AI script keeps that id on the company's own domain for 90 days, so a sign-up or payment within 90 days of the first click is credited to the link.
  • Sign-ups and payments. When that person signs up or pays, the company's own site sends us the event: its own id for the person, their name and email, a photo if it sends one, and for a payment the amount and currency. We store what the site sends.
  • Consent. The company must name PostCat AI in its own privacy policy and cookie banner, and ask its visitors for consent where the law requires it. For visitors in the European Economic Area and the United Kingdom, the script waits for that consent before it stores the short id or records anything.
  • Never LinkedIn. We never match these people with LinkedIn members: no comment or reaction is linked to a visitor or a customer.
  • Who sees them. In the workspace, names, emails and amounts are shown to the owner, the admins and those given the right to see revenue. Other members, and Brand Ambassadors in their earnings, see only what their own posts brought, and other guests see no customer data.
  • While a workspace is unpaid, its links lead to the postcat.ai home page instead (When a payment fails). Such a visit is a visit to our own website.

Session replays

Session replays let a company watch visits to its own website by people who came through its tracked links. They run only when the company turns them on, and we record them for that company under the Data Processing Addendum. The consent rule in Tracked links and your customers' data applies to them too.

  • A replay shows the pages of one visit, with its scrolling, clicks and pointer movement.
  • What a visitor types is hidden by default, and the company may show chosen fields. Passwords and card numbers are always hidden. Text a page shows by itself, such as an email it repeats back, is recorded unless the company marks it hidden.
  • Recording runs up to and including sign-up, and stops once the visitor is signed in to the company's own app.
  • The visitor is shown without a name, such as "Someone in Germany", until they sign up on the company's site; after that the name comes from the company's own data. A replay never carries a LinkedIn identity.
  • Replays are kept for 180 days, or for less if the company sets a shorter time.
  • In the workspace, the owner, the admins and those given the right can watch all replays; other members only those from their own links; guests and Brand Ambassadors none.

Analytics and cookies on postcat.ai

  • PostHog counts page views and the buttons people press on postcat.ai. It keeps a random id in a cookie and in your browser's storage, so repeat visits from one browser count once. Each event carries your IP address, which PostHog stores and uses to work out a rough location. A visitor who has not signed up or joined the waitlist gets no profile in PostHog. Events reach PostHog's region in the United States through an address of our own on postcat.ai. In the app, the same analytics are tied to your account.
  • Recordings of visits. PostHog records visits to postcat.ai: the pages, scrolling, clicks and pointer movement, with what you type into fields hidden. We watch them to make the site better, and PostHog keeps them for 30 days.
  • Vercel hosts the site and keeps logs of the requests it serves. Vercel Web Analytics counts visits without cookies: it tells visits apart by a hash of the request and discards each visit's session after 24 hours. Vercel Speed Insights measures how fast pages load.
  • Iconify. Your browser loads the site's icons from Iconify's public servers (api.iconify.design), which receive your IP address and the address of the page that asked for them.
  • Cookies. The Cookie Policy lists each cookie and how long it lasts. You can block or delete cookies in your browser's settings.
  • The free tools run in your browser. What you open in them is not uploaded anywhere, and an event only says that a tool was used or a file was opened. A recording of the visit can show what a tool displays, with what you type into fields hidden.
  • The Enterprise form opens a prepared email in your own mail app. Nothing reaches us until you send it.

Public totals

Once accounts open, the footer of postcat.ai may show running totals across all customers: how many impressions posts made with PostCat AI received, how many clicks their links got, and how much customers earned through them. They are sums that point to no one. We never show a single customer's numbers.

Who we share it with

  • Companies that run parts of PostCat AI for us: Vercel for hosting and the AI Gateway, Zernio for LinkedIn, Anthropic and OpenAI for AI, Stripe for payments, PostHog for analytics, Google Workspace for our mailbox, Crisp for the support chat, Slack for our team's messages, where waitlist entries arrive, and the providers of our database and of our emails. Each one may use the data only to do that job for us, under a contract, except that Stripe also uses payment data for its own fraud checks and legal duties, under its own privacy policy, and that Zernio may turn the data it handles into anonymous statistics under its own terms. When a charge is disputed, Stripe passes our record of the purchase to the bank that issued the card. Subprocessors lists every one, what it does and where.
  • LinkedIn, when a workspace publishes, replies or boosts. LinkedIn is not our processor and handles that data under its own terms.
  • Your workspace. Its people see data by their role and by the access each profile gives them. Everyone who can draft for a profile reads that profile's chat with its agent.
  • People at PostCat AI, only to answer a request from you, fix a problem or keep the service safe.
  • Authorities and courts, when the law requires it, or to protect rights, property or safety.
  • A buyer or successor, if PostCat AI is sold or merged. We will tell you before your data falls under a different privacy policy.

How long we keep it

  • Your account and workspace: for as long as they exist.
  • After an account or a workspace is deleted: its LinkedIn accounts are disconnected at once and the data that came from LinkedIn is gone within 10 days; the rest of its personal data is gone within 30 days, and from our backups within 90 days.
  • An unpaid workspace: kept until its owner deletes it, or until nobody has signed in to it for 3 years, when we delete it after emailing the owner 30 days before. The LinkedIn data is erased earlier, as Data from LinkedIn describes, and data with a shorter period of its own, such as session replays, goes when that period ends.
  • Data from LinkedIn: up to 24 hours, 48 hours, 8 weeks, 6 months or 1 year, by kind, as listed in Data from LinkedIn.
  • Clicks, sign-ups and payments from a company's site: as long as that workspace exists. The IP address of a click is used to work out its country and city and to filter out bots, then dropped within 24 hours.
  • The short id on a company's site: 90 days.
  • Session replays: 180 days, or less if the company chooses.
  • A Brand Ambassador's bank and tax details: until they leave and their last invoice is marked paid. Their invoices stay with the workspace, so the company can keep them as long as its tax law asks.
  • Payment records and invoices: 7 years, as tax and accounting law requires.
  • The record of what you accepted: as long as the payment records it backs up, or the account if there are none.
  • The record that an owner has had a free trial: after their account is deleted, we keep only a one-way hash of the owner's email and Stripe's fingerprint of the card, so the trial is given once.
  • Technical logs of requests, errors and sign-ins: up to 30 days, longer only while we look into an attack.
  • Emails and chats with us: for 3 years after the last message, or longer while a legal claim needs them.
  • The waitlist: until your account opens, or until you ask us to take you off it.
  • Website analytics in PostHog: 2 years.
  • Totals that identify no one: with no time limit.

International transfers

PostCat AI LLC is a US company, and so are most of the companies on Subprocessors. Zernio is in Spain and keeps its main database in London; its own providers are listed at zernio.com/subprocessors. Our database is in the United States or the European Union.

When personal data from the European Economic Area, the United Kingdom or Switzerland goes to a country without an adequacy decision for it, we rely on the Standard Contractual Clauses of the European Commission, with the United Kingdom's addendum, or on the EU-US Data Privacy Framework where the recipient is certified. Write to meow@postcat.ai for a copy of these safeguards.

Your rights

Depending on where you live, you can ask us to:

  • tell you what personal data we hold about you and send you a copy;
  • correct it;
  • delete it, unless the law makes us keep it, as with payment records;
  • give it to you in a format you can take to another service;
  • stop or limit a use of it, or object to a use that rests on our legitimate interests;
  • take back a consent you gave, without affecting what was done before.

Write to meow@postcat.ai, from your account's email if you have one. We may ask you to confirm who you are, and we reply within one month. You can also complain to the data protection authority where you live or work.

For data we hold for a company, such as its workspace, its site's visitors and buyers and its session replays, ask that company first: it answers your request and we help it. A request sent to us is passed on to it.

Emails

We send the emails the service needs: invitations, posts waiting for your approval, the weekly drafts email for Brand Ambassadors, billing notices, and a reminder 30 days before an annual plan renews. We email product news to the people who sign up for PostCat AI themselves, and they can unsubscribe in any email. People invited to a workspace, Brand Ambassadors included, get product news only if they ask for it. Unsubscribing leaves the emails the service needs in place. People on the waitlist get an email when their account can open.

Children

PostCat AI is for businesses and the people who work with them, all of them 18 or older, and we do not knowingly collect data from anyone younger. If you think a child has given us personal data, write to meow@postcat.ai and we will delete it.

Security

We protect personal data with measures that fit the risk:

  • every connection to PostCat AI is encrypted in transit (HTTPS);
  • LinkedIn's tokens stay with Zernio, and we never see a LinkedIn password;
  • bank details and the keys of connected accounts are stored encrypted;
  • inside a workspace, roles and the access each profile gives decide who sees what;
  • people at PostCat AI open customer data only when their work needs it.

No system is perfectly secure. If a breach affects personal data we control, we tell the authorities and the people affected where the law requires it. For data we hold for a company, we tell that company, as the Data Processing Addendum says, and help it tell others.

Changes

When this policy changes, the new version gets the date it takes effect, and earlier versions stay readable at their own dated address. Before a change that affects how we use your data takes effect, we email everyone with an account it concerns.

Contact

Questions about this policy or your personal data go to meow@postcat.ai.

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