MeetClara meetclara.org

Privacy Policy

Effective date: August 16, 2026 · Last updated: August 16, 2026

The short version: we collect only what it takes for Clara to call your loved one and save their stories for your family. We never sell or rent your data. This policy explains everything in plain English — if anything is unclear, email privacy@meetclara.org.

1. Who we are

"MeetClara" (the "App", "we", "us") is operated by Alex Koby (sole proprietor). The App is a service that places scheduled, AI-driven phone calls to a "loved one" (typically a parent or grandparent) on behalf of a "buyer" (typically an adult family member). The buyer reviews recorded calls, transcripts, and AI-extracted summaries from a mobile dashboard.

2. Who can use MeetClara

MeetClara is intended for use by adults age 18 and over. We do not knowingly collect data from anyone under 18. If you believe a minor has provided data to us, contact us and we will delete it.

3. The people involved

MeetClara is unusual: the person paying for the service ("buyer") is not always the person being called ("loved one"). Both are covered by this policy — as are care-team members the buyer invites (§6).

4. Data we collect

From the buyer (when you sign up + use the App)

CategoryExamplesWhy we collect it
Email addressyou@example.comAccount login (one-time codes), care-team invites, support
Google / Apple identity (optional)Name + email from your Google or Apple account if you use Sign in with Google or Sign in with AppleAccount creation and login
Phone number (optional)+1 555 123 4567Account contact, account recovery
Name + relationship"Alex", "Daughter"Personalize emails + dashboard
Profile photo (optional)Avatar uploaded to Supabase StoragePersonalize dashboard
Loved-one details you enterName, phone, relationship, life context, photosRequired to call them and personalize the conversation
Coarse location (optional)City of the loved one (resolved via Google Places)"Margaret in Louisville, KY" personalization in the dashboard and call prompts
Authentication tokensIssued by Supabase Auth on sign-inKeep you signed in; protected on-device by the operating system
Nothing from your microphoneThe App may request microphone permission (required by the audio session used for Listen In playback) — we never capture audio from your device
Server-side error reportsError details from our servers when something breaks (configured to exclude message content and to minimize personal identifiers)Diagnose failures and regressions

From the loved one (during a phone call)

CategoryExamplesWhy we collect it
Voice recordingLossless FLAC of the full conversationBuyer's review on the dashboard. AI summary + memory extraction
TranscriptText of what was said by the loved one and by ClaraBuyer review, AI processing
Conversation contentWhatever the loved one chooses to share — childhood memories, wellness signals, family stories, opinionsMemory extraction, buyer review
Sentiment / wellness signalsComputed mood score, "red flags" (e.g. mentions of falls or distress)Surfaced to the buyer as a "wellness pulse"
Phone numberAlready provided by the buyer; not separately collected from the loved oneRequired to dial the call

We do not collect:

5. Call recording (important)

Every Clara call is recorded — audio and transcript. That is the heart of the service: the recording is what lets your family listen to the conversation and keep the stories. On a first call, Clara introduces herself as calling on behalf of the buyer. The loved one can hang up at any time; the recording stops the moment the call ends.

Buyers are responsible for recording consent. Call recording laws vary by state and country, and some places require the consent of everyone on the call. By scheduling calls, you confirm that you have told your loved one that these calls are recorded and that they have agreed, to the extent your local law requires their consent. If a loved one does not want to be called or recorded, remove their profile in the App (which stops all future calls) — and email privacy@meetclara.org to have existing recordings deleted.

6. How we use your data

Buyer data

Loved-one data

Sharing within your family (care team)

Aggregated, non-personal use

7. Third-party services we share data with

We use the following processors. Each one receives only the data necessary to do its job. None resell your data.

VendorWhat they receivePurpose
Supabase (Inc., USA)Account data, profiles of loved ones, transcripts, summaries, audio file references, vector embeddingsDatabase, authentication, file storage
Twilio (Inc., USA)Loved-one phone number; live audio stream during the callPlace + receive the phone call
Deepgram (Inc., USA)Live audio stream; recorded audio for post-call transcriptionReal-time + batch speech-to-text (AssemblyAI Inc. or OpenAI LLC serve as automatic fallbacks if Deepgram is unavailable)
ElevenLabs (Inc., USA)Text of Clara's responsesSynthesize Clara's voice (Cartesia Inc., USA is a supported alternate provider)
OpenAI (LLC, USA) / Google (LLC, USA) / Anthropic (PBC, USA)Recent transcript + system prompt; memory and transcript passages, and your search queries, for embedding generation (Google)Generate Clara's conversational responses; post-call summary; memory extraction and search
OpenRouter (Inc., USA)Transcripts, conversation history, and profile context sent to certain of the language models aboveAPI gateway that routes some of our LLM requests (e.g. to Anthropic models)
Railway (Corp., USA)All data our backend processes, including live call audio in transit and transcripts in memoryHosts our servers
Resend (Inc., USA)Your email address; the content of sign-in-code and care-team-invite emails (invites can include short excerpts from the loved one's calls)Transactional email delivery
LiveKit (Inc., USA)A copy of the live call audio during calls, when our "Listen In" service is enabledLets a buyer listen to a call in real time from their app (listening itself is buyer-initiated)
Google Places API (Google LLC)City name typed by the buyer during onboardingCity autocomplete
Google / Apple (as identity providers)The fact that you signed in to MeetClara with their account systemSign in with Google / Sign in with Apple
Sentry (Inc., USA)Error reports from our servers — configured conservatively: no conversation content, no request bodies, personal identifiers excluded where possible. Not enabled inside the app on your device.Crash + error reporting
Vercel (Inc., USA)Standard web-server logs (IP address, browser info) when you visit meetclara.org pages, including invite linksHosts this website
EAS / Expo (Inc., USA)App build artifacts; no end-user dataApp build + distribution

We have signed standard data-processing agreements with each vendor where available. We do not sell or rent personal data to advertisers, brokers, or any other party.

8. Where data is stored

9. How long we keep your data

DataRetention
Active account data + recordingsUntil your account is deleted on request (below)
Recording access audit log (who played which recording, when, from where)While the account is active — it exists to protect the recordings; retained in pseudonymized form afterward
Authentication logsRetained by our authentication provider for a limited period for fraud/abuse investigation
Aggregated, non-identifying metricsIndefinitely (no personal data)

To permanently delete your entire account — including all profiles, recordings, and transcripts — email privacy@meetclara.org from your account email address. Deletion completes within 30 days. (An in-app deletion flow is on our roadmap; until it ships, email is the way.)

10. Your rights

Depending on where you live, you have the right to:

To exercise these rights, email privacy@meetclara.org. We respond within 30 days. If you live in California (CCPA/CPRA) or the European Economic Area / UK (GDPR), the same rights apply with the deadlines those laws impose.

11. Security

We use industry-standard practices to protect your data:

We are a small team and do not yet have SOC 2 or HIPAA attestations. We make security decisions conservatively but cannot promise an attack will never succeed. If we discover a breach affecting your data, we will notify you within 72 hours.

12. Children's privacy

MeetClara is not intended for, marketed to, or knowingly used by anyone under 18. We do not knowingly collect personal data from children. If you believe a child has provided us with data, contact us immediately and we will delete it.

13. Changes to this policy

If we materially change how we collect or use data, we will email you at least 30 days before the change takes effect, and update the "Last updated" date above. Continued use of the App after the change constitutes acceptance.

14. Contact

ReasonContact
Privacy questions, data requestsprivacy@meetclara.org
Security disclosuresecurity@meetclara.org
General supportsupport@meetclara.org