privacy

the pet profile you set up — a pet name, type, breed, birthday, adoption date, owner name, and notes.

the care tasks you define (feeding, walks, medication, training, grooming, and so on) — title, schedule, and frequency.

each logged completion or care entry — the date/time, a free-text name of whoever logged it, and an optional note. there are no user accounts, so "who logged it" is just a name someone types in, not a verified identity.

your browser locally remembers a "your name" convenience field and caches the caregiver link after it's created, so you don't have to retype either — neither leaves your device except as part of the link itself.

showing whoever has the caregiver or admin link what's already been done for the pet today, and letting them log the next thing.

sell your data, run ads against it, or share your pet's schedule with anyone outside the people you send the link to.

in a private, access-controlled postgres database. there's no public listing and no accounts — access is entirely by having the admin or caregiver link, each backed by a hashed token.

if you open mochicare from homebase, your homebase account email is shown in that session's page header only — mochicare doesn't store it.

certain care events are reported to your homebase timeline so your family can see what's happening with the pet across all your apps: when someone logs a feeding, walk, accident, or note, and when a feeding or walk task is marked complete. each event includes the timestamp, pet name, who logged it (as a free-text name), and any note you added.

this reporting happens whenever one of those events occurs, no matter how you got into mochicare — a private caregiver or admin link and a homebase launch are treated the same. other log and task types stay app-local and are never sent to homebase.

remove a task, a log entry, or an appointment any time from the admin page. email me if you want a pet's data gone for good.

email hello@theafoundry.com.