Build42
01 / TERMS AND SAFETY
Who can use the test
Build42 is a private-test running-planning app. It uses running records you permit it to read from Apple Health on iPhone or iPad, or Health Connect on Android, together with answers you provide, to create and track a plan on your device. You can also provide a running background without connecting a health service. Build42 does not connect directly to Strava or Garmin and does not ask an AI service to generate or change your plan.
You must be at least 18, have reached the age of majority where you live, have been invited to this closed test, and be in a country where Build42 is offered to that test group.
Running carries risk
You decide whether to start, continue, change or stop a run or race. Running and changes in training carry a risk of injury. Build42 cannot assess your individual medical fitness or guarantee that a plan is safe, suitable, achievable or effective for you. It does not provide medical advice, diagnosis, treatment, medical clearance, emergency support or injury prediction. Stop and seek appropriate independent healthcare advice if you have concerns about symptoms, illness, injury or participation. In an emergency, contact local emergency services.
This safety explanation describes the app's limits; it does not transfer all responsibility for injury to you. Nothing in these terms excludes or restricts liability for death or personal injury caused by negligence, fraud, or any other right or remedy that cannot lawfully be excluded where you live. Accepting these terms does not stop you bringing a claim. Build42 does not promise that the app will always be available or error-free during the test. Any limit on other liability is deliberately left out of these private-test terms.
02 / RUNNING DATA
Your data and permissions
Build42 asks for a separate, unticked choice to use imported running data locally before it first reads workouts. This is separate from accepting these terms and from the health service's own permission. On Apple devices, Build42 requests read access to permitted running workouts through Apple Health. On Android, it requests read access to permitted exercise-session and related distance records through Health Connect. You can change or withdraw those permissions in the relevant health service. Build42 does not write to either health service, and removing Build42 data does not remove the original records there. You can withdraw Build42's local-data choice in Settings; this stops further imports and removes Build42's current local imported workouts.
Your plans, saved plans, imported running history held by Build42, availability, answers, check-ins, preferences and acceptance record are stored on your device. Build42 does not upload your Health records or plan for coaching. Your device's own backup or transfer service may handle app data under its settings and privacy terms.
The training-availability question asks if you can fit the planned running into your life; it does not ask for an injury or other medical reason. A pause or later start is a scheduling choice, not a medical assessment or clearance. Earlier app versions may have stored an injury-labelled answer locally. It is preserved on update and is not covered by the separate imported-workout consent. The privacy notice explains the local answer and deletion route without claiming that older data is non-sensitive.
03 / OPTIONAL FEEDBACK
What you choose to send
If you choose Send to Build42, the report you review is sent to Build42's private feedback service hosted by Supabase. It includes your message and category, the screen, app version, platform and build number. You can choose whether to include the diagnostics shown before sending. Those diagnostics can include Health-link state, running-history source, goal distance and mode, available-day count, whether a plan exists and its session count, tester access and calendar-sync state. Individual Health samples, your full plan, event name, calendar contents and the text of saved answers are not automatically attached. Please do not put sensitive health details in the free-text message unless you intend to send them.
Before sending, you must say whether your message includes health or injury details. If it does, Build42 requires a separate, unticked explicit consent for that report and records that choice with the submission. Please classify your message accurately; Build42 cannot reliably detect every sensitive detail in free text.
You may separately provide an email address and agree to follow-up about that report. You may save that preference on your device for later reports; each report still requires its own Send action. Copy and Share do not send a report to Build42. Raw submitted feedback is retained for up to 12 months and then deleted or reduced to a minimal resolution record. It is used for private-test support and improvement, not advertising, data brokerage or automated coaching. Build42 also reads a basic private-test status; that check does not send your running history or plan.
04 / LEAVING THE TEST
Remove your data
In Settings, Leave private test and remove my data removes Build42's local plans, imported workouts held by Build42, answers, check-ins, settings, acceptance and feedback drafts. You can then delete the app. This does not delete records in Apple Health or Health Connect, device-backup copies, or feedback already submitted to Build42.
To ask about or request deletion of submitted feedback, use the Project42 Apps contact form and choose Build42. If you supplied a follow-up email, provide it along with the approximate submission date and a brief description so the report can be located. Do not send passwords or health details in that request. There is no Build42 account to delete.
Build42's full privacy notice explains data handling in more detail. Paul Conby trades as Project42 Apps; privacy and test queries may be sent to [email protected] or through the Project42 Apps contact form. These terms do not select an exclusive governing law or court. They do not remove mandatory consumer or privacy rights that apply where you live.
05 / ACCEPTANCE
When you accept
Before Build42 creates or changes a training plan, you must actively accept the notice version shown in the app. Build42 records the version, acceptance time, installed build and notice scope on your device. Reviewing an unchanged version does not ask you to accept again. A materially changed version requires fresh acceptance; an ordinary app update should retain the earlier record until that change occurs. Refusing or withdrawing acceptance prevents plan creation.