Build42Ask a question
Use the Project42 Apps contact form and choose Build42, or email [email protected]. A general enquiry does not automatically attach your plan or Health history. The contact-form privacy notice explains that route.
Please do not send passwords, payment-card details or unnecessary medical information. Support is not a medical or emergency service, and no reply time is guaranteed.
Help us reproduce a plan problem
In the app, choose Report an issue or Report a plan problem. Describe what you were trying to do, what happened instead and the affected week or run. If a change failed, tell us which change you made.
Review the exact diagnostic summary before sending. It includes the planning inputs and version used, bounded availability/weekly information and any failed step/explanation. You can choose one affected week to add its planned sessions. It does not automatically attach your full plan or individual Health workouts. Older or incomplete inputs may need follow-up.
Separate choices cover Health-derived totals, health details you type and emailing the full report to our support inbox. Nothing is sent simply because planning fails. You can cancel or use general contact instead. Read the issue-report privacy details shown in your version before sending.
Keep the receipt reference. It confirms the support queue received the report, not that its email arrived. If you need to follow up, quote that reference and your app version/build. If no receipt appears, sending was not confirmed; contact us if you are unsure rather than repeatedly submitting sensitive details.
Apple confirmed payment, but Plus is still locked?
Do not buy again. Check you are using the same platform/account, reconnect to the internet and choose Settings → Build42 Plus → Restore purchases. If verification is still unavailable, tell us the exact message, app version/build and whether you are using TestFlight or the App Store. Do not send the full receipt or signed transaction in a general email.
A verified purchase has a 30-day offline allowance, not an expiry or subscription. If that allowance ends while verification is unavailable, paid actions may need a successful recheck. Removing local data clears the access cache, not the store purchase; an eligible purchase can be restored.
Apple and Android purchases do not transfer between platforms. Android purchasing is not yet enabled. TestFlight/sandbox transactions are not charged production purchases or permanent tester codes. Store-issued early-tester codes are separate.
For refunds use the store's process; for Apple, request help with a purchase. Your statutory consumer rights are not removed by our terms or the store route.
Remove your data
Use Settings → Remove my Build42 data for local plans, recovery copies, imported workouts held by the app, answers, check-ins, preferences, acceptance, cached Plus verification and app-owned temporary CSV exports. The app also tries to remove identifiable Build42 calendar entries. Follow any cleanup warning and retry; Calendar permission may need restoring.
This cannot erase original Health records, backups, exports saved or shared elsewhere, store purchases or reports already sent. Android's calendar is device-local, not promised Google-account/cloud sync.
Delete a report already sent
Contact us separately and quote its receipt reference. If you have lost it, provide the approximate date and any reply email supplied. We may ask for proportionate information to find it safely. The request covers the private support queue and our email copies; local reset does not delete them.
Reports and related support emails are kept for up to 12 months. Email, Trash, downloaded and forwarded copies require separate operator cleanup; database retention does not automatically remove those copies.