Your syllabus is for planning—not profiling.
Syla is designed to create a calendar without retaining a copy of your PDF. You may sign in with email so your account follows you across devices.
What happens to a PDF?
Your browser reads the selectable text locally. The raw PDF file is not uploaded. The extracted text, file name, and page references are sent to the app's analysis endpoint so deadlines can be identified.
What is sent to the AI provider?
When live AI extraction is configured, the extracted text is sent to OpenAI through its API with response storage disabled. Syla does not put that text in its own database. If live extraction is not configured, a limited demo parser runs on the app server instead.
What small amount of technical data is kept?
A short-lived rate-limit counter prevents abuse. Anonymous browser and session IDs help us measure product use for up to 90 days, including landing visits, sign-ins, uploads, successful analyses, and first exports. To count activated accounts without storing emails, Syla uses a server-derived opaque identifier that cannot be reversed by analytics storage. Your account stores an authentication ID and limited access history. These records never contain syllabus text, file names, dates, or event titles.
What happens when you send feedback?
Feedback is optional. If you submit it after an export, Syla stores your rating, note, account ID, and submission time so the service can be improved. Feedback never automatically includes your syllabus or calendar. Do not put contact details, syllabus text, or other sensitive information in your note. Feedback is removed if its associated account is deleted.
What should you avoid uploading?
Do not upload documents containing grades, student ID numbers, medical information, or other sensitive personal records. Use only the course syllabus pages needed to identify deadlines.