School IT & vendor review

RaiseHub network and access requirements

This page is intended for district technology, network, privacy, procurement, and vendor-review teams evaluating RaiseHub for school fundraising access.

School setup overview Contact RaiseHub support

Allowlist

Core domains

Permit outbound HTTPS traffic on port 443 to the following domains. Secure WebSocket access to the Supabase host should also be permitted when district filtering inspects WebSocket traffic.

https://raisehub.apphttps://www.raisehub.apphttps://buoczurgckoazbkwgcik.supabase.co

Checkout domains

These Stripe domains are needed when a supporter completes a real payment. They are not required merely to view the school information or campaign-management screens.

https://checkout.stripe.comhttps://js.stripe.comhttps://api.stripe.com

Optional demo access

https://demo.raisehub.app

Browser requirements

• Current Chrome, Edge, Safari, or Firefox.
• JavaScript enabled.
• First-party cookies enabled for authentication.
• HTTPS/TLS inspection must not break RaiseHub, Supabase, or Stripe certificates.
• File downloads/printing are optional and used for CSV rosters and QR sheets.

Not required

• Camera access is not required for organization setup.
• Microphone access is not required.
• Device geolocation is not required for school fundraising setup.
• Browser pop-ups are not required for core organization management.
• Students do not need individual accounts for organization-managed seller QR codes.

Service architecture

Core vendors used by RaiseHub

• Vercel hosts and delivers the RaiseHub web application.
• Supabase provides authentication and application database services.
• Stripe processes checkout and payment information.
• RaiseHub does not require a school to install desktop software or a browser extension.

Accessibility & procurement

Need district-specific documentation?

Districts may require accessibility, security, privacy, purchasing, or vendor forms beyond this public page. RaiseHub does not represent that a formal VPAT or independent accessibility certification has been completed unless that documentation is provided directly.

Request vendor documentation →

Student-data minimization

Schools can use seller tracking without creating student logins

An organization administrator can create campaign roster entries using a seller display name, then generate a personal campaign link and QR code. The roster entry can track attributed pass sales without requiring the seller to provide an email address, password, home address, date of birth, camera access, or device location.

A permitted seller may optionally create a RaiseHub account and claim the existing roster entry so they can view their own totals and recover their link or QR code later. Schools that plan to have minors create accounts should complete their normal privacy and consent review first.

Vendor review links

Public policies and support

Copy-ready request

Suggested note for district IT

Please review RaiseHub for school fundraising access.

Core site: https://raisehub.app

Authentication/data: https://buoczurgckoazbkwgcik.supabase.co

Checkout: https://checkout.stripe.com, https://js.stripe.com, https://api.stripe.com

Vendor review: https://raisehub.app/schools/it-access

Support: support@raisehub.app

Districts may apply additional local security, procurement, accessibility, records, or privacy requirements. Contact support@raisehub.app if your review requires information not listed here.