Diese Seite gibt es noch nicht in Ihrer Sprache. Sie lesen den englischen Text.
Legal
Security reports
Edition 2, in force since 5 October 2026
Where to send it
One road in: the contact form on the support page. It works without signing in too.
Pick the topic Something else and put the word security at the front of the subject: the message lands in the owner's queue.
No account needed
A pass, if your browser holds one, ties the report to you. An expired pass does not get the message rejected.
Eight messages in ten minutes
That is the limit on the form, and rejected attempts count too, so a typo costs one of the eight.
A number comes back
The screen shows the request number after sending. Without it neither of us can point at the same message later.
What you get in return
Four commitments.
The owner's queue sorts paying customers first, so a report from someone who never bought anything waits behind them.
A first answer within five working days
Counted from the day the message lands. A person writes it, and it says what we make of the finding.
No move against a good faith report
No lawyer, no police, and no closed account for telling us something we did not want to hear.
The fix is listed in What's new
The entry carries the day the work landed and what changed, and a fix from outside is written down as such.
Your name in that entry, if you ask
Say so in the message. Saying nothing means no name.
Rewards and timing
We do not pay rewards for what is found. Card payment is temporarily disabled: we are not accepting new users right now.
There is no legal shield beyond the paragraph above. Beyond it, the Terms of Service apply.
No repair date is set in advance: we say what we intend to do and then name the day we did it.
Where the answer appears
Requests made while signed in, or with the confirmed address of your account, are listed with our answers under Your requests on your account page.
If there is no answer
What is ours and what is not
Ours is what we wrote: the server, this site, the app on your machine and the browser engine we compile. A finding in any of those belongs here.
Not ours is what a site does once a profile opens it, what a proxy seller does with your traffic, and what the upstream browser project publishes.
Report a hole in somebody else's product to its owner; we can pass a message along.
What to send and what to hold back
Send the steps, the build you ran and what you saw. A report written inside the app carries a description of that machine, with the secret fields cut out by name before it leaves your disk.
Hold back live passwords, cookies and keys. Your message is stored the way you typed it and a person reads it in a panel, so a secret there sits in the open.
Hold back other people's accounts too. A finding we cannot repeat without harming somebody who never agreed is one we will not act on.
Questions
- Is there a reward?
- No. We do not pay rewards for what is found. Card payment is temporarily disabled: we are not accepting new users right now.
- Can I report without an account?
- Yes. The form takes a message from anyone: a common reason to write is a failed sign-in.
- How fast will you answer?
- A first answer within five working days. Paying customers sit ahead of others in the same queue.
- Will you name me in the fix?
- Only if you ask. Say so in the message and the What's new entry carries your name.
- What if I hear nothing at all?
- Write again with the same subject and the request number.
Editions of this document
- Edition 2, 5 October 2026: The page is now called Security reports. The line about terms that did not exist yet now points to the terms. Your earlier requests and our answers are now shown on your account page.
- Edition 1, 13 September 2026: First edition.