Getting TA39 approved at your school shouldn't be the hard part.
Everything your IT team needs — privacy documentation, compliance agreements, and configuration guides — in one packet. Most schools complete approval in under a week.
We know how this works. You've seen the product, your teachers are interested, and now you need to get it past IT. We've built the approval process to be as clear and complete as possible — so you can hand your IT administrator a single packet and move forward.
TA39 is 1EdTech TrustEd Apps endorsed, LTI 1.3 certified, and data privacy certified. We comply with FERPA, COPPA, and GDPR. All documentation is available upfront — no NDAs required to review it.
What's in the IT Approval Packet
One packet, everything your IT team needs to review. Request it and we'll send it within one business day.
Privacy Policy
How we handle data: what we collect, what we don't, how long we keep it, and who has access. No advertising. No data resale. No exceptions.
Data Privacy Agreement
A formal agreement covering student data handling that complies with FERPA, COPPA, and applicable state-level student privacy laws. Ready to sign or adapt to your district's template.
Source Provider Letter
A standard vendor letter confirming TA39's data practices, security posture, and compliance status — the kind your procurement or IT team typically requires.
Configuration Guide
Step-by-step instructions for Google Admin Console setup, domain whitelisting, and LMS integration (Google Classroom or Canvas via LTI 1.3).
Built for school IT requirements
1EdTech TrustEd Apps Endorsed
Independently evaluated against the 1EdTech TrustEd Apps program for data privacy, security, and interoperability standards.
LTI 1.3 Certified
Standards-based integration with your LMS. Students submit and receive feedback where they already work — no separate login required.
Data Privacy Certified
Compliant with FERPA, COPPA, and GDPR. All data encrypted in transit (TLS 1.2+) and at rest. No student data used for model training.
Cloud-based, no on-premise setup
Nothing to install on school servers. Configuration requires only Google Admin Console whitelisting and optional LMS integration.
Google Classroom & Canvas
Native integration with the platforms schools already use. Class rosters, assignments, and feedback sync through existing workflows.
Dedicated school support
A real person to answer IT questions during setup — not a knowledge base. Most configurations are completed in a single session.
What the approval process typically looks like
Request the packet
Reach out through the contact page or ask your TA39 contact. We'll send the full IT Approval Packet within one business day.
Hand it to your IT team
The packet is designed to answer the questions IT administrators typically ask — without requiring a call or back-and-forth.
Review and configure
Your IT team reviews the documentation and follows the configuration guide. If anything needs clarification, we're available directly.
Teachers are ready to start
Once approved, teachers can log in through Google SSO or the standalone app. The PD program helps them use it well from day one.
Common IT questions
Where is student data stored?
All data is stored on encrypted servers in the United States. We use industry-standard encryption in transit (TLS 1.2+) and at rest (AES-256).
Is student data used to train AI models?
No. Student writing and teacher feedback are never used to train or fine-tune any AI model. This is a contractual commitment, not just a policy.
What authentication methods are supported?
Google SSO (via Google Workspace for Education) and LTI 1.3 launch from Canvas or other supported LMS platforms.
What domains need to be whitelisted?
The configuration guide in the IT Approval Packet includes the full list of domains and IP ranges. Typically two to three domains.
Can we use our own Data Privacy Agreement template?
Yes. We provide a standard DPA, but we're happy to work with your district's preferred template. Most adaptations are completed within a few days.
Is there a minimum contract or commitment?
No long-term commitment required for pilots. Schools can start with a single-term pilot and expand from there.
Ready to get started?
Request the IT Approval Packet, or reach out with any questions your IT team has. We're happy to join a call if that's easier.