Trust
Privacy
This page lists what Runlight stores, what it leaves out, and how its privacy features work.
Runlight is built so that it never needs to know who anyone is.
How visitors are counted
Each day Runlight makes a new random salt. A visitor is the SHA-256 hash of that salt, your site, the visitor’s IP address, and their browser’s user agent, cut to 64 bits.
The same person on the same day gets the same value, which is how visitors and visits are counted. Tomorrow they get a different one.
A site’s salt changes at midnight in the site’s own timezone, so a visitor is one visitor for the whole of the site’s day, the same way its reports count days. A salt is kept only while it is today in the site’s timezone or, for yesterday’s salt, while a visit begun yesterday is still open, so that a visit that runs past midnight stays one visit. Then it is deleted. A visitor therefore lasts one day, or until a visit that runs past midnight ends.
Deleting the salt prevents Runlight from using it to recompute visitor hashes. Runlight does not maintain a persistent visitor identifier across days.
What is stored
For each visit, Runlight stores the hashed visitor, when it started and ended, the pages viewed and their titles, engaged time and scroll depth, the referring site and source, UTM tags, country, region and city, browser and version, operating system and version, device type, screen size, and language. For each event, it stores the event name and the properties you chose to send.
What your site sends
Runlight keeps page paths, page titles, and event properties as your site sends them. If one of them holds personal details, Runlight stores those too. A customer’s name in an invoice page’s title, a reset token in a path, and an email address in an event property would all be kept.
Query strings are dropped from paths, apart from UTM tags. Fragments are dropped too, unless you turn on hash routing with data-hash. With hash routing on, the fragment is kept as part of the path, and some sign-in flows put access tokens there.
To keep such details out, leave them out of what you send, skip the pages that show them with data-exclude, or clean each payload in the browser with data-before-send.
What is never stored
- IP addresses. They are used to make the daily hash and, where needed, to look up a location, then dropped.
- User agents. They are read for the browser, operating system, and device, then dropped.
- Cookies or anything in the visitor’s browser. The script stores nothing, except an opt-out flag you can set for your own browser.
- An identifier that follows anyone across days. The hashed visitor stays with each visit for as long as you keep visits, but once its salt is deleted it cannot be recomputed or matched to anyone’s later visits.
The law
Runlight does not set analytics cookies, and its tracker uses browser storage only for an opt-out flag you choose to set. These design choices do not by themselves determine your obligations under privacy or cookie rules. Review the data you send, your integrations, and the requirements that apply to your deployment. The European Data Protection Board explains the distinction between anonymisation and pseudonymisation.
Runlight stores analytics in your own database. Optional integrations send the data they need to the services you configure. Email reports send report content and recipients to your mail provider. The dashboard assistant sends your questions, supplied details, and the aggregate reports it reads to your chosen AI provider. Connected MCP clients receive the reports their token can read.
This page describes how Runlight works. It is not legal advice.
Your privacy policy
Your privacy policy should say that you use Runlight and what it keeps. You can paste the paragraph below into it. Replace the retention period with the one set for your site in Settings, and add a line for each integration you turned on, such as email reports or the dashboard assistant.
We use Runlight to understand how this site is used. We host Runlight ourselves, and its data is stored in our own database. It sets no cookies and stores nothing in your browser. To count visitors, it combines your IP address and your browser’s user agent with a random value that changes every day and turns them into a one-way hash. Your IP address and user agent are then discarded, and the daily value is deleted, so the hash cannot be used to recognise you on a later day. For each visit we keep the pages you view, how long you stay, the site that sent you, your approximate location (country, region, and city), and your browser, operating system, device type, screen size, and language. We keep this data for [12 months] and do not share it with anyone or use it for advertising. We process it on the basis of our legitimate interest in understanding and improving our site.
Your own data
You own the database. You can query it and back it up like any other, and delete it whenever you like. Short link clicks and email report recipients live there too, and a report recipient can unsubscribe from any email.