CPU Bench — Privacy Policy

Effective date: August 28, 2026 · Last updated: August 28, 2026

The short version

Nothing is collected. No personal information, no identifiers, no analytics, no crash reports.
The app has no internet permission. Not a promise — a fact you can check in the app's manifest. It is technically incapable of sending anything anywhere by itself.
What it measures is your watch's processor. How long a piece of arithmetic takes, and what the watch says about itself: model, chip, cores, memory, Android version, battery level and temperature.
Results stay on the watch until you tap Send to phone. That opens a page on your phone with the results carried inside the link — see section 4, which explains exactly what our server does and does not see.
No account, no sign-in, no cloud backup. There is nothing to log in to, and device backup is switched off, so your scores are never copied to your Google account.

1. Who we are & what this covers

CPU Bench ("the app", "we", "us", or "our") is a processor benchmark for Wear OS smartwatches, operated by an independent developer based in Toronto, Ontario, Canada. This Privacy Policy explains what information the app does and does not handle, and the choices you have. By using the app you agree to the practices described here.

The app is standalone: it runs entirely on the watch and has no phone companion app. The one time it interacts with your phone at all is when you ask it to, and that is described in section 4.

2. Information we collect

CPU Bench does not collect, transmit, or share any personal information. There is no account, and the app declares no internet permission, so it cannot send data anywhere on its own. Specifically:

We do not collect your name, email address, phone number, contacts, photos, calendar, or location.
We do not use advertising identifiers, analytics, crash-reporting, or any third-party tracking SDKs.
We do not read your health, fitness, heart-rate, or body-sensor data. The app does not request those permissions. (One of the workloads is named "Health data" because it performs the kind of arithmetic a fitness app does — filtering a heart-rate signal, counting steps, smoothing a GPS track — on synthetic numbers the app generates itself. It reads no sensor and touches none of your data.)
We do not operate any server that receives your measurements.

a. Benchmark results (stored on your device)

Each run records how long each workload took, the scores computed from those times, and the conditions the run happened under: your watch's manufacturer and model, its chip and core layout, maximum clock speeds, total and free memory and storage, screen size, Android and Wear OS version, and the battery level, voltage and temperature before and after the run. It is a description of a watch, not of you, and it contains no identifier that is unique to your device or to you.

Every run is written as a file in the app's private storage on your watch, and is removed when you uninstall the app.

b. A diagnostic log (stored on your device)

The app keeps a rolling technical log of its own decisions — when a run started, which workload was running, why a run was stopped for heat or low battery — capped in size so it cannot grow without limit. It contains the same measurements described above and no personal information, and it is never sent anywhere.

3. Permissions the app requests, and why

Permission	Why the app uses it
`FOREGROUND_SERVICE` `FOREGROUND_SERVICE_SPECIAL_USE`	Keep measuring for the whole length of a run, which takes about two minutes and is the measurement itself. The ongoing notification it must show is how you can see it running, and stop it.
`POST_NOTIFICATIONS`	Show that ongoing notification while a run is in progress. Nothing else is ever posted.
`WAKE_LOCK`	A watch's processor sleeps within seconds of the screen going off, and a sleeping processor cannot be timed. Held only while a run is going, released when it ends.

That is the complete list. In particular the app requests no internet permission, no location, no body sensors, no microphone, no camera, no contacts, and no access to your files.

4. "Send to phone", and what our server sees

A watch is a poor place to read a table of numbers, so the app can hand your results to your phone. This only ever happens when you tap Send to phone. Here is precisely what that does, because the detail matters:

The app compresses your results and puts them into the fragment of a web address — the part after the # — producing a link to transitnowapp.com/cpu-bench-results.html.
It asks Wear OS to open that link on your paired phone. The app itself makes no network connection; the operating system and your phone's browser do the work.
A URL fragment is never sent to the web server. This is how the web works, not a policy we apply: your phone's browser keeps everything after the # to itself. Our server receives a request for the page and nothing else — your results do not reach it.
The page you land on is a plain file with a small script in it. It decodes your results in your own browser and shows them. It sends nothing anywhere, and it has no way to.

What our hosting does see is the ordinary record any web server keeps when a page is requested: that a request happened, roughly when, from which network address, and with which browser. That is standard web-hosting logging, it is not linked to you or to your results, and it would look the same whether you had run a benchmark or simply typed the address in.

The link is yours once it is on your phone. If you forward it to someone, they see the results inside it — so treat it as you would any other link you choose to share.

We do not sell, rent, or share your personal information, because the app does not collect or receive any. No data is shared with advertisers, analytics providers, or any other third party. The app contains no advertising.

6. Data retention

Your runs and the diagnostic log live on your watch until you delete them in the app or uninstall it, at which point they are removed with it. Because device backup is switched off for this app, no copy is kept in your Google account and none is restored to a new watch — deliberately, since a score is only meaningful next to the watch that produced it.

7. Security

Because no data leaves your watch unless you send it yourself, it is protected by the security of your device and the operating system's app-storage sandbox. Keeping data on-device and off any network removes the risks that come with transmitting or storing it elsewhere.

8. Children's privacy

The app is intended for a general audience and is not directed to children under 13. Because the app collects no personal information, it does not knowingly collect personal information from children.

9. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date above and post the new version on this page. Your continued use of the app after an update means you accept the revised policy.

10. Contact us

Questions about this Privacy Policy? Email us at support@transitnowapp.com.