← Study Hub

District review brief

Study Hub security and privacy whitepaper

A technical and operational overview for school technology, privacy, curriculum, and procurement reviewers.

Document scope

This document describes the controls implemented in the current Study Hub service at studyhubstudent.com. It is intended to support—not replace—a district's own legal, privacy, curriculum, accessibility, and vendor review. Study Hub does not claim an independent security certification, penetration-test opinion, or regulatory attestation unless one is supplied separately in writing.

Service purpose and data flow

Study Hub lets students create typed-answer practice sets from notes and approved uploads, collaborate within class Study Circles, optionally import read-only Google Classroom information, and share view-only progress with an approved parent account. Student-provided material may be sent to the OpenAI API to generate questions. Answers are graded inside Study Hub using deterministic comparison logic rather than a new AI request.

Hosting and subprocessors

  • Cloudflare Sites, D1, and R2: application delivery, structured records, and private file storage.
  • Supabase Auth: account authentication and session issuance.
  • OpenAI API: generation of practice questions from user-selected study material.
  • Google: optional read-only Classroom connection authorized by the user.
  • Stripe: hosted subscription checkout and billing management. Study Hub does not store complete card numbers.

Identity and authorization

  • Session tokens are placed in Secure, HTTP-only, SameSite cookies.
  • Private API routes resolve the authenticated user before returning account data.
  • Study sets and digital-library items are scoped to their owner.
  • Class materials require active class membership; removal is limited to the creator.
  • Parent access is view-only and begins only after the student accepts the link request.
  • Administrative functions require an explicit server-side administrator allowlist.

Data protection

  • HTTPS/TLS protects traffic in transit, with HSTS enabled.
  • Private uploads are stored with randomized object keys and retrieved only through authorized application routes.
  • Google refresh tokens are encrypted with AES-GCM before database storage.
  • Stripe webhook signatures are verified before billing status is changed.
  • Browser headers restrict framing, MIME sniffing, referrer leakage, browser permissions, cross-domain policy files, and executable/resource origins.
  • Authenticated API responses are marked no-store to reduce unintended browser or intermediary caching.

Abuse and cost controls

  • Generation allowances are plan-specific: Study Hub includes 30 monthly credits, 6 daily credits, and 2 hourly requests; Hub+ includes 39 monthly credits, 8 daily credits, and 3 hourly requests; Hub++ includes 48 monthly credits, 10 daily credits, and 4 hourly requests.
  • Only one generation may run per student, with a platform concurrency ceiling.
  • Generation output tokens are capped, and failed generations restore reserved credits.
  • Study/class uploads are limited to 250 MB per user and digital-library uploads to 500 MB per user.
  • Usage records include feature, model, status, and input/output token counts for operational review.

Google Classroom

The Classroom connection is optional and individually authorized by each student or other Study Hub user. Study Hub requests only read-only access needed to identify that user's classes and import course materials. A district administrator may globally approve the OAuth application in Google Workspace, but does not manage Study Hub accounts or receive access to student Study Hub content through this integration.

Users can disconnect Classroom from Study Hub or revoke access through their Google Account. Either action stops future imports. If Google reports that the application or refresh token was revoked, Study Hub clears the stored refresh token and marks the connection inactive; no new Classroom content is imported until the user reconnects. A material previously copied into Study Hub remains as a Study Hub material after disconnect or revocation and can be removed by the user under the normal class-material controls.

Student privacy and sharing

Study Hub does not sell student information or use it for targeted advertising. User-created practice is private unless the user deliberately shares it with a Study Circle. Class materials are visible only to members of that class space. Parent dashboards expose learning metrics only after student approval. Schools remain responsible for determining whether use is appropriate under FERPA, COPPA, local records rules, and district policy.

Retention and deletion

User-created study sets, shared materials, and digital-library records remain until removed by an authorized user or through an account-deletion process. Disconnecting or revoking Google Classroom does not delete materials that were already copied into Study Hub. Deleting a Study Hub account permanently removes the user's profile, practice data, answers, progress, uploads, library items, Classroom connection, and associated account records, subject to limited operational, billing, fraud-prevention, or legal records that may be retained when necessary. Access, correction, and deletion requests may be sent to privacy@studyhubstudent.com.

Vulnerability and incident contact

Report suspected vulnerabilities to security@studyhubstudent.com. Include the affected URL, reproduction steps, likely impact, and contact information. Testing must avoid unauthorized data access, service disruption, destructive activity, social engineering, and disclosure of another user's information. Report suspected privacy or student-data incidents to privacy@studyhubstudent.com. Study Hub will coordinate notice, containment, investigation, and remediation according to applicable law and any executed district agreement.

District network review

The primary domain is studyhubstudent.com. Districts may need to permit this domain and accounts.google.com for the optional user-authorized Google Classroom OAuth flow. Student browsers do not need direct access to Cloudflare, Supabase, OpenAI, or Google Classroom API infrastructure for normal Study Hub use. Google Classroom and payment features can be evaluated separately from core study-set access. The district review packet includes the requested OAuth scopes, lifecycle behavior, age and parent-authorization language, accessibility commitment, incident contact, and controlled pilot access terms. Questions from school reviewers may be sent to support@studyhubstudent.com.

Version: October 1, 2026.