Privacy Policy
Privacy Policy
How we collect, use, and protect your data. FERPA and GDPR aligned.
What this covers
This page describes two things: what the public website at runmycampus.com collects from visitors, and how the platform treats the student, staff, and family data a school keeps inside its own workspace. The two are different: a school decides what goes into its workspace, and the platform processes it for that school.
What this website collects
The website collects only what a visitor types into a form. Each form is listed here with its fields.
| Contact form | Name, email, school or organization, country, inquiry type, and message. |
|---|---|
| Demo request | Name, email, phone, school or organization, country, role, school type, approximate student count, and the jurisdiction that governs student records. |
| Security packet request | Name, email, organization, role, country, jurisdiction, NDA status, and the documents you ask for. |
When a form is submitted, the website forwards it to the inbound endpoint the operator has configured for enquiries. The form handlers do not write a copy into the website's own database. If no endpoint is configured, the form is acknowledged and nothing is stored.
Visit measurement
- Public funnel events record the country and the page path. They never record an email address.
- Analytics and marketing scripts are off until a visitor chooses otherwise. The consent banner starts with only strictly necessary storage granted.
What is stored in the browser, and for how long, is listed on the cookie policy.
Data inside a school
Your institution controls access, roles, and data exports. Directory information flags and parent or guardian access are configured per your policy. Role-based access, audit logs, and tenant isolation reduce exposure of student data to what each workflow requires.
- Parents and guardians can request an export of their child's data or its erasure from the parent portal.
- Requests for erasure, export, and correction move through a review. The person who asked never approves their own request, and the person who approved never carries it out.
- Audit records note which field changed, by whom, and when. They do not store passwords, tokens, or the values of a student's most sensitive attributes.
Your rights
Access, correction, deletion, and portability apply where the law gives them to you.
- About something you sent through this website: write to us through the contact page and say what you want done with it.
- About a child's or staff member's record in a school: ask the school, which is the controller of that record. The school can act on the request inside its workspace.