Privacy & security
Factual overview for district IT, security teams, counsel, and principals evaluating PassPlace. This page is not legal advice — school counsel should review agreements before loading live student data.
What we store
School-authorized student names, student numbers, roster links, pass history (who, where, when), staff directory fields, and operational audit metadata. PassPlace does not store medical reasons, behavior scores, or public student rankings.
Who can access data
Authorized school staff per role (teacher, security, principal). Each school is isolated in PostgreSQL with row-level security (RLS) enforced in the database — not UI hiding alone. PassPlace operators with infrastructure access can support the service; this is not a zero-access architecture.
Where data lives
Application hosted on Vercel (Next.js). Database, authentication, and file storage on Supabase (region chosen at project creation, typically US). Data is encrypted in transit (TLS) and at rest per vendor standards (AES-256).
Network & firewall allowlisting
Staff browsers need outbound HTTPS (TCP 443) to your PassPlace app URL (e.g. passplace.vercel.app or your school’s custom domain) and to your Supabase project (*.supabase.co). Auth callbacks use {APP_URL}/auth/callback — that origin must be allow-listed in Supabase. Optional phone alerts (PWA Web Push) use the device browser’s push vendor (Apple APNs, Google FCM, or Mozilla autopush) when staff opt in.
Security controls (technical)
Multi-tenant isolation by school_id · PostgreSQL RLS · Supabase Auth (invite-only staff accounts) · Role-based access (teacher, security, principal) · Append-only audit logs · Private object storage with signed URLs · MFA available for principals and system owners · Demo logins and simulation disabled in production by default · No third-party analytics or error trackers in the default product stack.
FERPA posture
PassPlace is designed to operate as a school official / service provider under FERPA (34 CFR § 99.31) with a written agreement per district. Schools retain control of education records; the vendor provides safeguards and limits use to the contracted hall-pass function. This page is not legal advice — school counsel should review agreements before live student data.
Subprocessors
Primary infrastructure: Supabase (database, auth, storage) and Vercel (application hosting). Both publish DPAs and SOC 2 reports. Optional Web Push uses browser vendor push services when staff enable phone alerts. See the full subprocessor list with DPA links below.
Production safeguards
Demo walkthrough logins, auto-simulation, and Demo Controls are disabled in production unless explicitly enabled. Principals and system owners can be required to enroll multi-factor authentication before admin access.
District review packet
Materials for your firewall, security, and legal teams — readable on this site (not internal repository paths):
- IT administrator brief — data inventory, architecture, firewall allowlist, production go-live checklist
- Subprocessors & DPAs — Supabase, Vercel, and optional push services with vendor trust links
School-official agreement and data-processing templates are provided by your PassPlace operator during onboarding — email alerts@passplace.app to request them for counsel review.