School sign in

← Privacy & security

IT administrator brief

Technical summary for district firewall reviews, security questionnaires, and production go-live. Share this page with your network and compliance teams.

Product summary

PassPlace is a multi-tenant SaaS hall-pass system: teachers issue passes, destinations track arrivals, principals monitor the hallway, and security uses a mobile hall monitor. Student identity is required for operations — not a zero-knowledge design.

Data inventory

  • Student PII: legal/preferred name, student number, grade — Postgres (students, enrollments)
  • Pass records: destination, times, issuer, status, notes — Postgres (passes, pass_events, arrivals)
  • Staff PII: name, email, role — Postgres + Supabase Auth
  • Audit: actor, action, target IDs, redacted metadata — Postgres (audit_logs)
  • Assets: school logo, print layouts — Supabase Storage (private, signed URLs)
  • Not in schema: medical reasons, behavior scores, public leaderboards

Architecture

Browser → Supabase Data API (publishable key + user JWT) → PostgreSQL with RLS per school_id. Next.js on Vercel runs Server Actions with user JWT and/or server-only service role for narrow admin paths. SUPABASE_SECRET_KEY is server-only and must never ship to the browser.

Firewall / allowlist checklist

  • Allow HTTPS to your PassPlace production URL (Vercel)
  • Allow HTTPS to your Supabase project URL (*.supabase.co)
  • Ensure {APP_URL}/auth/callback is registered in Supabase Auth redirect allow-list
  • If staff use phone alerts: allow browser push to vendor endpoints (device-dependent)

Production go-live checklist (IT)

  • PASSPLACE_ALLOW_DEMO_LOGINS unset or false in production
  • SUPABASE_SECRET_KEY and all secrets server-only (never NEXT_PUBLIC_)
  • Preview deployments not pointed at production DB with real students
  • Supabase project in agreed US region; DPA signed
  • Supabase Auth redirect allow-list limited to production (+ staging if used)
  • MFA enabled for Supabase org and PassPlace principal accounts
  • No demo seed on production student data

Contracts & legal (for counsel)

Districts typically need: (1) school-official / service-provider agreement under FERPA, (2) data processing terms with PassPlace operator, (3) Supabase and Vercel DPAs. Request agreement templates from your PassPlace operator — they are not published on this website because each district customizes them with counsel.

Questions or need agreement templates for counsel? Contact alerts@passplace.app.