Monitoring
Compliance
We understand the unique regulatory landscape of the education industry. Our platform is built and maintained with a focus on adhering to key security, privacy, and accessibility standards to give you peace of mind.

SOC 2® Type 1

1EdTech TrustEd Apps Certified
Resources
Explore our latest security and compliance resources and reports.
Privacy Policy
A detailed explanation of how we collect, use, and protect personal data, in compliance with regulations.
Terms & Conditions
The legal agreement that governs the use of our products and services.
Accessibility Charter
Our commitment to making our products and services accessible to all users, including those who rely on assistive technologies, in compliance with standards like WCAG.
Higher Education Community Vendor Assessment Tool Kit (HECVAT V3.06)
The Higher Education Community Vendor Assessment Tool Kit is used by colleges and universities to assess our security and privacy practices.
SOC 2 Type 1 Report
Service Organization Controls (SOC 2) (Type I) trust services principles.
SOC 2 Bridge Letter
A formal statement confirming our controls have remained in place since our SOC 2 Type I audit. This document also serves to confirm that Stukent is currently in the observation period for our SOC 2 Type II report.
K-12CVAT: K-12 Community Vendor Assessment Tool Kit Lite-V4.1
The K-12 Community Vendor Assessment Tool Kit provides a standardized method for K-12 institutions to evaluate our security and privacy posture.
CTE - Higher Education Community Vendor Assessment Tool Kit (HECVAT V3.06)
A version of the Higher Education Community Vendor Assessment Tool Kit tailored specifically for evaluating the security and privacy controls of our CTE platform.
Responsible Adoption of AI Policy
As a leader in edtech, Stukent is committed to the responsible use of artificial Intelligence. This policy outlines our perspective, evolving guidelines, and ethical framework for integrating AI to enhance teaching and learning while mitigating risk.
FAQs
Answers to your top security and compliance questions
Subprocessors
Our commitment to security extends to the partners we choose to work with. We carefully vet and manage all of our subprocessors to ensure they meet our rigorous security and compliance standards. Below is a list of our subprocessors and a brief description of how we use them.
Attention
Purpose: Sales touchpoint capture/automation for business operations. Data Categories Shared: Business contact details and communications metadata for sales/implementation interactions (not Student Data unless a student directly engages in a sales context).
AWS
Purpose: Core cloud hosting/infrastructure (compute, storage, databases). Data Categories Shared: Customer Data stored in the Services (Registration/Account Data, User-Generated Content, Usage Data), backups, and security logs necessary to host and operate the platform.
Azure
Purpose: Hosting and managing some applications/data for scalability and availability. Data Categories Shared: Customer Data stored/processed in Azure-hosted components, operational telemetry needed to provide Services.
Azure Active Directory
Purpose: Identity and access management for secure user/system access. Data Categories Shared: Authentication and authorization metadata for workforce/system access; administrative access controls (not used to serve third-party ads).
Azure DevOps
Purpose: Developer services for planning, collaboration, and software deployment. Data Categories Shared: Software development artifacts; may include limited operational metadata needed for issue resolution (production data restricted in dev/test).
Cloudflare
Purpose: CDN and security protection against threats; performance optimization. Data Categories Shared: IP address, request metadata, security signals, and cached content necessary to deliver and protect web traffic.
Datadog
Purpose: Monitoring and analytics for infrastructure/app performance. Data Categories Shared: Operational logs, performance metrics, error telemetry; may include pseudonymous identifiers and request metadata as needed for reliability/security.
DigitalOcean
Purpose: Hosting/scaling specific parts of application environment. Data Categories Shared: Customer Data used in DigitalOcean-hosted components and related operational logs.
FormAssembly
Purpose: Web form collection and integration with internal systems. Data Categories Shared: Form submission content and contact details provided by the submitter (e.g., support, onboarding, sales/implementation forms).