/privacyPrivacy policy

Kelo privacy policy

It describes what the Kelo app and server actually do today.

Effective date: November 10, 2026 · Operator: Nam Ho Kang (Kelo)

In short

  • Your data is on your server. Chats, memory, files, keychain and cards are stored by the Kelo server you run. The operator has no way into it (section 2).
  • Your messages go to the AI company you choose, to get a reply, and to the services you connect (section 6).
  • kelo.chat helps with only a few things: the Kelo address (https through a Cloudflare Tunnel to your server), push notifications that carry only a signal, the Google and GitHub sign-in relay (tokens are not stored), the update check, and replies you choose to report (section 5).
  • No analytics. The apps have none. The only exception is Google ML Kit in the Android app, used to scan QR codes and cards, which sends anonymous diagnostics (section 3). This website sets no cookies.
  • Nothing on your server expires on its own: it stays until you delete it. What kelo.chat keeps is deleted on a fixed schedule (section 8).

1. What this policy covers

This policy applies to three things:

  • The Kelo app: the Android app (package chat.kelo.app) and the iPhone app.
  • The Kelo server: software you install and run on a computer you choose.
  • The operator server: this website at kelo.chat and the optional services the Kelo operator runs there (sign-in relay, push relay, Kelo address).

2. The basic idea: your data is on your server

Kelo is a server you run yourself plus a phone app. Your chats, memory, files, keychain, cards and calendar copies are stored by the Kelo server you installed, and you are the one in charge of it. The operator has no access to your server and does not receive your conversations, except a reply you choose to report (section 5). The app talks to the server you connected it to and contains no analytics of its own. The one component that sends usage diagnostics is Google ML Kit, used to scan QR codes and cards (section 3).

3. What the phone app handles

There are two Android apps. One comes from Google Play; the other you download straight from kelo.chat (an APK file). The one from kelo.chat does two more things: it reads steps, sleep, heart rate, weight and exercise from Health Connect, and you can update it to a new version from inside the app. Everything else is the same. Rows marked “only in the app downloaded from kelo.chat” in the table below are that difference.

The iPhone app follows the same rules, and the table below describes the Android app. The differences: its push notifications go through Apple's push service (APNs) and not Google FCM: when you allow notifications, iOS gives the app a push device token, the app sends it to your server only, and to notify you your server passes it through the operator server to Apple's push service, together with only the kind and ids of the notification, never a title or any text (the banner says just "Kelo has an update", worded on your phone, and the app then fetches the details from your own server); it adds no push SDK of any kind, and when push is not set up or you turn notifications off, it checks your server while it is open and when iOS lets it refresh in the background; it has no Google ML Kit, Firebase or analytics component, so no diagnostics are sent to anyone; it does not read health data; and the server address and access token are kept in the iPhone's Keychain. Camera scanning, Face ID and Touch ID are handled on the phone, and pictures and biometric data never reach the app's maker or any server.

Data · permissionWhen, and what forWhere it goes
Server address, device access tokenTo reach your server. You get them from a QR code or a connect link.The phone's secure storage (Android Keystore). Excluded from device backups.
Messages, attachments, photosOnly what you send or pick.Your server. Photos are re-saved without the location they were taken at, and the server strips location data again.
CameraOnly while you scan a connect QR code or a card. Recognition happens on the phone, using Google ML Kit barcode scanning and text recognition.The camera picture and the QR contents go nowhere. ML Kit sends Google anonymous diagnostics: device model, OS and app version, how long scanning took, and a per-install identifier (Google's ML Kit data disclosure).
Reports of a replyOnly when you press and hold an AI reply, choose Report, and send. To find and fix offensive, harmful or wrong replies.Through your server to the operator server (section 5): the reported reply, your message before it only if you tick that box, the reason and comment you gave, the model name and the app version.
MicrophoneOnly when you tap the voice input button.Your phone's speech recognition turns it into text. That is handled by the speech service set up on your phone; only the resulting text goes into the chat.
Calendar (read; write if you allow it)Only after you turn on Connectors → On this device → Calendar. It reads events from 7 days back to 60 days ahead (title, time, place, calendar name, number of attendees, event id). If you also turn on “allow adding and changing events”, the assistant can add, change or delete events in the calendar you pick, each one after you approve it on a card.Your server, where each new copy replaces the last one and is stored encrypted. Turning it off deletes the copy. Changes are made by your phone itself, only the ones you approved.
Contacts (read)Only after you turn on Contacts. Names, phone numbers, emails, company and job title, birthdays, used when the assistant needs to find someone.Your server (encrypted). Each new copy replaces the last; turning it off deletes it. Your contacts are never changed.
Text messages (read, send) — not in the apps you can downloadOnly after you turn on Messages. Received and sent texts (number, text, time) from the last 7, 30 or 90 days (your choice). If you turn on “allow sending texts”, the assistant shows you the recipient and the whole message on an approval card and your phone sends only what you approve. Neither the Google Play app nor the app downloaded from kelo.chat has this. Only a test version that the developers install themselves does.Your server (encrypted). Each new copy replaces the last; turning it off deletes it. Texts you approve go out through your mobile carrier.
Call history (read) — not in the apps you can downloadOnly after you turn on Call history. Calls from the last 30 days (number, saved name, incoming/outgoing/missed, time, length). Neither the Google Play app nor the app downloaded from kelo.chat has this. Only a test version that the developers install themselves does.Your server (encrypted). Each new copy replaces the last; turning it off deletes it.
Phone dialerOnly after you turn on Phone dialer. When the assistant asks to call someone and you approve, the app opens your dialer with the number filled in. You press call yourself; Kelo cannot place or listen to calls (it has no call permission).Nothing is sent.
Notifications (notification access) — not in the apps you can downloadOnly after you turn on Notifications, agree to the notice, and allow Kelo’s notification access in system settings. App name, title, text and time of new notifications. Kelo’s own, ongoing and system notifications and apps you leave out are not sent. Neither the Google Play app nor the app downloaded from kelo.chat has this. Only a test version that the developers install themselves does.Your server (each one encrypted). Deleted after 7 days, and at once when you turn it off.
Health Connect (read, only in the app downloaded from kelo.chat)Only the kinds you tick (steps, sleep, heart rate, weight, exercise), as daily summaries for the last 30 days, read while the app is open. Never used for ads, sale, credit or insurance decisions.Your server (encrypted). Each new copy replaces the last; turning it off deletes it. Nothing is written to Health Connect.
Notifications, push tokenTo tell you about finished tasks, approval requests and similar. The Android app gets a Firebase Cloud Messaging (FCM) token; the iPhone app gets an Apple push (APNs) device token.Registered with your server. To send a notification, your server passes the token through the operator server to Google FCM (Android) or Apple's push service (iPhone) (section 5).
Card detailsWhen you add a card to the wallet. Card scanning happens only on the phone (Google Pay card recognition or ML Kit text recognition): it fills in the number and expiry date, sends no picture anywhere and never reads the CVC.A card without auto-pay is encrypted with a key only your phone holds before it goes to your server, so the server can't read it. Auto-pay can be turned on only while Keyguard is on: such a card is sent once to your server over TLS and encrypted there with the key your phones hold (Keyguard), so the server can't open it after a restart until a phone unlocks it.
LocationOnly when you allow location on your phone. To give the briefing's weather and answer questions like "a pharmacy near me", the app sends the position, its accuracy and the town's name when you open it (at most every 15 minutes): precise or approximate, whichever you chose on the phone. Location is never read while the app is closed.Your server. Only the newest one is kept. Weather services only get coordinates rounded to about 1 km; the place-name lookup only coordinates rounded to about 110 m.
BiometricsTo approve payments, open the keychain and similar.Handled by Android. Fingerprint and face data never reach the app or any server.

4. What your server handles

The Kelo server you installed stores your conversations and their summaries, the assistant's memory and notes, files you upload and results it makes, its journal and the preference rules it has learned, task and approval history, tokens for connected services, keychain items, cards, and copies of what you turned on under On this device (calendar, contacts, texts, call history, notifications, health summaries).

  • Passwords, API keys, service tokens and card numbers are stored encrypted on your server. The AI model can't see them, and they are never sent to the operator.
  • Calendar, contacts, texts, call history, notifications and health summaries from your phone are stored encrypted, per phone. When the assistant answers, the parts it needs go to the AI model you chose (section 6).
  • When it sends a push notification, your server includes a random install secret (install_id) it uses with the operator server. The operator server keeps only a hash of it.
  • Who can see this data depends on how you run your server. The operator has no part in it.

5. What the operator server (kelo.chat) handles

The operator server is involved only when you use the features below, and never receives your conversations, apart from a reply you choose to report.

Update check — the Android app downloaded from kelo.chat and the desktop app (Windows, macOS) only fetch the public version list (kelo.chat/download/latest.json) at start and once a day. Nothing is sent but the app's name and version (User-Agent), and a new version is downloaded only when you tap Get. Google Play and the iPhone app are updated by their stores.

Sign-in relay (Google, GitHub, MCP services)

  • After you sign in with Google or GitHub, the way back passes through kelo.chat/oauth/relay and on to your server. The operator server learns which server address to send you back to, but doesn't keep it.
  • Google and GitHub need a secret that only the operator holds to turn a sign-in code into a token (and, for Google, to renew it). So the operator server makes that request for your server and passes the token straight back. The token exists only in memory while this happens and is not stored.
  • For MCP service sign-ins, the operator server publishes a public document describing the Kelo app (/oauth/client-metadata.json). It contains no personal data.
  • Google sign-in beta request: only the Google email address you typed in the app (plus the services you chose, the app's language and version, and a hash of the install secret). It is used only to add you as a test user and to email you once about the result, kept until the request is handled and deleted 30 days after that (an unhandled request is deleted after 180 days).

Push relay

  • To send a notification, your server sends up to 10 push tokens (FCM tokens for Android phones, APNs device tokens for iPhones, each with the app's environment) and a payload holding only the notification's kind and ids. The operator server hands them to Google FCM or to Apple's push service (APNs). No titles, no text, nothing the assistant wrote; an iPhone banner is a fixed line ("Kelo has an update") that the phone words itself.
  • Stored: the SHA-256 hash of your install secret, when it was first and last used, and a request count. FCM and APNs tokens and payloads are not stored and never written to logs; the operator's APNs key is read from a file on the operator server and is never sent anywhere except as a signature to Apple; logs record only the kind of notification and counts.

Kelo address (an address under kelo.chat)

  • Stored: the name you chose, the SHA-256 hash of your install secret, the Cloudflare tunnel and DNS record ids, and when the name was created and last requested.
  • Traffic uses https and goes through a Cloudflare Tunnel to your server, not through the operator's computer.
  • A name with no connection for 30 days is released and its record deleted. You can also give it back yourself with assistant connect off.

Reports of AI replies

  • When you report a reply in the app, your server sends the operator server: the text of the reported reply, the message you sent just before it (only if you ticked that box), the reason you picked and any comment you wrote, the name of the AI model your server is set to use, and the app version.
  • Nothing else is sent: no other part of your chat history, no account data, and not your server's address. Your server identifies itself with a random install secret, of which the operator server keeps only a SHA-256 hash, to limit abuse.
  • Why: to find offensive, harmful, wrong or privacy-exposing replies and improve Kelo, as Google Play requires of apps with AI-generated content.
  • Kept for 1 year, then deleted automatically. Ask through the contact below to have a report deleted sooner. Only the operator reads them.
  • Tester sign-ups (kelo.chat/tester): email, the phone model you typed, language and time. Used only to send the Google Play closed-test link and to contact you about the test. Emailed to the operator once; deleted when the test ends or on request, and after 180 days at the latest.

All requests

  • To prevent abuse, request counts per IP address are kept briefly in memory, then dropped.
  • The web server's standard access log (IP address, time, requested path) may be kept. Only the most recent 30 MB is kept; older lines are deleted first.
  • This website sets no cookies and loads no analytics, outside fonts or outside scripts.

6. Where data leaves your server

  • The AI company you choose: to write a reply, your conversation and any material it needs go to that company, under its own privacy policy. Before the first message is sent to such a company, the app tells you what is sent (your messages, attachments and results from connected services) and to whom, and asks for your permission once; if you say Later, nothing is sent. The model picker always shows where chats go. You can withdraw your permission at any time, and the app then asks again before the next message. A model you run yourself on your own network sends nothing to a company, so it asks nothing.
  • Services you connect: mail, calendar, GitHub and so on, as much as the assistant needs to use them.
  • Websites the assistant visits: they receive requests like any ordinary visit.
  • Google Firebase Cloud Messaging: delivers push notifications to Android phones (token, kind and ids only).
  • Apple Push Notification service (APNs): delivers push notifications to iPhones (device token, kind and ids only), under Apple's own privacy policy.
  • Google ML Kit (in the phone app): QR and card scanning send Google anonymous diagnostics (device model, OS and app version, scanning time, a per-install identifier). Camera pictures, QR contents and card numbers are not sent.
  • Weather services: for the morning briefing and weather questions, your Kelo server asks for the forecast at the last location your phone sent, rounded to about 1 km: Open-Meteo by default (no key), or the Korea Meteorological Administration (data.go.kr) or WeatherAPI.com when you add your own key. When you name a city in a weather question, that name goes to Open-Meteo. Weather data by Open-Meteo.com (CC BY 4.0).
  • Place names: only when Kelo needs to know which neighbourhood a position is in, or to find places near it (for example "parking near me"), your Kelo server asks Photon by komoot, with coordinates rounded to about 110 m and the words searched for. No key and no account; answers are kept on your server for up to 30 days so the same spot is not asked again. Place data © OpenStreetMap contributors (ODbL).
  • The operator: only a reply you choose to report, as described in section 5.
  • Cloudflare: traffic passes through it when you use a Kelo address or the Cloudflare way to connect.

The operator does not sell personal data.

7. Google user data

When you connect Gmail or Google Calendar with Google sign-in, Kelo asks for Gmail (https://mail.google.com/) and Calendar (calendar.readonly, calendar.events) access. Data received this way is stored only on your server and used only for what you ask the assistant to do (reading and sending mail, viewing, creating and changing events). Sending mail and changing or deleting events need your approval every time. This data is not passed to the operator, not used for advertising, and not read by people other than you. Kelo's use of Google data is designed to follow the Limited Use requirements of the Google API Services User Data Policy.

8. Keeping and deleting

  • Data on your server stays until you delete it. Results you delete in the app sit in the trash for 30 days, then go for good.
  • Removing a device in the app deletes that device's access token and push token.
  • Turning off an On this device item (calendar, contacts, messages, call history, notifications, Health Connect), or removing the phone, deletes that phone’s copy on your server. Notifications are deleted after 7 days even while it stays on.
  • Uninstalling the app deletes the server address and token on the phone.
  • Records on the operator server are deleted as described in section 5. Reports of replies are kept for 1 year and deleted sooner on request.

9. Security

The app talks to your server over https only. Secrets are stored encrypted, the assistant's browser is walled off from your home network, and the work room where code runs has no internet and no secrets. Keeping the computer that runs your server safe (system updates, guarding the .env file and so on) is up to you.

What Kelo reads from web pages, mails and files is treated as data, never as instructions. When such text tries to move data or money, Kelo ignores it and tells the owner. Sending, changing or deleting anything waits for the owner's approval; outside text alone never starts those steps.

10. Children

Kelo is not meant for children under 14.

11. Changes

When this policy changes, the new version is posted on this page with a new effective date.

12. Contact

Privacy questions and requests: [email protected] (operator: Nam Ho Kang)

13. Photo credits

The photographs on the home page come from Wikimedia Commons. Each one, its photographer and its licence:

Start your own AI assistant

Free and open source under AGPL-3.0. Any machine that runs Docker will do.