Privacy Policy
Last updated: October 2026
Sponsee is a sponsorship CRM for live streamers. This policy covers the marketing site at sponsee.app and the product itself — the pipeline, invoices, chase emails, and billing.
If a sentence here does not match what the product actually does, the product is wrong or this page is stale. Email hello@sponsee.app and we will fix the page.
1. Who this is for
This is for you if you create a Sponsee account, signed up for our waitlist before launch, or work at a brand and receive an email we sent because a creator asked us to send it.
We do not take custody of your money. Brand payments stay between you and the brand. Stripe on this page is how you pay us for Sponsee, not how a brand pays you.
2. Information we collect
Former waitlist. Until signup opened on October 2, 2026, the waitlist collected an email and, optionally, a channel handle, platforms, and a concurrent-viewer band. It is closed and collects nothing now. Section 7 covers what we kept.
Account. Email, name, and (if you use Google sign-in) the profile Google sends us. We store a session cookie, and we may store the IP and browser used to sign in.
Creator profile. Display name, pronouns, category, timezone, currency, avatar, and the platforms you add (Twitch, YouTube, Kick, TikTok) with the handle, URL, and stats you enter or that we sync.
Payout rails. Optional PayPal link, Wise instructions, and bank instructions you type in. These are template fields for invoices, not login credentials. Do not put passwords or full card numbers here.
Your sponsorship pipeline. Brands (name, category, domain), contacts (name, email, role), deals, deliverables, contracts, invoices, notes, CPVH calculator inputs, and chase-email templates.
Files you upload. Contracts and proof (VODs, clips, screenshots, PDFs). We store the file and enough metadata to show it back to you.
Emails we send for you. When a chase email goes out, we keep a copy of the subject, body, recipient, and delivery status (sent, delivered, opened, bounced, failed).
Sponsee billing. If you subscribe, Stripe sees your payment method and billing details. We store Stripe customer and subscription IDs, plan, and status — not your full card number.
Usage on the marketing site. The marketing pages (including this one) load Google Analytics, which sets cookies and collects device and usage data so we can tell whether the site is working.
We do not scrape your chat, VODs, or audience. Platform stats come from what you type, from a public lookup on the handle you gave us, or from an OAuth connect you chose (Twitch or Kick).
3. How we use it
- Run the product: your pipeline, invoices, deliverables, files, and CPVH numbers.
- Sign you in (magic link from noreply@sponsee.app, or Google).
- Send payment-chase emails to the contacts you entered, when you arm chase and approve a send.
- Bill your Sponsee subscription.
- Sync platform stats you asked us to sync.
- Figure out whether the marketing site is working.
- Reply when you email us.
We do not sell your data. We do not share it with anyone for their marketing.
4. Emails we send for you
This is the part our pre-launch policy did not mention, and it is the most important sentence on this page.
If you arm late-payment chase, we email the brand contacts you saved, on your behalf. Mail comes from chase@sponsee.app. Replies go to your email. We use the subject and body you set in your templates (or the defaults you left in place). We keep a log of what was sent so you can see it in the product.
You are choosing to give us those contacts and to let us write to them. Do not put a contact in Sponsee unless you have a reason to email them about a deal or an invoice.
We cannot unsend an email that already landed. Deleting your account does not pull a message out of a brand person's inbox.
5. Who else sees data
We use other companies to run Sponsee. They only get what they need to do that job.
| Who | What they see | Why |
|---|---|---|
| Neon | Everything in the database | Hosts Postgres. |
| Render | App traffic and the data the API reads and writes | Hosts the API (sponsee.onrender.com). |
| Vercel | Marketing-site traffic | Hosts sponsee.app. |
| Resend | Email addresses and the content of mail we send (sign-in, chase) | Sends the mail. |
| Stripe | Your Sponsee billing details | Charges your subscription. Not brand-to-you payments. |
| Brandfetch | Brand domains you save, the IP of the browser that loads the logo, and sponsee.app as the referrer | Primary logo fetch from the creator's browser. |
| unavatar.io | Brand domains you save, on a cache miss from our servers | Fallback logo fetch from our servers on cache miss. |
| Analytics on the marketing site; account profile if you sign in with Google | Analytics and optional sign-in. | |
| Twitch / Kick | The OAuth tokens you grant if you hit Connect | Subscriber counts, instead of a public lookup. |
If you upload files, they live in S3-compatible object storage we control. We will name that vendor on this page when it is locked.
Your browser talks to us, Brandfetch when a card logo is loaded, and Google Analytics. We do not run a marketplace, so other creators do not see your pipeline.
6. Brand logos
When you save a brand domain, the pipeline first loads a logo from Brandfetch using that domain. If Brandfetch has no logo or its request fails, our servers use a favicon and Unavatar fallback.
What they see: Brandfetch sees the domain, your browser's IP address, and Sponsee's origin as the referrer. The fallback provider sees the domain and our server's IP address. Neither receives your name, email, or the rest of your deals.
What they do not see: a full export of your pipeline. They see each domain whose logo we ask for.
If logo loading fails, we show a monogram instead. The fallback logo response is cached and shared across creators by domain; direct Brandfetch logos are not cached by Sponsee.
7. How long we keep it
- Account and pipeline (brands, contacts, deals, invoices, chase logs, activity): for as long as the account is open.
- Files you upload: until you delete the file or the account. Deleting a deal does not delete the file; that is on purpose, so proof and contracts survive a deal you archive.
- Former waitlist: we deleted the waitlist from our database when signup opened. We keep one archived export of it in our internal records, so we can honor removal requests and show that the mail we sent was asked for. We do not email that list. Ask, and we will delete your row from the archive too.
- Sessions: until they expire or you sign out.
- Sponsee billing records at Stripe: for as long as Stripe is required to keep them, including after you cancel.
- Emails already sent: copies we keep in Sponsee go away with the account. Copies at Resend, and the message in the recipient's inbox, do not.
We do not have a "delete after X days" timer on pipeline data. If you want it gone, ask.
8. Deleting your account
There is no delete button in the app yet. Email hello@sponsee.app from the address on the account and ask us to delete it.
We will delete the login, the workspace, the pipeline, the files, and any archived waitlist row for that email. We will not keep a copy "just in case."
We cannot delete:
- Chase emails already sitting in a brand person's inbox.
- Billing records Stripe is required to keep.
- Backups that have not yet rotated. Those age out; we will not restore a deleted account from them.
Waitlist-only: email hello@sponsee.app from the address you signed up with and we will delete your row from the archive.
9. Cookies
- Product: a session cookie so you stay signed in (
sponseeprefix). Required for the app to work. - Marketing site: Google Analytics cookies. The site works without them.
10. Your rights
Email hello@sponsee.app to access, correct, export, or delete what we have, including any archived waitlist row. We will do it.
If you are in a place with extra rules (California, EEA, UK, and others), use the same address. We are a small team; we will not hide behind a form.
11. Kids
Sponsee is for people running a sponsorship business. It is not for children under 13, and we do not knowingly collect their data.
12. Changes
If we start doing something this page does not describe — new subprocessors, a new kind of email, a new place data lives — we will update this page and change the date at the top. Material changes get a note in the product or an email.