EveryBand
EveryBand support
EveryBand is the public name for Boop. The installed iPhone app, TestFlight listing, Apple Health source and **Boop Full** purchase can still say Boop. This is the same product, not a second app or a new purchase. The website is every.band.
This guide describes the documented TestFlight beta, reviewed on 16 October 2026. App Store release remains pending. Check TestFlight for your available build, requirements and changes. Features and control labels can differ between betas; include your installed version when asking for help.
Is EveryBand the official WHOOP application?
No. EveryBand is **independent**, not affiliated with, endorsed by or sponsored by **WHOOP**, Apple or Bevel. Direct Bluetooth connection to compatible WHOOP hardware is a core feature. Optional Apple Health input adds another data path; it does not replace direct strap support.
There is no EveryBand account, and the app does not need access to your WHOOP account. It does not retrieve WHOOP cloud scores or promise to reproduce another app's Recovery, Sleep or Strain number. Its wellness estimates use their own methods.
Check hardware and choose a data path
Documented direct Bluetooth support covers **WHOOP 4.0, WHOOP 5.0 and WHOOP MG**, with model and firmware limits. Battery, firmware and supported history have been tested on these models. That does not validate every sensor or control. Unrecognized history remains unavailable; MG ECG and WHOOP 4.0 temperature/oxygen calibration are not validated features to rely on.
Alternatively, use supported records already in Apple Health, with or without a strap. Apple Watch contributes through Health: EveryBand has no native watchOS app or continuous live Watch stream. Other wearables contribute categories they actually save to Health, not an assumed direct connection.
Connect a new strap or reconnect a saved one
1. Charge the strap, enable iPhone Bluetooth and keep it nearby.
2. Open **Settings → Pair a new strap** in Boop.
3. For a new band, use pairing mode with blue lights blinking, choose **Find a new strap**, then select it in Apple's accessory sheet.
4. For an existing band, choose it under **Saved straps** rather than repeatedly adding it again.
5. Complete onboarding acknowledgements and let the first history transfer finish with the app open.
A strap can already be system-connected without appearing in a normal scan. An empty scan is therefore different from proof of unsupported hardware. Resolve any Bluetooth permission/system blocker shown by the app. Do not begin troubleshooting by deleting the app, resetting the band or erasing history.
If pairing still fails, describe the model and whether failure occurs before accessory selection, during connection or during transfer. Do not send device identifiers.
Understand the history-offload acknowledgement
EveryBand saves supported strap history on the iPhone before acknowledging it, then may trim acknowledged history from the strap. **Trimmed history can become unavailable to the official app.** Read the explicit onboarding acknowledgement before enabling this workflow. Using two apps does not guarantee both retain the same strap records.
Connection, receipt of history, local processing and Health export are separate stages. A connected indicator does not mean the history is complete or Health received it. Avoid deleting local data to repair a delay: the phone may hold records already removed from the strap.
Should I keep EveryBand open during initial strap history transfer?
Yes. Keep Boop in the **foreground** for the **initial** history pass, with the charged strap in range. Let the status settle before force-quitting. The local activity log can help identify the stage; do not send the log to support.
For a later delay, check the selected saved strap, Bluetooth, range and battery; open the app and use its refresh control. An old observation time differs from the time a catch-up completed: an unworn band may have no new valid readings after its backlog transfers.
Background imports have been observed, but iOS scheduling, radio interruptions and protected data affect timing. There is no guaranteed overnight freshness, exact delivery interval or uninterrupted connection. Force-quitting can prevent normal restoration; it does not make background sync more reliable.
How do I choose Apple Health input?
Choose **Apple Health** on **Your data** during setup, then select the categories you want in the system **permission** sheet. **Set Up Later** remains available. Local supported strap processing can continue without Health export.
Permissions are specific to category and direction. Reading sleep is different from writing sleep; one permission does not enable the other. Your selected path and actual available records also matter. A missing reading alone does not prove you denied access.
Can I change Health permissions later?
Yes. Review Boop's **permissions** in Apple Health or the corresponding iOS **Settings → Health → Data Access & Devices** controls; the exact route can vary by iOS version. Look for **Boop**, even though the website says EveryBand. Grant only the read/write categories you want. EveryBand cannot bypass denied permissions.
After changing one category, return to Boop and refresh the relevant day. Repeatedly toggling every permission obscures the failed step. Unlock the iPhone and allow processing to continue when a Health write was deferred while locked.
Can Apple Watch readings appear later?
Yes. Apple Watch or its originating app can save readings to **Apple Health later**. EveryBand reads saved records, not a live Watch stream. Confirm category, timestamp and source in Health, let the originating device/app synchronize, then return to Boop and refresh.
If the original record is absent in Health, EveryBand cannot import it through that path. With several sources, inspect their records rather than assuming every value came from one wearable. Imported Health readings are not automatically written back as new Boop records.
Troubleshoot missing Health imports or exports
Start with **one direction, one category and one period**—for example, reading last night's sleep rather than “all sync is broken.”
1. For an import, confirm the original record exists in Health and check its source and recorded time.
2. Check the selected data path and corresponding read permission.
3. For an export, confirm the local record finished processing and the appropriate write permission/export setting is enabled.
4. Unlock the iPhone, open Boop and allow pending work to continue. Initial strap transfer may need to finish first.
5. Inspect the resulting Health category/source. If still missing, describe the direction and failed step to support without sending the record.
Not every local estimate qualifies for every Health type. Experimental interval variation or local nightly RMSSD is not automatically eligible as Health HRV (SDNN) or a heartbeat series. Successful heart-rate export does not establish that sleep, HRV and workouts are also eligible or authorized.
Sleep is missing, incomplete or different
Check the selected day and whether transfer/import has completed. Inspect source coverage and the sleep interval. Connection or visible heart rate does not prove the night has closed or contains evidence for every detail.
Time in bed can include waking and differs from time asleep. A nap does not simply replace the main overnight sleep. Missing stages are not invented: sleep may remain unspecified without a complete stage chart. Fit, movement, quiet waking and incomplete observations affect estimated boundaries and stages.
Sleep combines duration against estimated need, regularity, efficiency and available sleep-stress context. Missing factors and algorithm versions can change the result. A stage chart is not a sleep study. Hand off a completed night still absent after foreground catch-up; do not infer a sleep disorder or promise an overnight fix.
Recovery, HRV and calibration
Current Full Recovery requires **local nightly RMSSD, resting heart rate and a Sleep score**, plus at least **two prior complete baseline nights**. Each prior qualifying night needs HRV, resting heart rate and three hours of recorded sleep. That is a software completeness rule, not advice that three hours is sufficient sleep. The reference uses up to 30 prior calendar days; producing any score does not require waiting 30 days.
EveryBand's documented Apple Health HRV input is **SDNN**, separate from nightly **RMSSD**. It does not replace the required Recovery input. A Watch-only setup can therefore show useful Health records while Recovery stays unavailable. Full unlocks features; it cannot supply missing measurements or complete nights.
Check the missing input instead of manually inserting a value to unlock a score. EveryBand is not a medical device. Scores are independent wellness estimates, not clinical probabilities, diagnoses or safe-training clearances. Differences from WHOOP or Bevel do not establish medical correctness.
Workouts, activity and Strain
In supported Full builds, **Fitness** shows recorded activities and selected-day detail; **Add Workout** is available from Fitness or the global Add action. Check day, activity type, start/end interval and whether a session remains active or paused before creating another entry. Resume or finish it using its controls; leaving the screen does not establish completion.
Duration, heart-rate coverage and Strain describe different things. Missing strain is not zero; incomplete heart-rate coverage does not establish complete zone time. Strain is an independent exertion index and can exceed 100; it is not a percentage of your capacity or a target you must reach. Strength logs do not establish validated muscular-strain measurement. Recent betas include activity-finalization corrections. Report your build and whether an activity was truncated or mislabelled, without sharing GPS routes or health exports.
Where available, **Export overlapping detected workouts** under Apple Health settings can create duplicates when enabled if another app recorded the same period. With it off, detected overlapping workouts are skipped; manual workouts are separate. Inspect existing Health sources before changing it or adding another workout.
Storage, export frequency and older days
EveryBand keeps a bounded local store, not an unlimited backup. Supported Full builds expose **Local retention** under **Export Schedule**. Read your build's raw-detail/graph-history day counts and confirmation before changing them. Options differ between betas; longer retention uses more local space and cannot reconstruct already-deleted detail.
Export frequency differs from retention and Bluetooth sync frequency. Export Schedule provides heart-rate and steps/calorie cadence controls. Continuous **1 Hz** heart-rate export can create about **86,400 samples daily** before other records. Workout heart rate and interval events have their own behavior. These settings do not force iOS to run or improve sensor accuracy.
Older history can come from Apple Health when records exist and access is permitted. If export was unavailable before retention expired, some detail may be unrecoverable. Do not uninstall as a routine repair. There is no EveryBand account or health-data cloud from which support can restore your complete history.
Free, Boop Full and restoring purchases
The documented offer is free download plus optional **Boop Full**, a **one-time purchase**, not an EveryBand subscription. Full adds analysis/history and features such as Journal, Fitness and Biology in supported builds. Availability depends on version and data. The purchase sheet shows any localized price; no fixed amount is promised here.
Open the Boop Full purchase screen from Settings and choose **Restore Purchases** with the purchasing Apple Account. Wait for its result before retrying. TestFlight purchases are free sandbox transactions and **do not carry over to the App Store version**. A sandbox entitlement does not establish a production purchase.
If restore fails, describe version, distribution channel and displayed error without sharing receipts, payment details or Apple credentials. A person must handle entitlement disputes, refunds or missing real purchases. The assistant cannot inspect an Apple account, grant Full or issue a refund.
Journal, Biology and Ask Boop
In supported Full builds, Journal records factors and notes for the selected local day. Check that day before editing an older entry. Comparisons require enough measured days with and without a factor; association does not prove the behavior caused the outcome.
Energy Reserve is a wellness index, separate from calorie expenditure. Stress describes recorded physiological context, not emotions or an anxiety diagnosis. Boop Age and Biology outputs are wellness estimates with input/calibration requirements, not medically measured biological age. Experimental outputs and VO₂max work are not validated measurements for every workout, device or beta.
Ask Boop** inside the app differs from this support assistant. It uses on-device Apple Intelligence when available and deterministic on-device guidance otherwise. Device/model readiness affects availability. App health context is not sent to a third-party model. Neither assistant should diagnose personal readings or decide whether strenuous exercise is safe.
Privacy, deletion and safe recovery
Strap and authorized Health processing run on the iPhone, without an EveryBand health-data cloud or app analytics. Health export, shared files and Apple backup/synchronization follow your choices; this is not a promise that data never leaves the phone. Diagnostic exports can contain biometric bytes and identifiers—do not upload them to chat.
Deleting Boop removes its local container. Existing Health records are managed separately with Health's source controls. Local detail or already-trimmed strap history may be lost. Ask for help before deleting if your goal is recovering or repairing history.
Support is a separate service: X70 Help stores messages, and an automated model may process the question with approved documentation. Do not include health values, exports, GPS routes, passwords, recovery codes or device identifiers. Only voluntarily upload screenshots after removing personal/health information. The website contact form is not a diagnostic-export or attachment channel.
What should a useful support description contain?
Include the **Boop app version/build**, **iOS version**, distribution channel, strap model if relevant, and a short **description** of expected versus actual behavior. Explain the failed step, selected day and whether the issue concerns Bluetooth, processing, Health import/export, purchase or UI. Describe the category without its personal reading. A redacted error message is more useful than a raw log.
Ask for a person when pairing remains blocked, history may be lost, a crash repeats, purchase/restore needs investigation, or your version contradicts this guide. Personal medical interpretation, guaranteed overnight results, unsupported sensor accuracy and account/data recovery also require handoff. The assistant cannot inspect your phone, recover unavailable history, change purchases or certify health outcomes. Personal health concerns need a qualified healthcare professional; support can explain app behavior but cannot make a medical decision.
