By default, no, and that is on purpose. SleekAI on edtech marketing sites is configured for buyer-facing surfaces (teachers, administrators, CTOs, district procurement), not for K-12 students directly. Display conditions exclude student-facing pages and learning surfaces. If the product offers a student-facing AI tutor, that is a separate surface with a different system prompt, different refusal boundaries, and different data-handling rules, typically governed by COPPA and the district DPA. Keeping the marketing-site bot off student surfaces is the safest default.

Yes, if you publish it on the Compliance page. The bot reads your real Compliance entries, including FERPA-alignment statement, COPPA-compliance posture, parental-consent workflow specifics, district DPA template, and any state-specific privacy laws like California's SOPIPA. It quotes only what is published, never invented credentials. The conversation log captures any place where a district's expectation does not match published reality, which is useful intelligence for compliance, legal, and content marketing.

Yes. The bot reads your pricing page, including per-student pricing by grade band, volume discounts, multi-year district licenses, and any pilot offers. District procurement requires this level of specificity to put together an internal budget request, and a bot that can quote real numbers compresses the pilot-to-license conversion timeline. The system prompt should still route the actual quote to a district-pilots SE, because procurement-grade quotes usually include district-specific terms that the bot should not invent.

Yes. SleekAI is multibot, so the K-12 surface can run a K-12-aware bot with COPPA-aligned defaults, and the higher-ed surface can run a higher-ed bot with different defaults. Display conditions scope each bot to the right URL pattern or post type. Higher-ed buyer personas (procurement, IT, instructional designers) ask different questions from K-12 personas (CTOs, curriculum directors, ESC procurement), and a multibot setup keeps each conversation crisp and contextually correct.

The bot lives on the marketing site, so it does not pull live data from the LMS or SIS. It reads from your WordPress integrations directory, which describes the actual LMS and SIS integrations (LTI 1.3, OneRoster, Clever, ClassLink). Hand-off for a district pilot is via your district-pilots form, which then writes to your CRM with the right pipeline and stage. The marketing-site bot's job is to accelerate self-qualification on integration coverage; the actual integration runs inside the product, not the marketing site.

If you have published your posture on the Compliance page, the bot can quote it. California SOPIPA, New York Education Law 2-d, Illinois SOPPA, and similar state laws are increasingly important for district procurement, and a chatbot that can confirm your alignment with each in one sentence accelerates the legal-review step of procurement substantially. The system prompt should explicitly forbid claiming alignment with laws you have not published a posture on, because false claims at this level invite both regulatory and contractual risk.

Yours. SleekAI is BYO API key, so you bring your own OpenAI, Anthropic, Google, or OpenRouter key. For edtech specifically, the model provider must align with FERPA and COPPA-relevant data-handling expectations, which the major providers offer for enterprise accounts. The marketing-site bot generally avoids any PII or student data by design (display conditions exclude student-facing pages), which keeps the chatbot surface out of the FERPA and COPPA scopes entirely. The per-month model cost for a typical edtech marketing site runs $30 to $150.

On your WordPress install. You control retention and exports, and you can pipe interesting conversations to a Slack channel for the GTM team via webhook. Districts evaluating an edtech vendor often ask for a data-handling diagram during procurement, and 'conversations live on the vendor's WordPress, with the LLM API as the only external data path' is a simpler diagram to defend than a hosted chat tool that adds a third-party SaaS to the data flow. Retention can be set short (24 hours or 7 days) to match data-minimization expectations common in district contracts.