1. Information We Collect

Check In Together collects the following information:

Accounts:

There is no username, password or email sign-up. The app signs in with an anonymous account created on your phone, and everything below is linked to that account.

From Primary Users (People Being Checked In On):

One account can be set up for the account holder, or by a caregiver for one or more people they look after. For each person checked in on we collect:

• Name
• Phone number (optional)
• Check-in preferences (method, time, and how long to wait before alerting contacts)
• When check-ins were completed or missed. In-app answers are not stored in our database, but they are sent to Anthropic to be summarized, and what they say is added to the recap we store (below).

From Emergency Contacts:

• Phone number
• Name and relationship (provided by primary user)
• Opt-in consent timestamp and method, and the time of any opt-out
• Whether our texts to them were accepted for delivery, and any error code

Consent texts to emergency contacts and to people being checked in on are sent by our servers, at most twice per request, and only for people the account holder added and asked us to contact. People added from app version 1.3 or earlier were sent the request once, by the app, when they were added; from version 1.4 the account holder can ask us to send it again (at most twice) (emergency contacts get the version 1.3 wording shown under SMS Consent). If a contact added in an earlier app version was saved only on the phone, updating the app saves them with us and sends the consent request (at most twice).

Automatically Collected:

• Your phone's time zone, so check-ins happen at your local time
• App usage data (check-in completion, settings changes)
• The status of our texts and calls (for example, whether a call was answered, went to voicemail, or failed)
• Standard request logs kept by our hosting providers, which can include IP addresses

Device Permissions:

• Contacts: Used only when you tap "Import from Contacts" to select an emergency contact, or "Save our number to your contacts" to add Check In Together's number to your phone. We only store the name and phone number of contacts you explicitly choose. Your contact list is not uploaded or scanned.
• Notifications: Used to remind you when a check-in is due.

Check-In Calls, Texts and Answers:

• Voice check-ins are placed as a regular phone call to the number you provide. The call audio is carried by Twilio and relayed through our voice server (hosted by Fly.io) to OpenAI in real time, so the AI companion can converse naturally and the call can be transcribed.
• Text check-ins are a back-and-forth series of SMS messages: we text a few check-in questions and read the replies. The message content is processed to run the check-in.
• A text transcript of the voice call or text conversation is stored on our servers. The account holder who set up the check-ins can read the full conversation, the AI summary, anything it flagged to follow up on, and the running recap in the app. The transcript is processed by our AI provider (Anthropic) to generate the summary. Your responses can include wellbeing or health-related details. You can request deletion of your transcripts at any time by emailing support@checkintogetherapp.com.
• In-app check-ins: your answers are sent to our AI provider (Anthropic) to write a short summary shown in the app, to update the recap described below, and to decide whether your opted-in emergency contacts should get a short heads-up text describing what was noticed (for example, that you mentioned a fall).
• We also keep a short, evolving written recap of how the person has been over time — their usual routine, things they've mentioned, and anything worth following up on — built from their check-in responses and updated after each check-in. We retain your check-in responses to maintain this recap, and it is included when our AI provider (Anthropic) summarizes your next check-in, so the recap reflects how you've been over time rather than a single day. It is kept while your account is active and can be deleted on request.
• The check-in companion is not a doctor and does not provide medical advice, diagnosis, or health monitoring. Check-ins are intended as friendly conversations, not assessments.

2. SMS Text Message Consent

Check In Together sends SMS text messages to emergency contacts, and check-in texts to people who choose text check-ins. We obtain explicit consent via text message (VIA_TEXT) before sending any messages to an emergency contact, or to a person someone else set up check-ins for:

• Opt-in method: They receive an SMS with an opt-in request and must reply with the keyword "YES" to consent to receiving SMS text messages
• Messages sent: To emergency contacts, the messages listed under SMS Consent above (alerts when a check-in is missed, and a one-time opt-in confirmation among them); to people receiving check-ins, their check-in texts or calls and a notice if their check-ins are paused after three days without a response; the account holder is also texted at their own phone number, if one is saved in the app, when check-ins pause
• Message frequency: For emergency contacts, rare — only when a check-in is missed or another listed event happens, so there may be none in a month; for people receiving check-ins, their scheduled check-ins (typically once a day), with up to 6 texts or calls in all for each scheduled check-in if it goes unanswered (just one if the person has no emergency contact who can receive alerts), plus any check-in the account holder starts from the app
• Opt-out: Reply STOP at any time to stop receiving SMS text messages
• Help: Reply HELP for assistance or email support@checkintogetherapp.com
• Message and data rates may apply

We do not sell, rent, or share your phone number with third parties for marketing or promotional purposes. Your phone number is used only for the messages and calls described on this page, and is shared only with the service providers that deliver them (see section 4).

3. How We Use Your Information

• Check-in tracking: Track check-in completion and trigger alerts to your designated contacts when you miss check-ins
• Emergency notifications: Send SMS alerts to opted-in emergency contacts
• Concern alerts: Notify your emergency contacts if what the person says in a text or call check-in suggests they may need help (for example "I fell"). That alert does not quote what was said or say what the concern was. When a missed check-in is later answered, contacts are told either "all clear" (only if nothing in the replies raised a concern) or that the person has replied but we cannot confirm all is well. Our automated check-in number cannot send help: a reply that mentions an emergency is answered with a reminder to call the local emergency number.
• Consent management: Store and honor opt-in/opt-out preferences
• Check-in summaries: Summarize check-ins for the account holder, keep the running recap, and (for in-app check-ins) decide whether to send contacts a heads-up, using the AI providers in section 4
• Reliability: Check whether check-ins, texts, calls and alerts went out as they should, to find and fix problems
• Support: Respond to user inquiries and technical issues

4. Who We Share Your Information With

We do not sell, rent, or share your personal information with third parties for marketing purposes.

Service Providers:

• Supabase - Backend hosting (United States): stores your account data, emergency contacts and their opt-in status, your check-in schedule for server-side reminders and alerts, voice and text check-in transcripts and summaries, and the running recap. Provides authentication (the anonymous accounts described above) and serverless functions.
• Twilio - SMS and voice call delivery (data processor only). For voice check-ins, Twilio carries the audio of the call between you and our AI companion and detects whether a person or voicemail answered; Twilio does not record or retain call audio for us. Twilio keeps its own records of the texts and calls it delivers.
• Fly.io - Hosts our voice server, which relays call audio between Twilio and OpenAI during voice check-ins and saves the transcript to Supabase. It does not store call audio.
• OpenAI - Real-time voice conversation engine for users who choose voice check-ins. Audio of the call is sent to OpenAI to drive the conversation and to transcribe it. OpenAI does not train on this data per their API terms.
• Anthropic (Claude) - After each check-in, the transcript (voice or text check-ins) or your answers (in-app check-ins) are sent to Anthropic to generate a short plain-language summary, to maintain the running recap described above (which can include wellbeing/health-related details shared over prior check-ins), and, for in-app check-ins, to decide whether to send your emergency contacts a heads-up. It also reads each reply as it arrives, together with the conversation so far and a short profile, to decide whether to text the emergency contacts; the person's first name is removed first, other names they or their profile mention may not be. So a reply can be sent to Anthropic several times (with each later reply of the same check-in). Anthropic does not train on this data per their API terms.

When an alert is sent, or a reply could not be read automatically in time, we may review that conversation to check the alert was right and to decide whether to follow up (for example by contacting the account holder). This review is done with AI tools from Anthropic, so the conversation is also sent to Anthropic for it.

Account Holder and Emergency Contacts:

• The account holder who set up your check-ins - can read the full conversation, the AI summary, anything flagged to follow up on, and the running recap (as described in section 1)
• Your opted-in emergency contacts - alerts, and for in-app check-ins, a heads-up that may describe what you said

Legal Requirements:

We may disclose information if required by law, court order, or to protect the safety of users in genuine emergency situations.

With Consent:

Emergency alerts are only sent to contacts you explicitly designate and who have opted in.

5. Data Retention

• Active users: Data retained while account is active
• Check-in transcripts, summaries and the recap: Kept while the account is active, and deleted when the account is deleted or on request. In-app check-in history is stored on your phone.
• Consent records: Kept with the contact's (or checked-in person's) entry in the account, and deleted when the account holder removes them or deletes the account. Our SMS provider separately keeps blocking texts to any number that replied STOP.
• After account deletion: Deleting your account in the app (Settings → Delete Account) immediately and permanently removes your check-in schedule, check-in history and summaries, the running recap, your emergency contacts, and the account itself — and stops all check-in texts and calls and all alerts to your emergency contacts. Deletion requests made by email are completed within 30 days. Deletion does not reach records held outside our database: our providers' own records, such as Twilio's logs of texts and calls already sent, and short-lived server logs are kept under those providers' retention periods.
• Uninstalling the app: Does not delete your account or its data, and does not stop check-in calls and texts or alerts to your emergency contacts. Delete your account in the app first (Settings → Delete Account), or email us.

6. Your Rights

You have the right to:

• Access: Request a copy of your personal data
• Correct: Update inaccurate information in the app settings
• Delete: Permanently delete your account and all your data at any time, right in the app under Settings → Delete Account (or request deletion by email)
• Opt-out: Unsubscribe from SMS alerts at any time (reply STOP)
• Data portability: Request your data in a machine-readable format

To exercise these rights, email: support@checkintogetherapp.com

7. Data Security

We implement industry-standard security measures:

• Encrypted data transmission (HTTPS/TLS)
• Secure cloud storage with encryption at rest
• Access to our database is limited to Check In Together LLC

8. International Users

Check In Together operates from the United States. If you use our service from outside the US, your data will be transferred to and processed in the United States. By using our service, you consent to this transfer.

9. Children

Check In Together is not directed to children under 13 and we do not knowingly collect their information.

10. Changes to This Policy

We may update this Privacy Policy. Changes will be posted on this page with an updated "Last Updated" date. Continued use of the service after changes constitutes acceptance.

11. Contact Us

For privacy questions or concerns:

Email: support@checkintogetherapp.com
Service Operator: Check In Together LLC
Location: United States