Privacy Policy

Capo is a Chrome extension that helps users create visual bug reports. Users can capture screenshots or screen recordings, add annotations and comments, and submit those reports to connected services such as Google Drive, Google Sheets, GitHub, Jira, and Linear.

Capo is designed as a bridge to the platforms you already use. We do not view your captures as a product operator browsing your content, and we do not sell your screenshots, recordings, or report contents. Captures go to destinations you choose. Capo only captures content when you intentionally start a capture or recording.

This Privacy Policy explains what information Capo collects, how it is used, and the choices you have.

Account information: When you connect Google, GitHub, Jira, or Linear, Capo may access basic account details such as your email address, name, username, avatar, and account identifier so the extension can show the connected account and submit reports to your selected destinations.

Authentication information: Capo uses OAuth access tokens to connect to those platforms. Capo does not collect or store your account passwords. For Google, Capo requests the limited drive.file scope and uses Google Picker so you explicitly choose which spreadsheet and Drive folder Capo may access.

Capture content: Screenshots, screen recordings, annotations, comments, and report fields are processed on your device and sent only to the destinations you select when you submit. Capo does not keep a media library of your captures on our servers.

AI fill (optional): If you use AI autofill, the annotated screenshot and field schema are sent securely to generate field suggestions. That content is used to draft suggestions for that request and is not sold or stored as your capture archive.

Settings and preferences: Capo stores extension settings such as selected spreadsheet, Drive folder, repositories/projects, labels, capture preferences, and billing plan status — primarily in your browser.

Usage and billing status: Capo may store usage counts, plan type, subscription status, and related billing identifiers needed to enforce plan limits and provide paid features. Payment card details are handled by the payment provider and are not stored by Capo.

To provide Capo's single purpose: creating and submitting visual bug reports.

To capture screenshots or screen recordings only after you start a capture.

To upload selected captures to Google Drive and create rows in Google Sheets when you choose that destination.

To create issues in GitHub, Jira, or Linear when you choose those destinations.

To generate optional AI field suggestions when you request AI fill.

To save your settings so you do not need to reconnect or reconfigure the extension each time.

To manage usage limits, subscriptions, billing status, and account access.

To troubleshoot errors, improve reliability, and respond to support requests.

Capo does not sell user data.

Capo does not transfer user data for purposes unrelated to its visual bug reporting purpose.

Capo acts as a bridge: we send data only to services you connect or use as part of the workflow, including Google APIs, GitHub APIs, Jira/Atlassian APIs, Linear APIs, optional AI model providers for autofill, Supabase, and Dodo Payments.

Google Drive and Google Sheets receive captures and report data only when you submit to Google destinations. Capo does not browse or sync your entire Drive; it operates on the spreadsheet and folder you select through Google Picker.

GitHub, Jira, and Linear receive issue content and attachments only when you submit to those destinations.

Supabase may be used for account, usage, and billing state. Dodo Payments may be used to process checkout and subscription events.

We may disclose information if required by law, to protect rights and security, or to prevent abuse.

activeTab: Used temporarily when you start a capture from the current tab.

scripting: Used to run the region selection and capture helper after you initiate a screenshot capture.

tabs: Used to open and manage Capo extension pages such as capture, annotation, settings, pricing, and success pages.

storage: Used to save settings and preferences locally in Chrome storage.

identity and identity.email: Used for Google authentication and to show the connected Google account.

Host permissions: Used to support user-initiated captures and communicate with required services such as Google, GitHub, Supabase, and payment endpoints.

Capo does not load or execute remote JavaScript or WebAssembly as part of the extension. Extension code is bundled with the extension package. Network requests are used only to communicate with APIs and services needed for the visual bug reporting workflow.

Extension settings are stored locally in Chrome storage unless they are needed by connected backend services for account, usage, or billing state.

Captures submitted to Google Drive, Google Sheets, GitHub Issues, or GitHub Projects are retained according to the settings and policies of those services and your accounts with them.

You can delete submitted captures or reports from Google or GitHub directly from those services.

You may disconnect Google or GitHub in Capo settings. You may also request deletion of account-related data by contacting us.

Capo uses OAuth where available and does not ask for your Google or GitHub password.

Access tokens are used only to perform actions you request, such as uploading a capture, updating a sheet, or creating a GitHub issue.

No internet transmission or storage method can be guaranteed to be completely secure, but we take reasonable steps to protect data used by the extension.

You can choose whether to submit a capture to Google Sheets, GitHub, both, or download it locally.

You can disconnect Google or GitHub from Capo settings.

You can remove the extension from Chrome at any time.

You can request access, correction, or deletion of account-related data by contacting us.

Capo is not directed to children under 13 and is intended for productivity, QA, product, and development workflows. We do not knowingly collect personal information from children under 13.

We may update this Privacy Policy as Capo changes. When we make material updates, we will update the effective date on this page.

If you have questions about this Privacy Policy or want to request deletion of account-related data, contact us at pawanpandey9761@gmail.com.