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.

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

How to send feedback right now

There are three easy ways to reach us during the beta: the Send Feedback button in the app, TestFlight, or email.

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. Before you send a screenshot, check it for names, photos, or health details. Crop or cover them first. If you can't, describe the screen in words instead. 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 feedback@carehaven.org. 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?

You can tap Send Feedback in the app, under Settings → About & Help → Send Feedback, to write a note without leaving CareHaven. It needs you to be signed in to iCloud. If it shows an error, email feedback@carehaven.org instead.

It covers the same ground as TestFlight and email above — a suggestion, a bug you tripped over, or a plain "this part is working great." Here is the flow: open Settings → About & Help → Send Feedback, write your note, and check the box that consents to sending. Nothing ever leaves silently on its own. If you are not signed in to iCloud, the app asks you to sign in first.

What gets sent when you use Send Feedback

• Your message — first run through an aggressive scrub that catches names, emails, and phone numbers, right on your device, before it ever leaves your phone. That scrub is best effort, not a guarantee, so give your own note a glance before you send it too.
• The app version and build, plus a coarse device descriptor like "iPhone, iOS 26" — never a serial number or exact model.

Opt-in and private by design. It only sends after you personally tick that consent box. No names, no person IDs, no care data ride along with it. You will need to be signed in with iCloud for it to go through. If it shows an error, email feedback@carehaven.org instead.

What makes a report most useful

You do not need to write a bug report like an engineer. Plain language is perfect.

Please leave out names, photos, and health details. Say "my son" or "the person I care for" instead of a name. We never need to know who you care for to fix a problem.

A few specifics help us find and fix things faster:

• Which screen you were on, and what you tapped just before things went wrong.
• What you expected to happen, and what actually happened instead.
• Your device and iOS version, if you know them. TestFlight adds the build number for you.
• A screenshot, if it is something you can see (TestFlight makes this easy). Before you send a screenshot, check it for names, photos, or health details. Crop or cover them first. If you can't, describe the screen in words instead.

The kinds of feedback that help most:

• Anything that looks wrong with your data. After an update, the most important check is whether everything you had before is still there. If something is missing or changed, tell us which screen and what changed. You do not need to tell us what the entry said.
• "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 situation. Tell us which screen it was on and what it said, in a few words.
• 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 you use the in-app Send Feedback button, your message gets an aggressive scrub on your own phone before it ever leaves — names, emails, and phone numbers it can recognize are stripped out. The scrub is best effort, so give what you wrote a quick glance too before sending. Only the app version and a coarse device label go with it — no person IDs and no care data ride along. 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 is not scrubbed, so please do not include names, photos, or health details. Say "my daughter" or "the person I care for" instead. We never need to know who you care for to fix a problem.

A reminder that holds for everything in CareHaven: your care log lives on your device and, if you turn on sync, is reachable only by the people you specifically invite into your circle. Backups are encrypted too. 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