Privacy Policy

Effective: July 18, 2026

Kindmemo is a private memory for the people you care about. This policy explains how the iPhone app and this website handle information. It is written in plain language and is not legal advice.

Summary

Kindmemo does not require a Kindmemo account. Your notes and details start on your device. Sync with iCloud is optional and off by default. The developer does not operate a Kindmemo backend that stores your relationship content, and does not run ads. The app uses user-controlled, content-free Firebase Analytics and Crashlytics diagnostics as described below; the website itself remains free of analytics and cookies.

Local storage on your device

Every device starts local-only. People, notes, facts, reminders, and related details you save are stored in Kindmemo’s local database on that device. The local store uses Apple’s complete file protection so the data is protected when the device is locked, according to iOS file protection behavior.

When Sync with iCloud is off, new changes stay on that device.

Optional private iCloud sync

Sync with iCloud is optional and off by default on each device. If you turn it on while signed in to iCloud, Kindmemo can make your Kindmemo data available through your private iCloud database (Apple CloudKit) on other devices signed in to the same iCloud account.

When sync is on, the people, notes, facts, reminders, and related Kindmemo records you save may be stored in that private iCloud database. Protection of synced data follows your iCloud security settings. Kindmemo does not claim universal end-to-end encryption independent of those settings.

Other devices must use the same iCloud account to see synced Kindmemo data. Synchronization is asynchronous; Kindmemo does not promise instant delivery or a guaranteed “up to date” state.

Disabling sync versus deleting data

Turning Sync with iCloud off stops new changes from syncing from that device. It is not the same as deleting your data.

User-controlled app diagnostics

The iPhone app uses Google Firebase Analytics and Firebase Crashlytics to understand coarse feature use and fix crashes. Share usage analytics and Share crash reports are each on by default on a device and can be turned off independently at any time under Diagnostics in Me. The choices are stored only in that device’s app preferences; they are not part of Kindmemo data, iCloud sync, exports, widgets, Spotlight, notifications, or the share extension.

Usage events have fixed names and fixed, content-free choices: for example, that a person was added manually or through the user-selected Apple Contacts import, that a detail or note was saved, that a briefing was opened, a reminder action happened, search was used, or the iCloud sync setting changed. The allowlist also includes purchase lifecycle changes with only these fixed states: pending, purchased, restored, expired, or revoked. Kindmemo does not send the person’s name, profile, photo, notes, facts, searches, reminder text or schedule, calendar information, AI input or output, private counts, transaction IDs, prices, or any Kindmemo, CloudKit, notification, calendar, share-operation, or App Intent record ID.

While usage analytics is on, Firebase Analytics may automatically process a per-install app instance identifier, timestamps, app and iOS version, device characteristics, session timing and statistics, and an approximate region derived from the network request. Kindmemo disables IDFA and IDFV collection, automatic screen reporting, ad storage, ad user data, and ad personalization. It sets no Analytics user ID, user property, or default event parameters and does not link Firebase to advertising products.

While crash reports are on, Firebase Crashlytics may process installation identifiers, timestamps, the app and OS version, device model and technical characteristics, and fatal crash stack traces. Kindmemo sends no custom Crashlytics user ID, key, log, or non-fatal error and does not deliberately add Kindmemo content to crash reports.

Turning usage analytics off stops collection, clears its on-device Analytics state, and resets the app-instance ID. Turning crash reports off disables collection and deletes unsent reports; Firebase documents that the persisted Crashlytics override applies fully on the next launch. These controls cannot retroactively remove data already uploaded. Kindmemo’s release process requires the Firebase property to use the shortest available Analytics user/event retention (currently two months); Google notes that this setting does not remove standard aggregate reports. Firebase documents a 90-day retention period before beginning removal of Crashlytics crash traces and associated identifiers from live and backup systems.

This processing is pseudonymous, content-free, aggregate usage and diagnostic data. It is not linked by Kindmemo to a Kindmemo account, person, or memory, but it is not literally anonymous. Google acts as the Firebase service provider/processor under its applicable terms and may process data on global infrastructure. Kindmemo does not use this data for tracking across other companies’ apps or websites, advertising, resale, identity, or enrichment.

What the developer does not do

The developer does not operate a Kindmemo user-account system or developer-operated backend for your relationship content. The developer does not retrieve your private CloudKit records or per-user CloudKit telemetry as part of providing Kindmemo. Apple provides iCloud/CloudKit under Apple’s terms and privacy practices. The only third-party app diagnostics are the two Firebase controls described above.

Optional Apple system features

These integrations are optional and under your control:

This website

This site is static. It sets no cookies and runs no analytics scripts. Pages are served by Vercel. Vercel may process operational request data (such as IP address, user agent, and request metadata) to deliver and protect the site, under Vercel’s own privacy policy. Kindmemo does not use that operational data for advertising or product analytics.

European privacy note

The developer is based in the European Union (Czech Republic). Kindmemo does not collect app content into a developer-operated account, and does not sell personal data. Google processes enabled Firebase diagnostics as described above. Apple services (App Store, iCloud/CloudKit, device OS features) and Vercel website delivery process data under their own services and policies. If you have a privacy question about Kindmemo itself, emailsupport@kindmemo.app.

Support

Michal Kos
Email: support@kindmemo.app

This draft is not legal advice. Before App Store submission, a human should confirm that this policy matches the submitted build and App Privacy answers.