Keep Every Page Alive does not run accounts, advertising trackers, or fingerprinting. Session lists stay on your device. The website uses self-hosted, cookieless pageview analytics (details below); the browser extension still phones home to no one.
keepalive.page is a static page. The list of sites you ask it to keep alive is held in your browser's localStorage on your own device. Your list, your intervals, your refresh counts and your settings are never uploaded, and closing the tab or clearing your browser data removes them.
There is one deliberate exception, and it is small: when you add a page, we count the bare hostname — mail.google.com, not the address you actually typed — so we can see which services people are fighting with and write better advice about them. What that means precisely:
.local and .internal addresses, IP addresses and localhost. An internal hostname would identify your employer, so it never leaves your machine.That same hostname is also the only thing behind the on-site leaderboard: a small, self-hosted counter of our own (separate from the analytics below) tallies how many times each public hostname has been added, across everyone who uses the tool, and the page can show that running count. Nothing beyond a hostname and a total is ever kept for it — no visitor identifier, no IP address, no timestamp is ever exposed — and a hostname only appears once a handful of additions have counted it, specifically so one person's single unusual site can never surface on its own as a de-facto reveal of who uses it.
To switch it off entirely, run this once in your browser's console on this site — it is remembered on this device and nothing further is ever counted or added to the leaderboard:
localStorage.setItem('keepalive:no-count','1')
Any content blocker that stops the analytics script does not also stop the leaderboard counter, since that one isn't a third-party script — use the console command above if you want both off. The tool works exactly the same either way.
The site loads no advertising trackers, no fingerprinting scripts, and no third-party fonts or frames. Its content security policy allows network requests only to itself and to our self-hosted analytics endpoint (below).
Our web server keeps ordinary short-lived access logs (IP address, requested path, user agent) as any web server does. These are used only to keep the service running and are not combined with anything else or shared.
We run a self-hosted Plausible Analytics instance at plausible.junovin.com (not Plausible Cloud). It records pageviews without cookies and without storing personal information: path, referrer, browser, OS, and coarse country from the request. There is no cross-site tracking and no advertising profile. You can block it with any content blocker; the tool still works.
The extension stores your list — a nickname, the site's origin, and your chosen interval — using chrome.storage.local on your own machine. Nothing is uploaded, there is no remote code, and the extension never contacts keepalive.page or any third party.
It does talk to the sites you keep alive: reloading their tabs, and on some rungs of the keepalive ladder sending a background request to that site carrying your browser's own cookies — the same traffic your browser would send if you reloaded the page yourself. Those requests go only to the site being kept alive, never to us.
Its permissions, plainly:
activeTab — reads the address of the tab you clicked, at the moment you press Keep this tab alive, so it knows which site you meant.webRequest and cookies — used on your machine to tell whether a kept site's session is actually still alive (for example, spotting a redirect to a login page). Cookie values are inspected locally for that check only; they are never stored beyond it and never transmitted anywhere.scripting — injects the on-page agent into sites you granted, so in-page keepalive methods can run.alarms, storage, idle — scheduling timers, saving your list locally, and pausing work when your screen locks.The extension does not request the tabs permission and therefore cannot read your browsing history or the addresses of tabs you have not explicitly added.
Reloading a page you asked us to keep alive causes your browser to send its own cookies to that site, exactly as it would if you pressed reload yourself. The website cannot see those cookies at all; the extension can inspect them locally on sites you granted (that is how it verifies a session is still alive) but never stores them beyond that check or sends them anywhere. No session information ever passes through us.
The product is free today. If optional paid features ever ship, payment processing will go through a standard provider (for example Stripe). We will not sell browsing data to fund the product. License state, if any, stays on your device unless you explicitly opt into a sync feature that does not exist yet.
Questions about this policy: brandon.gatz@gmail.com.