Collect the context a report needs, not private browser values.

Account and website data

IssueProbe stores the account email for authentication. It stores website names, exact origins, repository locations, public deploy keys, evidence category settings, report records, review decisions, and account activity.

IssueProbe sends outbound email only for account authentication and owner authorization. A reporter can optionally provide one unverified contact email inside a widget report. This is not email report intake, and IssueProbe never sends email to that address.

Visitor reports

A report contains the visitor's problem or suggestion, the page facts supplied by the widget, and the evidence categories that the website owner enabled. A reporter can also provide one optional contact email so the website owner can contact them manually.

The contact email is unverified and is never identity proof. IssueProbe stores it separately from evidence, shows it only to an authorized human or agent who opens that report, never sends email to it, and never gives it to the investigation. Customer text is untrusted and appears as escaped text in owner views.

Browser evidence

A visitor-approved screenshot can contain visible page data. The visitor sees a preview and can remove it before submission. Console and request evidence use bounded metadata and text redaction.

Cookie, form, and local-storage values are never collected. Each browser-state item contains only a name, a presence state, and a size. Read the exact widget privacy rules.

What the widget stores on the device

The widget stores one value on the visitor device: which corner of the screen the report button sits in. A visitor who drags the button to another corner keeps that choice on the next visit.

The stored value is a corner name and nothing else. It holds no identifier, no visitor data, and no report content. It stays on that one website and IssueProbe never receives it: it is not part of any report and never appears in browser-state evidence.

Repository access

Each website uses one separate SSH deploy key. The owner adds the public key with read-only access. IssueProbe does not ask for a Git password, personal access key, general SSH key, or private deploy key.

Retention

Free keeps screenshot artifacts for seven days. Pro keeps screenshot artifacts for thirty days. IssueProbe removes expired screenshot bytes automatically and retries a failed removal.

The optional reporter contact email remains with the report and account record until the report or account is removed through normal data controls. It is not deleted on the shorter screenshot schedule.

Human and agent access

A human owner can create and revoke API credentials. An agent needs owner authorization, narrow scopes, and an expiry. Each agent action appears in customer-safe account activity.

Marketing-site analytics

These public IssueProbe pages load one analytics script from a self-hosted service that IssueProbe operates. It counts page views without cookies and without a cross-site visitor profile. It honours the browser Do Not Track setting and it records no query values and no address fragments.

The script runs on IssueProbe pages only. The widget never loads it, so a website that installs the widget sends no analytics about its own visitors to IssueProbe.

Billing

Stripe-hosted pages collect payment details for Pro. IssueProbe does not receive card data. A Free account needs no card and no Stripe customer.

Questions and account requests

Use the authenticated account surfaces for account actions. IssueProbe does not accept reports by email and does not operate a visitor conversation thread. A website owner can use their own mail client to contact a reporter who chose to provide an address.