Privacy Policy

日本語 | English

About the Revision of November 3, 2026

We revised this Policy on November 3, 2026, and it took effect on the same day. Users do not need to take any action. If you do not agree to how we handle information after the revision, you can stop using the Service and leave it from the account deletion page.

The points we clarified or changed in this revision are as follows:

• We rewrote the information we handle and the utilization purposes to reflect how we actually handle them
• We removed the delivery of advertisements, analysis for the purpose of provision to third parties, and use for marketing from the utilization purposes
• We removed the provisions on provision to third parties by the opt-out method and on obtaining information through integration with external services
• We stated that the Operator does not use posted content to train AI models
• We explained the scope of information made public on the Service, such as pages in public topics
• We set out the information provided through the public API and the remote MCP server to OAuth apps and MCP clients you have authorized, and how to revoke the authorization
• We specified the external services we use and the countries where information is stored, and the information your browser transmits to outside parties
• We set out how we handle logs and our security control action
• We set out how to make a demand for disclosure, etc., how we verify your identity, and the fees
• We rewrote the information we delete and the information that remains for a certain period when you leave the Service, to reflect how we actually handle it
• We set out that we provide our address upon request
• We changed how we notify you when we change this Policy

The previous version is available in Japanese only: プライバシーポリシー (2025年5月17日版).

The operator (the "Operator") of "Wikino" (the "Service"), a wiki where you create pages in spaces and connect them with links, sets out this Privacy Policy (this "Policy") on the personal information handled by the Service as follows.

This English version is a translation of the Japanese original. If there is any discrepancy in interpretation between the Japanese version and the English version, the Japanese version prevails. This Policy is governed by the laws of Japan, including the Act on the Protection of Personal Information.

1. Information We Handle

The Operator handles the following information about users of the Service:

• Account information: email address, username, password (we store only its hashed value), and the secret key and recovery codes for two-factor authentication
• Profile: name and bio
• Settings: display language and time zone
• Posted content: pages, drafts, attachments, and suggestions and their comments
  • Each time a page or draft is saved or published, we keep its content at that time as a revision
  • We record the members who edited a page and the date and time of the last edit
• Space and member information: the names and settings of spaces and topics, and members' roles and the dates and times they joined
• API usage records: the names, scopes, expiration dates, and last-used dates and times of personal access tokens, OAuth apps, MCP clients, and authorizations
  • We store tokens and client secrets only as hashed values
• Access information: IP address, browser information (User-Agent and so on), URL of pages viewed, date and time of access, and cookies
  • For each device you are signed in on, we record the IP address and browser information from when you signed in
• Inquiry information: the email address and content of inquiries

The Service uses cookies to keep you signed in, to prevent unauthorized submissions, to remember display settings (such as the time zone), and to distinguish devices when we release features gradually. All cookies are issued by the Service (wikino.app).

2. Utilization Purposes

The Operator utilizes the information it handles for the following purposes:

3. Use for Training AI Models

The Operator does not use content posted by users to train AI models. Nor do we provide it to outside businesses for the purpose of training. When we change this handling, we will change this Policy.

4. Information Made Public

Content posted on the Service and part of users' information are made public within the following scope:

• Pages in public topics (titles, bodies, and attachments) can be viewed by anyone on the internet, and may also appear in search engine results
• Pages in private topics can be read only by members of the space and by tokens and apps that members have authorized
• Drafts can be read only by the person who wrote them and by tokens and apps that person has authorized
• Usernames, names, bios, and the spaces a user has joined can be viewed by anyone on the user's profile page

The scope of publication is determined for each topic. For details, see 公開トピック and 非公開トピック (in Japanese).

5. Provision through the Public API and to Authorized Apps

The Service allows programs and AI apps to read and write topics and pages in spaces through the public API and the remote MCP server. The public API is called with a personal access token issued by a member of the space, or with a token of an OAuth app that a member has authorized. The remote MCP server is called by an MCP client (an AI app that connects to the remote MCP server, such as Claude or ChatGPT) that a member has authorized. Every token can handle only the scopes permitted within the space for which it was issued.

When you authorize an OAuth app or an MCP client, the app can obtain the following information about the authorized space and perform operations such as creating pages, within the scopes you permitted on the consent screen. This is provision based on the principal's consent. When you authorize an MCP client, you choose one space to connect on the consent screen.

• Topics, pages, and attachments of the space
• The drafts of the member who authorized the app
• The usernames and names of the members of the space (we do not provide email addresses)

You can revoke an authorization at any time from "Authorized apps" in the space settings. Once revoked, the app can no longer call the public API or the remote MCP server of the Service. Deleting the registration on the MCP client side alone does not revoke the authorization. The provider of the app is responsible for how the app handles the information it obtained while authorized, and the Operator cannot delete that information.

Information that an MCP client obtains is passed to the AI service of that MCP client. Likewise, if you pass information obtained with a personal access token or the official CLI to another service, such as an AI agent, the handling of that information is governed by the rules of the service you passed it to.

For how to use them, see 公開API, OAuthアプリ, and リモートMCPサーバー (in Japanese). For the conditions of use, see the API Terms of Use.

6. Provision to a Third Party

The Operator does not provide personal data to a third party without obtaining the principal's consent in advance, except in the following cases:

• Cases based on laws and regulations
• Cases in which there is a need to protect a human life, body, or fortune, and when it is difficult to obtain the principal's consent
• Cases in which there is a need to cooperate with a central government organization or the like in performing affairs prescribed by laws and regulations, and when there is a possibility that obtaining the principal's consent would interfere with the performance of those affairs
• Other cases permitted under the Act on the Protection of Personal Information
• Cases in which we entrust the handling of personal data within the scope necessary to achieve the utilization purposes ("7. External Services We Use")
• Cases in which personal data is provided accompanying business succession caused by a merger or other reason

Provision when the principal authorizes an OAuth app or an MCP client is as described in "5. Provision through the Public API and to Authorized Apps".

7. External Services We Use

The Operator uses the following external services to operate the Service, and entrusts the handling of personal data to them within the necessary scope. For services whose storage country cannot be identified, we describe the reason and reference information.

• XServer VPS (server)
  • Purpose: servers and databases of the Service
  • Information handled: all information handled by the Service
  • Country where the provider is located: Japan
  • Country where the information is stored: Japan
• Cloudflare (traffic relay, storage, and bot protection)
  • Purpose: relaying traffic, storing attachments, export files, and database backups, and bot protection
  • Information handled: traffic content, IP addresses, attachments, export files (the content of pages in spaces), and database backups
  • Country where the provider is located: United States
  • Country where the information is stored: Cannot be identified
    • This is because traffic is relayed at Cloudflare's locations around the world
    • This is because Cloudflare discloses the storage location of files only down to the region (Asia-Pacific)
• Sentry (error monitoring)
  • Purpose: detecting and investigating errors
  • Information handled: user ID, username, URL of the page where the error occurred, and browser information (User-Agent and so on)
    • We do not send IP addresses or cookies
  • Country where the provider is located: United States
  • Country where the information is stored: United States
• Resend (email delivery)
  • Purpose: sending emails for verification codes, password resets, and export results
  • Information handled: email addresses, and email subjects and bodies
  • Country where the provider is located: United States
  • Country where the information is stored: Japan
• Google Workspace (receiving email)
  • Purpose: receiving and storing inquiry emails
  • Information handled: the email address and content of inquiries
  • Country where the provider is located: United States
  • Country where the information is stored: Cannot be identified
    • This is because Google does not disclose the country where it stores information
    • For details, see Google's Privacy Policy

We will provide, upon request, information on the action taken by providers in foreign countries for the protection of personal information. Please contact us at the email address in "12. Contact".

8. External Transmission

When you open a page of the Service, your browser transmits information to the following providers:

• Cloudflare Turnstile (Cloudflare, Inc.)
  • Purpose: preventing unauthorized operations by bots
  • Information transmitted: IP address, browser information (User-Agent and so on), and information on browser behavior used to distinguish bots
  • Pages that transmit the information: the sign-in, sign-up, and password reset pages
• jsDelivr (Volentio JSD Limited)
  • Purpose: loading a program that displays a screen component (menus)
  • Information transmitted: IP address, browser information (User-Agent and so on), and the domain of the site being viewed
  • Pages that transmit the information: some pages of the Service, such as the profile, search, settings, and space settings pages
• Cloudflare R2 (Cloudflare, Inc.)
  • Purpose: storing and retrieving files
  • Information transmitted: IP address, browser information (User-Agent and so on), and the files you upload
  • Pages that transmit the information: pages where you upload or download attachments, or download export files

9. Handling of Logs

For each access, the Service records the IP address, browser information (User-Agent and so on), URL of the page viewed, and the date and time in logs. Some records, such as password reset requests and failed email address verifications, also include IP addresses and email addresses. Logs are used to investigate unauthorized access, access concentrated in a short period, and failures. Logs are stored for one year and then deleted.

To prevent the same operation from being repeated in a short period, we store IP addresses and email addresses as records for attempt limits. These records are deleted after one day.

10. Security Control Action

The Operator takes the following action to prevent leakage, etc. of personal data:

• Organizational action
  • The Operator also serves as the person responsible for the handling of personal information
  • There are no screens for the Operator that display the content of users' spaces or users' personal information
  • We publish a vulnerability reporting contact
• Human action
  • Only the Operator can operate the production environment (servers, databases, storage, and the admin screens of external services)
• Physical action
  • We do not own our own facilities and use providers' servers and cloud services
  • The Operator's work devices have disk encryption and screen lock enabled
• Technical action
  • Communications are encrypted with HTTPS, and connections over HTTP are redirected to HTTPS
    • Communications from Cloudflare to our servers are also encrypted
  • Passwords are stored only as hashed values
    • Personal access tokens, OAuth tokens and client secrets, and tokens used to reset passwords are also stored as hashed values
  • Cookies that keep you signed in are sent only over HTTPS and cannot be read by JavaScript
  • API tokens can be used only for the space and member for which they were issued, and have scopes and expiration dates
  • Viewing and editing pages is restricted according to the visibility of topics and the roles of members
  • Sign-in, sign-up, and password reset have bot protection
  • Email address verification, password reset requests, use of the public API, and so on have attempt limits
  • Connections to databases are limited to those from within the Operator's VPN
  • Database backups are taken daily and stored for 30 days
  • Error monitoring masks values such as passwords, tokens, and email addresses
  • We receive vulnerability information on the software we use and update it
  • Secrets such as passwords are not included in source code and are managed in a password management service
  • Production data is not used for development; we use data created for development
• Understanding the external environment
  • We use services of providers in foreign countries. The countries where the providers are located and where the information is stored are as described in "7. External Services We Use"
  • We take the above action after understanding the personal information protection systems of the United States through the Personal Information Protection Commission's survey (in Japanese)

11. Demands for Disclosure, etc.

The principal or their agent may demand the following regarding the retained personal data held by the Operator:

• Notification of the utilization purpose
• Disclosure (including disclosure of the records of provision to a third party)
• Correction, addition, or deletion when the content is not factual
• Utilization cease or deletion
• Cease of the provision to a third party

Please send your demand to the email address in "12. Contact". There is no prescribed form. Please state the type of demand and the information it concerns.

• Identity verification: the Operator sends a confirmation email to the registered email address and verifies your identity by your reply
  • For agents, we verify the relationship with the principal and the fact of the delegation
  • We do not ask for images of identification documents or the like
• Fees: free of charge
• Method of response: in principle, we respond by email
  • Information to be disclosed is provided as electronic files

If we are not obligated by laws and regulations to respond to the demand, or if we cannot verify identity, we will notify you of that and the reason.

You can also check and change your account information and profile on the settings screen, and take out the pages of a space by exporting them.

12. Contact

Please send opinions, questions, complaints, and demands regarding this Policy and the handling of personal information to the following contact:

• Operator: Koji Shimba
• Email address: [email protected]

The Operator's address will be provided without delay upon request.

13. Handling When You Leave the Service

Users can leave the Service from the account deletion page. Before leaving, you need to delete all the spaces you have joined.

When you delete a space, we delete its pages, drafts, attachments, suggestions and their comments, topics, members, personal access tokens, and OAuth apps and authorizations. When you leave, we delete your account information, profile, settings, and the records of devices you are signed in on. Deletion is carried out in sequence after the procedure, so it may take some time to complete.

The following information remains for a certain period after you leave and is deleted after the period ends:

• Export files: 7 days from creation
• Records of email delivery processing (including email addresses): up to 7 days
• Records of email address verification (email addresses and verification codes): 1 day
• Records for attempt limits (IP addresses and email addresses): 1 day
• Database backups: 30 days
• Logs: 1 year
• Error monitoring (Sentry) records: 30 days
• Email delivery (Resend) records: 30 days

14. Changes to This Policy

The Operator may change this Policy in response to amendments to laws and regulations or changes to the Service. When we change it, we will announce the changes and the effective date in the announcements on the Service, and also on the Service's official accounts listed on コミュニティ (in Japanese). When a change requires the principal's consent under laws and regulations, we will obtain consent.

Supplementary Provisions

• Established: May 17, 2025
• Revised: November 3, 2026
• Effective: November 3, 2026

The revision history is as follows (available in Japanese only):

• プライバシーポリシー (2025年5月17日版)