Last updated: March 13, 2026
External Transmission
Fraska may transmit limited user information to external service providers for authentication, billing, AI response generation, and file storage. The list below reflects the providers currently used at launch.
Data sent: name, email address, and Google account identifier returned during Google sign-in
Purpose: authentication and account creation
- Stripe
Data sent: customer identifiers, plan information, and subscription status needed for billing
Purpose: payment processing, billing management, and subscription state sync
- OpenAI / Anthropic / Google Gemini
Data sent: chat input, conversation context required for generation, selected model metadata, and attachment contents
Purpose: AI response generation and provider-backed search workflows when enabled
- Supabase Storage
Data sent: uploaded attachment files and related storage metadata
Purpose: storing and serving chat attachments
1. When transmission occurs
Account information is received from Google when you sign in with Google authentication.
When you send a chat message, the selected model provider receives the input and related context required to generate a response.
When you start or manage a paid plan, billing-related information is sent to Stripe.
2. Cases where transmission cannot be disabled
Authentication, AI response generation, billing, and attachment storage are core parts of the service, so disabling these transmissions would make Fraska unavailable.
If a material change is made to the destinations or transmitted data, the related legal pages or in-product notices will be updated.