Privacy, in plain language.

Your recording and feedback

Recording is optional. You can record in the page or choose an existing audio file. We ask for your consent before sending it for analysis. While the page stays open, the browser holds your chosen audio so you can listen to it or submit it. Our server reads it in memory, sends it to OpenAI for transcription, then sends the resulting transcript and the practice prompt to OpenAI for feedback. ClairParle does not save a copy of the audio file in its database.

OpenAI returns a transcript and feedback to the page. If you do not choose Save this attempt, ClairParle does not store that transcript or feedback as practice history. The feedback is generated by AI, can be mistaken, and is not an official score or exam result.

What we keep for your account

Clerk manages sign-in and account information such as your email address and session. ClairParle uses your Clerk user ID to link daily attempt usage, an optional saved practice history, and subscription status. If you choose to save an attempt, we store its drill, transcript, feedback, duration, and date in a Neon database. You can save up to 50 attempts and delete individual saved attempts in your account view.

Deleting a saved attempt removes it from the active practice-history table. It does not erase earlier processing at OpenAI, Clerk or other providers, or immediately remove copies that may remain in database recovery history. We also keep limited usage, security and billing records needed to operate the service.

Services that process data

• OpenAI processes audio for transcription and transcript text for feedback. We set store: false for feedback Responses. According to OpenAI's API data controls, the audio transcription endpoint has no listed application-state or abuse-monitoring retention. The Responses endpoint can retain abuse-monitoring logs for up to 30 days by default, sometimes longer for stated exceptions. OpenAI says API data is not used to train its models unless the customer opts in. ClairParle does not have OpenAI's Zero Data Retention setting.
• Clerk provides sign-in and account sessions. Clerk's policy distinguishes its own data from customer data handled for services such as ClairParle.
• Neon hosts our database for saved attempts, usage and subscription records. Database recovery history can outlast deletion from the active table; see Neon's explanation of point-in-time restore.
• Stripe processes checkout, subscription management and payments when billing is enabled. ClairParle stores Stripe customer and subscription identifiers and status, but not card numbers. Stripe applies its own privacy terms and retention rules to payment data.
• PostHog receives limited product-use and billing-event metadata. We do not send it audio, transcripts, feedback text, email, or raw Stripe identifiers.

Analytics and browser storage

The browser stores a random analytics identifier and limited attribution information, such as campaign tags and the origin of a referring site, in local storage. PostHog receives events such as opening a drill, requesting feedback and saving an attempt. Billing events include the plan, paid or refunded amount, and hashed identifiers when billing is enabled. These events help us see whether the practice flow works. Clerk and Stripe may use their own session or checkout storage. Clearing browser storage removes the local identifier from that browser; it does not delete events already received by PostHog.

Site delivery

Our web host, DigitalOcean, receives ordinary request information, such as your IP address, browser headers and the pages you request, to serve and protect the site. Pages also load typefaces from Google Fonts, which causes your browser to request font files from Google. See how Google Fonts serves fonts.

Your choices and questions

For a copy of your saved data, help deleting your account, a privacy question, or a billing-data request, email [email protected]. Tell us the email used to sign in so we can locate your account; please do not email recordings, passwords or payment-card details. We will review requests in light of the data we control and applicable provider obligations.