Who we are
TazFund is software for schools, youth sports, booster clubs, first responders, nonprofits, and other groups that raise money season after season. Related products in the suite include events, ticketing, CRM, commerce, and forms.
If you use TazFund on a campaign site, you are usually interacting with both TazFund (the platform) and the organization running that fundraiser. The next section explains which of us is responsible for what.
Scope and roles
Fundraising platforms sit between two kinds of relationships. Which one applies depends on why we have your information.
TazFund as a business (controller). We decide how to collect and use information about people who visit tazfund.com, request a demo, create an organization account, sign in as an administrator, or contact sales. That includes billing contacts, how the admin product is used, and how we run TazFund itself.
Organizations as campaign operators (controller); TazFund as processor. When a school, team, or nonprofit runs a fundraiser on TazFund, that organization is responsible for the campaign: who is listed as a participant, who is asked to donate or buy tickets, what appears on public pages, and how supporter records are used after checkout. We process that information on the organization's instructions to operate the campaign, take payment, attribute dollars to the right person, send receipts and tickets, and produce settlement reports.
If you supported a raffle, bid in an auction, bought squares, made a donation, or joined a team page, the organization running that campaign is the primary party to contact about that record. We can help route a request, and we will not ignore a valid rights request sent to us, but the organizer usually has the context to fulfill it.
Organizations may publish their own privacy notice on their TazFund location. When they do, that notice applies to how they use supporter and participant information in addition to this policy.
Information we collect
What we collect depends on how you use TazFund.
Organizers and account holders. When you create an organization or location, request a demo, or contact us, we collect information such as name, email, phone, organization name, role, industry, address (including a place identifier used to confirm the address), public subdomain, password, and any message you send. Administrators sign in through Auth0. We also store campaign settings, roster and team structure, fee and payout configuration, and records of how the account is used.
Participants and team members. Organizations often roster athletes, students, volunteers, or other fundraisers so each person gets a page that can be shared. That typically includes name, contact details the organizer provides, team or group assignment, fundraising totals, and coaching or how-to progress. Participants who sign in to manage their page or send outreach may verify identity with a one-time code. We store a session so they do not have to repeat that every time during a campaign.
Supporters, donors, bidders, and buyers. Checkout collects first name, last name, email, and phone so we can complete the order, send tickets or receipts, and let the organizer fulfill prizes or pledges. You may be able to mark a contribution anonymous on public leaderboards or donor walls; the organization still needs your identity to process payment and issue a receipt. Silent-auction bidders may verify email to view or manage bids. We also store order contents (tickets, squares, donation amount, pledges), fee and tax lines, and fulfillment status.
Payment information. Card numbers are entered on the payment provider's hosted form (Stripe or Square, depending on how the organization is set up). Full card numbers do not pass through TazFund's application. We receive tokens, last-four digits, charge identifiers, and similar metadata needed to reconcile, refund, or investigate a payment.
Device, usage, and security data. Like most web services, we collect IP address, browser and device type, pages viewed, referring URL, timestamps, and diagnostic logs. Signup and demo forms may use Cloudflare Turnstile to reduce automated abuse. Address fields may send what you type to an address-suggestion service so we can offer a confirmed address. Marketing forms may capture advertising click identifiers (such as gclid, fbclid, or ttclid) when those are present in the URL so we can tell which campaign sent a lead.
Information from the organization. Organizers upload or enter rosters, prize lists, auction lots, custom copy, images, and tracking-pixel IDs. They may also import contact lists they already have permission to use. We process that information to provide the service they configured.
How we use information
We use personal information to:
- Provide, operate, and improve TazFund, including campaign pages, checkout, drawings, leaderboards, reporting, and settlement.
- Attribute clicks, shares, and dollars to the participant or team who raised them, which is the core of peer-to-peer fundraising.
- Create accounts, authenticate users, keep sessions, and protect against fraud, spam, and unauthorized access.
- Process payments through the organization's processor, send receipts and tickets, and help with refunds or payout questions.
- Send service messages: order confirmations, draw results, bid updates, payout notices, and product changes that affect an account.
- Respond to sales, support, and compliance questions, and to follow up on demo or pricing requests.
- Comply with law, enforce our terms, and protect TazFund, organizations, and supporters.
We do not sell supporter lists, and we do not use supporter checkout data to market unrelated third-party products.
How we share information
We share information in these situations:
- With the organization running the campaign. Organizers and their authorized admins see supporter and participant records needed to run the fundraiser: who bought, pledged, or bid; contact details; ticket or square assignments; and settlement. That is the point of the product.
- On public campaign pages, when the campaign is designed that way. Names may appear on leaderboards, donor walls, squares grids, bid histories, or published drawing results, unless the organization offers an anonymous option and you use it. Do not expect a live fundraiser to be private in the way a closed database is private.
- With service providers. We use vendors to host the product (currently Microsoft Azure in the United States), authenticate administrators (Auth0), process payments (Stripe or Square), reduce bot traffic (Cloudflare Turnstile), suggest addresses, send email or SMS, and operate related Tixoola suite products such as CRM lead capture. These providers are allowed to use the information only to perform services for us or the organization.
- Across the Tixoola suite, when an organization uses more than one product. Organization and location records may be shared with related products (for example TazCRM or TazTix) so a group is not forced to recreate the same account in each tool.
- For legal reasons. We may disclose information if we believe it is required by law, regulation, charitable-gaming inquiry, payment-network rule, or to protect rights, safety, or the integrity of a drawing.
- In a business transfer. If we sell, merge, or reorganize, information may transfer as part of that transaction, still subject to this policy or a successor notice.
Payments
TazFund is not a bank and does not store full payment-card numbers. Each location connects a wallet or card-payments setup. Supporters complete card entry on Stripe or Square. Those companies process the charge under their own privacy policies and under the organization's merchant relationship.
We keep the metadata required to show an organization what was collected, what fees were taken, what was refunded, and what should settle. If you have a billing question about a specific donation or ticket, start with the organization that ran the campaign; they can see the order. Payment-network disputes are handled through the processor.
Campaign sites, participants, and supporters
Each organization gets a public TazFund site. That site is the organization's fundraising storefront. Information you submit there is collected for that organization.
Fundraising has a few industry-specific realities that generic SaaS policies often skip:
- Peer-to-peer pages exist to be shared. A participant's first name, team, and amount raised are often public because that is how the campaign motivates the rest of the roster.
- Raffle and squares purchases create a record that may be needed later for a drawing, prize fulfillment, or state charitable-gaming review. We retain those records with the campaign.
- Sport-A-Thon pledges may be collected before results are known and billed later. The pledge, contact, and estimated amount stay on file until the organization completes billing or cancels.
- Winner lists, when the organization publishes them, may include names associated with a ticket or square. Treat a published drawing as public.
- Organizers are responsible for telling supporters what they are buying (a donation, a raffle ticket, squares, a pledge) and for following the raffle, sweepstakes, and charitable-solicitations rules that apply to them. TazFund does not decide whether a particular raffle is legal in a given state.
Cookies and similar technologies
We use cookies and similar storage to run the product, not to build an advertising profile of people who merely browse tazfund.com.
- Essential cookies. These keep you signed in to admin (Auth0), remember a supporter or bidder session after a one-time code, store a short-lived cart or checkout snapshot, and remember a theme preference (`tazfund-theme`). Without them the product cannot function.
- Consent storage. On campaign sites that use a Meta Pixel, we store your choice to accept or decline advertising cookies in local storage (`tazfund.analyticsConsent`) so we do not ask on every page.
- Security. Cloudflare Turnstile and similar checks run on signup and demo forms to tell humans from bots.
You can block cookies in your browser. If you do, sign-in, checkout, bidding, and theme preference may stop working.
Advertising and measurement pixels
Organizations may connect a Meta (Facebook) Pixel to a campaign so they can measure visits, checkout starts, and completed donations or ticket sales. We do not load that pixel unless the organization enabled it and, on the campaign site, you accept advertising cookies. If you decline, we still record that a conversion event was attempted so the organizer can see that measurement was blocked; we do not send the event to Meta.
If you accept, Meta receives standard pixel events (page view, view content, initiate checkout, purchase) along with whatever Meta collects through its own script. That sharing is for the organization's advertising measurement, not for TazFund to sell your data. You can decline the banner or use Meta's own ad settings to limit ads.
AI features
Administrators can ask TazFund to draft campaign copy or summarize reports they already have access to. Those requests are sent to the model provider we use (currently Azure AI Foundry) to generate a response. We use this to help organizers write faster, not to train a public model on supporter checkout records as a business purpose.
Do not paste government IDs, card numbers, or other sensitive data into an AI assist field. Organizers remain responsible for reviewing anything the model drafts before they publish it.
Children and youth programs
TazFund accounts and admin access are intended for adults acting for an organization. We do not knowingly allow a child under 13 to create a platform account.
Many customers are youth sports teams, schools, and PTOs. Those organizations may list minors as participants (for example, an athlete's first name on a Sport-A-Thon page) so families can fundraise for that child. The organization is responsible for having the authority to do that, for limiting what they publish, and for handling parent requests. If you believe we have an account for a child under 13, or a campaign is exposing more about a child than it should, contact us and we will work with the organization to correct it.
How long we keep information
We keep information as long as it is needed for the purpose it was collected, including:
- Account and billing records for the life of the organization account, and for a period afterward as needed for invoices, disputes, and tax or processor requirements.
- Campaign, order, ticket, pledge, and drawing records for as long as the organization retains the campaign and as needed to reconstruct a settlement or respond to a charitable-gaming or payment inquiry.
- Marketing leads until they are worked, declined, or you ask us to delete them, subject to a thin suppression record so we do not email you again by mistake.
- Security logs for a shorter operational window unless we need them to investigate an incident.
When an organization closes its account, we delete or de-identify personal information we hold solely as their processor, except where we must keep a copy (for example, a completed payment, a legal hold, or a chargeback). Backup systems may take additional time to cycle.
Security
We use administrative, technical, and physical safeguards appropriate to a hosted fundraising product: encrypted transport (HTTPS), access-controlled admin sign-in, httpOnly session cookies, tenant isolation by organization and location, and card data handled by PCI-certified processors rather than by TazFund. No method of transmission or storage is perfectly secure. Organizers should use unique passwords, limit who has admin access, and treat exported reports as confidential.
Where information is stored
TazFund is hosted in the United States (Azure East US and related services). If you access the product from another country, your information is processed in the United States. Service providers listed above may process data in the countries where they operate.
Your rights and choices
Depending on where you live, you may have the right to know what personal information we have, to access or correct it, to delete it, to export it, to opt out of certain sharing, or to appeal a decision. We will not discriminate against you for exercising a privacy right.
California and similar U.S. state laws. We do not sell personal information for money. Campaign-site advertising pixels, if you accept them, can be "sharing" for cross-context behavioral advertising under some state laws. You can opt out by declining the cookie banner. You may also send a "do not sell or share" request through our contact form. We do not use sensitive personal information to infer characteristics about you for advertising.
If you are a supporter or participant. Ask the organization first — they control the campaign roster and order records. If you cannot reach them, contact us with the campaign URL, your email, and what you want changed. We may need to verify it is you, and we may not be able to erase a record that is part of a completed drawing, tax receipt, or settled payment.
If you are an organizer. Most account information can be updated in admin. For deletion of an organization, contact us; we will explain what must remain for settlement and processor reasons.
Email, SMS, and other messages
We send transactional email required to run the product: receipts, tickets, magic links or one-time codes, bid notices, and account messages. You cannot opt out of those and still use the feature that depends on them.
We may email people who requested a demo, pricing, or other sales follow-up. You can unsubscribe from marketing email using the link in the message or by contacting us.
Organizations may send fundraising texts or emails to people they already have permission to contact. When the product asks an organizer to confirm they have permission to text a list, that confirmation is their responsibility. If you received a campaign message you do not want, reply STOP where supported or tell the organization. We are not the sender of that outreach in the way a brand advertising campaign is; the organization is.
Changes to this policy
We will update this page when our practices change. The Last updated date at the top will change. For material changes, we may also notify organization admins by email or through the product. The updated policy applies going forward; we will not use previously collected information in a newly disclosed way without a lawful basis and, where required, additional notice.
How to contact us
Privacy questions, access or deletion requests, and "do not sell or share" requests can be sent through our contact form. Please say that it is a privacy request and include the email you used on TazFund and, if it is about a campaign, the public campaign URL.
If you are writing about a specific fundraiser, include the organization name. That is usually enough for us to find the right tenant and route the request.