Pitch Unfairly

Privacy Policy

Effective October 22, 2026

The short version. We collect your email to give you an account, store the decks and brand kits you choose to publish, keep your workspace's company context (built from your company's public website when you set one up), keep basic server logs, count how people use this website (with an analytics cookie you can turn off, and only if you agree where the law asks), and, if you join our tester community, see what you post there. We don't see your ChatGPT or Codex conversations, we don't sell anything, and we don't train AI models on your content. Published decks are unlisted: anyone with the link can view them.

This Privacy Policy explains how Unfairly, Inc. ("Unfairly," "we") collects, uses, and shares information when you use the Pitch Unfairly plugin for ChatGPT, Codex, and other agents (the "Plugin"), host decks at pitchunfairly.com, or visit this website (together, the "Service"). The Service is also governed by the Pitch Unfairly Terms of Service. If you also use Unfairly's main platform, the Unfairly Privacy Policy covers that use.

1. What the Plugin does on your computer

The Plugin is software that runs inside your agent's workspace, such as ChatGPT or Codex, on your computer or in the agent's sandbox. It writes your deck's files, builds it, and checks it there. When you ask it to capture a brand from a website, it opens that public website in a headless browser in that same workspace and saves measurements, screenshots, and assets locally. None of that reaches Unfairly unless you publish a deck or save a brand kit.

You install the Plugin from our GitHub repository or an agent's plugin directory. Those services' own policies cover the download; we only see aggregate download counts.

In agents without a code workspace, such as an ordinary ChatGPT chat, the Plugin builds your deck in a studio we host instead: your deck's files, story, and brand work are written to a private sandbox run for us by Daytona, built and checked there, and deleted when the session ends or after about two hours. While it checks a deck, the studio sends screenshots of its slides and their text to an AI model (through OpenRouter, on Microsoft Azure) for a design review. Brand capture from a website in the studio uses that public website and Brandfetch's public brand data.

Your conversations with ChatGPT, Codex, or any other agent are handled by that agent's provider under its own terms and privacy policy. Unfairly does not receive your conversation. We only receive what the Plugin sends to our hosting tools, described below.

2. Information we collect

2.1 Account information

Publishing requires an Unfairly account. When you sign in, we collect your email address and create a workspace handle used in your deck links (for example, pitchunfairly.com/handle/deck). If you belong to an Unfairly organization, we also use your organization's name and slug as a workspace option.

2.2 Connection information

When you connect the Plugin to your account, your agent signs in through OAuth. We keep the record of that authorization, including the name of the connecting app and the time you approved it, so the Plugin can act for you until you revoke it.

2.3 Decks you publish

When you publish, we receive and store the deck's files (such as HTML, CSS, JavaScript, fonts, images, video, and its PDF), its title, slug, version history, file list, and sizes. Anything you put in a deck, including names, numbers, or images of people, is part of the deck you publish.

2.4 Brand kits you save

When you save a brand kit, we store its settings (colors, fonts, physical style, voice and layout notes) and any files you include, such as logos, font files, and imagery. You can keep one saved kit. A kit captured for a single deck is stored with that deck.

2.5 Your workspace and company context

When you set up a workspace while connecting (a company name and, optionally, its website), we research that company from public sources: its website, Brandfetch's public brand data, and public web search (Tavily and Exa), summarized by an AI model (through OpenRouter, on Microsoft Azure). We store the results as your workspace's company context, such as a company overview, positioning, audiences, brand voice, team, and website notes, along with each published deck's story and the lessons you ask the Plugin to remember. People you invite to the workspace can see it. While the workspace keeps making decks, we refresh that research about once a month; anything a person in the workspace has written or edited is left as they wrote it. If you publish without a workspace and sign in with a work email address, we research the company at that email's domain the same way and keep the results private to you. We research companies, not you.

When you publish a deck, the Plugin may pass along what you told it that should carry over to future decks, such as a correction, how you like your decks, or a fact about your company. An AI model (through OpenRouter, on Microsoft Azure) sorts that into your own preferences, which only you and your future decks see, lessons for your workspace's decks, and updates to your workspace's company context, which people in the workspace can see and edit.

2.6 Logs

Our hosting providers record standard request logs when anyone uses the Service or views a deck, including IP address, browser and device type, the page requested, and timestamps. We use these to run, secure, and debug the Service.

2.7 Website analytics and cookies

On pitchunfairly.com's own pages (not inside published decks), we use PostHog to understand how people use the site: pages viewed, which slide of the home page they reached, the links and buttons they click (such as which plan, template, or guide they choose), whether they submitted the website field (not what they typed), visits to the install page, which install steps they copied, whether they used the TAM SAM SOM calculator's examples or copied its prompt, and PDF downloads. PostHog also receives your IP address, which it uses to estimate your country and city, your browser and device type, the page that sent you here, and any campaign tags in the link you followed (such as the "pitch unfairly" badge on a free deck).

What we store in your browser. PostHog keeps a random ID for your browser in a first-party cookie and in local storage on pitchunfairly.com (named ph_ followed by our project key and _posthog), so we can tell a return visit from a new one. It holds no name or email and isn't shared with other websites or with the domain that serves published decks. It lasts a year from your last visit. Your analytics choice is kept in local storage (pu_analytics_consent) so we don't ask again.

If you make an account. When you go from this site to app.unfairly.ai to sign up or sign in, the random ID goes with you in the link, and we join your visits on this site to your account's analytics record. That record uses a scrambled (hashed) form of your account ID, never your name or email, so we can see which pages lead people to make and pay for decks. If you've declined analytics, or haven't chosen yet where we ask first, nothing is carried over.

Where we ask first. If you visit from the European Union, the European Economic Area, the United Kingdom, or Switzerland, we start without the cookie: PostHog uses your browser's session storage, which is cleared when you close the tab, and we ask before setting it. Accept turns the cookie on. Decline turns analytics off on this site and clears what PostHog stored. Everywhere else the cookie is on by default and you can turn it off below.

PostHog processes this for us as our service provider, in the United States. We keep analytics events for as long as our PostHog project's data retention setting allows, and delete yours sooner if you ask.

Analytics loads a moment after the page does.

We also record a few product milestones in PostHog from our servers: when you publish a deck (new or updated, and whether it's your first), when someone opens one of your decks, and when a plan's trial starts, it becomes paid, or it ends. These are linked to a scrambled (hashed) form of your account ID, not your name or email. A deck view records only that the deck was opened; nothing about the viewer is sent.

2.8 Messages you send us

If you email support, including about a paid plan, we keep the message and our reply.

2.9 Payments

If you buy a paid plan, Stripe processes your payment through its checkout and customer portal. Stripe handles your card details; we don't receive your full card number. We receive and keep your plan, billing period, subscription status, and the email and Stripe customer record linked to your account.

2.10 Our tester community

If you join our tester community on Slack, Slack (a Salesforce company) handles your Slack account and the messages you post under its own terms and privacy policy. We can see your Slack name and profile and what you post in our channels, and we use it to support you and improve the Service.

2.11 People who view a deck

When someone opens a published deck, we record the visit for the deck's owner and its workspace: when it was opened and which version, how long each slide was on screen while the tab was visible, how far they got, the approximate city and country worked out from the request's IP address (we don't store the IP address), the kind of device (computer, phone, or tablet), and the site that linked to it. Visits through a named link, one the owner made for a particular recipient, are credited to that recipient. If the owner asked for an email before the deck shows, the email the viewer gives is kept with their visits, and the form says the owner sees it. Some decks and proposals open only for emails their owner has allowed: the viewer enters their email, we send a six-digit code to it, and the right code opens the deck and keeps them signed in to it with a cookie. We keep the email, when each code was sent and used, and failed tries (we store only a scrambled form of the code, and too many wrong tries lock that email out of the deck for 15 minutes). Where the owner asks for an email without a code, we don't verify it. A random ID in the viewer's browser storage on pitchunfairly.com ("pu-viewer") lets return visits to the same deck group together. It is scrambled (hashed) separately for each deck, so visits can't be linked across decks, and it isn't kept when the browser sends Global Privacy Control or Do Not Track. Previews in the owner's own Pitch Unfairly gallery aren't recorded.

Every owner sees how many times a deck was viewed, and is emailed when a deck gets its first view and at view milestones, with the viewer's approximate city, how long they stayed, and how far they got, but not who they were. Owners on Solo and Team, and their workspace members, also see who viewed it (by named link or email, or as anonymous with an approximate place), for how long, and slide by slide, and the owner can be emailed whenever someone views it, with who it was and their path through the slides. If you viewed a deck and want your visit removed, ask the deck's owner or email us.

2.12 Signing agreements

When a deck or site is sent for signature, we keep a signing record so the signature can be relied on later. For each signer that is their name, email, title and role; the one-time code we emailed them and when they entered it; when they were asked, opened it, and signed or declined (with the reason they gave); the IP address and browser they signed from; the values they filled in; and the signature they adopted, either the name they typed and the style they chose or the image they drew. If the sender signs as they send it, we record that they were signed in to Unfairly instead of a code. Unlike deck views, the signing record keeps the IP address, because it is part of the evidence of who signed.

We use the record to run the signing (asking each signer in turn, reminding them, and telling the sender who has opened or signed), to make the signed PDF and its certificate page, and to show that the agreement was signed if that is ever questioned. Signers and anyone the sender copies get the signed PDF. The sender and their workspace's owners and admins can see the record and export it. The parties' signatures and the values they filled appear on the agreement itself, to everyone who can open its link.

2.13 What we don't collect

pitchunfairly.com uses no advertising trackers. Besides the analytics cookie above, the only cookies are ones a deck's own gates need, each limited to that deck's link: one remembering that you entered its password, one remembering the email you gave a deck that asks for one, and one keeping you signed in to a deck after you confirm your email with a code. Deck views are described in 2.11 and are never used for advertising. The website field on our home page sends what you type to our install page in your browser's address bar, where it is used to write your prompt; we don't store it or send it to analytics. The TAM SAM SOM calculator runs in your browser; the numbers you enter aren't sent to us.

3. How published decks are shared

A published deck is unlisted. It lives at a link with a random code, it isn't listed anywhere, and it tells search engines not to index it. Anyone who has the link can view it and download its PDF, and they can share the link further. Don't publish anything you need to keep confidential. You can unpublish a deck at any time, which stops it being served.

Decks on free accounts show a small "pitch unfairly" badge that links to pitchunfairly.com.

4. How we use information

We don't sell your information, we don't use it for advertising, and we don't use your decks or brand kits to train artificial-intelligence models. For people in the European Economic Area and the United Kingdom, we rely on performance of our contract with you, our legitimate interests in running and securing the Service, and compliance with legal obligations.

5. Who we share information with

We share information only with the service providers that run the Service (the ones that handle customer data are also listed on our subprocessors page), when required by law or to protect people and the Service, in connection with a merger or acquisition (with notice), or at your direction. Decks are visible to anyone you give the link to, and a deck's views are visible to its owner and their workspace (see 2.11).

ProviderPurposeLocation
Supabase (on AWS)Accounts, sign-in, database, and file storage for decks and brand kitsUnited States
VercelHosting and content delivery for pitchunfairly.com and the Unfairly appUnited States, with global edge delivery
ResendTransactional emailUnited States
InngestBackground jobs, such as building proposals, making signed copies and sending remindersUnited States
GitHub (Microsoft)Our source code, and for proposal customers their templates and the change requests they send usUnited States
PostHogAnalytics for pitchunfairly.com's own pages, and for product milestones in your accountUnited States
Slack (Salesforce)Our tester community for the betaUnited States
StripePayments and subscriptions for paid plansUnited States
SentryError monitoring for the Unfairly app, which runs the Plugin's hosting toolsUnited States
NangoConnecting a proposal customer's CRM, when they connect oneUnited States
DaytonaPrivate sandboxes for the hosted deck studioUnited States
OpenRouter, on Microsoft AzureAI design review of slides in the studio, summarizing public company research, and learning your preferences from what you tell the PluginUnited States
BrandfetchPublic brand data (logos, colors, fonts) for a company's domainSwitzerland
Tavily and ExaPublic web search about your workspace's company, or the company at your work emailUnited States

6. How long we keep it

To delete a deck, your brand kit, or your whole account, email privacy@unfairly.ai from your account's address. We complete deletion within 30 days, apart from information we must keep by law.

7. Security

We encrypt data in transit, restrict access to the people and systems that need it, and serve every deck from a separate, sandboxed domain (cdn.pitchunfairly.com) so code inside a deck can't reach your account or our pages. No system is perfectly secure; we'll notify affected users of a material incident as the law requires.

8. Your rights

Depending on where you live, you may have the right to access, correct, delete, or export your personal information, and to object to or restrict how we use it. California residents have the right to know, delete, and correct their personal information. We don't sell or share personal information as California law defines those terms, and we won't treat you differently for using your rights. To use any right, email privacy@unfairly.ai. You can appeal a denied request by replying to our response.

9. International users

We operate in the United States and store information there. If you use the Service from elsewhere, your information is transferred to the United States, with appropriate safeguards where the law requires them.

10. Children

The Service is for people 18 and older. We don't knowingly collect information from anyone under 18; if you believe a minor has an account, contact us and we'll delete it.

11. Changes

We'll post any update here with a new effective date, and give reasonable notice of material changes by email or on the Service.

12. Contact

Unfairly, Inc., 455 Market Street, Suite 1940 PMB 875030, San Francisco, CA 94105. privacy@unfairly.ai.