Privacy policy
Last updated: June 2026
This policy explains what data Steward LMS collects, who sees it, and how it is used. We have written it for the people who actually use the platform: mentors, coordinators, regional managers, super admins, and the parents whose children's records appear here. If something is unclear, send feedback from Settings and we will rewrite the section.
Who we are
What we collect about students
- Name, grade level, and academic year.
- Region and the mentor and coordinator the student is assigned to.
- Behavioral ratings recorded by the student's mentor across multiple dimensions.
- Attendance records for events the student is invited to.
- Book completion logs and Quran or Khatm assignments.
- Tasks assigned to or by the student, with completion status.
- Notes recorded by mentors and coordinators about the student's progress.
- An anonymized internal ID (for example,
student-abc12345) so we can refer to students in logs without exposing their names.
What we collect about platform users
Mentors, coordinators, regional managers, and super admins each have a platform account. For each account we collect:
- Username, password (stored as a salted hash; we never see the plaintext), and the region you belong to.
- Login history (timestamps and device type). We do not display IP addresses in the user interface; they are visible to our infrastructure provider only.
- Audit log entries for sensitive administrative actions you perform.
- Notifications routed to you.
- Feedback you submit through the Send Feedback form in Settings.
What we do not collect
- Real-time location or GPS data.
- Microphone, camera, or screen-recording access.
- Cross-site browsing history outside of Steward LMS.
- Marketing tracking pixels or third-party advertising identifiers.
- Information about race, health, political opinion, sexual orientation, or other sensitive categories beyond what is inherent to a student's enrollment in a religious-academic program.
Who can see this information
Access is enforced both in the application code and in the database itself (row-level security). Your visibility depends on your role:
- Mentors see their own students plus students they co-mentor. In the Social Graph view they can also see peer-student names and relationship structures at the region level, but not those students' profiles or records.
- Coordinators see every student in their team (every student of every mentor reporting to them).
- Regional managers see every student in their region.
- Super admins see all students across all regions. Their administrative powers are limited to the regional-manager layer; coordinators and mentors remain under their regional manager's authority.
- Students and parents do not directly access the platform; their information is recorded by their assigned mentor.
We never sell data, share it with advertisers, or send it to data brokers.
Children's privacy
Steward LMS records data about minors as part of normal mentoring activity. We comply with the principles of the Family Educational Rights and Privacy Act (FERPA) regarding educational records and the Children's Online Privacy Protection Act (COPPA) for users under 13.
If you are a parent or legal guardian and want to review, correct, or request deletion of your child's records, contact your child's mentor or coordinator. They can use the Send Feedback option in Settings to escalate your request. We will act on it within 30 days.
Students themselves do not have direct accounts on the platform.
Third parties
The platform runs on the following infrastructure providers:
- Supabase hosts the database, authentication, and file storage. They process the data we collect on our behalf, under their data-processing agreement. They do not use our data for their own purposes.
- Vercel hosts the web application. They receive request URLs and the user's IP address as part of normal traffic, and store access logs for short periods to protect against abuse.
- Sentry receives error reports when the application crashes. We strip student names and IDs from error messages before they reach Sentry, but the scrub is not perfect; assume Sentry may occasionally see internal identifiers.
We do not use Google Analytics, Facebook Pixel, advertising trackers, or third-party social-login providers.
Cookies and local storage
We use one cookie to keep you signed in (Supabase auth session) and one to remember your language preference. We do not use marketing or analytics cookies.
We use the browser's sessionStorage (which clears when you close the tab) to remember the last region code you entered on the login page so you don't have to retype it. We do not use localStorage for any personal data.
How long we keep data
We keep records as long as your account or your student record exists in the system. Archived students remain in our records until a coordinator or above explicitly deletes them. We do not auto-purge on a schedule because educational records often need to be referenced years later.
When an archived student is deleted, their behavioral ratings, attendance records, notes, and tasks are removed immediately. Audit-log entries about the deletion itself are retained for forensic purposes.
To have a student record fully removed, ask your coordinator or regional manager to delete the archived account.
Contact
To reach us about anything in this policy, use the Send Feedback option in Settings, or ask your coordinator or regional manager to forward your request through the same channel. We aim to respond within 7 days.