Privacy Policy
Effective October 22, 2026
The short version. Companies use Sell Unfairly to turn their deal details into proposal websites. We build proposals from totals, not records about people, and turn away requests that identify a person. When you read a proposal, the company that sent it sees that you opened it, how far you read and what you clicked. We don’t sell personal information, we don’t use it for advertising, and our AI providers can’t train on our customers’ content.
This Privacy Policy explains how Unfairly, Inc. (“Unfairly,” “we”) handles information for Sell Unfairly: the proposals we build and host for our customers, the people who review, read and sign them, and visitors to sellunfairly.com. Each customer’s services agreement with us also governs how we handle that customer’s data, and where the two differ, the agreement controls.
1. Who is responsible for what
When a company (our customer) sends you a proposal, it decides what goes in the proposal, who may read it and what it does with what it learns. We process that information on the customer’s behalf, as its service provider. If you read a proposal and have a question about your information, the company that sent it is the first place to ask, and we’ll help it answer. For our own website and for the accounts of the people who work with us, Unfairly is responsible.
2. Information we handle
2.1 What customers send us
A customer sends us the details a proposal needs: its client’s company name, plan details, rates, totals such as headcount or how many people live in each state, notes from its calls, and its brand. Proposals take counts only. A request that carries names, birth dates, member or employee IDs, or a row per person is refused before it’s read, and a template can require small groups to arrive blank so a count can’t point at anyone. Customers agree not to send us health information about any identifiable person.
If a customer connects its CRM, a deal reaching the stage it chooses starts a proposal: we read that deal’s fields that the customer maps to the proposal, and write the proposal’s link back to the deal.
2.2 The customer’s team
The people who work on proposals sign in to the Unfairly app with their email address. We keep their name, email and role, the comments they leave on drafts and who approved each version. An AI assistant reads review comments to sort them into changes, questions for a person, or nothing to do, and the team can see how it sorted each one.
2.3 People who read a proposal
A proposal lives at a link on the customer’s domain. The customer can make it open only for email addresses it has allowed: you enter your email, we send a six-digit code to it from the customer’s domain, and the right code opens the proposal and keeps you signed in to it with a cookie. We keep your 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 for 15 minutes.
When you read a proposal, we record for the customer: when you opened it and which version, how long each section was on screen while the tab was visible, how far you got, the links and buttons you clicked, the approximate city and country worked out from your IP address (we don’t store the IP address), the kind of device, and the site that linked to it. If you verified your email or opened a link made for you, your visits are shown under your name or email. A random ID in your browser groups your return visits to the same proposal; it isn’t kept when your browser sends Global Privacy Control or Do Not Track.
2.4 Signing
When a proposal or agreement is sent for signature, we keep a signing record so the signature can be relied on later: each signer’s 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 any reason they gave); the IP address and browser they signed from; the values they filled in; and the signature they adopted. Signers and anyone the sender copies get the signed PDF.
2.5 Visitors to sellunfairly.com
We use PostHog to understand how people use this website: the pages you view, when you leave a page, and the buttons you click, such as booking a demo. PostHog receives your IP address, which it uses to estimate your country and city, your browser and device type, and the page that sent you here. It keeps a random ID for your browser in a first-party cookie and in local storage, so we can tell a return visit from a new one. It holds no name or email, and we don’t record your screen. You can block or clear the cookie in your browser, or ask us to delete your analytics data.
2.6 Messages and payments
If you email us or book a demo, we keep the message, the booking and our reply. Customers pay through invoices that Stripe sends; Stripe handles card and bank details, and we keep the invoices and payment status.
3. How proposals are built
Each proposal is built in a private sandbox, run for us by Daytona, with all network access blocked. It stops itself after 15 minutes and is deleted as soon as the build finishes, and always within the hour. To write and review a proposal, we send the customer’s details to AI models through OpenRouter, to our own Microsoft Azure account, on a route that doesn’t keep or train on what it receives. Stock photos come from Pixabay, which receives only the search words. Nothing reaches a customer’s client until someone on the customer’s team approves the version, and the customer can withdraw a proposal at any time, which takes its link down at once.
4. How we use information
- To build, host, gate and measure proposals, and report on them to the customer that sent them.
- To run signing, make signed copies, and show that an agreement was signed if that is ever questioned.
- To keep the service safe: verify readers, prevent abuse and investigate problems.
- To support customers and send messages about their account or the service.
- To understand how people use this website, and improve it.
- To improve the service. A customer’s agreement may let us learn from its content and how its proposals perform, including to train our own AI models, but only after we remove anything that identifies the customer, its clients or any person. We never use personal information or health information for this, and we never show one customer’s content to another.
- To comply with law and enforce our agreements.
We don’t sell or share personal information as California law defines those terms, we don’t use it for advertising, and we never let our AI providers train their own models on our customers’ content.
5. Who we share information with
We share information with the customer a proposal belongs to; with the service providers that run Sell Unfairly, listed below (the ones that handle customer data are also on our subprocessors page); when required by law or to protect people and the service; and in connection with a merger or acquisition, with notice.
| Provider | Purpose | Location |
|---|---|---|
| Vercel | Hosting this website, proposal sites and the Unfairly app | United States, with global edge delivery |
| Supabase (on AWS) | Accounts, sign-in, database and file storage | United States |
| Inngest | Background jobs, such as builds, signed copies and reminders | United States |
| Daytona | Private sandboxes where proposals are built | United States |
| OpenRouter, on Microsoft Azure | AI models that write and review proposals and sort review comments | United States |
| GitHub (Microsoft) | Our source code, customers’ proposal templates and their change requests | United States |
| Nango | Connecting a customer’s CRM, when they connect one | United States |
| Resend | Email from the customer’s domain: codes, review and signature requests, reminders | United States |
| Stripe | Invoices and payments | United States |
| PostHog | Analytics for this website, and product events | United States |
| Sentry | Error monitoring and alerts | United States |
| Pixabay | Stock photos for a proposal; it receives only the search words, never customer data | Germany |
6. How long we keep it
- Customer data and proposals: while the customer’s agreement is in effect. When it ends, we hand the customer its live proposals, keep them online for 30 days, and then delete the customer’s data, apart from records we must keep.
- Reading reports: 13 months, or until the proposal is deleted.
- Signing records and signed PDFs: as long as the customer’s workspace exists, and at least seven years after the agreement is completed.
- Build sandboxes: deleted when the build finishes, and always within the hour.
- Website analytics: under our PostHog project’s data retention setting; the browser cookie for a year from your last visit, or until you clear it.
- Logs: for limited periods set by our providers for security and debugging.
7. Security
We encrypt data in transit, restrict access to the people and systems that need it, build every proposal in a sandbox with no network, and keep drafts visible only to the customer’s team until it approves them. No system is perfectly secure. We tell a customer within 72 hours of confirming a breach of its data, and notify affected people 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 it’s used. If you read a proposal, you can ask the company that sent it, or email us and we’ll pass your request to it and help it respond. For anything else, email privacy@unfairly.ai. We won’t treat you differently for using your rights, and 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 Sell Unfairly or read a proposal from elsewhere, your information is transferred to the United States, with appropriate safeguards where the law requires them.
10. Children
Sell Unfairly is for businesses and isn’t directed at anyone under 18. We don’t knowingly collect information from children; if you believe we have, contact us and we’ll delete it.
11. Changes
We’ll post any update here with a new effective date, and give customers reasonable notice of material changes.
12. Contact
Unfairly, Inc., 455 Market Street, Suite 1940 PMB 875030, San Francisco, CA 94105. privacy@unfairly.ai.