Privacy Policy — DreamVoice (Yume no Koe)

Last Updated: 2026-09-14
Operator: Takahiro Nishinobu (individual)
Contact (Support Form): https://forms.gle/9eEJhVS64nKTxdgr8

Related: Terms of Service / Markdown / 日本語版

1. About This Policy

This Privacy Policy explains how the Operator handles user information in DreamVoice (“Service”). The Service is intended for users aged 13 or older. Users under 13 may not use the Service. If a higher age requirement applies under the applicable store age rating or local laws, that requirement applies. We do not knowingly collect information from users below the applicable age. If we learn that a user is under the applicable age, we will delete the information. Minors should use the Service with guardian consent.

2. Information Collected

The Service may collect the following:

The feedback survey does not ask users to provide their name, user ID, or dream content. The Service does not append a Support ID, anonymous authentication ID, dream identifier, dream content, or usage history to the survey URL, and does not link survey responses with in-app usage history.

Safety support flags, levels, and reason categories are used only to display supplemental in-app guidance when the input may include strong distress or safety concerns. They do not constitute medical, psychological, legal, or other professional judgment.

3. How It Is Collected

4. Purpose of Use

5. Third-Party Services

The Operator uses third-party services to provide and operate the Service. Their handling of information is governed by their own policies.

Apple Ads Measurement

To measure Apple Ads performance, the attribution token obtained from Apple’s AdServices.framework is sent temporarily to Apple through the Service’s server. The token itself is not stored and is not written to logs or analytics. From Apple’s response, only attribution fields such as campaignId, adGroupId, and keywordId are stored on the device and recorded in Google Firebase Analytics. This process does not display the OS tracking-permission prompt.

Sending to OpenAI

To provide AI-generated features and classify Dream Dictionary symbols, user input such as dream text, Today's Voice text, titles, emotion tags, dates, daily question notes, daily Dream Voice outputs, Today's Voice outputs, source dream information, daily question notes and related question text needed for Weekly Dream Letter generation, references, and generated results may be sent to OpenAI. After a new Dream Voice finishes, the Service may send the symbol name, the meaning returned for that dream, the language, and information about candidate representative symbols to OpenAI to organize the symbol under the same representative symbol. This classification request does not include the dream text or a user identifier.

By using AI-generated features, users agree that user input and related information necessary for generation may be sent to external AI services within the scope necessary to provide those features.

OpenAI states that API inputs and outputs are not used to train or improve its models by default. However, OpenAI may retain inputs, outputs, and related metadata for a limited period for purposes such as abuse monitoring, service operation, legal compliance, and safety. Retention and handling are governed by OpenAI’s policies and the API settings used by this Service.

Your Dream Dictionary

Opening, searching, refreshing, or correcting the grouping in Your Dream Dictionary uses previously stored Dream Voice outputs and Dream Dictionary derived data on the Service's server. These actions alone do not send new dream text, symbols, or meanings returned for an individual dream to OpenAI for AI reanalysis.

Sending information to OpenAI when a new Dream Voice is generated, and when its symbols are classified after generation completes, is described above in “Sending to OpenAI.”

6. Disclosure to Third Parties

The Operator does not provide personal information to third parties without consent, unless required by law. However, data may be sent to the above service providers within the scope necessary to provide the Service.

7. Cross-Border Transfer

Because the Service uses cloud services provided by overseas operators, including Apple, Google Firebase, OpenAI, and Google Forms, collected data may be processed or stored on servers outside your country/region, including but not limited to the United States.

8. Retention

9. User Rights and Choices

Information submitted through the support form or feedback survey form is not automatically deleted when you use the in-app account deletion feature. If you want it deleted, please contact the Operator through the contact form and provide information that identifies the submission.

If you delete a Today's Voice record, the stored data, generated result, and related snapshot for that Today's Voice record are subject to deletion. Today's Voice is not used as a source for Weekly Dream Letter generation in v1.

Even if you delete an individual dream entry or daily question note, Weekly Dream Letters already generated before deletion may still contain summaries, keywords, symbols, reflections, or text based on that entry or note. To delete derived weekly results as well, please use the Weekly Dream Letter deletion feature or the account deletion feature.

If you delete an individual dream entry, content in Your Dream Dictionary derived from that entry is excluded from the active Dictionary and is not shown again after later syncs. To prevent it from being shown again, source references, symbols, and meanings returned for that dream may be retained in a deleted state within your account. If you delete your account, Dream Dictionary derived data, including source-dream references, display summaries, and grouping corrections, is also subject to deletion.

Deletion mainly applies to data managed by the Service. Logs, backups, audit records, abuse-prevention records, legal-compliance records, and dispute-response records held by external services may remain for the period required by each service or applicable law.

Identifiers issued through anonymous authentication may remain on the device or be restored after reinstalling the app, depending on the device and OS behavior. To delete related server-side data, please use the account deletion feature.

10. Security

The Operator takes reasonable measures to prevent unauthorized access or leakage, including:

11. Incident Response

If a breach or similar incident occurs, the Operator will investigate impact, prevent recurrence, and notify when legally required or deemed necessary.

12. Changes to This Policy

This Policy may be updated; notices will be given in-app or on the web.

13. Contact

For inquiries about this Policy: https://forms.gle/9eEJhVS64nKTxdgr8