Privacy Policy

Effective date: June 1, 2026  ·  Last updated: September 21, 2026

Keeso ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains what information we collect, how we use it, and the choices you have.

1. Information We Collect

We collect information you provide directly:

• Account information — name, email address, and date of birth when you register.
• Family data — events, tasks, shopping lists, contacts, vault document metadata, finance records, maintenance items, and saved locations that you and your family members create inside the app.
• Photos and files — images you upload for pantry favourites, recipes, and vault documents. These are stored securely in cloud object storage.
• Voice input — if you use the voice inbox feature, your spoken input is transcribed locally on-device via the speech recognition API and sent to our servers only as text.
• Push notification token — a device token so we can deliver family notifications you have opted into.

We also collect limited technical information automatically:

• App version and operating system (for error diagnosis).
• IP address and request logs retained for up to 30 days for security monitoring.
• Optional usage analytics — when you enable "Share usage analytics" in Settings, we collect pseudonymous screen visits and feature-use events, app version, and device type. We do not include names, email addresses, family content, document contents, voice transcripts, images, locations, or financial values. You can disable analytics at any time.

Automatic app updates — Keeso uses Expo Updates to check for and download compatible JavaScript-only updates when available. These updates may contain bug fixes, copy, routing, and other app code. Native capabilities, permissions, and entitlements cannot be changed by an automatic update and require a new app release. If an update cannot be downloaded or launched, the app uses the code already included in the installed release.

2. How We Use Your Information

• To operate and deliver the Keeso service — syncing family data, sending push notifications you enable, and powering intelligent briefings and smart inbox parsing.
• To retrieve your local weather forecast: when you are signed in and location permission is granted, we obtain your device's exact coordinates, derive your city name via on-device reverse geocoding, and pass the coordinates to Open-Meteo. A rounded version of your coordinates (approximately 1 km precision) is held in server memory for up to five minutes as a weather cache key. So that we can send your family's morning and evening weather notifications when the app is closed, we also store the most recent approximate location (rounded to about 1 km) reported by a family member's device on the family record. It is not kept as a history, is deleted when the family is deleted, and is never shared with other family members. Exact coordinates are not written to a database or log file.
• To send geofence proximity notifications when you are near a saved family place (only if you separately enable background location). If you enable it, your device holds a revocable background token so it can check nearby places while the app is closed; the token is stored on our servers, expires automatically, and is removed when you sign out or change family.
• To authenticate you securely via Clerk.
• To manage your subscription and process payments via RevenueCat and the relevant app store.
• To improve the service by diagnosing errors (we do not use family content for model training).
• To understand feature adoption and improve Keeso when you opt into usage analytics.

3. Third-Party Services

We share data with the following third parties solely to operate the service:

• Clerk (clerk.com) — identity and authentication. Processes name, email, and session tokens.
• Anthropic (anthropic.com) — powers the Smart Inbox and daily briefings. We send relevant family context (events, tasks, shopping lists) to generate responses. Anthropic's data retention policy applies; we do not use family data to fine-tune models. Keeso asks for your permission before the first time it sends anything to Anthropic, and you can turn AI features off at any time in Settings.
• Expo / EAS (expo.dev) — push notification delivery and app distribution.
• Expo Updates (expo.dev) — automatic delivery of compatible JavaScript-only app updates.
• RevenueCat (revenuecat.com) — subscription management and entitlement tracking.
• Google Cloud / Replit — cloud infrastructure, database hosting, and object storage.
• Open-Meteo (open-meteo.com) — weather data. When you are signed in and location permission is granted, your exact latitude and longitude are sent to Open-Meteo to retrieve your local forecast. No account identifiers are included in these requests. A rounded form of your coordinates is held in server memory for up to five minutes as a cache key. Open-Meteo requests never include account identifiers.
• OpenStreetMap Nominatim (nominatim.openstreetmap.org) — when you add a saved place by address, the address you type is sent to Nominatim to find its map coordinates. No account identifiers are included.
• Nager.Date (date.nager.at) — public holiday data. Only the country code you choose for your family calendar is sent.
• PostHog (posthog.com) — optional, pseudonymous product-usage analytics when enabled in Settings. No family content or financial values are shared.
• Google Calendar — optional access when you connect your Google account. Keeso reads only the calendars you select and displays them as a read-only layer in your family calendar. Keeso does not copy Google events into editable family events or store your Google access token.

We do not sell your personal data to advertisers or data brokers.

4. Data Retention

We retain your data as long as your account is active. When you delete your account, your personal profile and associated family data are permanently removed within 30 days, subject to legal obligations.

5. Children's Privacy (COPPA)

Keeso requires users to be at least 13 years old to create an account. We do not knowingly collect personal information from children under 13. Child members of a family are added by a parent, who is responsible for any data entered on behalf of minors.

If you believe we have inadvertently collected information from a child under 13, please contact us immediately and we will delete it.

6. Data Security

All data is transmitted over HTTPS. Passwords are managed by Clerk and are never stored by Keeso. Uploaded files are stored in private cloud buckets accessible only via short-lived signed URLs.

7. Your Rights

You may access, correct, or delete your personal information at any time from the Settings screen in the app. You may also request account deletion by contacting us. Depending on your jurisdiction, you may have additional rights under GDPR, CCPA, or other privacy laws.

8. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of significant changes by updating the effective date above and, where appropriate, via an in-app notice.

9. Contact Us

If you have questions about this Privacy Policy, or to request data deletion, please contact us at: support@keesoapp.com