Privacy Policy

A. Information you provide

• Account information: full name, email address, username, password.
• Eligibility (age gating): date of birth (birthday). We collect and store your date of birth to support age-gating and legal compliance. You must be 13+ to create an account (and older where required by local law). In the EEA and UK, we comply with the specific "age of digital consent" in each member state/jurisdiction, which may be 13, 14, 15, or 16 depending on where you are located.
• Non-account use for users without accounts: If you are not eligible to create an account (for example, because you are below the applicable age threshold), or if you otherwise choose not to create an account, you may still be able to use certain limited, non-account features. In that mode, we do not ask you to create an account and we do not request identifiers like your name, email address, or date of birth.
• Local-only LMS analytics: In non-account mode, LMS analytics (as described in Sections 1.C and 1.D) are collected and stored locally in your browser/device by default and are not sent to BetterCampus.
• Essential technical processing: We may still process limited technical information (such as IP address and security logs) strictly necessary to deliver and secure the Services.
• Optional profile details: school type (for example middle school, high school, college, graduate school, or other), school/institution name (including your university, if applicable), graduation year, study interests, and a profile photo (if you upload one).

Required vs. optional information. Your full name, email address, and date of birth are required to create and maintain an account. Optional profile details are optional. If you choose not to provide required account information, you will not be able to create an account (and certain account-only features may be unavailable).

• Support and communications: messages, bug reports, survey responses, and other information you send to us.
• User-generated content (UGC): themes, study sets, notes, prompts, screenshots, and files you upload to our AI study tools.
• Payments: if you purchase a subscription, we receive limited transaction details (for example plan, billing period, payment status, and partial payment identifiers). Payment card details are processed by our payment processor (for example Stripe) and are not stored by BetterCampus.

Social sign-in. If you use third-party sign-in (for example Google or Microsoft), that provider may share certain information with us (such as your name and email address) based on your settings and authorizations.

B. Information we collect automatically when you use the Services

• Device and network information: IP address, device identifiers, browser type, extension version, operating system, language, and time zone.
• In-product usage, diagnostics, and product analytics (PostHog; in-product only): pages and features you use within BetterCampus, clicks and feature interactions, in-product navigation signals, performance metrics, and error/diagnostic signals to help us operate and improve the Services. We configure product analytics to be privacy-protective (for example, avoiding collection of the contents of what you type into fields, limiting identifying metadata where feasible, and disabling session replay by default for EEA/UK users unless you opt in).
  • No browsing history: We do not collect or store your general web browsing history (for example, the sites you visit outside of BetterCampus). Our extension only interacts with the Document Object Model (DOM) of authorized LMS domains while those pages are active, and we do not use product analytics to track you across unrelated websites.
  • Controls: Product analytics are on by default, and you can opt out as described in Section 4 (and where required by EEA/UK ePrivacy rules, we request consent before enabling non-essential analytics).
• Approximate location: derived from IP address (for example, city and country).
• Local device storage: extension settings, preferences, and cached content stored on your device via browser storage.

C. LMS analytics (local-first) and sharing modes

LMS analytics are collected "local-first." In all cases, LMS analytics are first collected and stored locally in your browser/device by default. Whether anything is sent to BetterCampus depends on the mode below.

C.1 Core principle: local-first collection

• Local storage first. LMS analytics are collected and stored locally on your device (for example, in browser storage) by default.
• Sharing depends on mode and settings. In non-account mode, nothing is sent. If you create an account, we may send aggregated analytics by default. Individual analytics require a separate opt-in.

C.2 Mode 1: Non-account (default)

• Local only. LMS analytics are stored locally and are not sent to BetterCampus.

C.3 Mode 2: Account (default) (de-identified, aggregated school insights)

If you create an account, LMS analytics remain stored locally by default and may be sent to BetterCampus only in de-identified, aggregated form to power school-level insights.

• On by default for account holders. You can opt out (Section 4).
• De-identified and aggregated. These signals are processed in a way designed to avoid identifying individual students in school-level reporting.
• Thresholds. We apply a minimum threshold (typically 10 or more users in a cohort) before displaying any aggregated school or cohort insights to reduce the risk that an individual student's patterns could be inferred from group statistics.
• No re-identification. We do not attempt to re-identify de-identified data except as permitted by law.

Examples of aggregated metrics may include:

• Engagement: Time on Canvas; Activity Heatmap; Active Weeks This Term; No-Activity Streaks
• Timeliness: Submission Rates; Avg Hours Early/Late; Cram Index
• Content Mix: Assignment Types
• Planning / Behavior: Time to First View After Posted
• Course Balance: Time Distribution by Course; Neglected Course Indicator

C.4 Mode 3: Account + Individual Insights (optional; off by default)

If you opt in to Individual Insights, LMS analytics may be sent to BetterCampus on an individual basis and linked to your account to generate your personal Insights dashboard.

• Off by default. You must opt in to enable it.
• Age and consent requirement for opt-in. You may opt in to individual-level LMS analytics only if you meet the minimum age required in your jurisdiction to provide valid consent for this kind of processing (which may be higher than 13). If you do not meet the applicable age threshold, Individual Insights will remain unavailable to you.
• Details. See Section 1.D for the Individual Insights opt-in details, including historical sync, withdrawal, and accuracy limitations.

D. Individual Insights opt-in (individual LMS analytics; off by default)

Individual Insights is the optional, individual-level version of LMS analytics (Mode 3 above). If you opt in, we can associate certain LMS analytics with your BetterCampus account to generate your personal Insights dashboard.

• Individual transmission to BetterCampus. If you opt in, LMS analytics stored locally in your browser/device may be transmitted to BetterCampus and linked to your account for the purpose of generating your personal Insights.
• Historical sync from this browser. If you opt in, LMS analytics stored locally in this browser since you installed the extension (including activity from before you created an account or before you opted in) may be synced to our servers to generate long-term trends. Your opt-in covers both (a) this sync of historical browser-held activity and (b) ongoing collection going forward.
• Withdrawal. If you turn it off, we stop collecting new individual Insights signals going forward. We may retain prior Insights data for a limited period for security, troubleshooting, legal compliance, dispute resolution, and recordkeeping, then delete or de-identify it consistent with Section 7.
• Accuracy. Insights are estimates intended for learning support. You should rely on your LMS and your school as the authoritative source for grades, deadlines, and submissions.
• Informational nature of Insights. The insights, predictions, and study recommendations provided by the Services are generated by automated processing. They are intended for informational and motivational purposes only. They do not produce legal effects or similarly significant effects concerning you (such as determining your grade, eligibility for graduation, or academic standing). You should always verify deadlines and grades directly in your LMS.

E. LMS data and third-party platforms (enabled by default for core functionality)

LMS-connected processing is enabled by default when you install the extension and use it on supported LMS pages. Our browser extension may read certain information from the LMS pages you visit (for example, assignments, due dates, completion status, grade summaries, announcements, calendar items, and other items you choose to import) to provide core features. You can disable LMS-connected features in settings (where available) or uninstall the extension to stop this processing.

Scope-limited extension. The BetterCampus extension is designed to interact only with authorized LMS domains and only when you are actively using those LMS pages (for example, when an LMS tab is open and you use BetterCampus features). It does not monitor your activity on unrelated websites (for example personal email, banking, or social media), it does not run analytics on non-LMS pages, and it does not collect, store, or infer your general web browsing history.

How data is transmitted. Some extension features are delivered through external pages we host at ext.bettercampus.com, which may be loaded inside secure iframes within the extension UI. When you use those features, the extension may transmit certain LMS information to BetterCampus web services via browser-to-website messaging (for example, embedded frames and postMessage-style communication).

These data requests are scope-limited and designed to occur only when you actively open the extension and only while an authorized LMS tab is active. Requests are restricted to approved origins we control (for example, ext.bettercampus.com) and to a set of pre-approved, hard-coded extension functions (for example, a function that requests and forwards assignment lists). Communications with our services are protected using encryption in transit (HTTPS/TLS).

No password collection. BetterCampus does not require your LMS password. Where access occurs, it typically occurs through your authenticated browser session, permissions you grant, or other user-authorized methods.

Important security note. While we use reasonable safeguards, no system is perfectly secure. If our website or systems were compromised, an attacker could potentially access information processed through LMS-connected features. You should consider this risk when deciding whether to enable LMS-connected features.

Minimization. We aim to collect and transmit only what is reasonably necessary for the feature you choose to use. Some LMS information may be processed transiently (for example, to render a feature) and may not be stored long-term.

F. Information from third parties

We may receive information from:

• Service providers that help us operate the Services (for example hosting, email delivery, customer support tools, security providers, and payment processors).
• Referral and invite flows (for example if another user shares an invite link with you).
• Affiliate and offer partners (for example if you click a deal link, we may receive confirmation that a click or purchase occurred, often using an affiliate identifier).
• Public sources where permitted by law.

G. School partnerships and student account linking

If your school, district, or institution enters into an agreement with BetterCampus (a "School Partnership"), we may provide reporting, licensing, and support services to that institution, as described in the applicable contract and this Policy.

We may process additional information in connection with a School Partnership, such as:

• institution name, cohort/segment membership, and license eligibility
• student identity tokens and identifiers provided through school authentication (for example SSO or LTI), which may include a school-issued identifier (for example an SIS ID)
• usage and engagement data, subject to the sharing rules in Section 3.D and the school contract

Important: A School Partnership does not change what your LMS collects about you, and BetterCampus does not control your LMS.

A. Information you choose to share

Depending on your settings, certain content or profile elements may be visible to others (for example, public themes or study sets you publish). You control visibility where available.

B. Service providers

We share information with vendors that process data on our behalf to operate the Services (for example hosting, email delivery, customer support, security, product analytics providers such as PostHog, and payment processing). They may use personal information only to provide services to us, subject to contractual obligations.

Key service providers. Depending on which features you use, we may share certain data with the following categories of vendors:

• Email delivery (Amazon SES): used to send account and product emails (for example verification, password reset, receipts, and support responses). This involves your email address and the content of the email.
• Payments (Stripe): used to process subscriptions and taxes. Stripe processes payment card details. BetterCampus does not store full payment card numbers.
• Database and app hosting (Supabase): used to store account and product data (for example your name, email, birthday, school details you provide, and content you save in the Services).
• Edge and application infrastructure (Cloudflare Workers): used to route requests, run backend logic, and help protect and accelerate the Services. This may involve IP address, request metadata, and content sent to our endpoints.
• Data minimization. We take steps to minimize personal information sent to AI providers (for example, stripping identifying account metadata like your email address from the context sent for processing where feasible). When you use AI features, we may transmit the text, files, or other inputs you provide (and relevant context needed to generate an output) to these providers for processing. Provider use limits. Where available, we configure these services to process your inputs only to provide the requested output and to support safety and abuse prevention. We access these AI services via APIs; according to the providers' published terms for those API offerings, your inputs are not used to train their general models.
• Voice and audio models (Groq or other providers): used to power voice-enabled features (where available). This may involve audio you provide and related metadata, depending on the feature.

We may update or change vendors over time. We work to select providers with appropriate security measures and contract terms.

Sub-processors list and updates. We maintain a current list of our sub-processors (service providers that process personal data on our behalf) and make it available on our website (the "Sub-processor List"). We may update that list from time to time.

• Notice of material changes. Where required by law or contract (including for EEA/UK processing and many School Partnerships), we will provide notice of material sub-processor changes primarily via email to the address associated with your account (and, where appropriate, via an in-product or website notice).
• Right to object (where applicable). Where applicable, you may object to a new sub-processor by contacting privacy@bettercampus.com within the notice period. If we cannot reasonably accommodate an objection, your remedy may be to stop using the Services and request deletion of your account (subject to Section 7).
• School Partnerships. For School Partnerships, sub-processor notice and objection rights may also be governed by the school's DPA.

C. Affiliate and offer partners

If you click a deal link or redeem an offer, we may share or receive limited information to attribute the referral (for example, an affiliate click identifier and purchase confirmation). Partner privacy practices also apply.

D. Schools, districts, and institutional partners

If your school partners with BetterCampus, we may share certain data with that institution as described below and as permitted by the contract and applicable law.

Pre-contract (no School Partnership)

Before a School Partnership is in place, we do not provide student-level data to that school. Schools may see only de-identified and aggregated insights (for example total active BetterCampus users at the institution and aggregated usage clusters) subject to thresholds.

Post-contract (School Partnership) and student linking

After a School Partnership begins, student-level sharing depends on the flow and your actions. In the context of a School Partnership, BetterCampus acts as a Data Processor (or Service Provider) and the School acts as the Data Controller. All data processing in this context is governed by the Data Processing Agreement (DPA) signed with the school.

Secure account linking. When linking a student account to an institution, we use industry-standard encryption in transit and at rest to protect the association between your BetterCampus identity and your school-issued identity token/identifier. BetterCampus employees cannot view your school-issued identity unless strictly necessary for technical support, security, compliance, or as required by the School Partnership agreement:

• Case 1: Existing BetterCampus user. If you already have a BetterCampus account, we may present you with a prompt to link your account to your school identity (for example via SSO). If you choose to link, the school may gain access to certain student-level BetterCampus data and analytics you have enabled, within the scope defined in the contract and your settings. This may include historical BetterCampus engagement data generated before the School Partnership began, but only for students who link and only to the extent allowed by the school's contract, the DPA, your settings, and applicable law.
• Case 2: New user through the school. If you start BetterCampus through school SSO or an LTI launch, we may create and link your account to your school identity. The school may see license administration information (for example verified status and high-level usage needed for billing and adoption reporting) as defined by the contract. Detailed individual analytics are shared only if you take an additional action that clearly explains what will be tracked and what the school will be able to view (for example, opting in to detailed Insights under the school program).

Withdrawal and limits. If you withdraw an optional opt-in, we stop collecting new data for that opt-in going forward. Data already shared with a school under an active School Partnership and within the contract scope may be retained by that school and/or BetterCampus as required for compliance, billing, auditing, security, and recordkeeping.

E. Legal, safety, and enforcement

We may disclose information if we believe it is reasonably necessary to comply with law, enforce our policies, prevent fraud or security issues, or protect rights and safety.

F. Business transfers

If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction.

G. With your direction or consent

We may share information when you ask us to do so.