Privacy policy
Last updated November 17, 2026
Project EduLegacy helps school districts plan toward state assessment goals. This policy explains what information the service holds, why, and how it is protected. Our customers are school districts; “you” means the district and the people it gives access to.
What we collect
- Account information. When someone signs in with Google or Microsoft, we receive their name and email address. We do not receive or store passwords.
- Access settings. Each person’s role (district admin, campus user or viewer) and the campuses they can see, as set by the district’s administrators, and pending invitations by email address.
- Summary results. Percentages of students at each performance level by campus, test, year and student group, as published by the Texas Education Agency or entered by the district, plus goals and benchmark summaries.
- Planning content. Action plan strategies, owners, due dates and notes that users enter, and a history of changes showing who changed what and when.
We do not collect student-level records. The service stores summary percentages, not names, IDs, scores or other records about individual students. Districts should not enter student names or identifiers in notes or other free-text fields.
How we use it
- To provide the service: showing results, goals, suggestions and reports to the people the district authorizes.
- To secure the service and keep a record of changes.
- To support the district when it asks for help.
We do not sell information, use it for advertising, or build profiles of users. District data is used only to provide the service to that district.
Who can see it
Access is controlled by the district: district admins see their whole district, campus users see only the campuses assigned to them, and viewers can see but not change information. These rules are enforced in the database itself. Project EduLegacy staff access district data only to provide support or keep the service running.
Service providers
We use a small number of providers to run the service, each limited to that purpose:
- Supabase — database and sign-in, hosted in the United States.
- Vercel — website hosting.
- Google and Microsoft — sign-in, when a user chooses to sign in with them.
Security
Information is encrypted in transit. Access rules are checked by the database on every request, and changes to results, goals and plans are recorded.
Keeping and deleting information
We keep district information while the district uses the service. A district can ask us to export or delete its information at any time; when a contract ends, we delete the district’s information within 60 days unless the district asks us to keep it longer. District admins can remove a user’s access at any time.
Student privacy laws
We support districts’ obligations under the Family Educational Rights and Privacy Act (FERPA) and Texas student privacy law, and will sign the district’s student data privacy agreement where required. Where such an agreement applies, its terms govern alongside this policy.
Changes
If we change this policy in a way that affects how district information is used, we will tell district administrators before the change takes effect.
Contact
Questions about this page or your data: privacy@projectedulegacy.com
