What Data NOCK Collects
A clear breakdown of the data captured with NOCK tickets and which settings control optional context.
NOCK collects ticket data so your team can understand and resolve feedback without repeatedly asking users for browser, page, and reproduction context.
What is collected depends on the submission source and project settings.
Ticket data
| Data type | Collected | Notes |
|---|---|---|
| Title | Always | Typed by the reporter or sent through the API. |
| Description | Optional | Typed by the reporter or sent through the API. |
| Category | Usually | Selected in the widget when categories are configured. |
| Reporter email | Optional | Present only when submitted or collected by the flow. |
| Source | Always | Widget, Customer Portal, dashboard, Public API, or integration. |
| Page URL | Widget submissions | URL where the widget was open. |
| Browser name/version | Widget submissions | Captured automatically by the widget. |
| Operating system | Widget submissions | Captured automatically by the widget. |
| Viewport and screen size | Widget submissions | Captured automatically by the widget. |
| Images | User action | Up to 3 PNG, JPEG, GIF, or WebP files, 5 MB each. |
| Website annotations | User action | Pins and text-edit suggestions created from explicit widget actions. |
| Console logs | Project setting | Controlled by Settings > Console. |
| AI follow-up Q&A | User action and project setting | Stored when AI is enabled and the user answers questions. |
| Customer-visible replies | Team/customer action | Stored in the ticket conversation. |
| Internal notes | Team action | Visible only to team members, not customer portal visitors. |
Images
Images are never captured silently when the widget opens. Users must click Screenshot to capture the current viewport, click Pin element to capture or reuse a screenshot and place a pin, drag and drop image files, paste an image, or add a manual image while the widget is open.
During screenshot capture, password input values and placeholders are temporarily masked before rastering. This is not a full redaction tool; other visible page content can still appear in the screenshot.
NOCK accepts PNG, JPEG, GIF, and WebP images. Each ticket can include up to 3 images, with a 5 MB limit per image.
Website annotations
Website annotations are explicit user actions:
| Annotation | Stored data |
|---|---|
| Pin | Page URL, viewport size, x/y coordinates, coordinate ratios, selector context, nearby element text, and a screenshot reference when available. |
| Text edit | Page URL, viewport size, selector context, nearby element text, readonly original selected text, suggested replacement, and optional comment. |
Text edits do not capture a screenshot. Pins need a screenshot reference so the dashboard can show where the point was placed.
Console logs
Console capture is configured in Settings > Console. Depending on the selected level, NOCK can collect:
| Source | Example |
|---|---|
| Console methods | console.error, console.warn, console.log |
| Runtime failures | Unhandled JavaScript errors and promise rejections |
| Network failures | Failed fetch requests and non-2xx responses |
Exclude patterns can remove noisy messages before they are stored. Review your production logging before broadening capture so secrets and unnecessary personal data are not written to browser logs.
AI follow-up questions
If Settings > AI enables AI Enhancement, users can click Refine with AI. NOCK sends the draft title, description, category, and your optional custom prompt to generate focused follow-up questions. Answers the user provides are stored with the ticket.
AI usage is limited by your plan.
Customer Portal visibility
Customer Portal visitors see only customer-safe information: ticket title, description, category, status, and customer-visible replies. They do not see internal notes, API keys, webhook settings, billing, team settings, or Linear internals.
What NOCK does not collect
NOCK does not intentionally collect:
- Passwords or account credentials
- Payment card details
- Private keys or API secrets from your application
- Data from unrelated browser tabs
- Images or annotations unless the user chooses the relevant widget action
- Internal notes in the Customer Portal
Billing
Manage your NOCK billing settings, understand the automatic no-card 14-day Lite trial, upgrade to a paid plan, and understand what happens when a subscription changes.
Privacy Basics
A plain-language overview of how NOCK uses collected data, what gets shared with third parties, how long data is retained, and how to delete it.