Skip to content
Hoosier Boy Greenhouse

Privacy Policy

What we collect, why, and who sees it, in plain language.

Effective November 2, 2026

Who we are

Hoosier Boy Fundraising is the fundraising program of Schlegel Greenhouse, a family greenhouse in Indianapolis, Indiana that has been growing plants since 1972. This policy covers hoosierboyfundraising.com and the emails we send from it.

Questions about this policy or your information: call 317-784-6038, ext. 1, or email fundraisers@schlegelgreenhouse.com.

What information we collect

We only ask for what we need to run your fundraiser.

  • Organizers (the person who signs a group up): your name, email, phone, the group's name and type, the delivery address and date, and what the fundraiser is for. Before we pay out proceeds we also ask for organization details such as who the check should be made out to, a mailing address, and a tax ID (EIN) where the organization has one.
  • Sellers (the people sharing a link): a name and an email address. For student sellers this is usually a parent's email. We also record which orders came through each seller's link.
  • Customers (the people buying plants): your name, email, phone, and what you ordered. If a seller is delivering to you, we ask for a delivery address. Some fundraisers add one optional question at checkout (for example, a dedication for a poinsettia); your answer is kept with the order.
  • Payments: card payments are handled by Stripe on a page Stripe hosts. Card numbers never reach our website or our database. If an organizer chooses to receive proceeds by bank transfer, the bank details are entered on Stripe's site too; we keep only the bank name and the last four digits.
  • Interest and contact forms: whatever you type in, usually a name, email, phone, organization, and which season you're interested in.
  • Church preorders: the church's name, contact person, billing and delivery addresses, and the order.
  • Support calls: if you book a call with us, the phone number and topic you give us.

What is collected automatically

  • Website logs. Like most websites, our hosting provider records the pages requested, the time, your browser type, and your IP address. We use this to keep the site running and to find problems.
  • Google Ads measurement. Our site includes Google's advertising tag. It sets cookies so Google can tell us when an ad led to a signup or an interest-form submission, and it may be used to show our ads to people who have visited our site. You can opt out of personalized ads at adssettings.google.com. If you fill out one of our lead forms on Google itself, Google passes what you entered to us.
  • Bot protection. Our signup, contact, and checkout forms use Cloudflare Turnstile to tell people from automated programs. It looks at browser signals to do that.
  • Email opens and clicks. Emails we send contain a small image and tracked links that tell us whether an email was opened or a link clicked. We use this to know whether our messages are getting through.
  • Your browser's storage. We save small conveniences in your browser, such as a draft of a form you started or which sections of a dashboard you've hidden. This stays on your device.

How we use it

  • To run the fundraiser: take orders, send confirmations and pickup codes, deliver plants, and help the group hand them out.
  • To pay groups their proceeds and to bill them for what they owe.
  • To send emails about your fundraiser: dashboard links for organizers, invites and welcome emails for sellers, and order confirmations, pickup reminders, and pickup changes for customers.
  • To tell organizers and people who asked about our program when a new season opens. Every one of these emails has an unsubscribe link.
  • To answer your questions and support calls.
  • To measure whether our advertising works and to stop fraud and abuse.

Who sees it

Inside your fundraiser. A fundraiser is run by its organizer, so the organizer can see every order placed for their group, including customer names, contact details, and what was ordered. That is how they know who is picking up what. A seller can see the orders placed through their own link. If you buy through a seller's link, the seller and the organizer will know you ordered.

Companies that work for us. We use a small number of services to run the site, and each one handles only what it needs to:

  • Stripe for payments and, optionally, bank transfers to groups.
  • Supabase to store our data and Vercel to host the website.
  • Resend to send email.
  • Cloudflare for bot protection on forms.
  • Google for advertising measurement.
  • A QR-code image service that draws the QR codes in our emails (the code contains a link or a pickup code, not your name).

We do not sell your information, and we do not share it with other advertisers or marketers. We will share it if the law requires us to, or to protect our customers or our business from fraud.

Children

Many sellers are students. We ask that a parent or guardian provide the email address for a seller under 13, and we don't knowingly collect personal information directly from children under 13. If you believe a child has given us their own information, contact us and we will remove it.

Your choices

  • Marketing email: use the unsubscribe link at the bottom of any message. Emails that are part of an order you placed (confirmations, pickup reminders) are sent as part of the service.
  • See, correct, or delete your information: call or email us. We'll keep records of orders and payments as long as accounting and tax rules require, and remove everything else you ask us to.
  • Advertising cookies: you can block or clear cookies in your browser, and opt out of personalized Google ads at the link above.

How we protect it

The site uses encrypted connections, card and bank numbers are held by Stripe rather than by us, and only our staff can see the records behind the website. No system is perfectly secure, but we have deliberately kept the most sensitive information out of our hands.

Changes to this policy

If we change how we handle your information, we'll update this page and the date at the top. This version is effective November 2, 2026.