App Information, Privacy Policy & Support

App Information

Kehai

Kehai is a passive check-in app for families and carers of someone who lives alone. It reports whether that person's phone showed any sign of use during the day, so that someone at a distance can tell they are up and about without calling or being tracked. It observes a phone, not a person: there is no location tracking, no camera monitoring, and no access to the content of calls or messages.

• Features
  • Hourly check-ins from the watched person's phone, running in the background
  • Detection of whether the phone was used (screen unlock, Android only) or carried (walking)
  • Battery level, so a flat battery can be told apart from an unresponsive person
  • A daily status that escalates if no sign of activity is seen, and a month calendar of past days
  • Pairing by invite code, which the watched person must approve before anything is shared
  • The watched person can see who is watching them, and end any of those at any time

Privacy Policy

This Privacy Policy explains what information Kehai collects, how it is used, and with whom it is shared.

Information We Collect

• Account information: When you sign in, we use Firebase Authentication (Sign in with Apple on iPhone, Google Sign-In on Android). We store a unique user ID (UID) associated with your account. We do not receive or store your Apple/Google account password.
• Display name: The name from the account you signed in with, or a name you enter yourself in the app. It is shown to the people you are paired with so they can tell who you are.
• Activity signals: Whether the phone was unlocked or interacted with (Android only; iOS provides no way for an app to detect this), and whether walking was detected. We record only whether such activity occurred, never what was done, which apps were opened, or what was typed or read.
• Step counts: On Android, the device step counter value is recorded alongside each check-in. It is used to tell a failed reading apart from a genuine absence of walking, so that a sensor error is not reported as "did not move".
• Battery level: The percentage of battery remaining, so that a phone that has run out of power is not mistaken for a person who has stopped responding.
• Device type: Whether the phone is an iPhone or an Android device, because the two can detect different things and the app states which.
• Subscription status: Whether you have an active Premium subscription, managed via RevenueCat. Payment details (card numbers, billing address) are handled directly by Apple's App Store or Google Play and are never received by Kehai or RevenueCat.

Kehai does not collect location data, photographs or camera images, the content of calls, messages or email, browsing history, contacts, your address, telephone number or date of birth. The camera is used only to scan a pairing invite code; images are neither stored nor transmitted.

How Information Is Used

• To show the people you are paired with whether your phone showed any sign of activity on a given day, and how much battery it has left.
• To decide when to show a "no response yet" state, and when a phone has stopped reporting altogether.
• To show you who is currently able to see your information, and when each of those arrangements began.

Your information is shown only to people you have explicitly approved. A pairing request does nothing until the person being watched approves it. Either side can end a pairing at any time from within the app, after which the other side can no longer see any further information. We do not sell, rent or otherwise provide your information to third parties.

Health Data (iPhone)

On iPhone, Kehai reads step data from Apple HealthKit in order to detect walking. This data is used solely for the check-in purpose described in this policy. It is not used for advertising, marketing, or any form of data mining, and it is not sold or disclosed to third parties.

Third-Party Services

• Firebase (Google LLC): Kehai uses Firebase Authentication for sign-in, Cloud Firestore to store check-ins and pairings, and Cloud Functions to process them. Data is stored on Google's servers in the Tokyo region (asia-northeast1).
• Sign in with Apple / Google Sign-In: Used for authentication only. We receive a user identifier and, where you have chosen to share it, a name.
• RevenueCat: Used to manage in-app subscription purchases and verify your subscription status. Apple or Google pass RevenueCat a device/account identifier and your purchase information; no payment card details are included.

Data Retention

• Individual check-in records are deleted automatically 90 days after they are recorded.
• Your account, display name and pairings are kept until you delete your account.

Children's Privacy

Kehai is intended for adults arranging to check in on a family member or someone in their care. It is not directed at children under 13, and we do not knowingly collect information from them.

Your Choices

• You can see every person currently able to view your information, and the date each arrangement began, from within the app.
• You can end any pairing at any time, from either side.
• You can change the name shown to others at any time.
• You can sign out, or delete your account and all associated data, from the app's settings.
• On Android, the permissions the app relies on (usage access, physical activity) can be revoked at any time in the device's settings. Doing so stops the corresponding detection.

Data Deletion Requests (Kehai)

You can delete your account and your data directly in the app:

1. Open Kehai and tap the settings icon in the top right of the home screen.
2. Tap アカウントを削除 (Delete Account).
3. Read the confirmation, which tells you how many people are currently paired with you, and confirm.

If you are unable to use the app (e.g., it has been uninstalled), you can request the same deletion by emailing us at the address below with the account information you used.

What is deleted and how long it takes: Your account record, display name, every pairing you are part of, any outstanding invite code, and your entire check-in history are deleted immediately (within seconds) from our database (Cloud Firestore). Check-in history is deleted outright rather than being left to expire under the 90-day retention described above. Your Firebase Authentication account (UID) is deleted immediately afterwards. We do not maintain separate backups of this data, so once deleted it is not recoverable.

Deleting your account ends the arrangement for everyone paired with you. If others were checking in on you, they will no longer receive any information. The app does not notify them that this has happened, so please tell them yourself if that matters.

Support

If you have any questions, bug reports, or feature requests regarding this application, please contact the developer.

Email:
contact@sieqxeon.com

Developer

sieqxeon