Subprocessors

Last updated: 2026-05-12

This page lists named vendors that process end-user data for the live aloworld product surface, plus vendors documented immediately before an activation-ready rollout.

This is intentionally a slim public list. Internal infrastructure detail that is not needed for public disclosure does not belong here.

Current named subprocessors

Google

• Purpose: AI text generation, chat-aid generation, progress report generation, skill scoring, and related AI inference
• Data categories: user prompts, conversation context, transcripts, profile context, safety instructions, AI outputs, and operational metadata

Supabase

• Purpose: authentication, database, storage, and account state
• Data categories: account records, profile data, chat records, session records, reports, generated content, and related product state

AssemblyAI

• Purpose: real-time speech-to-text when voice input is used
• Data categories: user audio, speech segments, transcripts, and speech-detection metadata

Microsoft Azure Speech

• Purpose: pronunciation and speech assessment when speaking feedback is used
• Data categories: user audio, transcripts, pronunciation scores, fluency signals, prosody signals, and assessment metadata

Cartesia

• Purpose: speech synthesis when a character uses a Cartesia voice
• Data categories: AI reply text and speech-generation metadata

Inworld

• Purpose: speech synthesis when a character uses an Inworld voice
• Data categories: AI reply text and speech-generation metadata

MiniMax

• Purpose: speech synthesis when a character uses a MiniMax voice
• Data categories: AI reply text and speech-generation metadata

Fish Audio

• Purpose: speech synthesis when a character uses a Fish Audio voice
• Data categories: AI reply text and speech-generation metadata

PostHog

• Status: enabled only when configured for the live product surface
• Purpose: product analytics and session replay
• Data categories: usage events, page views, pseudonymous identifiers, device/browser metadata, performance metadata, and replay data

Vercel

• Purpose: web hosting, web analytics, and performance telemetry
• Data categories: IP address, request metadata, page views, browser/device metadata, performance metadata, and logs

Railway

• Purpose: server hosting, logs, and operational telemetry
• Data categories: API request metadata, server logs, error metadata, and operational diagnostics

Expo

• Purpose: mobile app builds, app update delivery, and runtime update checks
• Data categories: app version, device/update metadata, update request metadata, and operational diagnostics

Update policy

We update this page before or at the time a new named vendor begins processing end-user data in the live product surface.

If a vendor stops processing end-user data for the live product surface, we remove it from this page in the next review cycle.