Privacy

There are two different groups of people in this document, and the distinction matters throughout:

• Customers — people with a Beacon account. We are the data controller for their account data.
• Visitors — people browsing a customer's website while our script is installed. The customer is the controller for that measurement data; we process it on their behalf, on the terms in our agreement.

This service is operated by Sudhanshu Mishra, based in India. Privacy questions go to timblenge@gmail.com.

When a visitor loads a page on a site that has our script installed, we record the measurements and the minimum context needed to make sense of them:

• Core Web Vitals and related timings — how long the main content took to appear, how long the page took to respond to the first interaction, how much the layout moved, and how long the server took to respond.
• The page URL, without its fragment or query string.
• What was responsible for the slowest measurement: a CSS selector for an element, an image URL, or a script URL. These come from the browser's own performance API.
• Coarse context that explains a difference between visitors: country, browser family, operating system family, device type (phone, tablet or desktop) and connection class (4g, 3g and so on).
• A random session identifier, stored in sessionStorage, used only to avoid counting one pageview several times.

Country is derived from a header the hosting network has already added by the time the request reaches us. The IP address itself is never stored, logged by us, or written to the database.

• No cookies. None are set, and none are read.
• No persistent identifier. The session id lives in sessionStorage and is gone when the tab closes — there is nothing that can link a visitor across sessions, devices or websites.
• No fingerprinting. We do not read canvas, fonts, audio, plugins or any other signal used to derive a stable device identifier.
• No IP address in storage, as above.
• No form contents, keystrokes, clicks, mouse movement, scroll positions or session recordings.
• No cross-site tracking, no advertising identifiers, and no data sold or shared with any advertising network. There is no such network in this product.

A consequence worth stating plainly: we could not produce a profile of one of your visitors if we were asked to, because we do not hold anything that identifies one.

For people with an account, we hold:

• An email address or phone number, and an authentication record — held by our authentication provider, not in our own tables. If you sign in with Google we receive the email address associated with that account and nothing else.
• Your organisation name, the domains you have added, and any logo you upload for branded reports.
• Optional contact details you enter against your website.
• Operational records: which jobs ran, which emails were sent, and the aggregated measurements described above.

• Per-page and per-segment measurement history: 30 days on the Free plan, 90 on Starter and 400 on Agency, after which it is deleted automatically by a scheduled job.
• The recent-visits feed: the newest few thousand events, and no more than 30 days. It is a diagnostic view, not an archive.
• Generated reports and the measurements behind them: kept while your account exists, because a report you have sent someone must not stop working.
• Account data: kept while your account exists.

Deleting your website deletes everything belonging to it — measurements, pages, reports, alerts and share links — immediately, enforced by the database rather than by a cleanup job that might not run. Removing the script from your site stops collection instantly.

For account data, the lawful basis is performance of our contract with you, and our legitimate interest in operating and securing the service. For measurement data collected from your visitors, you are the controller and you determine the basis — most customers rely on legitimate interest, since the data is aggregated and contains no identifier.

We are not lawyers and this is not legal advice. What we can tell you as a matter of fact is that the script sets no cookies and stores no identifier that persists beyond the tab.

We use a small number of providers to run the service — a database, a host, a mail provider, and one testing API. Each is listed with what it handles on the sub-processors page. We do not sell data, and we do not share it with anyone not on that list.

You can ask us for a copy of your account data, to correct it, to delete it, or to stop processing it. Most of this you can do yourself: the dashboard lets you edit and delete your website and its data directly. For anything else, write to timblenge@gmail.com and we will answer within 30 days.

If you are in the EU or UK and unhappy with how we have handled a request, you may complain to your national data protection authority.

If we change this policy in a way that affects what we collect or who processes it, we will email account holders before it takes effect. The date at the top is always the date of the current wording.