This notice supplements the Privacy Policy by identifying the principal service providers and integration providers reflected in the current vendor inventory and data inventory. Some providers function as core service providers used by Think Tech across the Services, while others are district-enabled integrations that are activated only when a Customer chooses to connect them.
Core service providers and subprocessors
| Provider | Purpose | Data involved | Notes |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting, computing, storage, backups, logging, transactional email infrastructure | Customer Data, account data, files, logs, backups, notification-related data | Core cloud subprocessor; primary application infrastructure in U.S. AWS regions including us-east-1 |
| Stripe | Payment processing, subscriptions, billing metadata, invoicing support | Adult billing contacts, payment transaction data, invoices, subscription metadata | Used for paid flows and payment operations |
| HubSpot | CRM, Educator communications, site forms/chat, knowledge base | Adult Educator, administrator, and procurement contact data; site interaction data | Adult-facing communications and support resources; not intended for Student marketing use |
| Mailchimp | Adult email communications and marketing lists | Adult email addresses and related campaign/list metadata | Referenced in the current user-data inventory |
| Google Analytics | Website analytics | Website usage, browser/device data, analytics identifiers, cookies | Public-site analytics only |
| Heap Analytics | Product / site analytics | Usage and session analytics, cookies or browser identifiers | Present in current cookie audit |
| Google Ads | Advertising attribution / conversion measurement | Click and conversion attribution data on adult-facing pages | Present in current cookie audit |
| OpenAI | AI-enabled educational features | Prompt and response data needed to deliver educator-triggered AI features; student references minimized or de-identified where feasible | Used for configured AI workflows |
| Anthropic | AI-enabled educational features | Prompt and response data needed to deliver educator-triggered AI features; student references minimized or de-identified where feasible | Used for configured AI workflows |
| Google Cloud AI services | AI / platform enhancement as configured in certain features | AI workflow data as needed for the configured feature | List if enabled for the applicable feature release |
| Firebase Cloud Messaging | Push notification delivery | Device push tokens and related notification routing data | Used when mobile notifications are enabled |
District-enabled integrations and identity providers
| Provider | Typical use | Typical data involved |
|---|---|---|
| Clever | Single sign-on, rostering, teacher/student identity and class synchronization | Teacher and/or student identity data, provider IDs, roster information, OAuth tokens where applicable |
| ClassLink | Single sign-on and rostering | Teacher and/or student identity data, provider IDs, roster information |
| Single sign-on and Google-related integrations | Identity data, provider IDs, OAuth tokens, roster or sync data where applicable | |
| Microsoft | Single sign-on and Microsoft-related integrations | Identity data, provider IDs, OAuth tokens where applicable |
| Schoology | Single sign-on / rostering integration | Identity data, schoology_user_id, sync metadata, roster information where applicable |
| EdLink | Single sign-on / integration bridge | Identity and provider data needed to support the enabled workflow |
District-enabled integrations are generally activated at the Customer's direction and may be governed by the provider's own terms and privacy materials in addition to Think Tech's agreements. Think Tech will update this notice as its provider landscape changes.