KoiKeep
FeaturesHow it worksFAQWeb app
Get the app

KoiKeep

Privacy Policy

Last updated: November 16, 2026

1. Who we are

KoiKeep is a pond journal for koi keepers. It is made and run by Peter Chan, an independent developer based in California, USA ("we", "us"). This policy explains what information the KoiKeep mobile app, the KoiKeep web app at koikeepapp.com and this website collect, why, where it is kept, and the choices you have. If anything here is unclear, email [email protected].

2. Using the app without an account

You can look around a sample pond, read the care articles and glossary, browse the koi variety catalog and use the pond calculators without signing in. We don't ask for any personal information to do that, and nothing you do in those parts of the app is saved to an account.

3. Information we collect

When you create an account and use KoiKeep, we store the following:

  • Account details: your email address and, if you add one, a display name. If you sign up with an email and password, the password is handled by our sign-in provider and stored only in scrambled (hashed) form. We never see it.
  • Details from Google or Apple: if you choose Sign in with Google, we receive your name, email address and a link to your Google profile photo. If you choose Sign in with Apple, we receive your email address (or a private relay address, if you choose to hide yours) and your name if you choose to share it.
  • Your pond records: everything you add in the app, including:
    • ponds: name, size, the city and state you type in, and an optional photo
    • water tests: readings such as pH, ammonia, nitrite, nitrate, phosphate, KH, salinity and temperatures, plus the date and any notes
    • journal entries, including tags, any cost you enter and which items from your medicine cabinet a treatment used and how much, and pond memories (photos and videos with a title, including any sound recorded with a video, and whether you marked them as a favourite)
    • feedings you log: when, the food, the amount, how many times that day, how your koi ate, which bag of food it came from and any note
    • the bags of food in your pantry: brand, food, size, cost, the dates you bought, opened and finished each one, the label figures you add (protein, fat, fiber and ash, whether the pellets float and their size), up to three photos and any note
    • the items in your medicine cabinet (medications, water treatments and salt): name, brand, type, active ingredient, size, cost, the label's dose as you enter it, the dates you bought, opened and finished each one, its expiry date, up to three photos and any note
    • your koi: nickname, variety, status, sex, age, length and weight (including the growth measurements you record over time, each with the date it was taken), dealer, breeder farm, notes, birth and purchase dates, the price you paid and an estimated value if you enter them, and photos and short video clips (including any sound recorded with them)
    • koi varieties you add yourself, and the varieties you mark as favourites
    • reminders: title, notes, schedule, time zone and the categories you create
    • preferences such as your temperature unit, which tiles show on your home screen, which journal tags you hide and how many grams your feeding scoop and pinch hold
  • A connected water sensor (UbiBot): if you connect a UbiBot to a pond, we store the device's channel ID and the read-only key you create for it in the UbiBot console, its name and model, which of its probes is in your pond, and your alert settings. Every 15 minutes our server asks UbiBot for the device's latest readings and keeps three of them, with their times: the water temperature, the air temperature and the humidity. When you first connect, it also copies up to 30 days of hourly averages of those three readings. UbiBot's reply also includes things like the device's light and battery readings, WiFi signal, network name, network address and location. We don't keep any of those. The WiFi signal and power are shown on screen only while you check the connection. The read-only key stays on our server: the app can't read it back, and it only lets us read that one device, not change it. We never ask for your UbiBot password.
  • A connected water sensor (Seneye Pond): if you connect a Seneye Pond to a pond, we store the secret key from your Seneye Web Server's settings, a random address we make for that pond, your alert settings and which device the pond's water temperature comes from. Your Seneye Web Server then sends each new reading to that address, and we keep, with its time: the water temperature, the pH, the free ammonia (NH3), whether the device is in the water and whether its slide needs replacing. Each reading also names the device (its serial number, its Seneye Web Server's ID and the name you gave it in Seneye), and we keep those too, to show which device is connected. The Seneye Web Server only sends to plain http addresses, so these readings travel unencrypted from your home to Cloudflare, which forwards them to our server over an encrypted connection. They can't be faked without your secret key: each one is signed with it, and the key itself is never sent. The key stays on our server, and the app can't read it back. We never ask for your Seneye password, and we never contact Seneye.
  • A notification token: after you sign in, the app asks whether it may send you notifications. If you allow it, a token that identifies the app on your device (issued by Expo's push notification service) is saved to your account. Signing out removes it. It is used for the water-sensor alerts you choose, which our server sends; your reminders don't use it, because they are scheduled on your phone itself. You can turn notifications off at any time in your phone's settings.
  • An app update identifier: when the app checks for updates, it sends Expo a random identifier created for that installation, along with the app's version details. It isn't tied to your account by our code.
  • Photos for the Koi Identifier: if you use the AI Koi Identifier, the one to four koi photos you choose are sent through our server to OpenAI, which suggests the likely variety. The app asks your permission before the first time it sends photos. We don't save these photos to your account or anywhere else; our server keeps only the varieties suggested, in its logs. We also count how many identifications your account has used this month, to apply the monthly limit.
  • Photos for the label reader: if you tap Read the label on a bag of food or an item in your medicine cabinet, the one to three photos on it are sent through our server to OpenAI, which reads the label to fill in its details: for food, the brand, size and guaranteed analysis; for a medicine cabinet item, the name, brand, active ingredient, size, expiry date and printed dose. Our server doesn't keep the photos; the ones you save on the bag or item are stored with your account like your other photos. We count how many labels your account has read this month, to apply the monthly limit.
  • Subscription details: whether you're in your free trial or have an active subscription, your purchase history, and your locale and currency. RevenueCat, our subscription service, holds these against your account's user ID and email address, so we can find your subscription when you ask for help. Payment is handled entirely by Apple or Google, and we never receive your card details.
  • Server logs: our providers automatically record technical details of requests to our servers, such as IP addresses and times, to run and secure the service.
  • Messages you send us: if you email us, we keep the email so we can reply.

What we don't collect. KoiKeep doesn't use your device's location (the city and state on a pond are only what you type in). It doesn't read your contacts, show ads, or include advertising, tracking or crash-reporting tools. We don't track you across other companies' apps or websites. The app only uses your camera, microphone and photo library when you choose to add a photo or video, and only the items you pick are uploaded. Your light or dark theme choice is stored on your phone, not on our servers.

4. How we use your information

We use your information only to run KoiKeep for you, and to understand how the subscription is doing:

  • to show your ponds, water history, charts, koi, journal, feedings, food pantry, medicine cabinet, memories and reminders, and keep them in sync on any phone where you sign in
  • to send account emails: confirming your email address, resetting your password, and a one-time welcome email with tips for using the app when you join, and a confirmation when you delete your account
  • to suggest a koi's variety from the photos you send to the Koi Identifier, and to fill in a bag's or a medicine cabinet item's details from the label photos you send to the label reader
  • to notify you on your device when a reminder is due, if you allow notifications
  • if you connect a water sensor, to read it, show its readings and charts, use its water temperature for the feeding advice, and send the alerts you choose (cold or warm water, a fast temperature swing, high free ammonia, pH out of your range, a Seneye out of the water or needing a new slide, or the device going offline)
  • to deliver app updates
  • to manage your free trial and subscription, and to see subscription reports through RevenueCat
  • to answer your support requests and keep the service secure

We do not sell your personal information, share it with advertisers, or use it to build advertising profiles.

5. Where your data is stored and who helps us

A small number of companies help us run KoiKeep. Each one only gets the information it needs to do its job, and each handles it under its own privacy policy:

  • Supabase: sign-in, our database, and storage for your photos and videos. This is where your account and pond records live. Your photos and videos are kept in a private storage area. Only your account can open them, and the app shows them through links that expire after an hour.
  • Google Cloud: runs our small server, which passes Koi Identifier and label reader photos to OpenAI, checks your sign-in for those requests and sends the welcome and account-deleted emails (it receives your email address and display name to do so). If you connect a water sensor, it also reads a UbiBot from UbiBot every 15 minutes, receives the readings a Seneye Web Server sends, and sends your sensor alerts. It also stores our private, encrypted database backups in the United States.
  • GitHub: runs the automated nightly job that creates those backups, so the backup data passes through it while the job runs.
  • Resend: delivers our emails: address confirmation, password reset, the welcome email and the account-deleted email. It receives your email address, the content of those emails and, for the welcome and account-deleted emails, your display name.
  • RevenueCat: manages subscriptions. It receives your account's user ID, your email address, your purchase history, and your locale and currency, and gives us subscription reports. We don't send this data on to any other service from RevenueCat.
  • OpenAI: only if you use the AI Koi Identifier or the label reader. It receives the photos you send (nothing else from your account) and returns a suggested variety or the figures on the label. OpenAI doesn't use them to train its models, and may keep them for up to 30 days to monitor for abuse before deleting them. See OpenAI's API data usage policy.
  • UbiBot: only if you connect a UbiBot. Your device's readings are already stored by UbiBot under your own UbiBot account and its privacy policy. Our server sends UbiBot the channel ID and read-only key you gave us to fetch them; we don't send UbiBot anything else from your account.
  • Expo: issues the notification token described above, delivers app updates, for which it receives the app update identifier, and delivers water-sensor alerts, for which it receives each alert's text (your pond's name and the reading, such as the water temperature, pH or free ammonia).
  • Google and Apple: only if you choose to sign in with them. They also run the App Store and Google Play, where you download the app and pay for a subscription.
  • Cloudflare: hosts this website and the KoiKeep web app. Like any web host, it handles basic request information (such as your IP address) to deliver pages. This website doesn't use cookies or analytics. If you connect a Seneye Pond, Cloudflare also runs the small relay your Seneye Web Server sends readings to, which passes them straight to our server; it sees your home's IP address, as any web request does, and we don't keep it.

These providers may process data in the United States and other countries where they operate.

6. How long we keep it, and deleting it

We keep your information for as long as you have an account. You can delete your account yourself, at any time. In the app, open the Home menu and go to Account → Edit Profile → Delete Account. In the web app, go to Account at koikeepapp.com. This permanently deletes your account, every pond record listed above, any connected water sensor with its key and readings, and all the photos and videos you uploaded, straight away. We then send one last email to the address on the account, confirming the deletion. If you can't sign in, email us instead. Our data deletion page explains both options.

You can also disconnect a water sensor on its own, from the device's page in the app. That deletes its key and all its readings from KoiKeep straight away. It doesn't change your device or its data in UbiBot; to stop the key working altogether, delete it in the UbiBot console too. Disconnecting a Seneye deletes its key, its readings and the pond's address, so readings your Seneye Web Server still sends there are refused; switch off Local Data Exchange in its settings to stop it sending.

After deletion, copies of your account and records stay in our private, encrypted database backups until each backup expires: nightly backups after about 8 days, weekly backups after about 35 days, and monthly backups after about 100 days. Backups don't contain your uploaded photos and videos. OpenAI may keep Koi Identifier and label reader photos for up to 30 days, as described above. Server logs are kept by our providers under their own retention periods. Support emails are kept only as long as we need them to help you. When you delete your account in the app, it asks RevenueCat to remove your email address. RevenueCat keeps the rest of its subscription record, under your user ID; email us if you want it removed or if you want us to confirm your email address is gone. Deleting your account does not cancel a subscription. Cancel it in your App Store or Google Play settings, and note that Apple and Google keep their own purchase records.

7. Security

Everything sent between the app and our servers is encrypted in transit (TLS), and our hosting providers encrypt stored data and backups at rest. Database access rules mean an account can only read and change its own records, and uploaded files sit in a private storage area that only their owner can open. The one exception is our admin page, open only to accounts we have marked as administrators, which we use to run the app and help people. It shows each account's email address, display name, sign-up and last sign-in dates, sign-in method, how many of each kind of record it has, when it last added one, how many devices are registered for notifications, how many Koi Identifier uses it has this month, and its subscription status. It shows those counts and dates only, not what your notes, readings or photos say. From it we can also give an account free access for a set time, and those changes are logged. No system is perfectly secure, but we work to protect your information and keep only what the app needs.

8. Children

KoiKeep is not meant for children under 13, and you must be at least 13 to create an account. We don't knowingly collect personal information from children under 13. If you believe a child has given us personal information, email us and we will delete it.

9. Your rights and choices

You can see and change most of your information directly in the app, and you can delete all of it with the in-app Delete Account option. You can also email [email protected] to ask for a copy of your data, a correction, or deletion. Depending on where you live (for example, California, or the EU and UK), the law may give you these rights formally. We will honour them wherever you live.

If you're in the EU or UK: we use your information because we need it to provide the service you signed up for, because it is in our legitimate interest to keep the service secure and answer your messages, and, for notifications, because you agreed to them. You can also complain to your local data protection authority.

10. Changes to this policy

If we change this policy, we'll update the date at the top of this page. If the change is significant, we'll also let you know in the app.

11. Contact

Questions about this policy or your data? Email [email protected].

KoiKeep

Log your water, keep a record of every koi, and never forget the pond chores — all in one app built for koi keepers.

Product

FeaturesHow it worksFAQDownload

Support

Contact usGet helpDelete your data[email protected]

Legal

Privacy PolicyTerms & Conditions

© 2026 KoiKeep. All rights reserved.