Your documents are yours.
Full stop.

When you upload a PDF, Word document, or PowerPoint file, Syllabi processes it entirely in server memory. The raw file is parsed, the text is extracted, and the file buffer is discarded immediately — it is never written to disk, never saved to a database, and never uploaded to any cloud storage.

What Syllabi retains is the generated course content — the modules, assessments, and learning objectives that were built from your document. The source document itself leaves no trace after processing.

Every course, module, learner record, and assessment in Syllabi is scoped to a specific organization account. Database rows are tied to your org ID — no user or organization can access another organization's content.

Role-based access control (RBAC) further restricts access within your organization: admins, L&D managers, compliance officers, and learners each see only what their role allows. Invitations are required to join an organization; there is no way to discover or access other tenants' data.

Syllabi uses Anthropic Claude and OpenAI APIs to generate course content. Both providers operate under policies that explicitly prohibit using API inputs for model training.

Your documents and the text extracted from them are sent to these APIs only to generate your course — they are not retained by the AI providers for training purposes, and they are not used to improve Syllabi's own models. What you upload stays private to your organization.

All data exchanged between your browser and Syllabi travels over HTTPS (TLS 1.2+). This includes document uploads, course generation requests, API calls, and learner activity. Connections over plain HTTP are automatically upgraded.

Data stored in the database (courses, learner records, assessments, compliance data) is protected at rest by Neon Postgres's managed encryption. Authentication tokens are signed with a secure secret and expire after 7 days.

Access to your organization's data is gated by two layers of control: authentication (proving who you are) and authorization (confirming what you're allowed to do).

Authentication uses passwordless magic links — no passwords to phish or breach. Authorization uses RBAC with six distinct roles, each with narrowly scoped permissions.

Syllabi engineering staff does not access your organization's course content or learner data in normal operations. Access for support purposes (e.g., debugging a reported issue) requires explicit escalation and is not routine.

Generated courses are private by default. They are accessible only to authenticated members of your organization with appropriate roles.

Shareable public links — which allow anyone with the link to view a course — are available as an optional feature and must be explicitly enabled by your organization's L&D Manager or Admin. Public links can be revoked at any time, immediately revoking access for all external viewers.

Syllabi is hosted on industry-standard cloud infrastructure with proven security track records. We do not build custom data centers or run our own hardware.

We're honest about where we are. Here's what's planned but not yet live:

If a specific compliance requirement is blocking your evaluation, email us — we may be further along than this list suggests, or can accelerate what you need.