Evident School Procurement Packet
A self-serve starting point for school leaders, privacy officers, IT reviewers, and procurement teams evaluating Evident for a pilot or school license.
Related review links
Security overview
Controls designed to protect student-support records.
Evident uses Supabase-hosted PostgreSQL with Row Level Security policies to keep users and organizations scoped to the records they are authorized to access.
Application access is authenticated, role-aware, and designed around teacher, school admin, and organization membership boundaries.
Data is encrypted in transit with HTTPS/TLS and encrypted at rest by the hosting and database providers.
Data privacy summary
How student-support data is collected, used, and controlled.
Evident stores student display names, goals, daily logs, evidence notes, family-visible summaries, parent portal interactions, and account metadata needed to provide the service.
Teachers and school admins control what becomes family-visible. Staff-only notes are not shown to families unless a user explicitly publishes family-visible content.
Evident is designed for data minimization and recommends using student display names instead of unnecessary sensitive identifiers.
DPA / NDPA information
Contracting path for school privacy review.
Evident provides DPA/NDPA documentation for schools and districts evaluating or using the product.
District-specific terms can be reviewed through the privacy contact path when a standard agreement does not satisfy local requirements.
The DPA page provides DPA information, subprocessor details, and the request path for agreement documentation.
Subprocessor list
Core vendors used to host, operate, bill, email, monitor, and protect the service.
Vercel: hosting and application compute.
Supabase: database, authentication, and storage-backed application services.
Stripe: payment processing and billing portal.
Resend: transactional email delivery.
Sentry: error monitoring.
Upstash: rate limiting infrastructure.
OpenAI: AI-assisted translation and writing support only where product features explicitly invoke AI.
Data retention and deletion
How data export, deletion, and disposition requests are handled.
Teachers and authorized admins can export or delete student and account data through supported product workflows or a support request.
Audit logs are retained for the life of the account so administrators keep a usable history, and they are removed with the account under the standard disposition timeline.
School or district disposition requests should be sent through the privacy contact path so scope, timing, and verification can be confirmed.
Retention behavior should be reviewed against the signed agreement for each school or district.
FERPA-conscious workflow explanation
Product controls that support school FERPA obligations.
Evident is designed to support FERPA-conscious workflows through role-based access, staff-only notes, explicit family visibility controls, audit logs, export/delete workflows, and DPA support.
Schools remain responsible for their own FERPA determinations, directory information policies, parent rights processes, and internal staff training.
AI usage statement
Where AI may be used and how to review it.
Evident uses AI-supported functionality only where a product feature explicitly invokes AI assistance, such as translation or future writing-support features.
AI-assisted outputs should be reviewed by an educator before being shared with families or used in formal documentation.
Evident should not be described as making automated eligibility, discipline, placement, or service decisions.
Accessibility statement
Current accessibility target and readiness path.
Evident targets accessible, keyboard-friendly workflows for educators and families and maintains an accessibility guide for core patterns.
A public accessibility readiness statement documents current audit scope, known gaps, and the path toward VPAT/ACR readiness.
Formal VPAT/ACR completion should not be claimed until the readiness work and review are complete.
Implementation FAQ
How a school can pilot and roll out Evident.
Most schools can start with a small Team Pilot or school plan using invitations and CSV import before deeper rostering integrations are required.
School admins can invite staff, manage seats, and review school-level usage from the admin dashboard.
Pilot scope should define participating staff, student-support workflows, review dates, and success metrics before launch.
Rostering and provisioning options
Current and future paths for getting staff and students into Evident.
Current pilot-friendly options include staff invitations, CSV student import, and Google Classroom import where configured.
Clever, ClassLink, and OneRoster readiness should be evaluated through a separate integration audit before being promised as a production rollout path.
Support and contact path
Where schools send procurement, privacy, security, and implementation questions.
School purchasing and pilot questions can be sent to schools@evidentk12.com.
Privacy and DPA questions can be sent through the privacy contact path.
Security review questions can be sent through the security contact path.
Support and contact
School purchasing and pilot questions: schools@evidentk12.com
Privacy and DPA questions: see the DPA page.
Security review questions: see the Security page.