OldCare

Every day, a warm phone call for your parent — and a reassuring note for you.

OldCare calls at a time your parent chooses and keeps them company — an unhurried chat about their day. After each call, a short daily note lands in your inbox: how they sounded, and whether the day’s routines got done.

How it works

01

One warm call a day

Every day, at a time your parent picks, OldCare calls for an easy, unhurried chat — no rushing, no script.

02

A short daily note for you

After each call you get a brief note: how your parent sounded, whether the day’s check-ins were completed, and anything worth knowing.

03

Your parent stays in charge

Everything starts with your parent’s own consent. They decide what gets shared — and any conversation can stay private.

Sample note

Thursday, July 9

Uncle Lin has sounded brighter over his last few calls.

All 3 daily check-ins completed

Uncle Lin was in a good mood today — he finally fixed the garden fence he’d been talking about.

When your parent says private, it stays private

The note is not surveillance. Your parent can keep any day’s conversation private — you’ll simply see that the call went fine. That respect is part of the product.

Friday, July 10

A private day

The call took place as usual. Uncle Lin chose to keep today’s conversation private.

Saturday, July 11

No call today

We couldn’t reach Uncle Lin today. We’ll try again at the usual time tomorrow.

Privacy isn’t a setting. It’s the structure.

This section describes only database-side constraints already implemented. Incomplete production wiring, end-to-end deletion, and real drills are called out explicitly.

Revocation takes effect immediately

If your parent says on a call that they no longer want to share, you stop seeing notes from the very next read — and scheduled calls are cancelled automatically.

You see the note, never the conversation

Recordings, transcripts, and the assistant’s memory live in a private system the family app cannot query — guaranteed by the database structure, not hidden by the interface.

Consent is evidence, not a checkbox

Every consent is a verifiable record containing a cryptographic fingerprint of the exact text your parent saw. Without written consent, the system cannot place a single call.

Deletion still requires real end-to-end drills

The database implements part of the deletion inventory and state gates. The real log adapter, independent tombstone service, file-storage and phone-provider deletion, and post-recovery replay drills are not complete. We do not claim that end-to-end deletion has been verified.

Learn about our security

Honest answers to common questions

Start with the current test boundary

The current version is only for internal synthetic validation. Production billing, real-family use, and real calls are not open.

View the test entry

OldCare is in early access — we keep our current limits in plain sight. Read where we stand today