Privacy Policy
Institution-controlled student records and staff-operated administrative desktop software.
This notice describes the intended Windows workflow and its current limits. Release-specific security verification is pending. Use synthetic records for evaluation until a verified production release is available.
1. Desktop processing and institutional custody
Gradebook is designed for authorized staff to manage student profiles, courses, attendance, grades, curriculum milestones, and academic reports on institution-managed devices. The software processes these records; the institution determines authorized access and approved storage destinations.
The planned ordinary workflow does not require a Horizon-hosted student-record service. This is not a guarantee that records remain inside a building: institution-selected shared folders, cloud-backed drives, backups, email, and printing services may transfer or retain copies.
2. Records rights and authorized disclosure
Parents and eligible students should send requests to inspect, review, or amend educational records to their educational institution or registrar. Horizon Tech Services cannot retrieve institution-held records through this website.
The institution determines applicable privacy requirements, access authority, retention, and disclosure procedures. A staff or caseworker role in the software does not establish legal authority to receive records, including juvenile justice records. Gradebook is not presented as certified or as a guarantee of legal compliance.
The planned application is staff-operated, rather than a student-facing online service. Applicability to an institution’s actual use requires review. Consult the Department of Education’s FERPA regulations and FTC COPPA guidance.
3. Working files, backups, and exports
The developers describe local SQLite databases, WAL files, and JSON snapshots containing records and account information. Treat working databases, synchronization files, backups, temporary files, and PDF or CSV exports as sensitive. Do not assume they are encrypted.
Protection of a separately packaged archive does not establish protection of the active database or exported documents. Confirm supported formats and safeguards against the exact release before use.
4. Shared folders and device protection
Optional multi-station synchronization is designed to exchange snapshots through an institution-configured shared folder, for example \\FacilityServer\GradebookShare\SyncData. Keep each active SQLite database on its workstation; do not operate a shared WAL database across hosts.
Institutional IT must approve destinations and configure permissions, device and server protection, network transport, backup access, and recovery procedures. Disk encryption and SMB protections are not automatically enabled by Gradebook. Application roles do not prevent someone with direct file access from reading unprotected data.
5. Printing, sharing, and other services
Review transcripts before exporting, emailing, or printing them. Customer-selected mail, storage, and print services may create remote copies or spool files. Institutions control authorized recipients and must protect those copies.
This website loads Google Fonts and its hosting provider may process request information. Website visits, support inquiries, and Microsoft Store or operating-system services are separate from desktop record processing. A zero-telemetry claim for the entire application has not been verified for release.
6. Retention, deletion, and restoration
Follow institution-approved retention schedules and preservation requirements, including pending inspection requests and legal holds. Removing a record or uninstalling the application does not establish complete erasure of databases, replicas, backups, exports, or remote copies.
Deletion across synchronized stations and stale backups requires release-specific verification. Inventory all copies and test restoration with synthetic records before production use. Do not delete records or recovery files merely to troubleshoot a support issue.
7. Technical support privacy
Do not submit student names, identifiers, grades, transcripts, backups, passwords, or recovery keys through support forms or tickets. Support inquiries should concern installation, configuration, or defects and use sanitized error messages or synthetic examples.
If you accidentally send confidential information, notify support without resending it. Restricted intake, authorized handling, deletion subject to preservation duties, and incident escalation procedures must be confirmed before production support accepts sensitive material.
8. Privacy questions and release updates
Use the Horizon Tech Services inquiry form, select Other, and begin with “Harborleaf Gradebook privacy inquiry.” Send only a general description, without student information. Requests about a student’s records belong with the institution or registrar.
Microsoft Store and offline installer destinations will be added when the Windows release is available. This notice will be updated as release behavior and support procedures are verified.