Scope
This policy covers the Kigomo iPhone app and public website. Kigomo's parent company is Inang.com, an NYC company that develops innovative AI apps. References to “Kigomo,” “we,” “us,” or “our” in this policy include Inang.com as the company responsible for Kigomo. Kigomo is for adult parents and caregivers and is not directed to children or offered in Apple’s Kids Category.
Account and shared family information
We collect an account email address and user identifier to authenticate you. A private family workspace can contain cards, schedules, assignments, activity status, family profiles, children’s names and dates of birth, care notes, phone numbers, emergency information, progress, and chat history. Supabase stores this information so active members of the same family workspace can access it across devices.
Kigomo does not sell personal information, show third-party advertising, or use family information to track you across other companies’ apps or websites.
Photos and device access
Kigomo uses Apple’s system photo picker, and the camera if you choose to make a card from a photo. You choose the specific photos copied into the app; Kigomo does not request broad photo-library access. Child and caregiver profile photos, and card photos in the current snapshot planner, remain on the phone. In a cloud-enabled family planner, a family-card image you explicitly add is stored privately so authorized family members can see it; it is not added to the public catalogue. Kigomo shrinks and re-encodes that image on your phone or in your browser before it is uploaded, which removes the camera details and any GPS coordinates the original carried; if that step fails, the image is not uploaded. If you make a card from a photo, that photo is sent to Kigomo's AI service; the section on AI and link assistance below explains what happens to it. Kigomo does not run face detection, face grouping, or auto-tagging on any photo. The iOS contact picker does not grant general contact access; details you choose to save can become shared workspace information.
Notifications
If you explicitly enable exact-time reminders, Kigomo asks iOS for notification permission and schedules alerts locally on your device for eligible calendar plans. Lock-screen alerts use generic wording and do not include card, child, caregiver, health, location, or note content. You can disable reminders in Kigomo or manage notification permission in iPhone Settings.
Apple Calendar
If you explicitly enable Apple Calendar sync, Kigomo asks for full Calendar access so it can create, update, and remove events without duplicates. Kigomo writes scheduled card titles, dates, times, and durations to a dedicated Kigomo calendar on that device. It does not import unrelated personal events into Kigomo. Each caregiver enables this separately, and Apple handles the calendar copy under your Apple account and settings. Turning sync off removes Kigomo-exported events while Calendar access remains available.
Widgets
If you add the Kigomo Today widget, the app shares a minimal on-device snapshot with its WidgetKit extension through an Apple App Group. The snapshot contains only remaining and completed plan counts and the next exact time; it does not contain card titles, notes, child or caregiver identity, health information, locations, or photos.
AI and link assistance
When you use AI Chat, Kigomo sends your message, recent conversation history, and family context through a Kigomo-controlled Supabase function to OpenAI so replies are personalized to your family. That context includes your child's name and age, their care notes (allergies, favorites, and good-to-know notes), the current caregiver's name and city, and the day's planned cards. It also includes, when your message matches them, up to three cards and two decks from your family library — including their full descriptions. These are matched against the words of your message, so a message with nothing for the library to answer sends none at all. Allergy information is sent only so suggestions can avoid unsafe foods or activities. You control what is shared by choosing what you enter in each profile field. Kigomo sets store: false, so OpenAI Responses application-state storage is disabled. Under OpenAI's standard API data controls, request and response content may still be held in abuse-monitoring logs for up to 30 days. Kigomo stores the resulting shared conversation and any parent-confirmed card in the family workspace. Social-link import sends the link and optional caption through the controlled server boundary.
Making a card from a photo sends the photo itself. Kigomo shrinks and re-encodes the picture on your phone before anything leaves it, which also removes the EXIF details and any GPS coordinates the original carried; if that step fails, no photo is sent. The prepared image, plus any short note you add, then travels over HTTPS through the same Kigomo-controlled function to OpenAI, our AI provider, under the same store: false setting. Under OpenAI's standard API data controls, OpenAI may still hold a copy of that photo for up to 30 days for safety checks before deleting it. Kigomo's own servers do not keep the image: it is not written to the database or to file storage. Kigomo asks the model to write about the object rather than about any people in the photo; that instruction is our best effort, not a guarantee. Nothing reaches your family until you save it: you see the draft card first, and it becomes a card in your family workspace only when you tap Save. Saving keeps the photo on that phone as the card's picture and, in a cloud-enabled family planner, also uploads it to your family's private storage so authorized family members can see it — the same handling, and the same removal route, as any other family-card photo you add, described under Photos and device access above and Retention and deletion below. If you discard the draft, Kigomo keeps no copy of the photo on your phone.
Sharing you initiate
Family workspace members can see shared workspace information. If you use an iOS share action, you choose the destination and recipient; that recipient or service handles the shared information under its own terms. Sharing a card sends its text details and, for a cloud share, the number of attached photos — never the photo files themselves.
Public website
Public card and deck pages contain editorial ideas, not private family records. Hosting infrastructure may process IP address, browser type, requested page, and request time to deliver and protect the site.
These public pages also use Google Analytics so we can see which ideas and guides parents actually find useful. Google acts as our processor and collects usage and device information: the page you viewed, the page or search that sent you, your IP address (from which Google derives an approximate location), and browser, device, and language details. It stores cookies in your browser to recognize a returning visit. We use it to count and improve pages, not to identify you.
Google Analytics does not run inside the signed-in app. The product app, the admin pages, and family invite and share links load no analytics script, so no card, child, caregiver, schedule, or workspace information reaches Google. Kigomo does not use advertising trackers on any page and does not sell what analytics collects. You can prevent this collection with your browser's tracking-protection setting, a content blocker, or Google's Analytics opt-out add-on.
Retention and deletion
Shared information remains until a member removes it or the owner deletes the workspace. Deleting the app removes only that phone’s cache. Leaving a workspace revokes access and removes that workspace's offline cache, local photo files, chat cache, and interaction history from the phone after the server confirms the leave. Apple Calendar events are system calendar data; turn sync off before removing Kigomo, or remove the dedicated Kigomo calendar in Apple Calendar if app access has already been revoked. Users can delete their account inside Kigomo. Family-card photos become unreachable as soon as the card, family, or account that held them is deleted; their stored file copies are not yet removed automatically and are erased on request through support. OpenAI's standard abuse-monitoring retention is described above. See Data choices.
Security
Sessions are stored in the iOS Keychain. Supabase row-level security limits workspace access to active members, and HTTPS protects data in transit. Local caches are protected by Apple’s app sandbox. No system is risk-free.
Processors and contact
Supabase provides authentication, database, and server functions. OpenAI processes AI requests when you choose those features. Google Analytics measures use of the public website only. Questions or privacy requests can be sent to team@kigomo.com. Please do not email sensitive child information.