Privacy Policy
Atsuki Kakehi (“we”, “the developer”) provides the iOS app “Kamerii” (カメリー) (the “App”). This Privacy Policy explains how information is handled in the App, in compliance with the Act on the Protection of Personal Information of Japan (APPI) and other applicable laws.
Article 1 (Core Principle — Your Diary Data Stays on Your Device)
The App is a voice diary that requires no account registration.
Your transcribed text and diary entries are stored on your device and are not stored on our servers. Audio from the microphone is used only for live processing such as transcription, is not saved as an audio file, and is discarded when that processing is complete. We cannot read your diary. However, when you expressly use the AI Organizing Feature, transcribed text and related information are transmitted for processing within the scope described in Article 2.
Article 2 (Information We Handle)
Diary information normally processed and stored on your device
- Transcribed text (converted on-device by Apple’s Speech framework; microphone audio is neither sent to an external server for speech recognition nor saved as an audio file, and is discarded when processing is complete)
- Diary titles, summaries, AI-polished transcripts, daily summaries, and tasks
- Usage statistics (e.g., number of recorded days)
Information transmitted only when the AI organizing feature is used
The following information is sent to the Gemini API provided by Google LLC, via a server managed by the developer, only when you have enabled the AI organizing feature with your explicit consent and use it for title generation, entry summaries, transcript polishing, daily summaries, or suggested tasks.
- Transcribed diary text (up to 8,000 characters for organizing an individual entry, or an aggregate of up to 16,000 characters from the selected day for a daily summary)
- Only when creating a daily summary: the titles and start/end times of that day’s calendar events you adopted in the app that have already ended at the time of creation (locations and notes are never sent)
- Language setting and date
- A randomly generated app-user identifier (used to manage usage limits and anonymous app-user registration and not directly linked to your name, email address, or other personal details)
Our servers do not store or log diary content. To manage AI usage, subscription entitlements, trial grants, purchase and subscription event history, and entitlement checks, our servers record a random app-user identifier, an irreversible representation of registration replay-verification information, a RevenueCat user identifier, usage dates and counts, purchase, subscription, refund, and entitlement event types and timestamps, pseudonymous product and transaction identifiers, subscription-entitlement expiration, trial-grant timestamps, entitlement-check timestamps, and related operational data.
Information transmitted for usage analytics
The App uses Firebase Analytics to understand usage and improve its features. The following information is transmitted to Google LLC and processed in Firebase Analytics and its linked BigQuery dataset:
- Activity records such as app opens, diary saves from voice or text input, AI feature use, Reminders integration, onboarding, paywall impressions, and purchase actions
- Paywall placement, monthly or annual product period, and free, trial, or premium plan category
- A Firebase-generated app instance identifier and a pseudonymous RevenueCat App User ID
- Technical information such as app version, device type, and operating system; coarse region derived from the IP address; and purchase or subscription events
Analytics data never includes diary text, transcripts, audio, photos, task text, or calendar-event content.
Information transmitted for crash diagnostics
The App uses Firebase Crashlytics to investigate crashes and improve quality. When the App crashes, Google LLC receives the stack trace, exception type and message, timestamp, app version, device model, operating system, relevant memory and application state, a Crashlytics Installation UUID, and a Firebase installation ID. When Firebase Analytics is enabled, allowlisted usage events immediately preceding the crash may also be included as diagnostic breadcrumbs.
Diary text, transcripts, audio, photos, task text, and calendar-event content are not sent to Firebase Crashlytics.
Information transmitted for purchases, subscriptions, and abuse prevention
The App uses RevenueCat to manage App Store purchases and subscriptions and entitlement to paid features and the seven-day free-access period. A pseudonymous RevenueCat user identifier; product; purchase, subscription, refund, entitlement, and trial status; and a Firebase-generated app instance identifier are processed by RevenueCat and servers managed by the developer.
Payment information such as the card number registered to your Apple Account is not transmitted to the developer’s servers or external services such as RevenueCat.
Information we do not collect
The App does not collect your name, email address, or precise location through normal use and requires no account. If you contact us, we handle your email address and inquiry only as needed to respond. The App uses no advertising SDK, IDFA, or tracking across other companies’ apps or websites.
Article 3 (Purposes of Use)
Information is used solely for the following purposes:
- Managing AI usage limits and trial grants, and preventing repeated or abusive acquisition of benefits
- Verifying subscription entitlements and providing paid features
- Understanding App usage, improving features, and identifying defects
- Responding to inquiries
- Verifying that requests come from an authentic App and preventing API abuse
Article 4 (Transfers to Third Parties Located in Foreign Countries)
To provide the App, we entrust data processing to the following providers located outside Japan. The following information is provided pursuant to Article 28 of the APPI:
| Provider | Country | Data transmitted | Handling |
|---|---|---|---|
| Google LLC (Gemini API) | United States | Transcribed text; the titles and times of adopted events when creating a daily summary; language setting; date | Under the paid API terms, your data is not used to train AI models. Data is automatically deleted after a certain period of retention for abuse monitoring |
| Google LLC (Firebase Analytics / BigQuery / Crashlytics) | United States and other locations | Usage events, pseudonymous user and app-instance identifiers, plan category, device and app information, coarse region, purchase events, crash stack traces, and related diagnostics | Used to improve features, analyze usage, and diagnose defects. It is not used for ad personalization or cross-company tracking. Analytics events are retained for no more than 14 months. Crashlytics crash data and associated identifiers are retained for 90 days before removal from live and backup systems begins |
| Cloudflare, Inc. | United States | Transcribed text and the titles and times of adopted events when creating a daily summary (only while processing); pseudonymous app-user and RevenueCat user identifiers; an irreversible hash of registration-verification information; usage dates and counts; purchase, subscription, refund, and entitlement events; pseudonymous product and transaction identifiers; and timestamps relating to trial grants and entitlement checks | Diary content is never stored or logged. Data needed to manage usage limits, purchases, subscription entitlements, and trials is stored |
| RevenueCat, Inc. | United States | Pseudonymous RevenueCat user identifier; purchase, subscription, entitlement, and trial status; Firebase-generated app instance identifier | Used to verify App Store purchases and subscriptions and to provide paid features and trials |
For information about the data protection regime of the United States, see the survey published by the Personal Information Protection Commission of Japan (PPC). We have confirmed through each provider’s contractual terms and published data protection policies that appropriate safeguards are in place.
- Gemini API Additional Terms of Service
- Firebase privacy and security
- Cloudflare Privacy Policy
- RevenueCat Privacy Policy
Article 5 (Apple Calendar and Reminders Integration)
If you use Calendar integration, the title, start and end times, time zone, and related details of events you adopt or create in the App are written to Apple Calendar. A local copy and the corresponding Apple identifier are also stored in the App. The App does not bulk-analyze calendar events you have not adopted. When you choose to create a daily summary, the titles and times of adopted events on the relevant day are sent to Gemini as described in Article 2.
If you enable Reminders integration, task titles, due dates, and diary dates are written to Apple’s Reminders app, and completion, due-date, or deletion status may be synchronized. Diary text is never written to Reminders. Information written to Calendar or Reminders is synced by Apple according to your iCloud settings and may be visible to other members of a shared calendar or list.
Article 6 (Retention and Deletion)
- On-device data: Using iOS’s “Delete App” removes transcribed text, diary entries, and other App data from the App’s container on your device.
- Records on our server (Cloudflare D1): Records relating to AI usage; purchase, subscription, refund, and entitlement events; trial grants; and entitlement checks contain no diary content. They are retained for as long as necessary for their respective purposes, including managing usage limits, providing subscriptions, and preventing repeated acquisition of benefits, and are deleted when no longer necessary for those purposes.
- Firebase Analytics and BigQuery analytics data: Retained for no more than 14 months and then deleted according to the applicable service settings.
- Firebase Crashlytics diagnostic data: Crash data and associated identifiers are retained for 90 days before removal from live and backup systems begins. Because the App does not set a name, email address, or account ID in Crashlytics, we may be unable to identify or delete a particular user’s historical crash reports early.
- Data sent to the Gemini API: Retained for up to 55 days as described above, then deleted.
We normally rely on the retention periods and purpose-based deletion described above. We do not offer individualized early deletion as an always-available service. Individual requests are assessed and handled under Article 9.
Article 7 (Security Measures)
- All communications are encrypted with TLS.
- Credentials for the Gemini API are managed server-side only and are never included in the App.
- Our server is designed never to log diary content.
- We monitor the legal regimes of the countries where our processors operate and verify their handling terms (Article 4).
Article 8 (Provision to Third Parties)
We do not provide your information to third parties except as required by law (excluding the entrusted processing described in Article 4).
Article 9 (Your Rights)
The App has no accounts, and we do not ordinarily collect your name or email address through normal use. You may contact us under Article 12 to exercise rights of access, correction, restriction, deletion, or other rights under applicable law. Where applicable law requires a response, we assess and handle the request to the extent that we can reasonably identify both the requester and the relevant data.
An individual request does not guarantee immediate deletion of all data. Records that must be retained to manage usage limits, subscriptions, trial grants, prevent abuse, or comply with law; diagnostic or aggregate information that cannot be linked to an individual user; information retained by processors such as Google under their own policies; and data in Apple or other services managed by you may be outside the scope of deletion. If we cannot identify the data or fulfill the request, we will explain the reason or limitation.
Article 10 (Use by Minors)
Minors should use the App with the consent of a parent or guardian.
Article 11 (Changes to This Policy)
This Policy may be revised in response to legal changes or new features. Material changes will be announced in the App or on our website.
Article 12 (Contact)
For inquiries regarding this Policy:
- Developer: Atsuki Kakehi
- Email: support@kamerii.app
Established: August 22, 2026