Privacy and Transparency

Subprocessors

Observer uses a limited set of trusted third-party services to deliver its functionality. These providers may process data on our behalf as part of operating the product.

Below is a list of all subprocessors currently used by Observer, along with their purpose and the type of data they process.

Last updated: April 2026

Cloudflare
Website
Provides frontend hosting, content delivery (CDN), and security.
Traffic metadata and performance data
Global
Deepgram
Website
Provides real-time, low-latency speech-to-text transcription for meeting audio.
Audio streams (processed in real-time, not stored)
United States
Fly.io
Website
Hosts Observer's backend infrastructure.
Processes application requests (no long-term storage)
Global
Mailgun
Website
Delivers transactional emails such as authentication and account notifications.
Email address and basic contact information
United States
OpenAI
Website
Powers real-time AI responses, summaries, and language understanding across Observer.
Meeting transcripts (processed during requests, not stored by OpenAI)
United States
Paddle
Website
Manages payments, subscriptions, and billing.
Billing and payment information
United Kingdom / United States
Supabase
Website
Handles authentication, database storage, and backend services.
User account data (email, authentication), meeting transcripts, and application data
United States

Important note on data retention

Observer does not store raw audio from meetings. Audio is processed in real-time by Deepgram and is not retained by Observer. Transcripts are stored securely in our database (Supabase) to support features such as conversation history, meeting notes, and AI-assisted responses. Transcript data may be processed by OpenAI to generate responses, but is not stored by OpenAI beyond processing. We maintain data processing agreements with all subprocessors listed above.