Legal
Privacy Policy
This page explains what HourlyProgram stores today, why it is stored, and how that data supports sign-in, school routing, security, and basic product operation.
Last updated: June 1, 2026
What we collect
HourlyProgram currently stores the information needed to run the school scheduling workspace and keep access secure.
- Authentication data such as account identity, session state, and selected school context during sign-in.
- Operational data such as page-view logs, login events, referrer data, and user-agent strings recorded by the application itself.
- Browser-side preferences such as theme choice and the last active timetable selection.
Why we use it
The current data collection is functional and product-focused rather than advertising-focused.
- To sign users in and keep them in the correct school workspace.
- To remember language and interface preferences.
- To understand basic product usage and investigate operational issues.
- To support security checks, tenant access enforcement, and platform administration.
Third-party services
HourlyProgram does not currently load third-party analytics or advertising trackers on the public site.
If you choose to sign in with a provider such as Google or Microsoft, that authentication flow is handled through the selected provider and Auth.js.
Retention and changes
This policy reflects the current product state and will be updated as the platform adds more public features, school onboarding flows, or optional analytics tooling.
If non-essential tracking is added later, HourlyProgram should introduce consent controls before loading that tracking for users who require them.