Subprocessors
Effective October 22, 2026
These are the companies Unfairly, Inc. uses to process customer data when it builds, hosts, gates, measures and signs proposals for Sell Unfairly customers. Each is bound in writing to protect that data, and none may use it to train AI models. A customer’s services agreement refers to this list. How we handle information more generally is in our Privacy Policy.
| Subprocessor | What it does for us | Where |
|---|---|---|
| Vercel | Hosts sellunfairly.com, the proposal sites on customers’ domains, and the Unfairly app | United States, with global edge delivery |
| Supabase (on AWS) | Accounts, sign-in, the database, and file storage for proposals, reading reports, signing records and signed PDFs | United States |
| Inngest | Runs background jobs, such as building proposals, making signed copies and sending reminders | United States |
| Daytona | Private sandboxes, with no network access, where proposals are built | United States |
| OpenRouter | Routes requests to AI models for writing and reviewing proposals | United States |
| Microsoft Azure OpenAI | The AI model those requests reach, under our own Azure account | United States |
| GitHub (Microsoft) | Stores our source code, and each customer’s proposal templates and the change requests its team sends us | United States |
| Nango | Connects to a customer’s CRM, when the customer connects one, so a deal can start a proposal and get its link back | United States |
| Resend | Sends email from the customer’s domain: reader verification codes, review and signature requests, reminders, and signed copies | United States |
| Stripe | Invoices and payments | United States |
| PostHog | Analytics for our websites, and product events such as a proposal being sent or signed | United States |
| Sentry | Error monitoring and alerts for the Unfairly app | United States |
We’ll update this page before adding a subprocessor that handles customer data, with a new effective date. Questions go to privacy@unfairly.ai.