Privacy Policy
We set out the following regarding the handling of personal information in the desktop app Kakiniwa (KAKINIWA) and the related website and online features (Remote, Cloud, accounts, contact, etc.; collectively, the “Service”).
1. Basic policy
The Service is designed on the principle that “project data stays with the user.” As a general rule, project data such as scripts, character settings, and assets is stored on the user’s own PC and is not sent to our servers (except for features the user has explicitly chosen, such as the Cloud edition and cloud backup). The information we collect is limited to the minimum necessary for account management, providing features, and preventing abuse.
2. Information we collect and purposes of use
| Information | When it is collected | Purpose of use |
|---|---|---|
| Email address | Account registration and login (email / 6-digit code) | Identity verification, login, and important notices |
| Google account identifier, email address, and display name | When you log in with Google | Identity verification and login (we do not obtain your Google password) |
| IP address and approximate location at login (country, region and city estimated from the IP address, using estimates provided by Cloudflare, Inc. Because it is an estimate, it may differ from your actual location, for example when you use a VPN) | When you log in to your account | Preventing unauthorized use of your account and notifying you. Specifically, we use it only to show it to you under “Logged-in devices” in Settings; to notify your registered email address of a login from a new device, a login from a different country or region than last time, or repeated wrong confirmation codes; and to investigate unauthorized access. Our audit logs keep the IP address only in a form that cannot be restored (a salted hash) |
| Name, reply-to email, and the text of your inquiry | When you submit the contact form or the support chat (name and email are optional). We do not store your IP address itself (to detect abuse and request floods, we keep only an irreversible hash of it for a limited period) | Responding to your inquiry (we may use AI to organize the content and draft replies. See Section 4) |
| Survey responses (features you use, ratings, production environment, difficulties, thoughts on creative work and AI, free-text answers) | When you choose to respond on the survey page (/survey/). We do not collect your name or email address, and we do not store your IP address linked to your response (it is used only to limit the number of submissions in order to prevent repeated sending). We ask that you not write personally identifiable information in the free-text answers | Compiling results to help improve Kakiniwa |
| Project data (scripts, settings, assets, etc.) | When using features that involve server storage, such as the Cloud edition and cloud backup | Saving, syncing, and collaborative editing projects |
| Device information and connection information of the connecting device, and the name of each project you make available through Remote and the name of your device | When using the Remote feature | Mediating connections between devices (the contents of your projects, meaning scripts and assets, are exchanged directly between devices, encrypted, and are not stored on our servers. Only the name of a published project and the name of your device are stored on the server, so that we can show the list of places to connect to). Because devices connect to each other directly in Remote, your IP address is passed to the device you connect with |
| Payment information | When purchasing a paid plan | Payment processing (handled by Stripe as described below; we do not hold card numbers or similar information) |
| Anonymous launch statistics (random ID, app version, OS type, and CPU type (64-bit / Arm); device performance: number of CPU cores, CPU model, amount of memory, OS version, GPU model and manufacturer; usage: number of launches, usage time, number of speaker switches, number of crashes; and, if you are trying a troubleshooting launch option, which kind; your country (only the country name estimated from the connection; IP addresses are not stored); and the display language and OS language (without region, except that Simplified/Traditional Chinese and Brazilian/European Portuguese are distinguished)) | When the desktop edition starts. It is not used for the purpose of identifying individuals (your name, contact details, the content of your projects, and storage locations are not sent). Model names are recorded after removing clock speeds and device identifiers | Identifying bugs and making improvements: investigating the causes of sluggish performance, and deciding what level of performance to build for and when to end support for older OS versions, and which languages to translate into. You can turn this off in the settings |
| Fetching notices: the app version and display language | When the desktop edition starts, and every 6 hours after that (it asks our server, api.kakiniwa.jp, at /api/announcements). This request is still made even if you have turned off anonymous launch statistics in the settings (it is needed to receive important notices such as requests to update. It is not made by the demo or the browser edition) | Showing requests to update and other important notices in the app. The version and language are used only to choose which notices to return, and are not stored in a way that is linked to you (like any other access, the request itself appears in access logs) |
| Bug reports (error diagnostics): in addition to the app version, OS version, error details, and the preceding operations, information about your environment used to isolate the cause. Specifically: the names of third-party software hooking into the app (screen overlays, audio and mouse utilities, etc., including the names of their program files (DLLs)), whether assistive technology such as a screen reader is connected, the name of your antivirus product, the name of your Japanese input method (IME), whether you are using the app over Remote Desktop, the name of any sync software such as OneDrive, the GPU driver version, the type of disk, the power state (battery or power-saving mode), the amount of memory used by each of the app’s processes, an excerpt of the Windows event log entries recording the app crashing, the tail end of the app’s internal log, the screen resolution, scaling, and display language, and the size of your project (such as the number of lines and speakers), and the User-Agent (the name the sending environment gives itself) of the app that sent the report | Sent only when you press “Send anonymously” on the error screen or settings screen, or when you turn on “Send automatically when it crashes” in the settings (not sent automatically by default). Your name, email address, and manuscript content are not sent. We do not store your IP address itself (to detect abuse and request floods, we keep only an irreversible hash of it for a limited period). The location of your storage folder is masked before sending (only the file name may remain; user names contained in folder names are also masked) | Isolating the causes of bugs (which software combinations lead to crashes, and what environments cause sluggishness). When we investigate together with an inquiry, we may use AI to organize the content (see Section 4). You can turn this off in the settings |
| Memory dump at the time of a crash (a record of the app’s internal state) | Sent together with the error report’s reference number only if you turn on “Also send the dump” in the settings. It may contain part of the text you were editing, and information about your login (such as what keeps you logged in) (off by default) | Identifying the cause of bugs. It is deleted automatically after 14 days (it may be deleted sooner, once the cause has been identified) |
| Posts, user IDs, and thread names on the official Discord server | When you start a thread in the official server’s “Questions & Help,” “Feedback & Requests,” or “Bug Reports” forums, or post in such a thread (imported automatically as an inquiry). In Discord forum threads, we collect posts by other participants in the thread as well as by the person who started it | Responding to inquiries and investigating bugs (we may use AI to organize the content and draft replies. See Section 4). Posts on Discord are public to begin with. Even if you delete a post on Discord, it remains in our records of the case for our retention period. If you would like it deleted, please contact us |
| Images and log files (.txt / .log) attached to inquiries | When attached in the intake chat or on Discord | Investigating bugs. We keep the original files only for a limited period; after that, we keep only a text description of the image content and an excerpt of the logs (in both cases, email addresses and the like are masked automatically) |
| Email address of the person invited to co-edit | When a project’s owner invites someone to co-edit by email | Sending the invitation and matching it to the person invited. Deleted after the invitation expires, is withdrawn, or is accepted |
| Access logs and IP addresses | When accessing the Service | Preventing unauthorized access, spam, and excessive automated access (rate limiting) |
To help others facing the same problem, we may list a reported bug or similar issue as a known issue on the Status and known issues page. We publish only a summary written by us and the status of our response; we never publish the text of your inquiry, your name, or your contact details.
3. Cookies and local storage
To keep you logged in, we store session information in your browser’s local storage. This is used so that you can remain logged in, and we do not perform tracking for advertising purposes.
We also store, only on your device, backup copies of unsaved writing (kept until it can be saved) and records used to diagnose problems (such as your recent actions). These do not leave your device automatically (when you send a problem report, the diagnostic records are included in the report). For remote and cloud projects, these backup copies are removed from your device when you log out or go back to the library, and any that remain are deleted after 30 days.
On the introduction site (kakiniwa.jp), we use Google Analytics to find out which pages are viewed and how often. It uses cookies, and a record of your visit is sent to Google (IP addresses are shortened on Google's side and are not stored in their original form). It is not used for advertising. Even if you reject cookies in your browser settings, you can still use the site without any problem. The demo and the app itself do not perform this tracking at all.
4. Provision to third parties and outsourcing of processing
Except where required by law, we do not sell or provide the personal information we obtain to third parties. However, to the extent necessary to provide the Service, we outsource processing to the following external services.
- Cloudflare, Inc. — Delivery and storage for the website and API, protection against unauthorized access, and counting page views of the introduction site and the demo (Cloudflare’s measurement feature; the demo sends it over a path within the same site. No cookies are used and no personally identifiable information is collected)
- GitHub, Inc. — Checking for and distributing updates (when it starts, the desktop app asks GitHub whether a new version is available and downloads update files from GitHub. At that time, connection information such as your IP address is sent to GitHub)
- Amazon Web Services, Inc. — Storage of backups in preparation for failures and disasters (kept with a separate provider)
- Resend — Sending login emails, notice emails (project deletion, storage usage, co-editing invitations, logins from new devices, etc.; these may include project names), and notification emails for inquiries
- Google LLC — Authentication when you choose to sign in with Google, and counting of how the introduction site is viewed (Google Analytics; this includes the contact and survey pages. Google Analytics collects viewing information through Google’s own mechanism. The survey answers themselves are not sent to Google)
- Google LLC (YouTube) — Delivery of the introduction videos embedded in the introduction site (we use youtube-nocookie.com, which does not set cookies. When you play a video, communication information such as your IP address is sent to YouTube. Nothing is sent if you do not play it)
- Stripe, Inc. / Sold Through Link, LLC — Payment, billing, and refunds for paid plans (Stripe's Managed Payments. Sold Through Link, LLC is the seller of record. We remain responsible for the content and provision of the service)
- Discord Inc. — Operation of the official community server and handling of inquiries (posts, display names, and similar information of people who join the server reside on Discord's service)
- SAKURA internet Inc. — AI processing for handling inquiries (organizing the content, drafting replies, reading the content of attached images, and searching guidance documents). Processing takes place on servers in Japan. It is also used as a backup when Anthropic cannot be reached. Personal information such as email addresses is automatically masked before being passed to the AI
- Anthropic, PBC — AI processing for handling inquiries (organizing the content and drafting replies; normally handled here), and assistance with development and support work (AI-assisted development). Processing may take place on servers overseas, such as in the United States. We may also pass on the content of bug reports (error diagnostics) so that an inquiry can be investigated. Personal information such as email addresses is automatically masked before being passed to the AI. The attached images themselves are not passed on (they are read by SAKURA internet); a text description of the image content is passed instead
- OpenAI, LLC — Assistance with development and support work (AI-assisted development). Part of the content of an inquiry may be processed when the developer handles it. In this case as well, personal information such as email addresses is masked before handling
These providers handle information in accordance with their respective privacy policies. Processing may take place on servers overseas.
AI that assists development may read the content of inquiries (conversations, environment records, and descriptions of attachments) in order to investigate bugs and draft replies. The form the AI reads does not include contact details such as the reply-to email address (these are removed automatically). This development-assisting AI never replies to users directly. A person always reviews and decides whether anything is sent.
In the intake chat, however, depending on what you write, the intake AI may automatically show you confirmation questions and guidance on how to use the app or what it can do. These appear without waiting for a person to check them, and they are not an official reply. The final decisions and replies are made by a person.
5. Retention period and deletion
The periods for which we keep the main data are as follows.
| Item | Retention period |
|---|---|
| Cloud projects (while in use) | While the account is active |
| Cloud projects (after cancellation) | Up to 6 months (determined according to usage. We notify you 1 month before deletion) |
| Projects moved to the trash (Cloud edition) | 7 days after being moved to the trash (after that they are deleted permanently and automatically) |
| Files moved to the trash (inside Cloud projects) | While in the trash. Even after the trash is emptied, they can be restored for 3 days |
| Projects and files moved to the trash (Desktop edition) | While in the trash. When the trash is emptied, they are permanently deleted at that point (this is data on your own PC, so we do not hold it) |
| Version history (autosaves) | Up to 1 month (more recent ones are kept in finer detail) |
| Version history (saved manually) | Until you delete it |
| Accounts that have been closed | After a freeze, the account is permanently deleted together with its projects (until then, this can be undone). Deletion happens 30 days after you close the account, or, if a paid period remains, 30 days after that period ends |
| Survey responses | 1 year from the response |
| Anonymous launch statistics | 180 days from the last launch (daily totals that contain no random ID are kept for 2 years) |
| Cloud usage record (the day you last used it) | 2 years. Deleted when you delete your account |
| Payment records (held by Stripe) | For as long as the law requires. Even if you delete your account, the payment records on Stripe’s side (email address, name, etc.) are not deleted |
| Names of projects published through Remote, and device names | 30 days after the last connection (sooner if you stop publishing) |
| Login links and verification codes | 15 minutes |
| Login state (session) | 30 days (expires if there is no activity) |
| Records of devices used to log in | 1 year from last use |
| IP address and approximate location for each logged-in device | Until that device’s login ends (when you log out, or automatically 30 days after last use). Deleted afterwards |
| Country, region and time of your most recent login (one record, used to tell whether a login comes from a different place than last time) | Overwritten at your next login. Deleted when you delete your account |
| Operation records (audit logs) and bug reports | 90 days |
| Memory dumps from crashes | 14 days (if the linked bug report is deleted first, they are deleted at that time) |
| Inquiry cases (conversations and AI-organized results) | For as long as needed to handle them. Resolved cases are also kept in order to recognize recurrences of the same bug (they are deleted once no longer needed, and we delete the whole case on request) |
| Original images and log files attached to inquiries | 90 days after the case is closed and the last exchange took place (this includes Discord threads that stopped without being marked as solved; after that, we keep only a text description of the image content and an excerpt of the logs) |
| Reply-to email addresses for inquiries and internal notes (such as the sender) | 180 days after the case is closed and the last exchange took place (consultations that are still open are also deleted if nothing happens for 180 days) |
| Intake chat conversations marked “solved” and the original attachments (cases solved before being accepted as an inquiry) | 90 days from the start of the intake (after that, the whole conversation is deleted) |
| Discord user ID (of the person who started the thread) | 180 days after the case is closed and the last exchange took place (this includes Discord threads that stopped without being marked as solved) |
| Backups in preparation for failures and disasters | 30 to 180 days (as described below, data remains temporarily right after deletion) |
- Account information and project data (the portion stored on the server) are retained while the account is active.
- Even after a paid Cloud plan ends, project data is retained for up to 6 months (the retention period accumulates according to usage, with a maximum of 6 months, and time that has elapsed since cancellation is deducted). After that it is deleted, but we notify the registered email address 1 month before deletion (the account itself is not deleted).
- Email login links and codes expire in a short time (about 15 minutes).
- If you delete your account, the data on the server is deleted after a grace period (we will provide a way to export your project data before deletion).
- Backups in preparation for failures and disasters are kept for a fixed period (30 to 180 days) and are then erased in sequence after that period has passed. For this reason, data may temporarily remain in backups immediately after deletion. We do not rewrite past backups themselves (doing so would make it impossible to detect tampering and impossible to restore in a disaster). Once the period above has passed, each generation is erased.
- The content of inquiries is retained for as long as necessary for handling them and improving quality.
- The contents of the contact form and emails sent to us also reach the operator’s mailbox. The automatic deletion periods in the table above do not apply to copies in the mailbox. We delete them in sequence once they are no longer needed.
6. About project data
Scripts, settings, and assets that we hold in the Cloud edition are stored on the server in order to provide features such as syncing and collaborative editing. We have not provided any feature that lets the operator view the content of projects (projects cannot be opened from the admin screen).
We may access the content only in the following cases, and in every case we limit this to the minimum necessary.
- At the customer's own request (such as restoring data or investigating a bug the customer reported)
- When necessary to investigate a failure
- When requested under applicable laws and regulations
To be precise, we add the following. Project data is sent over encrypted communications, and the storage provider also encrypts it at the storage location, but our operators are in a position to access the stored data. We have not adopted, at this time, a form that "the operator can never read" (encryption where only the customer holds the key), because data could not be recovered if it were lost. For projects you do not want to entrust to anyone, please use the Desktop edition (stored only on your own machine).
7. Requests for disclosure, correction, deletion, etc.
If you wish to request disclosure, correction, deletion, or suspension of use of your own personal information, please contact us through the contact form. After confirming your identity, we will respond in accordance with applicable laws and regulations. You can take your projects out at any time with the export feature. If you contact us, we will hand over your account information, comments, login records and the like together.
We will respond to deletion requests, but erasure is carried out in line with the periods in the table above. It is not possible to bring this forward (immediate complete erasure). When you close your account, it is permanently deleted together with its projects after 30 days (or, if a paid period remains, 30 days after that period ends), and it is erased from backups within 180 days at most.
We apologize for the inconvenience, but this is because we have designed backups so that they cannot be rewritten afterward. If they could be rewritten, then in the event of unauthorized access the backups would be destroyed along with everything else, and we would be unable to protect the data of other customers. Making the account unusable immediately (suspending use) can be done on the spot through the account closure procedure.
8. Security management
To prevent leakage, loss, or damage of the information we obtain, we take reasonable security measures such as encryption of communications (HTTPS / device-to-device encryption), access restrictions, and rate limiting. Passwords are not stored (authentication is by email or external account).
9. Use by minors
If a minor uses paid features, please do so with the consent of a parent or guardian.
10. Changes to this Policy
This Policy may be changed as necessary. If we make an important change, we will announce it on this page or on the Service. The revised content takes effect when it is posted on this page.
11. Contact
For inquiries about this Policy and the handling of personal information, please use Contact (intake chat, community, or email form). For requests for disclosure, correction, or deletion, please include a reply-to email address so that we can verify your identity.