We only read the page context you choose to submit.

Account data: your email address for email sign-in; or the name, email, avatar, and account identifier GitHub provides when you choose GitHub sign-in.

Defects you submit: title, description, page URL with sensitive query parameters redacted, and the selected element's CSS selector, XPath, tag, non-sensitive attributes, limited text and HTML, viewport, and bounding rectangle.

Screenshots: the visible area of the active tab is captured only after you start the picker. You can crop it before submission.

Automation data: project configuration, issue state and events, agent pairing and run state, API token metadata, webhook configuration, and delivery results. Plaintext API tokens are shown only once at creation.

Technical data: IP address, browser user agent, session cookies, request time, and limited service logs needed for authentication, security, and troubleshooting. Public landing pages may use Google Analytics for aggregate traffic measurement.

The activeTab and scripting permissions are used only after you activate Pinhere and start the picker, so it can display the selector on the current HTTP/HTTPS page.

The identity permission opens Pinhere's secure authorization flow. The storage permission keeps sign-in tokens, pending captures, and editor state locally. Signing out removes sign-in tokens.

The extension does not read browser history, cookies, passwords, form values, or background tabs. It removes attributes associated with values, passwords, tokens, secrets, and sessions from selected DOM context.

Before submission, screenshots and page context are processed locally. They are transmitted to Pinhere over HTTPS only after you choose Create issue.

To provide sign-in, project matching, issue creation, screenshot display, agent claiming, and status reporting.

To generate readable issue identifiers, deliver webhooks you configure, and maintain the security and reliability of the service.

Pinhere's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

We use infrastructure providers only as needed to operate Pinhere: Vercel (hosting and private screenshot storage), Neon (database), Resend (email sign-in links), GitHub (optional sign-in), and Google Analytics (aggregate public-page analytics).

To asynchronously generate an English readable Issue ID, the issue title, up to 4,000 characters of description, page path, element tag, and up to 500 characters of element text are sent to Alibaba Cloud Model Studio/Qwen. Screenshots, full URLs, account information, and the full DOM are not sent to the model.

When you configure a webhook, Pinhere sends the Issue ID and agent repair prompt to the HTTPS endpoint you specify.

Data is retained while needed to provide your workspace and is transmitted over HTTPS. Screenshots use private object storage and require workspace authorization to access.

You can delete projects, revoke tokens, and remove webhooks. To request account export or deletion, contact us through the support page. We may retain the minimum records required for legal, security, or abuse-prevention purposes.

No system can guarantee absolute security. Do not include secrets, tokens, or personal data in a public support issue.

We will update this page and its effective date when our data practices materially change, and provide in-product notice when required.

For privacy, deletion, or security questions, contact the project maintainers through Pinhere Support.