CurricuPilot does not collect or store user passwords.
Security & Privacy
Clear controls. Honest claims.
CurricuPilot protects school curriculum workflows with authenticated access, server-enforced permissions, district-separated records, and accountable activity history.
Access is checked by the application before protected data or actions are returned.
District users are restricted to their assigned district, role, and sites.
Important order, user, permission, and support actions are recorded.
How access is protected
Security follows every request—not just the buttons on screen.
CurricuPilot checks identity, role, district, and site assignment on protected server routes before information is returned or changed.
Approved accounts only
Users sign in with Google. The Google account must match an active account that a District Admin or authorized CurricuPilot administrator approved.
Server-validated access
Sessions use secure, HTTP-only cookies in production and can be ended through CurricuPilot sign-out.
Boundaries enforced on the server
Teacher, Site Admin, District Admin, and Company Admin permissions are applied before protected records or actions are made available.
Private attachment delivery
Support files are retrieved through an authorized endpoint rather than unrestricted public links. CurricuPilot.com uses HTTPS for browser connections.
Information practices
What CurricuPilot handles
The platform is designed around staff-managed curriculum operations. Information may include staff account details, district and site assignments, curriculum records, orders, approval history, inventory, support requests, and demo-request contact information.
- Staff account information
- Name, work email, assigned role, district, and site are used to provide the correct workspace and permissions.
- District workflow information
- Curriculum, orders, approvals, inventory, shipping settings, and audit records support the district’s ordering process.
- Support information
- Support descriptions and attachments remain connected to the correct request and follow user, district, and company-support permissions.
- Demo requests
- Contact and organization information submitted through the public form is visible only to authorized Company Admins and is used for business follow-up.
Purposefully limited
Zero Student Data Policy
CurricuPilot is designed exclusively for administrative curriculum and ordering operations. CurricuPilot does not require or intentionally collect student records, student rosters, or student personally identifiable information.
Users must not enter or upload student information in orders, support requests, attachments, or any other part of the platform. This includes student names, IDs, rosters, photos, IEP or 504 records, and details that could identify a student indirectly. If information is submitted accidentally, stop sharing or exporting it and promptly notify your district’s privacy or security contact and CurricuPilot Support using a record number or location, without repeating the student information. Follow the student-information prohibition and accidental-submission procedure. Access restriction and appropriate handling are coordinated under applicable law, district agreements and retention procedures.
Shared responsibility
Technology is one part of protecting district information.
District administrators remain responsible for approving accounts, assigning roles and sites, removing access when duties change, and deciding what information belongs in CurricuPilot.
Each customer controls its users, sites, roles, curriculum, shipping rules, and approval workflow.
Customer agreements and district policy should define retention, deletion, required records, and any additional privacy obligations.
CurricuPilot will display certification or compliance marks only after the applicable review has been completed and can be substantiated.
Questions or concerns
Use the right protected channel.
Existing customers can sign in and use Support to report a technical or account concern. Prospective districts can contact CurricuPilot through the demo-request form.