Syllabus2CalLog in

Last updated: September 16, 2026

Privacy Policy

Syllabus2Cal, operated by Kamsiyochukwu Osigwe-Daniel. This policy explains how the service handles your information and how to exercise your account and privacy controls.

Information we collect and why

Syllabus files and saved text

Original raw files are not permanently stored by default. Processing can use temporary files. File metadata and extracted content are different from the original file and can remain saved. Optional persistent file storage depends on the service configuration; it is not enabled simply by uploading a syllabus. The current syllabus parser is rule-based and does not require external AI API calls to extract dates.

Saved extracted text supports reprocessing and future date checks. In Settings > Privacy & data you can see the available retention controls and delete saved syllabus text. Deleting a semester from your account view is not the same as deleting saved text or your entire account.

Calendar integrations

Connections are optional. When an integration is available and you authorize it, we process connected-account identifiers, granted permissions, selected calendars and event data needed for the calendar features you choose. Read-only overlays display existing events; private events appear as Busy, and other titles depend on your overlay settings. Calendar credentials are stored encrypted on the server rather than included in account exports.

Google Calendar direct writes are currently paused and unavailable. The service does not currently offer direct Google event creation, updates, cleanup, or “remove all synced events”. Review your dates and use PDF / ICS export instead. Importing an ICS file into another calendar is an action you perform there.

Disconnect through Settings > Calendar. A successful disconnect removes stored connection credentials; it does not remove events already exported to another calendar. You can also revoke access through your calendar provider.

Limited Use. Syllabus2Cal's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google Calendar data is not used for advertising or sold, and is shared only as needed to provide requested features or as required by law.

Service providers, sharing and device storage

Hosting, database and authentication providers (including Supabase) process information needed to operate the service. Calendar providers process the connections you authorize. If you create a sharing link, recipients can view its shared content; revoke links you no longer want available. We do not sell your personal information.

The app uses browser/device storage for sign-in state, preferences and cached workspace content, and a service worker for app assets and offline behavior. On shared devices, log out and use the browser's controls to clear local data. Downloaded files and copies on other devices need to be managed separately.

Retention and export

Account content is kept to provide the service until you remove it or account deletion is fulfilled, subject to available retention controls. Saved extracted text has no guaranteed automatic expiry: a retention window alone does not prove that cleanup is running. Settings reports the available retention state; longer-retention preferences can affect eligibility for automatic cleanup.

When available, Settings > Privacy & data > Export account data downloads a JSON file containing your ordinary account and user-created data, including profile, workspace, events, decisions and preferences. It excludes credentials, secret sharing tokens, raw extracted text/table blocks and internal security/operational records. This differs from PDF / ICS calendar export. If account controls are unavailable or you need help, contact support@syllabus2cal.com.

Account deletion and retained records

Account deletion requests are reviewed and fulfilled manually. Recording a request does not immediately delete your account and does not send an automatic confirmation email. Content cleanup and removal of the login account are separate steps; cleanup alone is not completed account deletion. Contact support to ask about the status of your request.

When deletion is fulfilled, we remove your account profile and login account, workspaces and semester data, uploaded-file metadata, saved extracted syllabus text and structure, event candidates and manually created events, corrections and review decisions, planning data, preferences, notifications, feedback and trial-request records, calendar connections and stored credentials, sharing links, export history, and account-linked product activity from the service's account data.

Deleting your Syllabus2Cal account does not delete your Google or Microsoft account, events already imported into another calendar, downloaded exports, or copies held by people you shared them with. Manage those copies separately.

Limited security and deletion-request audit records may be retained after user content is deleted for security, fraud prevention, legal, or audit purposes. These can include account identifiers, request dates, processing status, and evidence of security or deletion actions. Account deletion does not promise that every trace is erased.

Follow the account deletion instructions, including the email option when you cannot access your account.

Security, audience and your requests

We use access controls and encrypted calendar credentials to protect data; no system can guarantee absolute security. Syllabus2Cal is intended for college and university students and is not directed to children under 13.

Contact support@syllabus2cal.com about access, corrections, deletion or other privacy rights. We may need to verify account ownership before acting. Rights required by applicable law remain available. Policy updates will show a revised date here.