umeboshi-ask Install in 3 taps, use it free

Privacy Policy

Established October 7, 2026

Karimuto (hereinafter "we") establishes the following privacy policy (hereinafter the "Policy") for the study support service umeboshi-ask (hereinafter the "Service") that we provide.

Users shall use the Service upon agreeing to the Policy. Users may not use the Service unless they agree to the Policy. The key points shown in the consent dialog at send time are excerpts of the Policy; the full text of the Policy is authoritative.

1. Application of This Policy

This Policy applies to all aspects of the relationship between users and us concerning use of the Service. Where we separately establish rules or the like on the Service, they are treated as part of this Policy.

Age requirements are set out in Article 9.

2. Nature and Content of the Service

The Service generates text, information, suggestions, and other output (hereinafter "Output") using machine learning models.

Neither the Service nor the Output is guaranteed as to accuracy, completeness, timeliness, fitness for a particular purpose, or the like.

The Service is not intended to provide professional advice such as legal, medical, investment, or tax advice. Consult a professional or check primary sources as needed.

Please refrain from using the Service from within the EU/EEA until an EU representative has been designated. This sentence will be removed once the designation is complete.

3. Handling of Input Content and Output

3.1 Use of Input Content

Text and instructions that users enter into the Service (hereinafter "Input Content") and Output (together with Input Content, hereinafter "Content") may be handled by us for the following purposes.

We ourselves do not use Content to train AI models. However, log retention and product-improvement use by the transmission recipients (upstream LLM providers via OpenRouter) are governed by each provider's terms, and we cannot control them. Remove confidential information before sending.

We may, at our discretion, delegate handling of Content to contractors to the extent necessary to achieve the purposes set out in the preceding paragraph.

3.2 Rights and Responsibilities

Users represent and warrant to us that, with respect to Input Content, they hold the rights and authority to enter it lawfully and that it does not infringe the rights or interests of any third party.

Users grant us permission to handle Input Content to the extent necessary to achieve the purposes set out in 3.1 above.

We permit users to use the Service to the extent necessary to provide the Service.

4. Information We Collect

We collect information about users as follows.

Question information: We collect the question text users enter into the Service, the selected button name, the card context, the model name, and Effort. Saved Notes and thinking are not sent.

Device information: We store seven items -- the consent flag, settings, Refresh, the model ID, the Effort dictionary, the Worker URL, and the access token -- on the device (localStorage). Login access tokens are held in memory only. The ask_origin cookie holds only a port number and contains no information identifying an individual.

Usage records: For anonymous use, we collect a weekly ask count based on a hash of the IP address and user agent. We do not retain raw IP addresses. For signed-in use, we obtain the identifier (sub) through Google authentication. We do not obtain email bodies.

Authentication information: Along with the Google authentication identifier (sub), we receive the email address used to display the signed-in account on screen. We use them for identity verification and monthly plan association (the on-screen display stays within identity verification). We hold the email address on the server only for the 15 minutes it takes to pass the login code; after that we do not store it on the server (the token is held on the device only).

Payment information: We receive the monthly plan and purchase status via Stripe. Card numbers and the like are processed by Stripe; we do not retain them.

A hash made from the IP address and user agent could identify an individual when combined with other information, so we manage it as related personal information. We do not provide it upstream.

5. Purposes of Use of Information

We use collected information for the following purposes.

The lawful bases for processing data of users in the EU are as follows. Providing question answering, managing limits, storage, and handling inquiries rely on performance of a contract (GDPR Article 6(1)(b)); preventing misuse and ensuring security rely on legitimate interests (point (f) of the same paragraph).

On the transmission path, the Worker does not persistently store question text (except for temporary in-memory retention for transmission processing). The LLM API key is held only on the Worker side, not in the note type.

6. Disclosure of Information

We disclose information to third parties in the following situations.

Contractors: To obtain the business-operation support we need and to perform specific services and functions, we disclose information to OpenRouter (relay to generative AI), Stripe (payment processing), and Cloudflare (distribution infrastructure) to the extent necessary to achieve the purposes. Handling of logs by upstream LLM providers is governed by each provider's terms.

Cross-border transfers: Question text, model names, and the like are sent to US businesses. OpenRouter relies on a data processing agreement (with SCCs incorporated). Stripe relies on a data processing agreement and the Data Protection Framework (DPF). Cloudflare relies on a customer data processing agreement and the DPF. Google authentication issues identifiers with Google as an independent controller; this is not a delegated transfer to us. Conditions for onward transfers to model providers downstream of OpenRouter are governed by each provider's terms. If you do not agree, you may not use the Service.

Government authorities or other third parties: We may provide information only where necessary to comply with legal obligations, protect rights, detect or prevent fraud, or protect safety, in compliance with laws and regulations.

7. Retention

We retain information only for the period necessary to provide the Service or for legitimate business purposes. The retention period for each item of information is as follows.

Only when a save operation is selected, the question text and answers are retained until deleted. The list holds up to 50 items; one saved item holds up to 100 messages, and one message holds up to 20,000 characters of question and answer combined. Items exceeding 50 are discarded oldest first.

Settings expire after 10 years. The first-time determination marker for anonymous use expires after 90 days. The weekly ask count for anonymous use expires by the following Monday JST. Authorization codes expire after 15 minutes, access tokens after 1 hour, and refresh tokens after 30 days. Our authorization ledger expires after 1 year. Payment records on Stripe's side are retained according to Stripe's terms. Books required by law are retained for the statutory period. Duplicate-prevention records for Stripe notifications expire after 7 days, issuance records for purchase and management after 15 minutes, and model inventory after 24 hours.

8. Data Controls

The Service provides the following controls over the use and retention of information.

Saved Notes can be deleted one at a time, immediately, with the Delete button on the card.

Where a deletion request is made, we delete the relevant Saved Notes and settings within 7 days (calendar days) of the request. For deletion of settings, account deletion, and token invalidation, contact us at the contact email address. State subject Delete request in the subject line. The "Withdraw consent" operation in settings redisplays the consent dialog at the next send. Withdrawal stops future sends; it does not retroactively erase already-sent content or upstream records.

You may request disclosure, correction, suspension of use, and the like of retained personal data. Contact us at the contact email address with subject Privacy Request. We respond after identity verification, free of charge. We handle deletion requests in principle within 7 days (calendar days). We send an initial reply to general inquiries within 7 business days. In all cases we reply no later than the statutory limits of one month under the GDPR and 45 days under the CCPA; where the matter is complex and an extension is needed, we inform you of the reason and the expected timing within those periods.

9. Children

The Service may not be used by persons under 16. Persons under 18 shall use it only with the consent of a parent or other legal representative.

Where use by a person under 16 comes to light, we delete the related information.

10. Security

We take commercially reasonable technical and operational measures to protect information against loss, misuse, unauthorized access, leakage, alteration, or destruction.

However, transmission over the Internet is not completely secure or error-free. Take particular care in deciding what information to provide to the Service.

11. Note on Accuracy

Output is not always accurate. Users should not rely on Output from the Service as the sole source of true or fact-based information or as a substitute for professional advice.

Do not use Output relating to an individual as the sole basis for purposes that may have legal or significant effects on the individual, such as credit, education, employment, housing, insurance, legal, medical, or other important decisions.

12. Measurement

In the product, we perform only the weekly ask count for limit management and monthly plan and balance management.

On the public site, visit measurement by Cloudflare Web Analytics may apply. No cookies are used. The information sent, its recipients, and purposes are governed by Cloudflare's terms.

13. Changes to This Policy

When we change this Policy, we post the revised Policy and its effective date on this page. We announce material changes on this page and on the settings screen before they take effect.

Where purposes of use are added, contractors are added, transfer destinations are added, or retention periods are extended, we obtain consent again. The revision history is as follows. October 7, 2026: initial version established. October 12, 2026: added the receipt and retention period of the email address used to display the signed-in account on screen.

14. How to Contact Us

For questions about this Policy or deletion requests, contact karimuto.dev@gmail.com. State the matter (such as subject Delete request or subject Privacy Request) in the subject line. Until an EU representative is designated, we serve as the contact point. Users in the EU may lodge a complaint with a supervisory authority. For sales matters, see the Legal Notice.