Privacy

qed’bop is a small tool with a small data footprint by design. This page describes, in plain language, what we collect, why we collect it, and what happens to it.

The short version: students are anonymous and never tracked; teachers who use the demo identity store data locally in their own browser; teachers who sign in with a real account give us only what’s needed to recognize them next time. We don’t sell data, and we don’t run third-party ad trackers. We use privacy-preserving, cookieless analytics on teacher-facing pages only — never on student pages.

Students

The student page at /a/[slug] doesn’t require a login and doesn’t set any first-party cookies. Everything a student sees — the poem, the videos, the questions, the expiration date — is encoded in the URL the teacher shared with them. The page makes no AI calls. There is no student-side analytics SDK.

Videos are embedded from YouTube. When a student plays a video, YouTube’s servers see that view and apply YouTube’s own privacy practices. qed’bop has no involvement in or visibility into what YouTube records about a viewer.

Teachers using the demo identity

Some pages let a teacher experiment with a saved-lesson workflow by picking a demo identity (John or Dante) from the sign-in menu. That choice is stored in your browser’s localStorage only. It never leaves your device. Clearing your browser data clears it.

Teachers using a real account (when enabled)

When a teacher signs in with a real account, authentication is handled by a third-party provider (Clerk). We receive from Clerk: an opaque user ID, the email address you signed in with, and a display name if you provided one. We use those exclusively to recognize you between sessions and to associate saved lessons with your account.

Clerk’s own privacy practices are governed by its policy, available at clerk.com/legal/privacy. If you sign in with a Google or other SSO account, the third-party identity provider also receives sign-in events as part of OAuth.

We do not, at present, send marketing email. We do not share your email address with third parties for marketing.

Assignment data

All of an assignment’s configurable state — which poem, which videos, which audience level, the question text, the expiration date — rides in the URL itself. Sharing a URL is, by design, sharing the entire state of the lesson. There is no server-side record of which teacher created which URL or which students opened it.

One database table (VideoAnnotation) stores per-video annotation overrides editable through a private admin tool. Those rows contain interpretive notes about recordings; they don’t contain anything about students or teachers.

AI-generated content

Discussion questions, teacher commentary, and chat answers are generated by Anthropic’s Claude API. When a teacher requests generation, we send Anthropic the inputs to the prompt: the poem text (already public), the audience level, the topics and lengths you selected, and metadata about the videos. We do not send your identity, email, or any student information — there isn’t any to send.

Generated content is cached for seven days keyed to the inputs, so an identical request returns an identical result without a fresh API call.

Analytics

We use Vercel Web Analytics and Vercel Speed Insights to understand, in aggregate, how teachers use the site — which pages are visited and whether the lesson-builder flow is working — and to monitor real-world performance (load times and similar metrics). Both are cookieless: they set no cookies, use no localStorage, and build no cross-site or per-person profile. They record anonymized, aggregated events only.

Student pages are excluded entirely. On a student assignment page (/a/…) neither analytics script is even loaded — not loaded-and-filtered, but never present. So the “students are never tracked” promise above holds at the level of the code, not just our intentions.

Logs and operational data

Our hosting provider (Vercel), our database provider (Neon), and our DNS provider (Cloudflare) keep standard access logs (IP addresses, request paths, response codes, query metadata) for operational and security purposes. We do not retain or analyze those logs ourselves except when diagnosing a specific incident.

Children

qed’bop is designed for teacher-mediated use in classrooms, including classrooms with students under 13. Because students never sign in, never provide any personal information, and are not tracked, qed’bop’s student-facing surface collects no information from children directly.

Your choices

If you have a real account and want it deleted, email privacy@qedbop.com from the address on file and we will delete it within thirty days. Demo-identity data can be cleared at any time by clearing your browser data.

Changes

If this policy changes materially we’ll update the “last updated” date at the top and post a notice on the home page.

Who we are

qed’bop is operated by [ENTITY NAME], a [STATE]-based entity. Contact: hello@qedbop.com.