Semester Calendar Builder keeps the public site stack small.

Semester Calendar Builder is hosted on Cloudflare Pages. Cloudflare may process routine request metadata, such as IP address, user agent, request time, requested URL, and security signals, to deliver and protect the site.

The planner is account-free. Courses, study blocks, exams, deadlines, exports, and backup files are handled in the browser unless you choose to download or share them.

The app does not run hosted user accounts, payments, cloud schedule sync, school-system integrations, or a remote course database for visitor schedules.

Schedule details are sensitive in practical ways even when they are not formal school records. Class names, instructor names, room locations, work shifts, commute blocks, exam windows, and notes can reveal a student's routine. The product is built so those details stay in the browser-first planning workflow instead of being collected by a hosted planner account.

Exports are controlled by the user. If you download an ICS, CSV, PNG, or JSON file, that file is handled by your device, browser downloads folder, calendar app, cloud drive, email client, or any person you share it with. Semester Calendar Builder cannot control those downstream tools after export.

Cloudflare's role is infrastructure delivery and site protection. It is not used here as a hosted database for student schedules, advisor notes, registration choices, or calendar backups. The only expected production processing is the routine request handling needed to serve a public static site.

If Semester Calendar Builder later adds accounts, analytics, hosted sync, collaboration, payments, or school integrations, this disclosure should be updated before those services receive production traffic.

Questions about subprocessors, local storage, exports, or schedule privacy can be sent through the contact page. Include the page, browser, and workflow if the question is tied to a specific planning or export step.