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 Issues, and GitHub Projects.

This Privacy Policy explains what information Capo collects, how it is used, and the choices you have. Capo only captures content when you intentionally start a capture or recording.

Account information: When you connect Google or GitHub, 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 Google Drive, Google Sheets, GitHub Issues, and GitHub Projects. Capo does not collect or store your Google or GitHub password.

Capture content: Screenshots, screen recordings, annotations, comments, and report fields are processed when you create a visual bug report. This content may include website content that you choose to capture.

Settings and preferences: Capo stores extension settings such as selected Google Sheet, Drive folder, GitHub repository, GitHub Project, labels, capture preferences, and billing plan status.

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 GitHub Issues, apply selected labels, and add issues to GitHub Projects when you choose that destination.

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 sends data only to services you connect or use as part of the workflow, including Google APIs, GitHub APIs, Supabase, and Dodo Payments.

Google Drive and Google Sheets receive captures and report data only when you submit to Google destinations.

GitHub receives issue content, labels, screenshots, recording links, and project updates only when you submit to GitHub 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.