Architecture

The application is delivered over HTTPS through Cloudflare. Application records are stored in Cloudflare D1, private user files in Cloudflare R2, and authentication identities in Supabase Auth. Payment details are handled by Stripe rather than stored by Study Hub.

Student content standards

Study Hub screens new uploads, pasted materials, user-facing text, and generated study content for sexual exploitation, explicit material, hateful or abusive language, threats, graphic violence, and dangerous content. Academic discussion of history, literature, science, and health is considered in context. Documents, images, EPUB content, and supported audio are checked before acceptance; files that are unreadable or too large to check are rejected. If the content-check service is unavailable, new content cannot be accepted. Automated filters can make mistakes and do not guarantee that all inappropriate content will be detected. External provider links are checked as submitted text; Study Hub does not inspect the full content of third-party sites.

Access controls

Authentication tokens are stored in secure, HTTP-only, SameSite cookies.
API routes verify the current user before returning private information.
Study sets and digital-library records are restricted to their owner.
Course materials require active class membership.
Parent dashboards require a student-approved parent link.
Administrative actions require an explicit administrator allowlist.

Data protection

TLS protects data in transit.
Google Classroom refresh tokens are encrypted with AES-GCM before storage.
Uploaded files use private object storage and randomized object keys.
Stripe webhook signatures are verified before subscription data is changed.
Security headers restrict framing, content types, browser permissions, referrers, and resource loading.

Responsible reporting

Security researchers and school technology teams may report a suspected vulnerability to security@studyhubstudent.com. Please include the affected URL, reproduction steps, potential impact, and a safe way to follow up. Do not access, alter, retain, or disclose another user's information. Do not use testing that disrupts service or degrades availability.

Security and privacy contacts

Security reports: security@studyhubstudent.com
Privacy or data requests: privacy@studyhubstudent.com
Account and product support: support@studyhubstudent.com

Google Classroom approval model

Each student or other Study Hub user individually authorizes their own Google Classroom connection. District administrators are not expected to manage Study Hub accounts or view student Study Hub content. A Google Workspace administrator may globally approve the Study Hub OAuth application so users in the district can grant the requested read-only Classroom permissions to their own information.

Disconnecting Classroom stops future imports while materials already copied into Study Hub remain under the user's control. If Google revokes the application or a refresh token becomes invalid, Study Hub marks the connection inactive, clears the stored refresh token, and imports no new Classroom content until the user reconnects. Account deletion permanently removes the user's Study Hub account data.

Open the district network review checklist →

Read the Study Hub district security whitepaper →

Last reviewed: October 1, 2026.