Privacy Policy

The Jaw AI desktop app

Your audio stays on your device

Jaw AI processes your audio locally on your Mac. Your recordings, project files, and the edits you make are handled on your own device — your audio is never uploaded to us or to any third party. Editing works this way whether or not you are connected to the internet.

The AI Agent (optional, bring your own key)

Jaw AI includes an optional AI Agent. To use it, you connect your own account with an AI provider — currently Anthropic or OpenAI — and usage is billed directly by that provider. When you use the Agent, your messages and instructions to it are sent to whichever provider you've configured, so it can generate a response; that exchange is subject to your chosen provider's own privacy policy, not just this one.

Your provider API key is stored locally in your Mac's Keychain or Windows Credential Store and is never sent to our servers. Your audio itself is never sent to the AI provider, or to us, as part of this feature.

Data sent to our servers

The desktop app sends us:

• An anonymous install identifier, along with your OS, platform, and app version, so we can see aggregate usage across releases.
• If you rate an Agent response with a thumbs up or down, the conversation behind that rating — so we can review and improve response quality.
• Anything you write in the in-app feedback form (bug reports, suggestions, etc.).

Service providers (desktop app)

• Your chosen AI provider (Anthropic and/or OpenAI) receives your Agent messages when you use that feature, governed by their own privacy policy.
• Google Firebase is where the install telemetry, Agent feedback, and in-app feedback described above are received and stored on our behalf.

The jawaudio.ai website

We only collect personal information you actively provide on this site:

Account

If you create an account or sign in on this website, we collect your email address, your name, and — for password sign-ups — a password. Passwords are handled by Google Firebase Authentication; we never see or store your password ourselves. If you choose to sign in with Google, we receive the basic profile information (name and email) that Google shares as part of that sign-in.

Contact form

If you write to us through the contact form on this site, we receive the email address you enter, your name (optional), the subject you pick, and your message. We use this to read and reply to what you sent.

Basic technical data

Like most websites, our hosting and backend providers automatically log standard request information (such as IP address and browser type) needed to serve the site securely and prevent abuse.

Service providers (website)

• Google Firebase (Authentication, Firestore, Cloud Functions, and Hosting) is our backend and hosting provider. The account and contact-form data described above is stored in Google Cloud infrastructure on our behalf.
• Google reCAPTCHA runs on the contact form to block automated spam. When you submit that form, reCAPTCHA interacts with Google and is subject to Google's Privacy Policy.

Cookies and local storage

When you sign in, Firebase Authentication stores a session token in your browser so you stay signed in. We do not use advertising or cross-site tracking cookies.

What we don't do

• We do not use third-party analytics or advertising trackers on the website.
• We do not sell or rent your personal information.
• We do not use your audio to train AI models.

Your choices

You can ask us to access or delete the personal information associated with your website account, a message you've sent us, or the desktop app's install/feedback data. To make a request, or if you have any questions about this policy, reach us through the contact form.

Changes to this policy

If we update this policy, we'll revise the “last updated” date above. Material changes will be reflected here on this page.