Privacy summary

What gets collected

• Public signup form: full name, cell phone, Instagram handle, hometown—and optionally brothers known, major, year, notes, and a profile photo.
• Board state: statuses, votes, tags, and notes officers add about each rushee.
• Diagnostics on submission: the API records a short-lived rate-limit counter keyed off the requesting IP and the list token (used purely to slow down spam). No request bodies are logged.

Where the data lives

The chapter board (lists, names, phones, Instagram, notes, votes, statuses) is saved in this browser's local storage. Clearing site data, switching browsers, or using another computer will not carry the board over automatically. A cloud-backed officer account model is on the roadmap; until then, treat the device that holds the board as the system of record.

Each list also gets a random signup token that the app uses to build a unique /join/… link. Anyone with that link can submit the public form, so share signup links the way you would share a private group invite.

Signup queue (server side)

When a rushee fills out a /join/…link, the submission is posted to an API route on the chapter's deploy. If the host configured Upstash Redis, that submission is held briefly in a per-list queue until an officer taps Import signups—at which point it is removed from the queue and copied to the officer's browser board.

Without Redis configured, submissions are held only in the running server process and disappear on the next restart. In either case, there is currently no long-term server database.

Profile photos

Photos are optional. When provided, they are stored alongside the rest of the rushee's answers (server queue, then officer browser board). Photos are resized client-side before upload. Officers should only request photos if their chapter is comfortable handling that under FERPA / national org rules.

Accounts & analytics

RushIQ does not require rushees or officers to create an account for the core board today, and the public build does not ship any third-party analytics, ads, or tracking SDKs. If your chapter self-hosts, anything extra would come from the deploy or wrapper site.

Retention & deletion

Officers: removing a rushee from a list clears that rushee's record from the browser board. Clearing site data wipes the entire board.

Rushees: if you want your information removed, message the chapter you signed up with. They can delete you from their list. If you cannot reach them, see the contact below and we will route the request.

Chapters should purge each season's board after rush ends (export first if you want a record).

Contact

Questions or deletion requests: privacy@getrushiq.com. For chapter-specific deployments, also reach out to whoever runs your chapter site.