1. Overview

AudioPilot ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how our Chrome extension handles information when you use features such as instant transcription, translation, or audio analysis while watching videos.

2. Information We Collect

We designed the extension with a privacy-first principle. The extension stores only the minimum data necessary for it to function:

• User session and tokens: Access token and (if available) refresh token to authenticate API requests, stored in Chrome sync storage.
• API configuration: Server base URL and runtime settings needed to connect to our backend.
• Feature preferences: Output language, region preference, UI settings, credits cache and related feature flags for a smoother UX.
• Operational metadata: Operation type (e.g., transcribe vs. analyze) and snippet duration used for credits calculation.

3. Data We Do NOT Collect

• No personal information or identity data.
• No continuous browsing history collection or background tracking.
• No keystroke logging or page content scraping beyond what is required to provide the requested feature.
• No sale of personal data and no third‑party analytics embedded in the extension.
• No permanent storage of captured audio on your device by the extension itself.

4. How We Use Information and Audio

• On‑demand audio capture: When you actively trigger a feature, the extension captures the active tab's audio using Chrome tabCapture for a short snippet.
• Processing by our backend: The captured audio is sent to our servers for transcription, translation, or analysis. Depending on configuration, audio snippet data may be sent directly to third‑party APIs, or first uploaded to object storage (Supabase) and then referenced by URL.
• Credits and quotas: We use the operation type and snippet duration to compute credits usage on our backend. The extension performs a local pre‑check to reduce unnecessary network use.
• Local preferences: Language and region preferences are stored locally in Chrome storage to improve your experience.

5. Third‑Party Services

• Object storage (optional): When enabled by server configuration, the extension uploads the audio snippet to Supabase Storage via a signed URL, then submits only the resulting URL to our backend for processing.
• All transmissions are made over HTTPS. API keys/tokens are stored in Chrome's storage areas; we do not store them on content pages.

6. Data Sharing

We do not sell or rent user data. We share data strictly to operate the features you initiate:

• With our backend APIs to process the captured audio for the requested feature.
• With Supabase Storage (if enabled) to temporarily store your snippet, generating a URL for processing.
• As required by law, regulation, or legal process.

7. Data Security

• Authentication tokens are stored in Chrome's storage (sync/local) and transmitted over HTTPS.
• The extension runs under the browser's security model; background service worker and offscreen documents handle recording safely.
• No continuous collection; audio is captured only when you use a feature.

8. Your Rights

• You may clear the extension's stored data from the extension settings or by removing the extension.
• You control when recording happens; features run only on your action.

9. Extension Permissions

To function, the extension requests a minimal necessary set of permissions:

• activeTab: Temporary access to the active tab when you invoke the extension.
• storage: Save tokens and preferences in Chrome storage.
• scripting: Inject content scripts/styles as needed (MV3).
• tabCapture: Capture audio from the current tab for recording.
• offscreen: Use an offscreen document to record and process audio safely.
• host_permissions (video sites): Access to key video platforms for a stable first‑time experience:
  • https://www.youtube.com/*
  • https://www.bilibili.com/*
  • https://*.iqiyi.com/*
  • https://v.qq.com/*
  • https://*.youku.com/*
• optional_host_permissions: https://*/* requested only when you choose to use the extension on a new site, adhering to the principle of least privilege.

Not requested: The high‑sensitivity tabs permission is not used by the current implementation.

10. Changes to This Policy

We may update this Privacy Policy periodically. Material changes will be reflected on this page with an updated revision date. Continued use of the extension constitutes acceptance of any changes.

11. Contact

If you have questions about this Privacy Policy, please contact:

Email: wuchris695@gmail.com