CareHaven is now in beta on iPhone — install in ~60 seconds. Join the beta →

For Beta Testers Current as of Build 69

Giving feedback

You are an early tester, which makes you one of the most useful people in CareHaven's whole world right now. The things you notice — the screen you could not find, the wording that felt off, the moment the app did something surprising — are exactly what shape the next version. None of it is too small to mention.

On this page

This page covers how to send feedback today, what makes a report most useful, and how your feedback stays private.

How to send feedback right now

There are two easy ways to reach us during the beta.

TestFlight feedback

TestFlight (the app you used to install CareHaven) has feedback built in. Take a screenshot while you are using CareHaven, and TestFlight offers to attach it to a quick note. Or open the CareHaven page inside TestFlight and tap Send Beta Feedback. Your note goes straight to us, along with the build number and basic device info that TestFlight includes for every tester.

This is the quickest way to flag something the moment you hit it.

Email

You can also just email us at shawn@getcarehaven.app. Bugs, paper cuts, "I went looking for X and could not find it" — all welcome, anytime. A founder reads every message.

What about "Send Feedback" inside the app?

CareHaven is building a Send Feedback option right into the app, under Settings, so you can write a note without leaving CareHaven. It is built, but it is turned off in the current beta build, so you will not see it yet. Coming soon

When it does turn on, it will work like this: you pick a category, write your note, and check a consent box before anything sends — there is no silent send. Your message is cleaned of names, emails, and phone numbers right on your phone first. Only the app version and a rough device label (something like "iPhone, iOS 26") ride along — never names, never anyone's care data, never an exact serial or model.

For now, use TestFlight or email above.

What makes a report most useful

You do not need to write a bug report like an engineer. Plain language is perfect. But a few specifics help us find and fix things faster:

  • Which profile you were on — the person you had selected when it happened.
  • Which screen you were on, and what you tapped just before things went wrong.
  • What you expected to happen, and what actually happened instead.
  • A screenshot, if it is something you can see (TestFlight makes this easy).

The kinds of feedback that help most:

  • Anything that looks wrong with your data. After an update, the most important check is whether all your profiles and everything you logged are still there. If anything is missing or changed, tell us right away.
  • "I could not find it." If you went hunting for a feature and came up empty, tell us the words you searched. That tells us where the app's language does not match yours.
  • Wording that feels off — a card or a script that reads preachy, cold, or wrong for your person.
  • Anything that felt slow, janky, or confusing, even if it still worked.
  • A field you wish a feature had, or a step that was awkward to fill in.

If a feature is one we have flagged as still coming — a fast-follow we mention in the build's notes or here in the wiki — you do not need to report it as missing. But if you have an opinion on how it should work, we want it.

Your feedback is private

CareHaven is privacy-first, and feedback is no exception.

When the in-app Send Feedback channel turns on, your message gets an aggressive scrub on your own phone before it ever leaves — names, emails, and phone numbers are stripped out. Only the app version and a coarse device label go with it. No names, no person IDs, no care data, ever. And nothing sends at all unless you check the consent box yourself.

If you email or use TestFlight feedback, just a heads-up: free text you type by hand may still contain a name if you paste one in. You are always in control of what you write, so if you would rather not include a name, a quick "my daughter" or "the profile I care for" works fine for us.

A reminder that holds for everything in CareHaven: all of your care data lives on your device, and backups are encrypted. Feedback is a separate, opt-in channel — it never opens up your private logs.

A note of thanks

Testing an app for a family you are already carrying a lot for is generous. Every report, even a one-line "this felt weird," makes CareHaven better for the next caregiver. Thank you.


See also: Getting CareHaven · What's new · Known limitations & what's coming · Privacy & security · Troubleshooting

Was this page helpful? Send a note if something is missing, confusing, or out of date.

Give feedback
Maintainer note

Generated 2026-06-13. Current build marker: Build 69.

Sources: docs/BetaTesterNotes.md (Beta App Description feedback line; per-build "What to Test" data-survival + "I could not find it" prompts); FEATURES.md (Feedback + supplemental content: Send Feedback PII-strip + coarse device descriptor + consent gate); docs/ServerArchitecture.md (CloudKit Feedback record, opt-in, PII-scrubbed, free-text caveat); ios/CareHaven/Resources/WebContent/help_topics.json (sendFeedback topic); AVAILABILITY MAP (Send Feedback = Coming soon, hidden in current build); KNOWN FACTS (Send Feedback hidden; use shawn@getcarehaven.app / TestFlight today)