Security Built for Canvas

Cidi Labs tools are built to support teaching and learning in Canvas without storing sensitive student records.

Security Through Simplicity

At Cidi Labs, we believe educational technology should enhance institutional workflows without expanding institutional risk. That philosophy shapes how we design and build our tools for the Canvas LMS.

Cidi Labs tools are tightly integrated with Instructure’s Canvas and built to support course design, accessibility, and workflow improvement directly within the LMS environment that institutions already use. Rather than replicating or replacing institutional systems, our tools extend and improve existing Canvas workflows.

Our products are intentionally designed to minimize the collection and storage of institutional and student data. We are not a student records platform, and we do not build external student data repositories. Instead, we focus on improving the quality, consistency, accessibility, and usability of Canvas courses while leveraging existing Canvas authentication, permissions, and governance structures.

How Cidi Labs Manages Data

Cidi Labs tools minimize the storage of institutional and student data while supporting the functionality required to improve Canvas workflows.

Our tools:

Cidi Labs does not:

Core course and user management remains within Canvas, while access control is managed through existing Canvas authentication and permissions.

Authentication and Access Controls

Cidi Labs tools leverage existing Canvas authentication and authorization workflows to help institutions maintain centralized user governance and access control.

Authentication is managed through the Canvas LMS, and access to Cidi Labs functionality aligns with the permissions and roles already established within Canvas. Users only access features and workflows appropriate to their existing Canvas permissions.

By leveraging existing Canvas authentication and role structures, Cidi Labs helps institutions avoid unnecessary credential sprawl while maintaining familiar governance and administrative controls.

Many workflows operate within existing Canvas permissions and authentication structures, helping institutions extend Canvas functionality without introducing disconnected user management systems.

Security Practices

and Operational Safeguards

Cidi Labs follows security-conscious operational and development practices designed to support the reliability and integrity of our tools and services.

Secure Development Practices

Our teams follow ongoing product maintenance, review, and issue remediation processes to support secure and reliable platform operation.

This includes:

Infrastructure and Hosting

Cidi Labs services are hosted in Amazon Web Services (AWS) environments and utilize industry-standard security and encryption practices to protect platform communications and infrastructure.

Our operational safeguards include:

Internal

Access Controls

Access to administrative systems and infrastructure is restricted to authorized personnel with appropriate operational responsibilities. Cidi Labs follows principles of limited access and role-based administrative controls to help reduce unnecessary exposure to institutional information and systems.

Security Documentation

Available Upon Request

Cidi Labs works with colleges, universities, and institutional review teams to support vendor review, procurement, and security evaluation processes. Documentation and policy materials are available for institutions that require more detailed information.

Available documentation may include:


For additional information or documentation requests, please contact our team.

Frequently Asked Questions

Do Cidi Labs tools store student data?
Answer: Cidi Labs tools minimize the storage of institutional and student data. Our products primarily work within existing Canvas workflows and do not function as student records systems or external student data repositories. While certain tools may access limited information required to support functionality, Cidi Labs does not store sensitive student records.
How does authentication work?
Answer:  Cidi Labs tools leverage existing Canvas authentication and authorization workflows. Users access Cidi Labs functionality through their Canvas accounts, helping institutions maintain centralized authentication and user management within their existing LMS environments.
Do you use Canvas permissions and roles?
Answer: Yes. Cidi Labs tools respect existing Canvas permissions and role structures. Access to features and functionality aligns with the permissions already established within Canvas, helping institutions maintain governance and role-based access controls through their LMS. These tools can be installed at the Canvas root account or in any sub-account within your Canvas instance.
Do your tools integrate directly with Canvas?
Answer: Yes. Cidi Labs tools are tightly integrated with Canvas and are designed to enhance existing teaching, learning, accessibility, and course management workflows within the LMS. Our tools work alongside Canvas rather than replacing institutional systems or creating separate learning environments.
What data does Cidi Labs access?
Answer: Cidi Labs tools access the information necessary to support product functionality within Canvas. Depending on the tool and workflow, this may include course content, user role information, accessibility scan results, or other LMS-related data required to deliver features and services.
Does Cidi Labs sell or share institutional data?
Answer: No. Cidi Labs does not sell institutional or student data, create advertising profiles, or share institutional data with third parties for marketing purposes.

Name

Position

Description