# Licensing & Redistribution

This page summarizes how you may use the data. It's a plain-language guide, not the full terms of
service — for anything not covered here, or a use case you're unsure about, reach out before you
build.

## At a glance

| Use | Free | Developer | Pro | Business |
|---|:--:|:--:|:--:|:--:|
| Internal use (apps, analysis, research) | ✅ | ✅ | ✅ | ✅ |
| **Store & cache** returns in your own systems | ✅ | ✅ | ✅ | ✅ |
| Show returns to your **own end users** inside your product | — | — | — | ✅ |
| **Redistribute** the data as data (feeds, exports, datasets, or a competing offering) | — | — | — | ✅ |

## Internal use, storing & caching

**Allowed on every plan.** You may use the returns inside your organization — build applications,
run analysis and research, and **store and cache** results in your own database or application
layer. There's no requirement to re-fetch on every request or to purge after a window. Your usage
counts against your plan's [monthly quota](/errors) at fetch time, so caching is also the
recommended way to keep your request volume down.

The line for the lower tiers is **audience**: use the data freely for yourself and your team, but
don't surface it to people outside your organization.

## External use — Business plan

Two uses require the **Business plan** (or the Snowflake dataset):

- **Showing returns to your own end users** — displaying the data inside a product, app, or
  service you offer to customers or the public.
- **Redistributing the data as data** — publishing a feed or export, bundling the returns into a
  dataset you sell or share, or building a product whose primary purpose is to relay this data to
  others.

Both are available on the **Business plan**, or through the
[Fruit Stand fund-returns dataset on the Snowflake Marketplace](/api-vs-snowflake), which is
licensed for bulk and redistribution use. If either is core to what you're building, those are the
two supported paths.

## Not sure which side of the line you're on?

If your use case sits near the boundary — a partner integration, an embedded widget, a resale
arrangement — email [contact@fruitstand.dev](mailto:contact@fruitstand.dev) and we'll confirm in
writing before you ship.