Recoco Privacy Policy

Last updated: July 1, 2026　/　Effective date: July 1, 2026

This is a reference English translation. The Japanese version (プライバシーポリシー) is the authoritative text; in the event of any discrepancy, the Japanese version prevails.

Yuji Fujisaka (the "Developer") establishes this Privacy Policy (this "Policy") as follows regarding the handling of user information in "Recoco," a voice memo app for reflection (the "App").

This Policy explains data handling in the latest version of the App. In past versions, some functions, storage locations, synchronization methods, and the use of external services may differ. Where there are material differences, this Policy or the change history will explain the handling for each applicable version.

1. Administrator and Contact

2. Information Handled by the App

The App handles the following information depending on the user's settings, permissions, and the functions used.

Type of information Details Main storage / transmission destination Main purpose of use
Recorded audio Audio recorded by the user in the App In principle, within the user's device. When speech recognition is used, it may be transmitted to Apple's servers. Recording, playback, transcription
Transcription results Text strings of recognition results generated by the Apple Speech API and the like Within the device, Firebase database Reflection on recording content, search, playback assistance, synchronization, backup
Recording meta-information Recording title, tags, time information, playback state, recording duration, creation/update timestamps, and other information related to recordings Within the device, Firebase database Management of recordings, search, playback assistance, synchronization, backup
Calendar information Event titles and the like from the standard calendar, where permitted by the user Within the device; may be stored in Firebase as a recording title or meta-information. Assisting recording-title input, organizing recording content
Location information The device's location at the time of recording, where permitted by the user Within the device, Firebase database Recording the location of recording, organizing recording content
Identifiers Firebase authentication ID (in principle, an anonymous authentication ID), Firebase Installations ID (app instance ID), information used for ad-effectiveness measurement via SKAdNetwork, and the like. The App does not obtain the advertising identifier (IDFA) and does not perform tracking based on App Tracking Transparency. Firebase, Google Mobile Ads SDK, Apple Synchronization, backup, advertising display (non-personalized ads), failure investigation, fraud prevention
Usage data App launches, screen views, feature usage, operation events, and the like Firebase (Google) Statistical analysis of usage, feature improvement, failure investigation
Diagnostic data Crash logs, performance information, error information, and the like Apple, Firebase Crashlytics Failure investigation, quality improvement
Purchase information Purchase status through the App Store, subscription status, transaction IDs, and the like (where paid features are provided) Apple, systems managed by the Developer (where necessary) Purchase confirmation, provision of paid features, refund and inquiry handling
Inquiry information Email address, inquiry content, attachments, and information necessary for support Email service, support tools Inquiry handling, identity verification, failure investigation

Note: The table above reflects the handling that the developer actually performs in the latest version of the App. The app version and the Firebase configuration are managed by the developer, and if the handling changes as a result, this Policy will be revised accordingly. The scope of information actually handled, on the other hand, depends on the user's permission settings (such as calendar, location, and microphone access) and the functions used.

3. About Speech Recognition

  1. To provide the transcription function, the App may use Apple's Speech framework / Speech API.
  2. When speech recognition is used, audio recorded by the user or part of the audio data may be transmitted over the network to Apple's servers, where speech recognition processing is performed.
  3. Before using speech recognition, the App requests the user's permission through the speech recognition permission and microphone permission provided by iOS.
  4. The accuracy, completeness, and timeliness of speech recognition results are not guaranteed.

4. About Firebase

  1. The App may use Firebase, provided by Google, for purposes such as synchronization, backup, handover, and settings delivery of recording meta-information, transcription results, tags, playback state, and the like.
  2. Data stored in Firebase is associated with the Firebase anonymous authentication ID and the like, and is managed in a form accessible from the user's app environment.
  3. Use of Firebase is subject to Google's terms, privacy policy, the Firebase data processing conditions, and security settings.
  4. The current implementation uses Firebase Authentication, Firebase Realtime Database, Firebase Remote Config, Firebase Crashlytics, and Firebase Analytics. Usage events are sent from the App to Firebase Analytics. Diagnostic information about crashes and errors is sent to Firebase Crashlytics.

5. About Calendar and Location Information

  1. Only where permitted by the user, the App may reference event information from the standard calendar and use it as a candidate recording title or as recording meta-information.
  2. Only where permitted by the user, the App may obtain location information at the time of recording and store it as the recording location.
  3. Users can change permissions for calendar, location, microphone, speech recognition, and the like at any time via the iOS "Settings" app or the settings within the App. If a permission is disabled, some functions may be unavailable.

6. Purposes of Use

The Developer uses the information obtained or processed for the following purposes.

  1. To provide the App's recording, playback, transcription, tagging, search, organization, synchronization, backup, and handover functions;
  2. To make it easier for users to reflect on their recording content;
  3. To maintain and improve the App's settings, permissions, display, and operability;
  4. For failure investigation, ensuring security, fraud prevention, and quality improvement;
  5. To statistically analyze usage and use it to improve the App;
  6. For paid features, purchase confirmation, subscription management, and refund and inquiry handling;
  7. To respond to inquiries, deletion requests, exercise of rights, and support from users;
  8. To respond to laws and regulations, platform terms, and orders of courts or administrative agencies.

7. Provision to Third Parties and Transmission to External Services

  1. Except where based on laws and regulations, where the user consents, where external services necessary to provide the App are used, or where necessary to protect a person's life, body, or property, the Developer does not sell or provide users' personal information to third parties.
  2. To the extent necessary to provide the App, the Developer may use external services such as Apple, Google Firebase, Google Mobile Ads, the App Store, and email and support services.
  3. The Developer does not currently transmit users' recorded audio or transcription text to OpenAI, Anthropic, Google Gemini, or other third-party generative AI services. If, in the future, the Developer introduces a function that transmits users' personal data or user content to third-party AI services, the Developer will explain in advance the destination, the data transmitted, and the purpose of use, and will obtain any consent required by law or platform terms.
  4. The Developer does not provide users' recorded audio or transcription text for the purpose of training third-party AI models. However, if the Developer carries out such handling in the future, it will obtain explicit consent in advance.

8. Advertising and Tracking

  1. The App uses the Google Mobile Ads SDK to display advertisements. In the current version, the App serves ads with a setting that requests them as non-personalized ads (npa=1), and does not display targeted advertising based on the user's interests.
  2. In the current version, the App does not obtain the advertising identifier (IDFA) and does not perform tracking across apps and websites. Therefore, it does not display the App Tracking Transparency permission dialog, and there is no dedicated setting within the App to change tracking permission. Choices regarding ad personalization may be made separately via iOS settings or the advertising settings provided by Google.
  3. Even for non-personalized ads, Google may process information to the extent necessary for ad delivery in order to deliver ads, prevent fraudulent clicks, limit frequency, and the like. Details are governed by Google's advertising policies.
  4. The App uses Firebase Analytics, and usage events are sent from the App to Firebase Analytics.

9. Retention Period

  1. Recorded audio, transcription results, tags, meta-information, and the like stored within the device are retained until the user deletes them within the App or deletes the App. However, they may remain in iCloud backups, device backups, file export destinations, and the like.
  2. Recording meta-information, transcription results, tags, playback state, and the like stored in the cloud such as Firebase may be retained until deletion by the user, a deletion request, service termination, a review of the retention period, deletion necessary for operational or security reasons, or other reasonable grounds.
  3. Usage data, diagnostic data, logs, and inquiry records are retained for the period necessary to achieve the purposes of use, or for the period necessary for legal, accounting, security, or dispute-handling purposes.
  4. For stable operation of the Service, ensuring security, and optimizing storage capacity, the Developer may, after providing reasonable prior notice, delete or exclude from retention cloud data for which use has not been confirmed for a certain period.

10. User Choices, Withdrawal of Consent, and Deletion Requests

  1. Users can change permissions for the microphone, speech recognition, calendar, location, notifications, tracking, and the like via iOS settings.
  2. Users can delete or export recordings, transcriptions, tags, meta-information, and the like using the App's functions. Recorded audio and transcription text can be exported from the share menu on the playback screen, and transcription text can be copied to the clipboard.
  3. When you delete a recording or an individual transcription segment within the App, in addition to the target data within the device, the corresponding recording meta-information or segment information stored in Firebase is also deleted.
  4. If you wish to delete all cloud data associated with your Firebase anonymous authentication ID, you can check the Support ID displayed in the App and request deletion by contacting the Developer.
  5. When processing a deletion request, the Developer may confirm that the requester manages the target data in order to prevent erroneous deletion or unauthorized deletion by a third party.
  6. Responding to a deletion request may take time. For legal, security, backup, dispute-handling, accounting, or other legitimate reasons, certain information may be retained without deletion.

11. Security Management Measures

To prevent leakage, loss, damage, and unauthorized access to the information it handles, the Developer takes, to a reasonable extent, necessary security management measures such as access restrictions, authentication, communication protection, security settings of cloud services, log management, and permission management. However, due to the nature of using internet communications, devices, the OS, and external services, complete security is not guaranteed.

12. Transfers Overseas (Provision to Third Parties in Foreign Countries and Understanding of the External Environment)

  1. The App uses services provided by businesses located primarily in the United States, such as Apple (Apple Inc.), Google Firebase and Google Mobile Ads (Google LLC), and email and support services. As a result, user information may be stored or processed on servers outside Japan (primarily in the United States).
  2. Regarding the personal information protection systems of these countries and regions, you can refer to information on the systems of each country published by the Personal Information Protection Commission and the like. The United States differs from Japan in respects such as the absence of a comprehensive personal information protection legal framework at the federal level.
  3. The Developer uses these services on the premise that, in accordance with the applicable data processing conditions with these external service providers, reasonable security management measures such as encryption and access restrictions are taken. Specific handling by each provider is governed by the privacy policies and data processing conditions published by Apple and Google.
  4. Where the consent of the individual or other measures are required by law for the provision of personal data to a third party in a foreign country, the Developer will provide information on the name of the destination country, information on that country's personal information protection system, and the protective measures it takes, and will then carry out the necessary procedures.

13. Children's Privacy

If a minor uses the App, the minor should do so after obtaining the consent of a person with parental authority or another legal representative. Except where required by law, the Developer's policy is not to obtain additional personal information for the purpose of age verification.

14. Changes to This Policy

  1. The Developer may change this Policy in connection with changes to the App's functions, changes to the external services used, or changes to laws or platform terms.
  2. When making a change that materially affects users' privacy, such as the types of information obtained, purposes of use, storage locations, third-party recipients, retention periods, or deletion methods, the Developer will notify users through in-app notice, the Developer's website, or other appropriate means before starting the changed handling.
  3. If the Developer uses information already obtained for a new purpose that does not have a reasonable relationship with the purpose of use indicated at the time of acquisition, the Developer will provide the notice, publication, or consent acquisition required by law.

15. Contact

For inquiries regarding this Policy, data deletion, withdrawal of consent, exercise of rights, or other privacy matters, please contact the following.

Revision History

End