Privacy Policy
Last updated: September 30, 2026
This is an English translation provided for reference only. The Japanese version is the official version, and if there is any difference between the two, the Japanese version prevails. These terms are governed by the laws of Japan. Read the Japanese version (official)
AIZNOH SERVICE (“we” or “us”) sets out below how we handle personal information in “AIZNOH” (the “Service”), a memory support service.
What we want you to know first
To make your memories searchable and recallable, the Service processes the content of memories in plain text on the server side. It is not end-to-end encrypted (a method where we could never read the content). In addition, the content of memories and what you type into the memory assistant are sent to AI providers in the United States for search and to generate responses.
Because this is unavoidable given how the Service works, the Terms of Service ask you not to store passwords, card numbers, My Number (Japan's individual number), other people's personal information and the like.
We do not let your memories be used to train AI
We do not use the content of memories to train AI. We also do not analyze it for statistics or advertising.
Furthermore, we use the providers we send memories to with settings under which the data is not used for training.
- OpenRouter: a relay to AI models. In addition to the setting that refuses use for training, we apply the setting that limits routing to providers that do not retain data (Zero Data Retention). The instruction refusing use for training is also sent with every request (their explanation).
- OpenAI: data sent through the API is not used to train models (their explanation).
- Anthropic (not currently used; kept as a fallback): data sent through the API is not used to train models by default (their explanation). We do not use the feedback feature, so the exception does not apply.
- Voyage AI: we apply the setting that opts out of using data to train future models. According to their explanation, with this setting the data sent is not retained (zero-day retention).
However, once you pass memories to your own AI app through the integration (MCP), how they are handled depends on that app's terms and your settings. We cannot control this. See “4. Memories passed through the integration (MCP)” below.
1. Information we collect
| Information | Details |
|---|---|
| Account information | The email address of your Google account, and a display name you choose to set |
| Memories | The text you register, tags, where it was registered from, and when |
| Notes | The text you enter (meeting minutes, memos, etc.), titles, and creation/update times |
| Tasks | The to-dos you register, notes, due dates and times, groups, and whether and when they were completed or dropped |
| Search vectors | Numeric sequences generated to search memories by meaning. Because they may partially reveal the content, we treat them as personal data |
| Connection tokens | Hashes of tokens for connecting external apps, their names, last-used times and usage counts (we do not store the tokens themselves) |
| Inquiries | The name, email address and message sent through the contact form, and when it was sent (if sent while signed in, which account sent it) |
| Payment information | The status, plan and expiry of your paid plan, and the identifier of the subscription at the payment provider. Card numbers and other payment details are entered directly on the payment provider's screen; we never receive them |
| Search reports | When you report that a memory could not be recalled: the search terms, the number of results and any comment you add (only when you send a report) |
| Operation logs | Processing times, counts, error details, etc. We do not log the text of memories |
The PIN for the display lock is stored only in the browser on your device and is never sent to our servers. We therefore cannot know your PIN and cannot answer inquiries about it.
2. Purposes of use
- Providing the Service (storing, searching, recalling, summarizing and tagging memories, storing notes, and extracting key points from notes)
- Authenticating users and ensuring that each user sees only their own memories
- Billing fees and checking the status of subscriptions
- Responding to and handling inquiries
- Sending important notices (outages, maintenance, changes to the terms, etc.)
- Investigating defects and preventing misuse
We do not use the information for any other purpose. For use in training, see the box at the top.
3. Service providers (subprocessors)
To provide the Service, we outsource the database, running the app, AI processing, authentication and payments to external providers. All of them are headquartered in the United States, and this constitutes “provision to a third party in a foreign country” under Japan's Act on the Protection of Personal Information. The text of memories is sent to U.S. providers to generate responses and create search vectors.
The provider names, purposes, information provided, data locations and use for AI training are listed on the list of subprocessors (Japanese), which forms part of this policy. When we add or change a provider, we will update that page and announce it on the Service in advance. The change history is also recorded there.
For payments, we use card payments (Stripe). Payment by PayPal is also available.
4. Memories passed through the integration (MCP)
The Service offers an integration (MCP) that lets AI apps such as Claude, ChatGPT and Cursor read and write memories. How memories you pass to your own AI app through this feature are handled depends on that app provider's terms and your own settings. As this is beyond what we can control, we are not responsible for it.
If you want to avoid use for training, check the settings of the AI app you use (for example, enabling a privacy mode or turning off use for training). If you do not use the integration, this issue does not arise.
5. Writing other people's information in notes
The notes feature is designed for taking meeting minutes. Minutes may include the names, remarks or contact details of people other than you. In that case, we hold the information on your instructions (as a processor), and the decision whether to record that information is yours.
The text of a note is sent to AI providers when you extract memories from it (the recipients are as listed on the list of subprocessors (Japanese), and none of them use it for AI training). If you do not extract, the text of your notes is not sent to external AI providers.
If you use the Service for work, your organization's rules may restrict storing third-party information in external services. Please check your own responsibilities before using it.
Note that we do not guarantee the country or region where AI processes the text of memories and notes. All our providers are headquartered in the United States, but where a company is headquartered and where processing takes place are not necessarily the same. If you need processing limited to a particular region, please contact us through the contact form (in Japanese).
6. Voice input
Voice input with the microphone button uses the speech recognition built into your browser. This feature sends audio to the servers of the browser provider (such as Google) to convert it to text. It does not pass through our servers. If you do not want to send audio, type instead.
7. Security measures
- Encryption in transit (TLS) and encryption at rest for the database
- Per-user isolation with row-level security (each user can access only their own memories)
- Tokens for external app connections are stored as hashes; we do not keep them in plain text. You can revoke them at any time
- We do not write the text of memories to logs
These are reasonable measures and do not guarantee that every leak can be prevented.
8. Retention and deletion
- Memories and notes are stored until you delete them or delete your account.
- A “replaced” memory no longer appears in searches or recall, but remains as a record. To remove it completely, delete it.
- Deleting a note does not delete memories extracted from it (you can delete them individually on the memories screen).
- Inquiries are erased one year after they have been handled (they remain as a record of our response even if you delete your account).
- Payment information (subscription status, expiry and identifiers) is erased when you delete your account. However, records of payment notifications received from the payment providers (type of notification, subscription identifier, amount, etc.; no names or card details) are kept for accounting and troubleshooting. Transaction records kept by the payment providers are retained under their own rules.
- From the settings screen you can completely delete your account, memories and notes. This cannot be undone.
- To prevent the free trial from being used repeatedly, even after an account is deleted we keep only an identifier used to tell whether an email address has already had a trial and the date the trial started. The identifier is a transformation of the email address that cannot be reversed; we do not keep the email address itself. All content such as memories and notes is erased with the deletion.
- From the settings screen you can export all memories and notes in ZIP format. The exported file can be restored from the same screen. Notes are also included one by one as text, so you can read them in other apps even if you stop using the Service.
9. Requests for disclosure, correction, suspension of use, etc.
If you wish to request disclosure, correction, suspension of use, etc. of retained personal data, please contact us at the address below. We will respond after confirming your identity. You can view, correct, delete and export your memories yourself at any time after signing in.
10. Cookies and similar technologies
We use cookies to keep you signed in. We also use the browser's local storage to keep display lock settings and temporary on-screen states. We use Google Analytics cookies to understand how the public pages are used (see the next section). We do not use cookies for advertising.
11. Access analytics (external transmission)
We use Google Analytics, provided by Google LLC, to understand how the public pages of the Service are used and to improve our information and usability. As a result, the following information is sent from the devices of users who view the public pages to Google LLC.
- Pages covered: public pages such as the home page, pricing and free trial, how to connect, security, terms of service, privacy policy, list of subprocessors and the legal notice
- Information sent: the URL (without search strings and the like) and title of the page viewed, the time of viewing, the referrer, the type of device and browser, the approximate region, and an identifier stored in a cookie
- Recipient: Google LLC (United States)
- Purpose: to learn which pages are read and how much, and where visitors come from, in order to improve our information and usability
We do not measure inside the app (memories, notes, tasks, the memory assistant, settings and other screens after sign-in). We never send the content of memories or notes, email addresses or other information that directly identifies users to Google Analytics. We also do not use advertising features (Google signals or ad personalization).
How Google Analytics handles information is explained on Google's site. To stop the transmission, block cookies in your browser settings or use the Google Analytics Opt-out Browser Add-on. Stopping it does not affect your use of the Service.
12. Changes to this policy
We may change this policy when we consider it necessary. We will announce important changes on the Service.
Contact
AIZNOH SERVICE (the name of the business handling personal information is listed in the Notice under the Specified Commercial Transactions Act (Japanese))
1-2-12-707 Yushima, Bunkyo-ku, Tokyo 113-0034, Japan
Inquiries about personal information: Contact form (the form is in Japanese, but you can write in English)