1. Scope
This Privacy Policy applies to CurricuPilot’s public website, demo-request process, and authenticated curriculum-ordering service. A school district or other customer organization may also have a written agreement with CurricuPilot. That agreement may contain additional privacy, security, retention, or deletion requirements.
2. Information CurricuPilot handles
Account information
CurricuPilot may handle a staff member’s name, work email address, role, district, site assignment, account status, and Google-authenticated identity. CurricuPilot does not collect or store the user’s Google password.
Curriculum and operational information
The service stores information needed to manage curriculum operations, including curriculum items, order quantities, approvals, correction notes, shipping selections, inventory allocations, vendor information, purchasing records, notifications, reminder history, support requests, and audit history.
Demo and business contact information
When someone requests a demonstration, CurricuPilot may collect the person’s name, organization, role, work email, phone number, number of schools, and the message submitted. Owner billing tools also maintain district billing contacts and addresses, PO requirements, quote and invoice details, recorded payments, receipt snapshots and subscription dates. These are business records; the service does not need Social Security numbers, tax forms, banking credentials or payment-card details.
Public homepage counts
The public homepage records page views using a random browser identifier stored locally on the device, a random page-load identifier, and a timestamp. These counts are separate from login and district activity. This counter does not collect names, email addresses, IP addresses, or browsing activity on other websites. It respects the browser’s Do Not Track setting. Clearing local browser storage resets the identifier.
Technical information
CurricuPilot and its service providers may process basic technical records needed to operate and secure the service, such as request timestamps, browser or device information, network addresses, session records, and error logs.
CurricuPilot is designed for staff-managed curriculum and ordering operations. It does not require or intentionally collect student records, student rosters, or student personally identifiable information. Districts, schools and their users must never enter, upload or import student information anywhere in the service, including names, IDs, rosters, student records, photos, screenshots or details that could identify a student indirectly. Only staff and non-identifying administrative ordering information belongs here. The student-information prohibition in the Terms of Service includes examples and reporting instructions.
3. How information is used
CurricuPilot uses information to:
- authenticate approved users and maintain secure sessions;
- apply district, site, and role permissions;
- provide ordering, approval, inventory, purchasing, reminder, notification, support, and audit functions;
- respond to demo requests and customer support matters;
- protect the service, investigate errors, and prevent misuse; and
- maintain and improve service reliability.
CurricuPilot does not use district workflow information to advertise to students or sell student information.
5. Retention and customer control
Information is retained for as long as reasonably needed to provide the service, maintain required business and audit records, resolve disputes, enforce agreements, and meet legal obligations. Customer agreements or documented district instructions may establish more specific retention and deletion periods.
Authorized administrators control user access and much of their organization’s information. A customer may request access, correction, export, restriction, or deletion through its authorized administrator or CurricuPilot Support. Some information may be retained when required for security, audit integrity, legal compliance, or legitimate recordkeeping.
6. Security
CurricuPilot uses safeguards intended to protect information, including authenticated access, server-enforced permissions, district-separated records, secure production cookies, HTTPS connections, private attachment delivery, and activity records. No online system can guarantee absolute security.
For more detail, read the Security & Privacy overview. If student information or other sensitive information is submitted accidentally, stop sharing or exporting it and promptly notify your district’s privacy or security contact and CurricuPilot Support. Report the record number or location and approximate submission time; do not repeat student information or attach the original file to the report. Follow the accidental-submission procedure. Appropriate access restriction, removal and retention will be coordinated consistent with applicable law and customer agreements. Editing or deleting a screen does not guarantee immediate removal from logs, emails, exports or backups.
7. Choices and privacy requests
Users may ask their organization’s administrator to review or correct their account information. Customer organizations may contact CurricuPilot about their organization’s records. CurricuPilot will evaluate requests according to the requester’s authority, the applicable customer agreement, and applicable law.
The service is intended for authorized school and organization staff. It is not directed to students or designed for independent use by children.
8. Changes and contact
CurricuPilot may update this policy as the service or legal requirements change. The effective date at the top of this page will identify the current version. Material changes may also be communicated through the service or to the customer’s designated contact.
Existing customers should use the protected Support area in CurricuPilot. Other privacy questions may be submitted through the public contact form; do not include student information or other sensitive records.