Privacy Policy
Privacy Policy
The operator of DAIW (the “Operator”) processes users' personal information in accordance with Korea's Personal Information Protection Act and related laws. This policy explains what information DAIW processes and why, how long it is kept, and what rights you have.
In short. The server stores only what sign-in needs (email address, password hash, account ID, access token hashes). Your audio (bounced files) never leaves your Mac. The DAW requests that Claude or the AI in the DAIW app's chat window sends, and their results, are relayed through the server, and to improve the Service we keep a pseudonymous record of tool calls and of your requests (no audio, email addresses or file paths). You can turn this record off with “사용 기록 공유” (Share usage) in the DAIW app menu. Conversations in the DAIW app's chat window go straight from your Mac to the AI company you pick, with your own API key, which stays in your Mac's keychain. If you allow it, from November 8, 2026 we also keep your chat-window conversations under the pseudonym to build DAIW's AI models.
1. Why we process personal information
The Operator processes personal information only for the following purposes and does not use it for anything else.
- Sign-up and sign-in: creating an account with an email address and password or a Google account, and confirming that it is you.
- Connection authentication: authenticating the claude.ai connector and the DAIW app to the server under your account (OAuth).
- Providing the Service: passing the DAW requests Claude sends to the DAIW app on your Mac and returning the results. The compose feature generates MIDI data on the server and sends it to your Mac.
- Running the Service: using server access logs to find the cause of faults and respond to abnormal access.
- Improving the Service and developing AI models: using the pseudonymous usage record, and the chat-window conversations you allow, to make DAIW handle requests better and to build DAIW's AI models (a model that works the tools, and models for composing and mixing). No record is kept for users who turn usage sharing off.
- Paid subscriptions: linking a Pro payment to your account and unlocking Pro features according to your subscription status.
- Support: answering your questions and handling requests to leave.
2. What we process
Stored on the server
| Item | When it is collected | How it is stored |
|---|---|---|
| Email address | When you sign up with email, or the address Google confirms when you sign in with Google | We ask Google only for the openid email scopes |
| Password | When you sign up with email | Stored only as a scrypt hash; the original is never stored |
| Account ID | Generated automatically at sign-up | A random value |
| Sign-up time | Recorded automatically at sign-up | — |
| OAuth client registration | When you connect claude.ai and the DAIW app | The registration details of the connected apps (claude.ai, the DAIW app) |
| Access tokens | Issued when you sign in | Only a hash is stored, never the token itself |
| Usage record (pseudonymous) | When Claude, or the AI in the DAIW app's chat window, calls a DAIW tool, and when you rate an answer in the chat window (if usage sharing is on, which is the default) | A random pseudonym per account, time, connected app (such as claude.ai), DAIW app version, tool name, your request (the words Claude passes along when it calls a tool, or in the DAIW app's chat window the message you typed, up to 300 characters), a summary of the arguments and result (file paths masked, long content shortened), success, and duration. From November 6, 2026 it also holds random values that group the calls of one conversation (the connection's session ID, the chat window's conversation ID) and the chat window's message number, the name and version the connected app reports, the AI model used in the DAIW app's chat window, and the 👍/👎 you give an answer in the chat window (with the message you rated). It contains no email address and no audio |
| Chat-window conversations (pseudonymous) | When you allow “대화를 DAIW 모델 학습에 쓰기” (use my chats to train DAIW's model) in the DAIW app's chat window and usage sharing is on, from November 8, 2026, for each answered message | What you wrote, the AI's answers, the tool calls and their results (file paths hidden, each result cut at 20,000 characters), and the same pseudonym, conversation ID, message number and AI model name as the usage record. It contains no API key, email address or audio |
| Upgrade link token | Generated automatically the first time you check your plan or use a Pro feature | A random value |
| Subscription status | Sent by Paddle when you pay for, renew or cancel Pro | Paddle subscription ID, status (active, canceled and so on) and the time it changed. We never receive payment details such as card numbers |
Recorded automatically
- Server access logs: IP address, request path and time, kept as web server and application logs in the server's operating system log (systemd journal).
- DAIW app log: connection status is written to
~/Library/Logs/DAIW/daiw.logon your Mac. This log is never sent to the server.
Not collected at present
We do not currently collect names, phone numbers, postal addresses, payment details (Paddle handles these directly), marketing consent, or behavioral data from advertising or analytics tools.
3. What we process but do not store
Your audio never leaves your Mac. Audio (bounced) files stay on your Mac. Measuring happens on your Mac, and only the measured numbers reach the server.
- Tool requests and results: the tool requests Claude makes and their results (DAW commands, track names, plug-in parameters, measurements and so on) are relayed through the server to the DAIW app on your Mac and are not stored as they are. If usage sharing is on, only the usage record described in section 2 (pseudonymous, summarized) is kept.
- Compose data: the compose feature generates MIDI data on the server and sends it to your Mac; the MIDI data itself is not stored. The usage record keeps only a summary such as the chord progression, key and tempo.
- Your conversations with AI: conversations with Claude and other AI services are processed by that AI company, not DAIW, under its policies. The DAIW app's chat window works the same way: the conversation, and the tool results used in it, go from your Mac straight to the AI company you pick, with your own API key. Unless you allow “대화를 DAIW 모델 학습에 쓰기” (use my chats to train DAIW's model), they are not stored on the DAIW server; if you allow it, from November 8, 2026 the chat-window conversation described in section 2 is kept under the pseudonym. Your API key is kept only in your Mac's keychain and is never sent to the DAIW server. If you pick a local model running on your Mac, the conversation does not leave your Mac.
4. How long we keep it
| Information | Retention |
|---|---|
| Account information (email address, password hash, account ID, sign-up time) | Until you leave |
| Access tokens | Access tokens 1 hour, refresh tokens 90 days. A refresh token is replaced with a new one each time it is used, and is revoked when you sign out. |
| OAuth client registration | While the connected app uses the Service |
| Upgrade link token, subscription status | Until you leave. Payment records held by Paddle follow Paddle's policies. |
| Server access logs | Kept according to the server operating system's log settings; once a set size is exceeded, the oldest entries are deleted automatically. |
| Server backups (snapshots) | The whole server is snapshotted automatically every day; each snapshot is kept for 7 days and then deleted automatically. |
| DAIW app log | Stays only on your Mac, and you can delete it yourself. |
| Usage record (pseudonymous) | Kept for 3 years from collection, then deleted. The server gathers each day's record and moves it to AWS S3 (Seoul) the next day, then deletes it from the server. When you leave, the link between your account and the pseudonym is deleted, so the remaining record becomes anonymous and can no longer be tied to anyone. |
| Chat-window conversations (pseudonymous) | As for the usage record (3 years, S3 Seoul, anonymous once you leave). |
5. How we delete it
- Procedure: when a retention period ends or we receive a request to leave, we confirm it is you and delete the information without delay.
- Method: deletion from the server database. Copies in backup snapshots already taken are deleted together with those snapshots when their retention period (7 days) ends.
- Requests to leave: there is no delete-account button in the app or on the web yet. Please email midnight-mochi@naver.com with the email address you signed up with.
7. Your rights and how to use them
- You may at any time ask to see, correct or delete your personal information or to stop its processing, and you can withdraw consent by leaving.
- Send requests to midnight-mochi@naver.com. The Operator will confirm it is you, act without delay and tell you the outcome.
- You may also make requests through a legal representative or someone you have authorized.
- Signing out of the DAIW app revokes that access token.
- Turning off “사용 기록 공유” (Share usage) in the DAIW app menu stops the usage record from then on. To delete a record already kept, email the address above.
- Turning off “대화창 대화도 DAIW 모델 학습에 쓰기” (use chat-window conversations to train DAIW's model) in the DAIW app menu stops sending later conversations. To delete conversations already sent, email the address above.
8. Security measures
- Passwords are stored only as scrypt hashes and access tokens only as hashes; the originals are never stored.
- The usage record uses a random pseudonym instead of your account, and is uploaded to S3 with a dedicated write-only key. The S3 storage blocks public access and is encrypted.
- Communication with the Service is encrypted with HTTPS.
- Access tokens are valid for only 1 hour, refresh tokens are replaced on every use, and both are revoked when you sign out.
- The DAIW app runs only a predefined set of DAW commands.
- Audio processing and measuring happen on your Mac, keeping what is sent to the server to a minimum.
- The server is backed up (snapshotted) automatically every day.
10. Children under 14
DAIW does not accept sign-ups from children under 14. If you are under 14, please do not sign up. If we find that an account belongs to a child under 14, we delete it.
11. Privacy officer
DAIW is run by an individual, and the Operator serves as the privacy officer. Send questions, complaints and requests for redress about personal information to:
- Name
- 이창규
- midnight-mochi@naver.com
12. Where to get help
For advice on, or to report, a breach of your personal information, you can contact these Korean authorities:
- Personal Information Dispute Mediation Committee: 1833-6972, www.kopico.go.kr
- Personal Information Infringement Report Center (KISA): 118 (in Korea), privacy.kisa.or.kr
- Supreme Prosecutors' Office: 1301 (in Korea), www.spo.go.kr
- Korean National Police Agency: 182 (in Korea), ecrm.police.go.kr
13. Changes to this policy
This policy takes effect on October 29, 2026.
Revised October 30, 2026: adds the DAIW app's chat window (it sends to the AI company you pick, with your own API key, straight from your Mac) and more usage-record items (random values and message numbers that group the calls of one conversation, the connected app's name and version, the AI model used in the chat window, the 👍/👎 you give a chat answer). The added usage-record items are kept from November 6, 2026.
Revised November 1, 2026: if you allow it in the DAIW app's chat window, the conversation (what you wrote, the AI's answers, the tool calls and results) is kept under the pseudonym to develop DAIW's AI models. The chat window asks the first time it opens, and the app menu changes it any time. Applies from November 8, 2026.
If we change it, we will post the effective date and the changes on this page in advance.