Build42
01 / WHAT GOES IN A REPORT
A small snapshot, not your running history
A report contains what you type, the issue type, app version, build and platform. To help us reproduce a planning problem, the app shows you a summary before sending: the phone's calendar day, selected goal, number of days to the event and plan start (not the event name), the running baseline used for the plan, usual and attempted planned running days, weekly build cap, chosen training weekdays, minimum-run preference, up to 12 availability windows as relative day offsets, the bundled planning-rule version, Foundation mode, number of planned sessions and any plan-failure code. For a failed plan attempt, it also shows which step failed and the exact explanation displayed in the app. If the attempt would replace a saved plan, it includes only that plan's goal, start and end offsets, number of scheduled and past sessions, next-session offset and peak planned Long-run distance. It says whether the attempted inputs came from the saved plan, the current attempt or an older plan without a saved input snapshot, and whether that snapshot is complete. When reporting a current plan rather than a failed replacement, the summary can include up to 52 weekly totals, Long-run distances, run counts and phase names. You may optionally select one affected week to add up to seven planned sessions from that week: their type, phase, distance or planned duration, and day offset from the first planned session. It is not the full plan. Your individual Health workouts, exact session dates, calendar contents, store transaction, device identifier and saved answers are not automatically attached.
If those totals were derived from Apple Health or Health Connect, the app asks for a separate choice before sending them. If you choose to type health or injury details yourself, it also asks for an explicit choice for those details. Please share only what is needed to explain the problem. A reply email is optional and is sent only if you ask for one.
In builds that offer full-copy email, a separate unticked choice asks whether the complete report may also go through Cloudflare Email Service to the fixed Project42 Apps support inbox, [email protected]. That email includes your message, the reviewed planning summary, app/build details and any reply address you supplied. It can therefore contain the health-related information you separately chose to share. If you do not agree to this delivery, do not send the report; you can use the website contact form for a general question without an automatic planning summary.
02 / WHAT WE DO WITH IT
Investigate and fix the issue
The individual developer operating as Project42 Apps is responsible for the report. The developer's legal name is shown on the Apple App Store developer profile. The app sends the report over HTTPS to a Build42-only receiving function at Supabase. The function checks the permitted fields and size, rate-limits submissions and places the report in a private support queue in Supabase's EU North region. For newly consented full-copy reports, our server also sends the complete report to a separate Cloudflare mail worker, which delivers it to our fixed consumer Gmail support inbox. Cloudflare and Google may process that email outside the Supabase hosting region. Only the returned reference is shown in the app; it confirms the queue received the report, not necessarily that the email arrived. Reports do not become coaching inputs or change a plan. We use the report for support, reproduction and product improvements, not advertising or sale of data.
The receiver uses connection information to prevent abuse. It hashes the connection IP with a server-held key for a short rate-limit window; it does not store the raw IP in the report. Rate-limit counters are removed after about two hours. Supabase may process necessary service metadata under its data-processing terms. The app does not collect an account or track usage in the background through this route.
03 / YOUR CHOICE AND CONTROL
Nothing leaves until you agree
Before Send is available you must describe the issue and tick the per-report agreement. The separate Health-derived-summary agreement is required when that summary is attached; newer builds also require the full-copy email choice. You can close the form without sending; there is no silent upload or automatic retry. If the app cannot confirm queue receipt, it does not say the report was sent. If email delivery fails after the queue receives it, the report remains in the private queue for support review.
Raw reports and linked triage notes are removed after at most 12 months by a scheduled retention process. Full-copy support emails must also be deleted from the inbox and Trash within 12 months, or earlier on a valid deletion request; this is a separate operational check, not an automatic feature of Supabase retention. To request access or earlier deletion, use the Project42 Apps contact form and give the report reference shown after sending. Removing Build42's data from your device does not automatically delete a report you already chose to send. No Build42 account is needed to report or to ask about a report. Depending on the processing, UK privacy rights may apply, including withdrawal of consent and erasure. You may also complain to the Information Commissioner's Office.