Your privacy choices

KiwiBee uses optional Google Analytics, Google Ads, and Meta Pixel cookies to understand adult visitors, measure completed sign-ups, and improve campaigns. Essential cookies always stay on. OpenAI’s ChatGPT Ads Pixel also measures page views and completed enquiries after advertising consent, and may use hashed contact details for matching. Privacy policy

Skip to main content
Trust & security

Trust, security and compliance

Schools entrust KiwiBee with data about teachers, students and families. This page explains how we protect it.

Last updated: 2026-10-04

Security overview

Security overview

  • HSTS preload

    Strict-Transport-Security with preload directive. Browsers only ever connect to KiwiBee over HTTPS.

  • Cross-origin policies

    Cross-origin policies restrict access while allowing sign-in popups.

  • Permissions Policy

    Browser permissions are restricted by default. Selected classroom tools can request microphone access.

  • Clickjacking protection

    X-Frame-Options: SAMEORIGIN prevents external sites from embedding KiwiBee in an iframe.

  • MIME-type pinning

    X-Content-Type-Options: nosniff stops browsers from guessing content types.

  • Referrer policy

    Referrer-Policy: strict-origin-when-cross-origin minimizes data leaked to third-party domains.

  • Content Security Policy

    Content Security Policy restricts resource sources; permitted inline scripts and styles remain enabled.

Compliance roadmap

Where we stand on each major framework today.

  • SOC 2

    We plan to pursue a SOC 2 audit. No audit is under way yet. Ask us for our current security overview.

    Planned
  • GDPR

    Contact us to discuss data-processing terms and available documentation.

    Under review
  • FERPA

    For US schools, KiwiBee acts as a school official under the school's direct control and uses student records only to provide the service.

    Aligned
  • COPPA

    Designed to support schools' COPPA obligations: the school provides consent for students under 13, and we collect only what the service needs. A separate parental-consent flow is in development.

    Supported
  • Vietnam data protection

    Current requirements are under review. No verified compliance claim is made.

    Under review

Sub-processors

The third-party providers we use to deliver the service.

ProviderPurposeRegion
SupabaseDatabase, file storage and server functionsSingapore
VercelWeb hosting, edge network and AI gateway for the website chatbotGlobal edge
OpenAIAI drafting, images and transcription; retention depends on the workflow.US
MistralWebsite chatbot, document reading (OCR) and some teacher toolsEU
ElevenLabsText-to-speech audioUS
GoogleSign in with Google, Workspace email and AnalyticsGlobal
StripePayments and billingUS
ResendTransactional emailUS
Apple and GoogleMobile push notificationsGlobal

Data residency

Where customer data lives at rest.

Default region

Singapore (Supabase Asia-Southeast region)

Other regions

Customer data is stored in Singapore today. Other regions are not available yet.

Vulnerability disclosure

Found a security issue? We'd love to hear from you.

Acknowledgement

Within 24 hours

Initial response

Within 7 days

Coordinated disclosure

90 days from initial report

Related policies

Procurement, security or DPO teams can reach our team directly for evidence packs and questionnaires.