Privacy & student data

Start with student nicknames

Students use a teacher-created class login and do not need an email account. Use a first name or alias for Student Nickname. Do not include a student’s full last name. Keep personal access codes private and avoid entering sensitive personal information in business names, written work or feedback.

Before inviting students, teachers should confirm their school’s approval and data-handling requirements. If a school needs a specific storage country, agreement or retention period, contact Stephen before adding student records; those requirements have not been confirmed for this pilot.

What the Academy saves

Teacher accounts

Email address, account identifiers and email-provider account mapping. A name may be supplied when signing in through ChatGPT. Pilot access dates and status are also saved.

Classroom accounts

Class identifiers, nicknames, student usernames, login status and hashed personal access codes. The original personal access code is shown when created or reset; save it securely.

Learning records

Class and business names, team membership, launch plans, confirmed monthly decisions, forecasts, results, final pitches, individual contributions, rubrics, assessments and teacher feedback.

Pilot participation

Recruitment details supplied to Stephen, confirmation and setup status, and submitted weekly teacher feedback.

Sign-in and service operation

Session records, cookies and temporary sign-in rate-limit records. Hosting and authentication services also process technical requests and may keep their own operational logs.

Teacher email sign-in does not automatically subscribe that teacher to the VentureEd newsletter.

Who can see classroom work?

• The class teacher can view the class’s businesses, saved decisions, reports, contributions and assessments.
• Members of the same advanced business team share that business’s saved information, including team members’ nicknames, contributions and the business assessment. Individual contribution reflections are not private from teammates.
• The Academy owner administers access, reviews pilot feedback and can access stored records through administration and recovery backups when needed to operate the service.
• Service providers process information needed for hosting, storage, sign-in and support. The current setup uses ChatGPT Sites and Cloudflare hosting/storage, Supabase for teacher email authentication, and the email service used for support messages.

Other teachers do not receive access to your classes merely by joining the pilot. Public site access does not make saved class records public. Teachers control any reports or student files they download and share outside the Academy.

Cookies and Teacher Help

The Academy uses a secure sign-in cookie to keep a session open. Teacher sessions last up to 24 hours and student sessions up to eight hours unless ended or revoked sooner. Platform sign-in may use its own cookies.

Teacher Help searches prepared answers in the browser. It does not send questions to GPT or another AI service, and it cannot inspect student work. Avoid entering student details or credentials in help searches.

Retention, backups and deletion requests

The November 2026 pilot has a planned 30-day classroom-record retention window after teaching access ends November 30. Eligible pilot teachers can review saved advanced results and download reports through December 30, 2026 (UTC), without editing or trading. Teachers should export needed evidence before that date and contact Stephen in advance if grading needs an extension. An independently active membership keeps its normal access.

Private recovery backups contain database records, including student credential hashes, but exclude active sign-in sessions. A daily backup task is configured. A downloaded backup may also be kept separately for recovery. Uploaded resource files and external authentication-provider records are outside the database backup.

To request access to, correction of or deletion of records, email Stephen from your teacher account address. Identify the class using its name and describe the request without sending student access codes. Students and families can contact their class teacher or Stephen.

Requests are handled manually after verifying the requester’s authority. Removing live records does not automatically remove older backup copies, downloaded reports or external authentication records. The response to a deletion request will identify the records and copies involved and any remaining follow-up; deletion is not complete merely because access is disabled. An owner-only cleanup preview and manual verification process are available. Automatic deletion is not currently enabled. Closing the review period does not itself erase records: removal of pilot records and copies must be completed and verified separately. No automatic backup-erasure period is currently configured.

Questions or a suspected privacy problem?

Email ventureed.business@gmail.com. Describe what happened and which class is affected. Do not send passwords, personal access codes, email verification codes or an unredacted student list.