Why Sizzle · Your data

Your rosters aren’t our product.

Community software should not monetize families. Rosters, records, and payments belong to your organization. We don’t run ads against your people, and we don’t resell their data.

Read the legal policy too — this page is the plain-language stance.

What you own

Household profiles, volunteer credentials, payment history, program records — that’s yours. Export paths and operational ownership matter as much as encryption slides.

  • No advertising against your members or parents
  • No selling roster data to third parties
  • Clear access so the right staff see the right records

No lock-in theater

We want you to stay because the nights work — not because we trapped your data. Continuity and ownership go together: when Dave leaves, the organization still has its records.

How this shows up in products

Sign-ups without forcing parent accounts where they aren’t needed. Enterprise builds that put the organization in control of roles and retention. Support that treats your data as yours.

Trust, concretely

No ads

Your families aren’t inventory

Org-owned

Records stay with the school or nonprofit

Policy + practice

Legal terms and product decisions aligned

Questions buyers ask

Where is the legal privacy policy?

At /privacy. This page explains our stance for buyers; the policy is the binding detail.

Can we export our data?

Yes — talk to us about export for your product or enterprise build. Ownership without exit is not ownership.

Buy software that respects your people.

If data ownership is a deal-breaker, you’re in the right place.