At a Glance
Minimal Student Data
Students join with a class code and a username. No email, password, birthday, address, or phone number.
Encrypted Everywhere
All data is encrypted in transit (TLS/HTTPS) and at rest (managed database encryption).
Teacher-Controlled
Teachers own their content and control their classrooms. Student data exists to serve the teacher's instructional goals.
No Ads, No Selling Data
We do not run third-party ads, and we do not sell, rent, or share student data with advertisers or data brokers.
AI Suggests, Teachers Decide
AI never grades a student, and nothing it creates reaches a student until a teacher reviews it.
Student Names Replaced for AI
Student names are replaced before anything is sent to our AI provider, which does not train on our data.
Our Approach to Privacy
Honeycrane Academy is a classroom management and analytics platform built for teachers. Our product helps educators author interactive lessons, assign them to students, grade responses, and understand how their students are performing over time.
We designed the platform from day one with a privacy-first architecture. Rather than collecting student data and then figuring out how to protect it, we chose to collect as little as possible in the first place.
Our guiding principles:
- Minimal collection. We only collect what is necessary to deliver the educational service. For students, that means a username, the classrooms they are in, their work, and the results their teacher needs to see.
- Purpose limitation. Student data is used only to provide the educational service to the teacher or organization that set up the classroom. We do not use it for advertising, or to build profiles for any other purpose.
- Teacher control. Teachers decide what content to assign, which students are in their classroom, and how analytics are used. We provide the tools; teachers make the decisions.
- AI suggests, teachers decide. Our AI features draft and suggest. A teacher reviews everything before it counts toward a grade or reaches a student.
- Transparency. Our Privacy Policy says exactly what we collect, why, who processes it, and how long we keep it.
Student Privacy
Students on Honeycrane Academy are lightweight entities. They are not traditional user accounts. Here is exactly what we collect and what we do not.
What we collect from students
- A username. Entered by the student or assigned by the teacher at enrollment. We do not require or recommend that real names be used. A nickname, initials, or student number works perfectly.
- Classroom enrollment. Which of the teacher's classrooms the student has joined.
- Assignment and Live Quiz responses. Answers to questions within lessons, quizzes, and live quizzes assigned by their teacher.
- Progress metadata. When an assignment was started and submitted, and how long it took.
- Scores and teacher feedback. The grades and comments their teacher gives.
- Results we calculate. Skill results, "Needs practice" flags, and the reasons a student may need attention, shown to the teacher.
What we do NOT collect from students
- No email address
- No password
- No real name (unless one is used as the username)
- No date of birth or age
- No home address or phone number
- No analytics or advertising tracking: student pages never load Google Analytics
- No photos, videos, or biometric data
- No social media accounts or external identifiers
One exception to note: if a teacher adds a YouTube or Vimeo video to a lesson, the video loads from that provider when the student watches it, and the provider may set its own cookies.
How students sign in
Students join a classroom by entering a class code (provided by their teacher) and a username. That's it. No account creation, no email verification, no password to remember or reset. This model is similar to how platforms like Kahoot handle student access: minimal friction, minimal data.
A session token is stored in a cookie that scripts on the page cannot read. It expires after 7 days or when the student signs out. Students can return to their classroom at any time by re-entering their class code and username.
How student data is used
Student responses and progress data exist for one purpose: to help their teacher understand how they are performing. Our analytics show teachers which questions students missed, identify patterns across assignments, and highlight where individual students may need additional support.
We do not use student data to build advertising profiles, train AI models, sell to third parties, or for any purpose outside the educational relationship between the student and their teacher. When a teacher uses an AI feature, some student work is processed by our AI provider with names replaced, as described in AI and Student Data.
Consent and parents
Students never accept our terms themselves. Their use is covered by the acceptance of the organization whose teacher sets up the classroom, and that teacher, school, or organization is responsible for any notice and consent the law requires. A parent or guardian who wants to review, correct, or delete a student's information should ask the student's teacher or school, who can do it in Honeycrane at any time. Parents can also , and we will work with the teacher or school to respond.
AI and Student Data
Teachers on plans that include AI can use it to draft lesson modules and review materials, suggest skills for questions, suggest scores and feedback on written answers, and ask the AI Teacher Assistant questions. Students never use AI features.
Teachers decide
- AI never puts a grade on a student's work. A suggested score counts only once a teacher accepts it, and until then the answer counts as ungraded.
- Nothing AI creates reaches a student unless a teacher reviews it and chooses to save, assign, or send it.
- An organization's administrators can turn AI off for the whole organization, turn it off for one teacher, and set a monthly limit for each teacher.
Student names are replaced
Before every request to our AI provider, we replace the names of students in the teacher's classrooms with placeholders such as "Student 1", and put them back before the teacher sees the result. We do not keep a record of which placeholder stood for which student. Replacement works by matching class rosters, so it has limits, for example with names that are also common words, or text inside an image. Our Privacy Policy lists every limit, and we ask teachers to leave student details out of what they give AI.
What reaches our AI provider
- Score suggestions send the question, its rubric and sample answer, and the student's answer, with names replaced.
- Review materials send skill results and the questions missed, never student names or students' written answers.
- The AI Teacher Assistant can look up classroom analytics, such as averages and completion, with names replaced. It never looks up students' written answers.
- Lesson drafts and skill suggestions send the teacher's own description, material, and questions. Files a teacher adds are read in their browser and never uploaded.
Our AI provider
Our AI features run on Claude, from Anthropic, through its commercial API. Anthropic does not train its models on what we send. It deletes our requests and their results within 30 days, except that requests it flags under its Usage Policy can be kept for up to 2 years (and its safety scores for up to 7), and information can be kept longer where the law requires.
On our side, the content of AI requests, including drafts that were never saved, is deleted 7 days after the request finishes, and AI Teacher Assistant conversations are not stored on our servers. A reply a teacher rates is kept for 180 days, with student names replaced, so our team can improve the assistant's help content.
Teacher & Administrator Data
Teachers and administrators are the primary users of Honeycrane Academy. They create full accounts with the following information:
- Username and email address: Used for sign-in, account recovery, and service emails (billing, trial reminders, and the weekly classroom summary, which teachers can turn off).
- Password: Hashed and salted before storage. We never store or have access to plaintext passwords. Teachers can also sign in with Google.
- Organization and role: The organizations a teacher belongs to, and whether they are an administrator or a teacher in each.
- AI activity: Requests to AI features and their results (kept 7 days), ratings of AI Teacher Assistant replies (kept 180 days), and usage records that hold counts and credits, not content.
- Payment information: Handled entirely by Stripe. We do not store credit card numbers, CVVs, or bank account details on our servers.
Teachers also create content (lesson modules, classrooms, assignments) and manage student rosters. This content belongs to the teacher's organization. The full list is in our Privacy Policy.
Security Practices
We take the security of our platform seriously. Here is how we protect data at every layer:
Encryption
- In transit: All connections use TLS (HTTPS). Data moving between your browser, our application servers, and our database is encrypted using industry-standard protocols.
- At rest: Our database uses managed encryption provided by our hosting infrastructure. Data stored on disk is encrypted and inaccessible without proper authentication.
Authentication & Access Control
- Teacher/admin sessions: Kept in a cookie that scripts on the page cannot read, which expires after 7 days or at sign-out. API requests use Bearer token authentication.
- Student sessions: A separate session scoped to the student's classrooms, in the same kind of cookie, expiring after 7 days or at sign-out. There is no persistent student account.
- Password storage: All passwords are hashed and salted using industry-standard algorithms before storage.
- Role-based access: Teachers can only access classrooms and students within their own organization. Students can only access assignments in classrooms they have joined.
AI Safeguards
- Student names are replaced before every request to our AI provider, and restored only for the teacher.
- Material a teacher adds is sent as reference text, never as instructions to the AI.
- The AI Teacher Assistant reads data only through read-only lookups, never students' written answers, and opens a support ticket only after the teacher confirms.
- Replies are checked before they are shown: raw HTML is never rendered, and only links to pages in Honeycrane are allowed.
- AI requests are rate limited, and administrators can turn AI off or limit it per teacher.
Infrastructure
- Application hosting: AWS cloud infrastructure with automated deployments.
- Database: Managed PostgreSQL on DigitalOcean with automated backups, encryption at rest, and network isolation, with Cloudflare in front of the application.
- Media assets: Delivered via CDN with access controls.
- Secrets management: Environment variables and API keys managed through a dedicated secrets platform, never hardcoded or committed to source control.
Development Practices
- Input validation and parameterized queries to prevent injection attacks
- Rate limiting on authentication and sensitive API endpoints
- Automated CI/CD pipeline with build verification before deployment
- Dependency monitoring for known vulnerabilities
FERPA & COPPA Posture
FERPA (Family Educational Rights and Privacy Act)
FERPA protects the privacy of student education records and applies to educational institutions that receive federal funding. When an edtech platform processes student data on behalf of a school, it operates under the "school official" exception and must handle data in accordance with FERPA requirements.
Our position: We treat all student information in Honeycrane as education records, whether or not a student's username is their real name. Students often join with their first name, and a name combined with their work and scores can identify them. For this reason:
- We recommend teachers use non-identifying usernames (initials, student numbers, or nicknames) when possible.
- We use student data only to provide the educational service, and share it only with the service providers listed below.
- We replace student names before anything is sent to our AI provider.
- We provide data deletion capabilities so teachers and administrators can remove student records at any time.
We have not undergone a formal FERPA compliance audit. FERPA compliance is ultimately the responsibility of the educational institution, and our Terms of Service ask the teacher or organization that adds students to have the authority to do so. We support schools in meeting their FERPA obligations by keeping a minimal-data architecture and providing the controls schools need.
COPPA (Children's Online Privacy Protection Act)
COPPA applies to online services that collect personal information from children under 13. Honeycrane collects only what a classroom needs from students, with no contact information, and access is mediated entirely through the teacher, who provides the class code. Where COPPA applies, the teacher, school, or organization that sets up the classroom is responsible for giving notice and obtaining any parental consent before students use Honeycrane.
We do not use student information for advertising, student pages never load Google Analytics, and a student cannot discover or join a classroom without the teacher-provided class code.
Data Processing Agreements (DPAs)
For schools or districts that require a formal Data Processing Agreement, we are happy to work with you. Please to discuss your requirements. We are also open to participating in the Student Data Privacy Consortium (SDPC) National Data Privacy Agreement framework as our school customer base grows.
Third-Party Services
We use a limited number of third-party services to operate Honeycrane Academy. Here is who they are, what they access, and why:
| Service | Purpose | Data Access | Student Data? |
|---|---|---|---|
| Anthropic | AI features | AI requests: teacher prompts and material, questions, and student answers for score suggestions | Yes, with names replaced |
| Ably | Live Quiz updates in real time | Student usernames and quiz progress during a live quiz | Yes (usernames) |
| Stripe | Payment processing | Teacher billing info only | No |
| Google Analytics | Website traffic analysis | Page views and device information, never on student pages | No |
| Google OAuth | Teacher sign-in option | Teacher email (with consent) | No |
| Google reCAPTCHA | Bot protection on forms | Device and usage signals on pages with forms | No |
| Cloudinary | Media storage and delivery | Images uploaded to lessons and our website | No |
| AWS (EC2, SES) | Website hosting and email delivery | Application data in transit, and emails we send | Indirect (hosting, and the weekly summary email) |
| DigitalOcean | Database and application hosting | All application data (encrypted) | Indirect (hosting) |
| Cloudflare | Network in front of our application | Traffic to the application, encrypted | Indirect (in transit) |
| YouTube, Vimeo | Videos teachers add to lessons | Loaded directly by whoever watches the video | Only when a teacher adds a video |
What we do not do:
- We do not sell data to any third party.
- We do not run third-party advertisements.
- We do not share student data with advertisers or data brokers.
- We do not use student data to train AI or machine learning models, and our AI provider does not train on what we send.
- We do not build behavioral profiles of students.
Data Ownership & Retention
Who owns the data?
- Teacher content (lesson modules, assignments, classroom configurations) belongs to the teacher's organization. We do not claim ownership of content you create, including content drafted with AI.
- Student data (usernames, responses, progress) is held on behalf of the teacher's organization and exists solely to provide the educational service.
- Shared lessons: if a teacher chooses to share a lesson module in our public lesson library, the teacher still owns it, and grants us a license to offer it to other teachers, as our Terms of Service describe. Shared lessons must not contain student information.
Data retention
- Accounts and classrooms: Kept until the teacher deletes them or the organization is deleted.
- Student records: Teachers and administrators can delete student records at any time. Deletion is permanent and removes all associated response and progress data.
- AI requests: Content deleted 7 days after the request finishes. AI Teacher Assistant conversations are not stored on our servers.
- A few records outlast an account: support requests, usage records with the user removed, backups until they are replaced, and records the law requires. Anthropic keeps AI requests for up to 30 days.
Every retention period is listed in our Privacy Policy.
Data deletion
All deletion is fully self-service. Teachers and administrators can delete student records, classrooms, assignments, and their own account directly from the dashboard at any time. No support ticket or waiting period required. If you have any questions about data deletion or retention, feel free to .
Compliance Roadmap
We believe in being transparent about where we are today and where we are headed. Here is our honest assessment:
What we have today
- Privacy-first architecture with minimal student data collection
- Encryption in transit (TLS) and at rest (managed database encryption)
- Role-based access control with organization-scoped data isolation
- Secure authentication with HTTP-only cookies and hashed passwords
- No third-party advertising or data sales
- Student names replaced before AI processing, with an AI provider that does not train on our data
- AI that suggests and never grades, with teacher review and administrator controls
- Published, versioned Privacy Policy and Terms of Service that every teacher accepts
- Data deletion capabilities for teachers and administrators
What we are working toward
| Milestone | Status | Notes |
|---|---|---|
| Common Sense Privacy Evaluation | Planned | Free self-evaluation available; pursuing verified seal as customer base grows |
| SDPC National DPA | Planned | Will participate in the Student Data Privacy Consortium framework for school/district contracts |
| SOC 2 Type II | Future | Will pursue when enterprise contracts justify the investment (typically $30k-$80k for initial audit) |
| Formal FERPA Compliance Review | Future | Architecture is designed with FERPA principles; formal legal review planned alongside first school district engagement |
We are a small, focused team building alongside real educators. Our compliance posture will grow with our customer base, but our commitment to minimal data collection and student privacy is foundational and will not change.
Questions & Contact
We welcome questions about our privacy and security practices. Whether you are a solo teacher evaluating the platform, a school administrator conducting a vendor review, or a parent with questions about how your child's data is handled, we are happy to help.
You can also reach us through our .
For schools or districts requiring a Data Processing Agreement, vendor security questionnaire, or other formal documentation, please reach out and we will work with you directly.