1. Who this policy covers
This policy explains how the operator of Kapi handles information for the Kapi iOS/Android app and this website. Kapi is a personal time journal, and the website includes a temporary interactive demo.
Kapi does not require an account. This policy reflects the current app and website; changes to data handling will be reflected here.
2. Your journal and device preferences
The app stores activity labels, selected Kapi characters, record identifiers, start and end times, and running-timer state on your device. Recent activities are derived from your records. Widgets share timer state with the app using local device storage.
Kapi does not upload your journal to a Kapi server or provide account-based cloud synchronization. Your operating system may include app data in device backups or transfers, depending on its settings. Those copies are managed by you and your device provider.
Device language, time format, local time, and reduced-motion preferences are used to display the app. The landing-page demo keeps its sample moments in memory and resets them when the page reloads.
3. Usage analytics
Kapi uses Google Analytics for Firebase to understand which features work well and improve the experience. Starting with app version 1.0.1, usage analytics is collected automatically when you use the app. Events describe screen visits and generic app actions, such as timer actions, saving or editing a record, and opening a Kapi. App Store version 1.0.0 requests permission before enabling usage analytics. The website separately collects page visits, navigation, and timer-demo interactions automatically.
The app’s custom events contain only generic feature actions, screen names, and where an action was opened. They exclude journal text, activity labels and categories, recorded durations, journal record IDs, selected journal dates, and stored start/end timestamps. Website demo events can include fixed sample activity categories, broad demo-duration ranges, and interface language; these are separate from your app journal. Analytics still has its own event timestamps and session information.
The Google SDK also processes pseudonymous app-instance or browser identifiers, device/browser and operating-system information, app version, session and interaction information, installation diagnostic information, and approximate location derived from IP addresses. This is not the same as fully anonymous data. Google Analytics 4 does not log or store individual IP addresses, although IP addresses are used when requests are received and to derive approximate location.
Starting with iOS app version 1.0.2, Kapi enables Apple SKAdNetwork registration to measure installations attributed to Kapi advertising campaigns. Apple can send limited, delayed attribution reports to the ad network. This feature does not provide journal contents or an advertising identifier to the network, and Kapi does not request App Tracking Transparency permission for it.
In iOS builds that include Google’s event-data-based on-device conversion measurement, de-identified, temporary signals derived from app events, IP addresses and timestamps may also be used to help measure installations and in-app actions attributed to Kapi ads. Availability depends on Google’s regional, device and consent requirements; including the SDK does not guarantee ad attribution. Kapi does not provide email addresses, phone numbers or journal contents to this feature.
Kapi does not use analytics for targeted advertising or set an account-based analytics user ID. Advertising storage and personalization are disabled in our integration. Website page URLs sent by our integration omit query strings and fragments, and referrers are reduced to their origin.
4. Website analytics and cookies
This website automatically collects Google Analytics usage statistics when you visit, including page views and demo interactions. Website collection is separate from app collection and does not access your app journal.
Google Analytics uses first-party cookies such as _ga to recognize a browser and measure sessions. It also processes browser/device information and approximate location as described above. These cookies do not contain your app journal. Browser restrictions or blocked scripts may prevent collection.
5. Service providers and other disclosures
Google processes analytics information to provide Google Analytics for Firebase. Vercel hosts this website and processes technical request information, such as IP addresses, requested URLs, browser information, and security logs, to deliver and protect it. When you email support, your email provider and ours process that correspondence.
If you contact us, we receive your email address, any name you provide, message content, and attachments. We use these to respond, investigate the issue, or handle a privacy request; you do not need to send your journal to get support.
These providers may process information in the United States and other countries where they operate. Their handling is subject to their applicable terms and privacy safeguards. Kapi does not sell personal information or share it for cross-context behavioral advertising. Information may also be disclosed where required by law or necessary to protect legal rights and service security.
6. How long information is kept
Local journal records remain on your device until you remove app data or delete the app, subject to your operating system’s storage and backup behavior. Kapi does not automatically expire journal records. The website demo lasts only for the current page session.
The current Google Analytics property keeps event-level data for 2 months and user-level data for 14 months. The user-data retention period resets on new activity. These controls do not apply to standard aggregated reports; those can remain for longer under Google’s service settings. Expired Analytics data is removed according to Google’s processing schedule.
Support correspondence is kept for as long as needed to resolve the request and handle related follow-ups or legal obligations. You may ask us to delete correspondence that is no longer needed. Hosting and security records follow the provider’s applicable retention practices.
7. Access, correction, and deletion
You can review your journal in the app and correct an activity or its times. To remove all local app records in the current version, use Android’s app-storage “Clear data” control or delete the app on iOS. On iOS, “Offload App” keeps app data and is not the same as “Delete App.” The current app has no individual-record deletion or export button.
Deleting the app does not necessarily delete copies in your device backups, files you created elsewhere, or analytics already received by Google. Manage backups separately through your device/cloud provider. Kapi cannot remotely inspect or erase your locally stored journal, and there is no Kapi account to close.
Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing. Contact the address below. We may need proportionate information to verify a request and locate information, and we may be unable to match pseudonymous analytics to you without its identifier. Please do not send your full journal or sensitive details unless they are necessary. You may also contact your local data-protection authority.
8. Security and children’s information
We use HTTPS for this website and service connections and restrict access to service administration. Local records also depend on your device’s security. No storage or transmission method is completely secure; use device locks and keep your operating system up to date.
Kapi does not ask for a date of birth or knowingly request personal details from children. If a parent or guardian believes a child has provided personal information to us, contact us so we can review and handle the request under applicable law.
9. Contact and policy updates
For support or privacy requests, use the contact details below. We update the date on this page when the policy changes and provide further notice or seek consent where required.