Security

This is a small site of plain files. It has no accounts, no forms and no database behind it, and it sets no cookies. There is little here to attack and little to take.

How the site is protected

Pages are served over HTTPS only. A request made over plain HTTP is redirected, and your browser is told to keep to HTTPS on later visits.

The site tells your browser to refuse anything it did not send itself: no scripts at all, and styles, fonts and images only from this site. It cannot be shown inside a frame on another site.

The public site is kept apart from the workshop’s own records. It is built in advance from finished material and served as files. It has no access to those records and does not need them to run. That limits what a fault in the site could reach. It is not a claim that nothing can go wrong.

The site collects as little as it can. What that amounts to is on the Privacy page.

Reporting a problem

If you find a security problem with speybench.com, write to service@speybench.com with “Security” in the subject. Say what you found and how to see it again. Plain text is fine.

Reports are read by one person, so please allow time for a reply. A report made with care is treated as help. There is no reward scheme.

What is asked in return

This page covers the speybench.com website and nothing else.

Look, but do not take, change or delete anything that is not yours. Do not test in a way that could interrupt the site for other people. Do not try to get in by deceiving a person. Allow a reasonable time for a fix before making a problem public.

This is a request for care. It is not permission to break the law.