Reach us

We live on the repo.
And we read our email.

There is no support queue and no ticket you wait days on, because there is no company. NOOP is built in the open by a small independent team. For anything broken, the repo is the front door. And if you would rather just talk to a human, there is one address that reaches us directly. We read every one.

No account needed anywhere Public and searchable Read by the makers One direct address
Talk to a human

One address reaches us directly.

Not everything is a bug report, and not everyone wants to make a GitHub account to say hello. If you have a question, a thank-you, a worry about your privacy, a press query, or something that does not fit a public thread, email the team. It is an anonymous, project-owned address, not a personal inbox. A real person on the project reads it.

thenoopapp@gmail.com

For a bug we can actually fix, a repo issue is still the fastest route, it lands right where the code lives. But the door above is always open, and it is the warm one.

Where to reach us

Every door, one project.

Pick the one that fits. For anything broken, the issue tracker is the front door and the fastest route to a fix. To reach a person, the email above is the warmest.

Start here
🐛

Repo issues

The primary channel, and the one that actually changes the app. Bugs, crashes, a strap that will not pair, a number that looks wrong: file it here. One clear report from someone holding the hardware is worth more to us than anything.

File a bug
Talk to a human
✉️

Email the team

The warm, private way in. Questions, worries, press, anything that does not belong in a public thread. thenoopapp@gmail.com is anonymous and project-owned, not a personal address, and a real person reads it.

Email us
📚

The wiki

The manual and the deep dives. Pairing guides, the analytics and Fitness Age write-ups, device notes and troubleshooting. Worth a quick search before you file, your answer may already be written down.

Read the wiki
💬

Reddit, r/NOOPApp

The community hub. Release notes land here, people swap setups and tips, and it is the right place for questions, ideas and general chat that are not quite a bug report.

Join r/NOOPApp
🎤

Discord

For real-time help and a faster back-and-forth when you are mid-setup. Good for quick questions; if it turns out to be a genuine bug, we will point you to the issue tracker so it does not get lost.

Open Discord
💻

The source

Everything is here, in the open. Read the code, check the maths, fork it, or send a pull request. Nothing about NOOP is hidden behind a wall, and that is on purpose.

Browse the repo
♥️

Support the work

Not a contact channel as such, but people keep asking how to chip in. NOOP is free forever and always will be. If it is useful to you and you want to help keep it going, here is how.

See ways to help

The best message starts with your hardware on your wrist.

We cannot reproduce what we cannot see. A real strap, a real reading and a clear description of what went wrong tells us more than a hundred guesses. If you have the band on, you are already most of the way to a fix.

A two minute guide

How to file a bug we can actually fix.

You do not need to be technical. You just need to tell us what you did, what you expected, and what happened instead. Three steps.

1

Set the scene

Tell us what you are running so we can match your setup to ours.

Include: your platform (macOS, Android or iPhone), the app version (it is on the Settings screen), and which band you use (WHOOP 4.0, 5.0, MG or an Oura Ring).
2

Show the steps

Walk us through it like a recipe. The shorter and clearer the path to the problem, the faster we land on the cause.

For example: "Paired the strap, opened Today, tapped Charge. Expected a breakdown, got a blank card and a spinner that never stops."
3

Bring the evidence

A picture and a log turn a hunch into a fix. Nothing here leaves your device unless you choose to attach it.

Attach: a screenshot of the screen, and the diagnostics from Settings, Test Centre, Export. It bundles the local logs you can review before sending.

Point us at the screen

Show us exactly where it went wrong.

A screenshot of the actual screen is the single most useful thing you can attach. Here is the app you are looking at, so you know which view to grab and what to call it when you file.

The NOOP Today screen with Charge, Effort and Rest rings over a dusk sky and metric cards for stress, fitness age, HRV and resting heart rate.
A NOOP score breakdown screen showing what went into the day's number.
The NOOP More menu listing Coach, Workouts, Health, Lab Book, Stress, Breathe, Intervals and Compare.
The NOOP Settings screen, where the app version and the Test Centre export live.

Tell us the screen by name: Today, a score breakdown, the More menu, or Settings. The app version and the Test Centre export both live under Settings.

The short version

A great report answers five questions.

Hit these and there is a good chance we can reproduce the problem on the first read, which is more than half the work.

  • What did you do? The exact steps, in order.
  • What did you expect? What you thought the app would do.
  • What happened instead? The actual result, in your own words.
  • On what? Platform, app version and the band you are reading from.
  • How often? Every time, or only sometimes. Intermittent bugs need that clue most of all.

A little etiquette

What helps, and what slows us down.

Helps Do this

  • Search the issues and wiki first, your bug may already be open.
  • One issue per problem, with a clear, specific title.
  • Attach a screenshot and the Test Centre export.
  • Say plainly if you are unsure whether it is a bug or a question.
  • Be patient and kind. This is built by people, for free, in their own time.

Slows us Avoid this

  • Piling several unrelated problems into one thread.
  • "It does not work" with no platform, version or steps.
  • Posting private data: redact anything you would not want public.
  • Pinging multiple channels for the same issue at once.
  • Treating an issue like a chat. We answer with substance, then close.

What we cannot see

When you email us, your health data stays put.

This is the whole point of NOOP. There is no account, no cloud, no server, so there is nothing of yours sitting on our side to leak. Your heart and your sleep never leave your device unless you choose to attach something. An email reaches us; your readings do not come with it.

📲On your deviceBLE bytes from a strap you own, decoded and stored in local SQLite. Yours alone.
🧮Scored locallyPure on-device analytics. No reading is ever sent off the device.
You email usPlain words to thenoopapp@gmail.com. Only what you type, nothing pulled from the app.
Their wayYour signals uploaded to a company cloud, scored behind a subscription.

If you ever do attach a screenshot or a Test Centre export to help us debug, it is because you chose to. Redact anything personal first; once it is in a public issue it is public.

The bigger reason we are reachable, not sellable

The most sustainable wearable is the one you already own.

Trackers and watches are glued shut, hard to repair, and replaced on a two-to-three-year cycle driven by subscriptions and planned obsolescence, not by failure. Cancel the subscription and a perfectly good band becomes e-waste. NOOP keeps the strap you bought useful for years: no forced upgrade, no account, no subscription that can brick it. Open and local, it can outlive any one company, including this one.

62 Mtof e-waste generated in 2022, up 82% since 2010, about 7.8 kg per person
82 Mtprojected by 2030 on current trends
22.3%formally collected and recycled; about US$62bn of materials lost
~30%of fitness trackers and smartwatches end up abandoned

Sources: UN / ITU / UNITAR Global E-waste Monitor 2024 (ewastemonitor.info); abandonment figure, Gartner. NOOP is an independent project, not affiliated with WHOOP or Oura, and not a medical device; values shown in the app are approximate estimates.

Public by design, private by default.

The repo and the community are public so anyone can read, search and learn from them. The email is private, anonymous on our side, and project-owned. Your data is a different matter entirely: it lives on your device and only ever leaves it if you deliberately attach a screenshot or an export to a report. There is no account here, no analytics, no tracking, no ads, and no inbox of yours we can see, so please redact anything personal before you post.

0accounts, trackers or ads
1direct email to a human
100%of your health data stays on-device

Ready when you are

Found something? Or just want to say hello?

A bug goes to the repo, where it lands next to the code. Anything else, a question, an idea, a thank-you, comes to the inbox. Both doors are open and both are read by the people who make NOOP.

Prefer the community? Join us on Reddit r/NOOPApp or Discord.