Privacy Policy

WizeFund is a fundraising-intelligence platform for K-12 schools, districts, and nonprofit organizations. When a school or district uses WizeFund, the institution is our customer: it decides what data to provide and directs how that data is used. WizeFund acts as a service provider — a "School Official" under FERPA — processing data on the institution's behalf and under its instructions.

Throughout this policy, "we," "us," and "WizeFund" refer to the WizeFund service. "You" refers to the school, district, or nonprofit customer and its authorized staff. "Student data" means information in a student's educational record, or otherwise identifiable to a student, that we process as a result of the school relationship.

This policy covers the WizeFund application and related services. For an institutional customer, the binding terms are set out in that institution's Data Processing Agreement (DPA); where a DPA and this policy differ, the DPA controls for that customer.

For New York State educational agencies, additional terms apply. See Section 15 and our Parents’ Bill of Rights and NY Education Law § 2-d Supplemental Information.

We collect only the data needed to provide the service. The categories of personal information we process are:

• Account information: Name, work email address, organization name, role, and authentication credentials of staff users who register.
• Fundraising and donor records: Donor names, contact details, gift history, pledges, campaign and appeal data, and related notes the institution uploads, enters, or syncs.
• Student and family data: Where the institution chooses to associate records with students or families, this data is treated as a FERPA educational record and given the strongest protections (see Sections 5–7).
• Usage data: Pages visited and features used in the application are recorded with first-party product analytics so we can improve the service. Optional analytics and their cookie panel do not run on public giving, fundraising, embedded donation or event flows. Record ids, links and form contents are scrubbed first, screens are never recorded, and the data is never used for advertising. On other app surfaces, analytics are on by default and can be turned off from the cookie popup, in account settings, or with a browser Global Privacy Control signal.
• Email engagement: When an institution sends an email appeal through WizeFund, each copy carries a small image that tells the institution whether that copy was opened, and its links pass briefly through WizeFund on the way to their destination so the institution can see whether a link in that copy was clicked. This is how it sees how an appeal performed. Only the first open and the first link click of each copy are recorded, against that send (not which link or how often); no cookie is set. Recipients who have opted out of behavioral tracking receive no tracking image, and their links go directly to their destination.
• Event registrations: When someone registers for an event through an institution’s Event Page, we record what the institution’s registration form asks for — typically the registrant’s name and contact details, the guests they register, and their answers — so the institution can manage its event. An Event Page may also show a public attendee list. A registrant appears on it only if they choose to, with a checkbox on the registration form that is off unless they tick it, and it then shows only their name, affiliation and class year — never an email address, phone number or answer. Only a registrant can list themselves: the guests they register are never listed, registrations made before this choice existed stay unlisted, and a registrant the institution’s records identify as a student is never listed, whatever they chose.
• Device and connection data: Browser type, operating system, and IP address, used for security, abuse prevention, and diagnostics.

Sources. We receive data directly from the institution and its authorized staff, from data the institution imports (CSV upload), and from connected systems the institution authorizes (for example, a Blackbaud SKY API CRM sync).

Use. We use personal information solely to provide and secure the service the institution has engaged us for: maintaining the platform; generating analytics, insights, and reports from the institution’s own data; providing AI-assisted features scoped strictly to the institution’s own tenant; and sending service-related (transactional) communications such as receipts and security alerts.

Disclosure. We disclose personal information only to the institution and its authorized users, to the subprocessors listed in Section 10 strictly to operate the service, and where required by law. We do not sell personal information, and we do not sell or share student data for advertising (see Section 7).

Because the institution is the data controller, requests to access, correct, export, or delete records are directed through the institution. Authorized staff can manage records in the application, and the institution may request a full export of its data or deletion of its account and associated records.

• Access the personal data held about a record.
• Correct inaccurate data, including challenging the accuracy of a record (see the NY § 2-d Supplemental Information for the formal challenge process).
• Export data in a portable format.
• Request deletion of the account and associated records.

A registrant who chose to appear on an event’s public attendee list and no longer wishes to can ask the institution hosting the event, which can hide that event’s attendee list from its page at once.

Parents and eligible students should direct access, correction, and deletion requests to their school, which controls the educational record; the school will work with us to fulfill the request.

If you need to exercise any of these choices in an alternative format, or encounter an accessibility barrier doing so, see our Accessibility Statement at /accessibility or email [email protected].

WizeFund is a tool for institutions and their staff; it is not directed to children and does not knowingly collect personal information directly from children for our own purposes.

Where data about a child under 13 is processed as part of a school relationship, we act on the school’s behalf under the Children’s Online Privacy Protection Act (COPPA) school-consent framework: the school provides consent on the parent’s behalf for the limited educational purpose it has authorized, and we use the data only for that purpose.

• Any record classified as a child (under 13) is automatically placed in child-safe mode: it is never marketed to, never behaviorally tracked, and is treated as student data.
• We do not condition a child’s participation on disclosing more information than is reasonably necessary, and we do not use child data for advertising or profiling.

When a school shares education records with WizeFund, we act as a "School Official" with a legitimate educational interest under the Family Educational Rights and Privacy Act (FERPA), 34 CFR § 99.31(a)(1).

• We use education records only to perform the service for the school, under its direct control.
• We do not re-disclose education records except as the school directs or as law permits.
• The school retains direct control over its records and may direct access, correction, and deletion at any time.

Consistent with the Student Online Personal Information Protection Act (SOPIPA) and equivalent state laws, with respect to student data WizeFund:

• Does not engage in targeted advertising based on student data, and does not run behavioral advertising at all.
• Does not build a profile of a student except in furtherance of the school’s authorized educational purpose.
• Does not sell or rent student data.
• Does not disclose student data except as needed to provide the service, as the school directs, or as law requires.
• Maintains a comprehensive security program protecting student data (see Section 11).

WizeFund is adopting the commitments of the Student Privacy Pledge 2020 for the K-12 schools we serve. Each commitment is mapped to the specific control that enforces it. Formal signatory status is pending organizational sign-off.Target — not yet implemented

WizeFund is a staff-facing administrative tool and does not provide open internet browsing, messaging, or user-generated public content to students. It does not display advertising. Schools subject to the Children’s Internet Protection Act (CIPA) can use WizeFund without it introducing content that would require additional filtering, because the application surfaces only the institution’s own fundraising data to its authorized users.

We do not use third-party advertising networks, do not serve ads, and do not build advertising profiles.

• Marketing-class email is never sent to any record flagged as a student, child, or opted out of marketing; only transactional messages (receipts, account, and security notices) are sent to those recipients.
• No page sets advertising cookies. Product analytics never run for an account in child-safe mode or for anyone who has turned analytics off.

For details on the cookies and analytics we do use, see our Cookies & Tracking notice.

We use a limited set of vetted subprocessors to operate the service — for hosting, payments, transactional email, AI features, CRM sync, error tracking, and product analytics. Each subprocessor that receives tenant data is bound by a data-processing agreement and reviewed for security. Our current subprocessors and what each receives are listed on our Subprocessors page.

We require subprocessors to be bound by privacy and security commitments at least as protective as ours for any student data they receive, and we update the public list when subprocessors change.Target — not yet implemented

We protect data with administrative, technical, and physical safeguards appropriate to its sensitivity. Donor and student PII is classified as Restricted — our most protected tier — and handled accordingly.

• Tenant isolation: Each institution’s data is isolated at the database layer by Row-Level Security with a default-deny policy, enforced in addition to explicit tenant filters on every query. No other institution can access your data, and AI features operate only within your own tenant.
• Encryption in transit: All external traffic uses TLS (HTTPS); modern TLS (1.2+) only, with deprecated protocols disabled. Database connections use TLS.
• Encryption at rest: Application data, backups, and snapshots are encrypted at rest at the storage layer, and personnel endpoints use full-disk encryption.
• Access control: Role-based access controls; the application connects under a least-privilege database role; passwords are never stored in plain text.
• Audited PII access: Reads of donor and student PII flow through an audited service path that writes to an append-only audit log.
• No PII in logs: Application logs and error reports redact personal information; we log identifiers such as tenant and record IDs, not names, emails, or addresses.
• Breach notification: We monitor for unauthorized access and, in the event of a breach affecting your data, will notify the institution without undue delay in line with applicable law and the institution’s DPA.Target — not yet implemented

WizeFund’s production systems are hosted in the United States. For New York State educational agencies and other customers requiring US data residency, data is stored and processed in the United States. Where any transfer outside a customer’s region is involved, we rely on appropriate legal safeguards and the terms of the institution’s DPA.Target — not yet implemented

We may update this policy from time to time. For material changes that affect how student data is used, we provide prominent advance notice and, where required, choice before the change takes effect. Each published version is dated, and prior versions are retained for reference.Target — not yet implemented

For privacy questions, data requests, or to report suspected misuse of data, contact our privacy team at [email protected]. Institutional customers may also contact their designated WizeFund representative. We acknowledge privacy and abuse reports and respond within the timeframe set by the institution’s DPA or applicable law.

For educational agencies in New York State, WizeFund commits to the protections of New York Education Law § 2-d and 8 NYCRR Part 121. Two additional documents form part of this commitment:

• Parents’ Bill of Rights for Data Privacy and Security: The rights of parents and eligible students regarding student data.
• NY Education Law § 2-d Supplemental Information: The supplemental information required by 8 NYCRR § 121.3: exclusive purpose, subcontractor management, data deletion at contract end, the process to challenge data accuracy, data location, and encryption practices.