Last updated 15 August 2026
StandbyClaim makes no network requests. It has no server, no account and no analytics. Nothing you do in it is transmitted anywhere, because there is nowhere for it to go.
That is a stronger claim than most privacy policies make, so here is how you can check it rather
than take our word for it. Open the extension's folder and search every file for
fetch, XMLHttpRequest, sendBeacon or WebSocket.
You will not find one. Our release script refuses to package the extension if anybody ever adds
one, which means this page cannot quietly stop being true while the code moves on.
You can also just watch. Open Chrome's DevTools, go to the Network tab, and use the extension normally. It stays empty.
Nothing. We do not collect, store, transmit, sell or share any data about you or your leads. We do not know who our users are beyond the email address you gave Stripe when you subscribed, and Stripe holds that, not us.
All of this lives in Chrome's local storage on your machine and never leaves it. You can wipe it at any time by removing the extension.
| What | Why |
|---|---|
| The claim button | The appearance of the button you taught it, so it can find that button again. Text, element type and attributes. No page content beyond that. |
| Claim times | A list of timestamps, so it can honour the hourly limit and show you what happened overnight. Times only, with nothing about the lead or the customer. |
| Your settings | The delays and limits you chose. |
| Your licence key | Checked offline against a signature. Verifying it contacts nobody, so we never learn when or how often you use the extension. |
| A short activity log | What it did and, more usefully, why it declined to do something. Capped, and local. |
Your password. The extension has no login form and no credential storage. It works inside the browser session you are already signed into, as you. We could not obtain your portal password if we wanted to.
Your customers' details. It reads the page only far enough to identify buttons. It does not read, copy, store or transmit customer names, addresses, phone numbers or any other lead content.
| Permission | What it is for |
|---|---|
| Site access | The one site you grant it. The extension ships requesting no site access at all; you grant your own portal the first time you set it up, and nothing else. It cannot touch a site you did not grant. |
| storage | Keeping the settings and the learned button on your machine. |
| scripting | Running the watcher inside the granted portal tab. |
| tabs | Finding your portal tab, and reopening it if it has been closed. |
| alarms | Waking every thirty seconds to check. This is what lets it work with no window open. |
| background | Letting Chrome keep running after you close the last window, so a 3am lead is still caught. |
| notifications | Telling you a lead was claimed. A claim is irreversible and the clock starts immediately, so silence would be worse than useless. |
| power | Asking the machine not to sleep from idleness while it is watching. |
| activeTab | Reading the current tab when you click the extension's own button. |
Subscriptions are handled by Stripe, who process your card and hold your billing details under their own privacy policy. We never see your card number. Your email address is used for one thing: sending your licence key and its monthly renewal. It is not added to a mailing list, and it is not shared with anyone.
If this policy ever changes, the date at the top changes with it. If a change ever made the no-network claim untrue, that would be a different product and it would be said plainly here and on the front page, not buried in a revision.
Questions about any of this go to hello@standbyclaim.com.