Review the boundaries before you rely on the product
Explore how Synlecto separates lecture source, generated study support and learner activity; what accessibility work is currently visible; and where institutional claims must stop.
SynlectoPublic trust review · evidence before claimsGenerated study state is kept distinct from raw source material.
Reviewers can follow the route from source evidence to the student-facing guide without treating a complete raw transcript as normal synced study state.
- Raw transcript is not normal synced study state
- Short evidence excerpts support source return
- User content is not used to train models
Current position, known limits and review routes.
This page distinguishes current product controls from roadmap or controlled-review work. Compatibility with lecture systems does not imply endorsement, institutional adoption or readiness for procurement.
Current public readiness posture
Last reviewed: 2026-05-11
Synlecto is a lecture-learning system for higher education. It turns lecture material into structured study support, active recall, and next-step revision, with academic quality controls, accessibility-first design, and institution-ready deployment.
Synlecto is not a generic AI summary app. It is a quality-gated lecture-learning layer designed for university teaching, accessibility, and term-long revision.
This is not a legal, procurement, DPA, VPAT, SOC 2, ISO 27001, or accessibility conformance certificate. Formal evidence is handled through controlled institutional review when required.
Data handling
The product is designed around lecture-source study support, not open-ended data capture.
- Synlecto retains the generated guide and a cleaned source snapshot used to support source moments, evidence, quality checks, and guide continuity.
- Synlecto does not describe itself as retaining the raw original transcript in the standard lecture workflow.
- Synlecto does not describe itself as retaining the raw media file in the standard lecture workflow.
- Institution-uploaded or institution-linked content should be treated as institution-scoped for contractual and operational purposes and should not be reused across institutions without explicit permission.
Accessibility
Accessibility is treated as an ongoing product responsibility with visible controls and review evidence.
- Synlecto is designed with accessibility-first principles and aims toward WCAG 2.2 AA-aligned delivery, supported by automated checks, manual assistive-technology testing, and a published accessibility statement with known limitations and ongoing improvements.
- Synlecto supports accessibility-first study through keyboard-oriented controls, reading preferences, transcript-linked study support, automated checks, and manual assistive-technology testing evidence.
- Known limitations and ongoing improvements are stated openly rather than being hidden behind a blanket conformance claim.
Security and privacy operations
The public posture is intentionally specific about current controls and careful about formal assurance claims.
- Synlecto uses authenticated access controls, server-side verification, rate limiting, security headers, and privacy-aware observability.
- Sensitive content is not sent into analytics by default.
- Protected API flows are intended to require bearer-authenticated access in production, and legacy fallback authentication paths should be disabled in production.
- Synlecto has a documented security baseline and a roadmap toward stronger formal assurance suitable for institutional review.
University review boundaries
Institutional review begins with bounded questions about controller, processor, source ownership and support expectations.
- Direct-to-student use: Synlecto acts as controller for account, product, and billing data.
- Standard institutional deployment: the preferred model is that the university acts as controller and Synlecto acts as processor for student, lecture, and guide data processed within the contracted educational service.
- Synlecto may remain an independent controller for limited operational data such as account administration, billing, service security, fraud or abuse prevention, and clearly described product-improvement telemetry.
- Any future pilot shape remains subject to formal readiness review and named support ownership.
What is deliberately not claimed
Synlecto keeps roadmap-only items visible so students, universities, and reviewers do not confuse compatibility or intent with completed formal integration.
- SAML is roadmap or controlled-review work unless separately agreed.
- Shibboleth is roadmap or controlled-review work unless separately agreed.
- Entra enterprise SSO is roadmap or controlled-review work unless separately agreed.
- LTI 1.3 is roadmap or controlled-review work unless separately agreed.
- Canvas-native LMS integration is roadmap or controlled-review work unless separately agreed.
- ISO 27001 is roadmap or controlled-review work unless separately agreed.
- SOC 2 is roadmap or controlled-review work unless separately agreed.
- formal framework or reseller route if not yet secured is roadmap or controlled-review work unless separately agreed.
- campus-wide rollout automation is roadmap or controlled-review work unless separately agreed.
Review routes
Start with the public material below. Institution-specific security, privacy, accessibility and support questions require controlled review.