Privacy

Last updated 20 September 2026.

Shutterbug is run by Hypership Ltd, a company registered in Northern Ireland (NI736697) at Aisling House, 50 Stranmillis Embankment, Belfast, BT9 5FL. If you want to ask about anything here, write to human@hypership.tech and a person will answer.

This covers two things: the console at shutterbug.dev, and the capture widget that our customers embed in their own logged-in apps.

The two roles we play

For your account — the workspace you sign in to — we decide what is held and why, so we are the controller.

For the reports captured in a customer's app, the customer decides what their app sends and who sees it. We hold it on their behalf, so we are a processor and they are the controller. If you reported a bug in someone else's product and landed here looking for it, they are the people to ask.

What the widget sends

When someone files a report, the widget collects, in the browser:

• the note they typed and the page route they were on
• the build SHA of the release they were looking at
• viewport size and browser user agent
• the last 50 console entries
• status and timing for requests to the app's own origins; a response body only for requests that failed, redacted, and capped at 2 KB
• roughly the last 20 clicks and navigations, as CSS selectors — not as text
• a description of the element they picked
• one screenshot, cropped to what they picked or to the viewport

What it does not send

Masking runs in the browser before anything is transmitted. The raw page never leaves the machine — we receive the redacted bundle and nothing else. Whatever a mask covers is covered in the screenshot and in the text read from the picked element, because both are read under the same mask. Successful requests contribute no bodies at all. Keystrokes are not recorded; the note is what the reporter chose to write.

Account data

Sign-in runs on Clerk. That means Clerk holds your email address, your name and avatar if your provider supplies them, and the record of how you signed in. We read those to name your workspace and to show you on a report's trail. We never see your password, and if you sign in with Google we never receive your Google credentials.

If the app you are reporting from passes us an organisation and user id in its signed token, we store those against the report so the team can see who reported what. That identifier comes from the host app; we do not enrich it.

How long we keep it

Archiving a report hides it and keeps it. Deleting one for good — offered on an archived report — removes the row, its events, sessions, decisions, evidence rows and the screenshot.

Who else processes it

Models

A report is read by a model to give it a title, a summary and a guess at where in the code it lives. We do not use your reports to train models, and we have not agreed to let anyone else do so.

Cookies

One session cookie from Clerk, so you stay signed in. There is no advertising, no third-party analytics, and no tracking across other sites. The widget stores nothing in the host app's browser beyond what it needs for the report in progress.

Your rights

You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it, at human@hypership.tech. If the data is a report inside someone else's workspace, we will pass you to them, because it is theirs to decide.

You can complain to your data protection regulator. In the UK that is the Information Commissioner's Office.

Changes

If this changes in a way that matters, the date at the top moves and we tell account holders by email. Small corrections just move the date.