Data & Analytics

Bias Isn't Agreement: step-count validator

A step counter that reads exactly half the true count correlates with the reference at 1.0000 - perfectly - and is wrong on every single walk. A step counter that reads +500 on one walk and -500 on the next has a mean error of exactly zero and can still miss by a thousand steps on any given walk. Correlation and bias are the two numbers usually reported, and neither is agreement. The limits of agreement are: on eight walks with a mean error of zero and a spread of 534.52, an individual walk can differ by anything from -1,047.66 to +1,047.66 steps. That band is what a product decision is made against, not the zero.

← All products
Data & Analytics

Teams validating step counters, activity trackers and other wearable sensors against a reference, and anyone who has to defend an accuracy claim to someone who will check it.

How it works

  1. Add the paired counts, one row per walk: the reference on one side and the device on the other.
  2. Read the limits of agreement, not just the bias - they answer different questions.
  3. Set your tolerance and the low-count threshold: those are choices about your product.
  4. Look at the largest single difference next to the summary, and at the flagged short walks.

What you gain

  • Tells you whether two step counters actually agree with each other, not just whether they move together — a distinction a device can pass on correlation while being wrong on every walk.

Screenshot

Technical details

Standard27.99 USD · 1500 requests · 31-day license · one-time payment · 31-day access
Pro55.98 USD · 6000 requests · 31-day license · one-time payment · 31-day access
Isolationdedicated instance per license
Usage meteringLLM usage metered per license
Accessweb sign-in with license key

How to set up & use

  1. Buy the license — your key (lic_...) appears on the order page and in your email.
  2. Sign in at app.synoriaai.com with your license key.
  3. No installation — the product runs in your browser, on your own isolated instance.
  4. 1. Open the page and enter a label for your first walk (e.g., 'w1').
  5. 2. Enter the true step count in the 'Reference' field and the device's count in the 'Device' field.
  6. 3. Click 'Add pair' to record that walk. Repeat for each walk you have data for.
  7. 4. Once you've added all your walks, the page will show the bias, limits of agreement, correlation, and the largest single difference.
  8. 5. Review the results—if you set a reference threshold, any walks below it are flagged separately.

Frequently asked questions

What does this tool actually tell me about my wearable?

It shows the bias (average difference) and the limits of agreement (the range where an individual measurement might fall) between your device and the true step count. It also shows correlation, but clearly states that correlation is not agreement—a device that always reads half the true count will have perfect correlation but be wrong.

How does it handle very short walks or missing data?

You can set a reference threshold; any walk below that threshold is flagged separately rather than averaged in, because a 100-step miss is proportionally huge on a short walk. If a column doesn't vary (e.g., all references are the same), correlation is shown as 'undefined' instead of zero, which is the honest result.

Is my data safe? Does this tool store my walk data?

No. All calculations happen in your browser—your entered walk data is never sent to a server or stored. You can refresh the page and everything is cleared.

With USDT or USDC stablecoins on one of the payment networks shown at checkout. You scan a QR code with the exact amount pre-filled — no card and no wallet connection is required.
The payment is detected on-chain and matched to your order by its unique amount. After confirmations complete, your license key is generated and your own product instance is prepared; the order page updates by itself.
No. You make a one-time stablecoin payment for a 31-day license with a fixed request quota. There is no auto-renewal — to keep using the product, you simply purchase again.
Each plan includes a fixed number of requests for the license period. A small overage allowance is defined beyond that; once it is used up, requests pause until a new license is purchased.
Yes. Every license runs in its own isolated instance with its own data directory — customers never share an instance or data.
On-chain payments are never lost. Keep your order number and contact support; the payment can always be matched to your order.
Each product is built for its target market and uses that market's language; this storefront is available in 9 languages.

Related products