Skip to content

Cookieless web analytics · in development

Know what people read. Not who they are.

For blogs, documentation, and long guides: Tereon shows how far readers get through each section of a page and how long they stay there. It sets no cookie, stores nothing on the reader’s device, and cannot recognize anyone from one day to the next.

Status
In development; not available yet
Next
Running on our own sites
Legal review
Pending
Client script
3.3 kB, nothing stored
Tereon’s Reading panel for the blog post /posts/postgres-als-analytics-datenbank/: about 2,200 views, two and a half minutes of average engaged time, 63% average scroll depth, and 47% who reached the last section. Five sections are listed with the share of readers who got there (94%, 93%, 73%, 46%, and 47%), the change from the section before, and the average time in each, between 34 and 44 seconds. (opens the full-size screenshot)
The reading view One post of a demo blog, with demo data: 94% of readers reach the first section, fewer than half the fourth. The demo blog is written in German, so its section names are German. Scroll sideways, or open it full size.

The reading view

Which part of the article did they actually read?

Page views say a post was opened. Average time says little more. Tereon splits every article at its headings and measures each part on its own, so you can see where readers stop and which section holds them.

The section list of the Reading panel, enlarged: five sections from warum-postgres to fazit, each with a bar for the readers who got there (94%, 93%, 73%, 46%, 47%), the change from the section before (−1%, −19%, −27%, +1%), and a bar for the average time in the section (44, 43, 37, 34, and 38 seconds). Numbered markers sit on the three column headings. (opens the full-size screenshot)
The section list, annotated The same post as above, enlarged. The markers point at the three numbers explained below. Demo data. Scroll sideways, or open it full size.
  1. Reach per section

    The share of page views that spent any time in a section. When 94% get to the first section and 46% to the fourth, the article loses half its readers somewhere in the third.

  2. The change between sections

    How many readers the section lost or gained compared with the one before. A rise means readers skipped ahead, often to a conclusion or a code sample.

  3. Time per section

    The average engaged time a section held a reader. Time goes to the section in view: the last heading above the middle of the screen.

The idle rule

A tab left open is not a reader. Time counts only while the page is visible and focused and the reader has given a sign of presence in the last 30 seconds: a scroll, a pointer movement, a key, or a focus. After 30 quiet seconds the clock stops until the next sign. The 30 seconds are kept, so someone who sits still through a long paragraph is counted in full, and someone who walks away adds at most half a minute.

Video playing on the page does not count. Readers who read one screen for more than 30 seconds without touching anything are undercounted; we chose that over crediting forgotten tabs with an hour.

How engaged time is countedA reader scrolls four times in the first 19 seconds, then nothing happens until second 97. Time is counted from 0 to 49 seconds, which is 30 seconds after the last scroll, and not from 49 to 97. After three more signs between 97 and 112 seconds, time is counted again until the page is hidden at 132 seconds.Signs of presenceEngaged time0 s30 s60 s90 s120 s150 s30 s keptnot countedpage hidden
Engaged time over 150 seconds Four scrolls, a quiet minute, three more signs, then the tab is hidden. Only the bronze stretches count.
An article as Tereon sees it
<article>
  <h1>Postgres as an analytics database</h1>
  <h2 id="why-postgres">Why Postgres</h2>
  …
  <h2 id="the-schema">The schema</h2>
  …
</article>
Only the id and the position of each heading are sent, never the text of the page.

The rest of the dashboard

Everything else a site owner expects to see.

One page, one period, every panel answering the same filter. All screens below are the real dashboard with two months of demo data for two invented sites.

Visitors, visits, and how they behave

Eight headline numbers, each compared with the period before: visitors, visits, page views, views per visit, bounce rate, visit duration, engaged time, and scroll depth. Choose a number to chart it per day; the crosshair follows the pointer or the arrow keys.

Eight headline numbers for the last 30 days: 4,451 visitors, 4,793 visits, 8,194 page views, 1.7 views per visit, 57.1% bounce rate, 4 minutes 54 seconds visit duration, 2 minutes 21 seconds engaged time, 63.4% scroll depth, each with its change against the previous period. Engaged time is selected and charted per day, between about two and three minutes, with a tooltip for Wednesday, November 4. (opens the full-size screenshot)
Headline numbers and chart Engaged time chosen as the charted number, with the tooltip on one day. Scroll sideways, or open it full size.

Where visits come from, including AI assistants

A visit’s source is the referrer and campaign tags of its first page view. Tereon groups them into nine channels, one of which is AI Assistant: visits from ChatGPT, Perplexity, Claude, Gemini, Copilot, and similar tools, counted on their own instead of disappearing into Referral. Campaigns, referrers, and every UTM field have their own tabs.

The Sources panel on the Channels tab: Organic Search 1,497 visitors, Referral 1,494, Direct 981, Organic Social 368, AI Assistant 238, Email 145, each with its share and bounce rate. (opens the full-size screenshot)
Sources, Channels tab 238 visits, 5.3%, came from AI assistants in this demo month.

Pages, with time and depth beside each

Top pages, entry pages, and exit pages, each with visitors, views, engaged time, and scroll depth. Paths are stored without query strings, so one article is one row.

The Pages panel listing ten paths of the demo blog, led by /posts/postgres-als-analytics-datenbank/ with 2,083 visitors and 2,211 views, each with engaged time around two and a half minutes and scroll depth around 62%. (opens the full-size screenshot)
Pages The top pages of the demo blog. Its post addresses are German. Scroll sideways, or open it full size.

Technology

Browsers with their versions, operating systems, and device classes, derived on the server from the browser’s own request header. No screen size, no language, no time zone.

The Technology panel on the Versions tab of the demo software site: Chrome 156 with 481 visitors, Safari 27 with 316, Chrome 155, Safari 26, Edge 156, Firefox 158, and older versions. (opens the full-size screenshot)
Technology, Versions tab Browser versions of the demo software site.

Events and conversions

Outbound links, downloads, and not-found pages are recorded without setup. Your own events, such as a booking click, show the share of visitors who triggered them.

The Events panel: outbound 666 visitors with a conversion rate of 15.0%, download 106 at 2.4%, booking_click 29 at 0.7%, and 404 with 15 at 0.3%. (opens the full-size screenshot)
Events booking_click is a named event; the other three are automatic.

Sign-in

The dashboard is private. Today everyone signs in with one shared password; there are no individual accounts yet.

Tereon’s sign-in page: a card with the Tereon name, the heading Sign in, a password field, and a Sign in button. (opens the full-size screenshot)
Sign-in page One password for the whole dashboard.

Filters that apply everywhere

Click any row, a channel, a country, a page, a browser, and every number and panel narrows to it. Filters combine, show as chips, and live in the address, so a view can be bookmarked or sent to a colleague.

The dashboard filtered by two chips, Channel: Organic Search and Country: Germany, with a Clear all link. The headline numbers and the visitors-per-day chart below show only those visits. (opens the full-size screenshot)
A filtered view Organic search from Germany: two chips, one click each to remove. Scroll sideways, or open it full size.

The whole page, light and dark, on any screen

The dashboard follows the system’s light or dark setting and works on a phone. It loads nothing from any other host.

The complete dashboard of the demo blog in light mode: headline numbers, visitors per day with a spike on October 31, Pages, Sources, Reading, Locations led by Germany, Technology, and Events. (opens the full-size screenshot)
Full dashboard, light Every panel of one site for the last 30 days.
The same complete dashboard in dark mode, with light text on a dark blue-gray ground. (opens the full-size screenshot)
Full dashboard, dark The same view in dark mode.
The dashboard on a 390 pixel wide phone screen: the site and period pickers, the eight headline numbers in two columns, the visitors chart, and the start of the Pages panel. (opens the full-size screenshot)
On a phone 390 pixels wide.

On your site

One script tag. Everything else is optional.

The client script is 3.3 kB, 1.7 kB gzipped. It sends a page view when a page opens and one small message with scroll depth and time per section when the reader leaves or hides it.

Include the script
<script defer src="/_s/t.js"></script>
Served from the site’s own domain, so the browser talks to no other host. A site without the forwarding middleware loads https://<collector>/t.js instead.
Name an event on click
<a href="/book" data-tereon-event="booking_click">
  Book a call
</a>
Outbound links and file downloads are recorded without any attribute.
Mark the not-found page
<meta name="tereon:status" content="404" />
Broken links show up as 404 events with the path that was requested.
Send an event from code
window.tereon?.event("profile_pdf_download", {
  profile: "jane-doe",
})
Up to ten small, flat properties. Whatever you pass here is stored, so pass nothing personal.

Privacy by construction

What it keeps, and what it never sees.

Tereon was designed so that a site can measure reach without storing anything on the visitor’s device and without recognizing anyone beyond a single day. Here is exactly what that means.

What Tereon stores and does not store
StoredNever stored
Site, hostname, and path, without the query stringIP address
Referrer host and campaign (UTM) tagsThe full User-Agent header
Country code, from the delivery network’s request headerQuery strings and full referrer URLs
Browser with major version, operating system, device classScreen size, language, time zone
Scroll depth, engaged time, time per sectionCookies, local storage, any device id
Named events with small, flat propertiesAnything typed into the page, or its text
A visitor id that changes every day, cleared after 400 days
One stored row, an engagement message
site            blog
kind            engagement
hostname        blog.example.com
pathname        /posts/edge-postgres
referrer_host   www.google.com
utm_source      newsletter
country         DE
browser         Firefox 147
os, device      Linux, desktop
scroll_depth    72
engaged_ms      48210
sections        {"setup":[0,12040],"results":[1,30170]}
visitor_id      -4812736451209938171
Twelve seconds in the section “setup”, thirty in “results”. The visitor id is meaningless after today. Example values from our engineering briefing.

A visitor id that forgets itself every day

  1. 1

    For each message, the collector hashes the site, the visitor’s address, and the browser header with HMAC-SHA-256 and a key of 16 random bytes for the current UTC day. It keeps the first 64 bits as the visitor id; the address and header are used for that one step and never written anywhere.

  2. 2

    The first message of the next day creates a new random key and deletes the old one. The key was never derived from anything, so it cannot be recreated.

  3. 3

    Yesterday’s ids can no longer be linked to today’s, or to another site. Unique visitors are exact for one day; over a month, someone who returns is counted again.

  • Nothing on the device

    No cookie, no local or session storage, no other device storage. The script reads no screen size, language, or time zone.

  • Objection without a cookie

    Browsers that send Sec-GPC: 1 or DNT: 1 get the same answer as everyone else, and nothing is stored.

  • Retention

    After 400 days the visitor id is cleared from each row. Page views, time, and scroll depth stay; visits and visitors of those days become estimates, and the dashboard says so.

  • Bots are dropped

    Requests from known crawlers, and from browsers that announce they are automated, are answered and not stored.

No servers

No server to patch. No container to keep alive.

Tereon is two small programs on Bunny’s edge network and one table in Postgres. Nothing runs between requests, so there is nothing to keep up, and the raw rows stay in a database you own.

Tereon’s architectureThe visitor's browser loads the 3 kB script and sends small messages, either to the site's own domain, whose middleware forwards them, or directly to the collector. The collector is a Bunny Edge Script that drops bots and objections, computes the daily visitor id, and inserts one row into Postgres over HTTPS. The dashboard is a second edge script with a read-only database role; the site owner signs in to it with the shared password.Visitor’s browsert.js, about 3 kBstores nothingThe site’s own domain/_s/t.js and /_s/emiddleware forwards,signs addressCollectorBunny Edge Scriptfilters, hashes,inserts one rowPostgresappend-onlyevents tableDashboardBunny Edge Scriptread-only roleSite ownerone shared passwordPOSTsignedor directly to the collector’s hostSQL over HTTPSSQL over HTTPSTereon’s architectureThe visitor's browser loads the 3 kB script and sends small messages, either to the site's own domain, whose middleware forwards them, or directly to the collector. The collector is a Bunny Edge Script that drops bots and objections, computes the daily visitor id, and inserts one row into Postgres over HTTPS. The dashboard is a second edge script with a read-only database role; the site owner signs in to it with the shared password.Visitor’s browsert.js, about 3 kB; stores nothingThe site’s own domain/_s/t.js and /_s/emiddleware forwards, signs addressCollectorBunny Edge Scriptfilters, hashes, inserts one rowPostgresappend-only events tableDashboardBunny Edge Script, read-only roleSite ownerPOSTsignedSQL over HTTPSSQL over HTTPSpassword
From the reader to the database Bronze arrows carry data. The dashed path is the alternative without the site’s own middleware.
  • A collector on the edge

    It checks each message, drops bots and objections, computes the daily id, and answers only after the row is written.

  • Postgres over HTTPS

    Both scripts send SQL over HTTPS. No connection pool, no open port, and the dashboard’s database role can only read.

  • Append-only rows

    One row per message. Visits, sources, and bounces are worked out when you look, so a better definition applies to all past data at once.

  • From the site’s own domain

    The site’s middleware can forward /_s/t.js and /_s/e and sign the visitor’s address, so the reader’s browser contacts no other host.

How it compares

Where Tereon differs, and where it falls short.

Four tools many site owners know, against the same questions. The facts about them were read on each vendor’s own pages on November 13, 2026, for our competitor research; “not found” means we did not find it there, not that it does not exist.

Tereon compared with Google Analytics 4, Plausible, Fathom, and Microsoft Clarity
QuestionGoogle Analytics 4PlausibleFathomMicrosoft ClarityTereon
Reading time and reach per sectionOnly through custom eventsNot foundNot foundArea maps with regions drawn by hand; attention mapsYes, automatic from headings that have an id
Recognizes a visitor byFirst-party cookies, kept for two yearsA hash of a daily salt, the domain, address, and browser; salt deleted after 24 hoursA hash of address, browser, site, and a daily saltA random id in a cookieA hash of site, address, and browser with a random salt that is deleted daily
Stores on the visitor’s deviceCookiesNothing; reads an opt-out flagNothingFirst- and third-party cookiesNothing
Scroll depthOne event at 90%1% to 100%Not foundScroll mapsPer page and per section
Engaged timeTime the page was in focusVisible and focused; no idle timeoutA ping on departure, capped at 30 minutesNot foundVisible, focused, and a sign of presence within 30 seconds
Session replay and heatmapsNot foundNot foundNot foundYes, bothNo, by design
FunnelsYesBusiness planNot foundYesNot yet
Revenue reportsYesBusiness planValue and currency onlyPartialNo
AI-assistant channelYes, since May 13, 2026YesYes, since October 2, 2026Partial; AI Overviews not separableYes
Email reports and alertsEmail reports; anomaly alertsEmail and Slack; spike and drop alertsEmail reportsWeekly digest; traffic-drop alertNot yet
Served from the site’s own domainGoogle tag gatewayYes, with a proxy you set upNot foundNot foundYes, through the site’s middleware; not yet tried on Bunny
Retention2 or 14 monthsNo limit on the Starter planWhile subscribedRecordings 30 days; other data 9 monthsVisitor id cleared after 400 days; the rest of each row is kept
Access to the dashboardFive rolesTeams from the Growth planNot foundTwo rolesOne shared password
Client scriptNot foundNot statedAbout 2 kBNot found3.3 kB, 1.7 kB gzipped
Where it runsGoogle; EU data collected through EU serversPlausible’s EU infrastructure, or self-hostedEU traffic in the EU, other traffic in the USMicrosoft Azure; region not statedYour own Bunny edge scripts and Postgres
Price at 10,000 page views a monthFree$9$15FreeNot for sale

Tereon’s column describes the code as built and tested on our machines, not a running service. Among the fifteen tools in our research, only Microsoft Clarity reports attention below page level, through regions drawn by hand. Prices are list prices per month. Corrections are welcome.

Which one fits.

Google Analytics 4
You need funnels, revenue, and advertising reports in one free tool, and you ask visitors for consent anyway; Google says consent mode is needed for visitors from the EU and the UK.
Plausible or Fathom
You want a hosted, cookieless service that works today, with email reports and an import of your Google Analytics history, for a monthly fee.
Microsoft Clarity
You want to watch recordings and heatmaps of real sessions, free of charge. Microsoft requires a consent signal for visitors from the EEA, the UK, and Switzerland.
Tereon
Your question is which parts of your articles get read, you would rather run the measurement in your own Bunny and Postgres accounts, and you can wait until it is ready.

What Tereon does not do.

  • No funnels or goal definitions yet.

    Events show a conversion rate each; a multi-step funnel cannot be defined.

  • No session replay or heatmaps, by design.

    They record far more than measuring reach needs.

  • No returning visitors or cohorts.

    The visitor id changes every day, so someone who comes back tomorrow counts again. That is the price of not following anyone.

  • No revenue or e-commerce reports.

    Tereon is built for content and marketing sites.

  • One shared password.

    There are no individual accounts or roles, and access cannot be withdrawn from one person.

  • No email reports, alerts, or Search Console data yet.

    Today the numbers are in the dashboard and nowhere else.

  • No documented statistics API.

    The raw rows sit in your own Postgres, which you can query directly.

  • Reports read raw rows on every request.

    Fine for small sites; large sites and long periods will need pre-aggregated tables.

Status

Where it stands today.

Tereon is built by Sebastian Software, a small software company in Mainz, Germany, first for its own websites. It is not a product you can sign up for.

  1. Done

    Runs locally

    Collector, reports, and dashboard are tested against an in-memory Postgres and in a real browser. Every screenshot on this page comes from that setup.

  2. Done

    Published, not connected

    Both edge scripts are published to Bunny. They are not connected to a database yet and serve no site; nothing has been verified on the live platform.

  3. Next

    Our own sites

    Connect the database and measure our own sites. Then check what only the real platform can show, such as the visitor address the edge reports and where EU visitors are served.

  4. Pending

    Legal review

    A briefing for a German data-protection review is written. The review has not taken place.

  5. Later

    The known gaps

    Email reports, goal definitions, individual accounts, a documented API, Search Console data, and funnels. No dates.

Want to know which sections your readers reach?

Tereon runs on our own sites first. If you would like to hear when others can use it, or want to talk about measuring reading on yours, write to us.