Privacy
policy.

Account information. When you sign in with Google, we receive and store your name, email address, and profile picture from Google, along with the sign-in tokens needed to keep you signed in. When you sign in with an email link, we store your email address. If you complete onboarding, we also store the answers you choose to give (for example, your education level, field of study, and study goals).

Your study content. The core of the Service is content you create or upload:

• lecture audio you record in the app with your microphone, or upload as a file;
• slide and document files you attach (PDF and PPTX), including the text and images inside them;
• transcripts, notes, flashcards, quizzes, study sessions, and other materials generated from your content, including your edits to them;
• your answers to study questions (stored so mastery and the Estimated Grade can be computed), and your messages in study- and note-chat features;
• feedback and reports you submit, including any screenshot you attach.

Referral information. If you use or share a referral code, we store the code and the relationship between the referring and referred accounts.

Usage and billing records. We keep records of how you use metered features (for example, note generations, study generations, live-transcription sessions, and smart edits), your plan and billing status, and technical logs of generation runs — so we can enforce plan limits, bill correctly, and debug failures.

IP addresses. We record the IP address associated with your sign-ins and with referral-code redemptions, and we use IP addresses in rate-limiting counters. We use this information only for security, fraud prevention, and referral-abuse prevention — it is never shown to other users.

Device and log information. Like most web services, our servers and error-monitoring receive standard technical information such as browser type, pages visited, and error details when something goes wrong.

Cookies and on-device storage. See Sections 07 and 08 for the specifics of cookies, analytics, and what the app stores in your browser.

Lectify's features are powered by third-party AI providers. To deliver a feature, we send the relevant content to the provider that powers it, and receive the output back. The specific providers change as the product evolves; as of the date below, they include:

• OpenAI — transcribes uploaded lecture audio and helps plan the structure of your generated notes; also creates the text embeddings used to organize study material.
• Google (Gemini) — writes note sections from your transcripts, analyzes your slide files (slide files are sent to Google for analysis, including their images), generates study materials, and grades free-form answers.
• AssemblyAI — powers live transcription. During a live session, your microphone audio streams from your browser directly to AssemblyAI over an encrypted connection; the live transcript text is then sent to Lectify.
• Cerebras — powers interactive features such as Ask Notes and Smart Edit, receiving your question or instruction together with the relevant note content. It also helps select relevant visuals for generated notes, which can involve processing the note text and extracted images from your slides.
• Groq — an alternate audio-transcription provider we may route uploaded audio to.

We may swap, add, or remove providers at any time without updating this list, as long as what we've promised here stays true: providers receive your content only to provide their service to us under their API terms, and none are granted the right to sell your content. If a change materially alters how your content is processed — for example, sharing new kinds of data or for new purposes — we will update this policy as described in Section 16.

Beyond the AI providers above, we share information only with the service providers needed to run Lectify, and only what each needs. As of the date below, they include:

• Stripe — payment processing, subscriptions, and billing. Stripe receives your email and payment details directly; full card numbers never touch Lectify's servers.
• Google — sign-in with Google (authentication only).
• Resend — delivers our sign-in link and service emails to your email address.
• PostHog — product analytics, error monitoring, and session replay, as described in Section 07.
• Railway — hosts our servers and storage, where your account data and uploaded files live.

We may also disclose information if required by law or legal process, to protect the rights, safety, or property of Lectify, our users, or others, to investigate fraud or abuse, or as part of a business transfer (for example, if Lectify is reorganized into a company or acquired — in which case this policy continues to apply to your information).

We never share your recordings, notes, or study materials with other Lectify users, and there is no public sharing of your content in the product. The only exception is images you explicitly choose to share yourself (like badge or recap cards): those are composed on your device and shared only through your own device's share action.

We use a small number of cookies and browser-storage entries:

• Sign-in cookies — keep you signed in and protect sign-in forms against forgery (session, callback, and CSRF cookies). These are essential and expire on a rolling basis.
• Preference cookie — remembers your light/dark theme choice.
• Analytics cookie — PostHog's identifier, used for the analytics described in Section 07.
• Browser storage — the app stores working data locally in your browser, such as unsaved note drafts, in-progress study state, and (for up to 24 hours) a local copy of an in-progress recording so an interrupted session can recover. This data stays on your device, is scoped to your account, and can be removed by clearing the site's data in your browser.

We do not use advertising cookies or cross-site trackers.

Payments are processed by Stripe through Stripe-hosted checkout and billing pages. Lectify stores your Stripe customer and subscription identifiers, your plan, and billing status — not your card details. Stripe's handling of your payment information is governed by Stripe's own privacy policy.

In the app, you can delete individual notes, classes, study sessions, and eligible uploads using the available deletion controls. Deleting a note also deletes its associated audio, slides, transcript, note visuals, and note-specific conversations. A saved study session and its progress are kept until you delete that study session or your account; deleting a source note removes its link from the saved session. Stored files covered by a deletion are removed through a durable cleanup process.

To delete your entire account, email support@lectify.aifrom your account’s email address. We verify the request, then delete the account, its sessions, and its product data — notes, recordings, slides, transcripts, study materials, and related records — and queue permanent deletion of the stored files. Active subscriptions are cancelled as part of deletion.

A minimal payment-customer identifier may be retained for up to 180 days solely to prevent a late billing event from recreating a subscription, and limited payment, security, and accounting records may be retained where required for fraud prevention, legal compliance, or bookkeeping. Encrypted backups may persist for a limited period before they cycle out; backed-up data is not used to keep providing a deleted account.

Data already stored in your browser (like an offline draft) lives on your device; clearing the site's data in that browser removes it immediately.

We protect your information with measures appropriate to a service of our size: all traffic is encrypted in transit (HTTPS, with strict transport security), the app enforces a content-security policy and related browser protections, access to your content requires authentication and is checked against your account on every request, sign-in links expire after 15 minutes, and rate limits and abuse controls protect accounts and the Service.

No online service can guarantee perfect security. Your account is reachable by whoever controls your email inbox or Google account, so securing those (ideally with two-factor authentication) is the single most effective thing you can do to protect your Lectify data. If you believe your account has been compromised, contact us immediately.

You can access and edit your content and account details in the app at any time. In addition, wherever you live, you may email support@lectify.aito request: a copy of the personal information we hold about you, correction of inaccurate information, deletion of your account and data (Section 11), or an export of your content. We will verify the request came from the account’s email address and respond within a reasonable time, and we will not discriminate against you for exercising these rights.

Depending on where you live, local law may give you additional rights regarding your personal information. We honor valid requests under applicable law. Because we do not sell personal information or use it for targeted advertising, there is nothing to opt out of on that front.

Lectify is operated from the United States, and your information is processed and stored on servers in the United States (and by service providers that may process data in the United States). If you use the Service from outside the United States, you understand that your information will be transferred to and processed in the United States, where privacy laws may differ from those in your country.