one mailbox

Support, read by the person who built it

No ticket number, no queue position, no chat widget - the widget would be a third-party script on a site that loads none, and the number would be theatre on a queue this short.

most replies: same day
the outside of it: 2 working days
security issues: same day
past that: send it again

[email protected]write nowthe subject line is prefilled by every link below

section#write

Write about one thing, and say which

6 kinds of mail

A reading that is wrongsubject:Bug
The panel measured something and the page disagrees. The most useful mail this address gets, and the least common - a measurement is either right or reproducible.
A technology missed, or named wronglysubject:Detection
Every match is made by a fingerprint in a table, so a wrong one is a row to fix rather than a model to retrain. The site it happened on is most of the report.
→ what each tool answers
A payment that went through with the panel still lockedsubject:Billing
Pro is applied to the browser that paid by Stripe's webhook, seconds after the charge. Still locked next time you open the panel is a bug, not a queue to wait in.
→ what each plan carries
A refund, inside 14 dayssubject:Refund
No form, no retention flow and nothing to justify. The date of the payment is the only thing the mail needs to carry.
→ the window, in the terms
Your data - access, export or erasuresubject:Privacy
An account holds an address and the links to reports published from it, and it deletes itself from the dashboard. Write here if that route refuses, or if you want the answer in writing.
→ every field, listed
A security issuesubject:Security
Write before publishing and expect an answer the same day. There is no bounty programme and pretending otherwise would waste your afternoon; credit in the changelog if you want it.

Never paste an AI key, and look at a screenshot before you attach it. Keys are kept in your browser and are sent to the provider you chose and to nobody else - the quickest way to undo that is a screenshot of the AI settings. Mail arrives here in an ordinary mailbox with ordinary security, and a key that reaches it has to be rotated.

section#report

What makes a bug report answerable

six lines, and the first one is most of it

01
The address of the page, or of one that reproduces it. A tool that reads the document in front of it cannot be debugged without the document.
02
The browser and its version, and whether the panel was floating over the page or open in its own window.
03
The extension’s version - Settings → About, in the panel.
04
Which tool, by the name it carries in the panel rather than by what it does.
05
What you expected the value to be, and how you arrived at that. “Wrong” and “wrong by 4px” are different reports.
06
Whether the page’s own console shows anything at the moment it happens.

section#already

Answered without writing

faster than a reply, on the days it applies

section#blind

What this side cannot look up for you

the cost of the thing the product promises

Nothing here records which pages you inspected, which tools you opened or which version you are running. That is the whole claim the extension makes, and this is what it costs: a report has to carry its own detail, because there is no log on this side to read it out of.

The device id the panel mints identifies a browser for credit accounting and authenticates nobody - it is not a key your history can be looked up under, which is the point of it.

THE TWO EXCEPTIONS

A payment

Stripe holds it against the address you paid with.

An account

It holds that address and the links to reports published from it. Either can be answered from the mail you send.