This is an English translation to help you read these pages. We write the Japanese version first and then carry updates over to English, so if anything differs, the Japanese version is the official one. These terms are governed by the laws of Japan. Read the Japanese version (official)
AIZNOH is a service that keeps what you want to remember. That is why we explain up front what we protect and how, and what we cannot protect. We have avoided technical jargon as much as possible.
First, what we cannot protect
- The content of your memories is handled in a form our servers can read. It is not end-to-end encrypted (a method that not even the provider can read). This is because it is needed to search by meaning and for the AI to generate responses.
- The content of your memories is sent to AI providers in the United States. This happens when we create the search index and when we generate responses.
- We cannot promise to prevent every possible leak. The measures below are reasonable measures.
For this reason, we ask you not to store the information listed in the Terms of Service, such as passwords and credit card numbers.
1. Other people's memories are, by design, invisible to you
Separation between users is done not by the application program but by the database itself (row-level security). Because the condition "return only your own memories" is built into the data layer, even if the application has a bug, other people's memories are never returned.
2. We keep no key that can open everyone's data
In typical services, the server holds a key that can operate on the entire database, and the program is responsible for protecting "only this person's data". That means a mistake in the program can directly lead to a leak of everyone's data.
AIZNOH does not keep that key even on the application server. Account deletion and integration with external apps are each implemented with small components that handle only the rows of the person who called them. By design, there is no path that reaches everyone's data.
3. We do not let your memories be used to train AI
- We do not use memories for training, advertising or statistics.
- The AI providers we send them to are also used with settings under which data is not used for training (Anthropic does not use data by default and Voyage AI has opted out; OpenRouter, which we keep as a fallback and do not currently use, also has both training refusal and data retention disabled).
- Which providers receive what is described in full on the list of subprocessors. We announce changes to providers in advance.
However, once you hand memories to your own AI app through an external integration (MCP), it is outside our control. How they are handled from then on is determined by the terms and settings of the app you use. If you want to avoid use for training, please check the settings on that side. If you do not use integrations, this issue does not arise.
4. You can take your memories out and delete them at any time
- From the settings screen, you can export all your memories as a ZIP (a CSV that opens in spreadsheet software, and JSON for restoring).
- You can load the exported ZIP straight back from the same screen. You can also move it to another account.
- You can delete your account yourself. No inquiry is needed; your memories and account information are deleted.
We have not made it a service where you cannot take things out once you hand them over. We consider this part of safety.
5. About integration with external apps
- Tokens for integration are stored hashed. Looking at our database does not reveal the token itself.
- You can issue one for each app, and revoke only the ones you no longer need at any time.
- We set a limit on daily usage. Even if a token leaks, the damage cannot keep spreading.
- You can check the last-used time and today's usage count on the settings screen.
6. Protection from prying eyes
If you turn on the "display lock", a PIN is required to open your memories, notes and the dashboard. It is for when you step away or do not want your screen to be seen.
The PIN is stored only in your device's browser and is never sent to us. That is why we cannot know your PIN and cannot answer if you contact us about it. If you forget it, you can reset it from the screen. This is not a replacement for the real authentication (Google sign-in); it is only a light measure against prying eyes.
7. Other measures
- Encryption of communication (TLS) and encryption of the database at rest.
- Memories are stored in Japan (Tokyo). Part of the processing is done in the United States (described on the list of subprocessors).
- We do not write the text of memories to logs.
- Even if text that looks like an "instruction to the AI" is mixed into an imported document, we have processing in place so that it is not executed as a command.
- We use no advertising providers. On public pages only, we measure access with Google Analytics (nothing from inside the app, and none of the content of your memories, is sent).
If you notice something
If you find a security problem, please contact us through the contact form. We will review it and take the necessary action. It would help us if you contact us before making it public.
About this document
This page aims to explain how things work in an easy-to-understand way. For the official provisions on the handling of personal information, see the Privacy Policy; for the conditions of use, see the Terms of Service.