Help center

No. Neither original works nor reader-created branches are used to train AI. The AI providers we use also commit in their API terms not to use this data for training.

• Free credits are given out by the platform when users sign up or take part in promotions. Paid credits are purchased through a top-up.
• Free and paid credits have the same purchasing power when using AI to create story branches.
• Stories created with free credits must be public. Stories created with paid credits are private by default, but you can choose to publish them publicly.

• When a reader spends credits to create a story branch, the original author receives a share.
• The author’s share is slightly lower when the reader uses free credits rather than paid credits.
• For nested branches, the author of the parent branch also receives a reward. For example, if author A writes a novel and reader B creates a branch, then reader C spends credits to create another branch from B’s branch, B receives a reward. The platform funds this reward; it does not reduce the original author’s share.

Earnings are settled at the end of each month and transferred in Japanese yen to the author’s Japanese bank account by the 5th of the following month. Payment is made when accumulated earnings reach ¥3,000; smaller balances carry over to the next month. The platform covers bank transfer fees. Your legal name and bank details are used only for payments and tax purposes and are not made public. If artificial activity or other abuse is detected, the platform reserves the right to suspend payments and recover revenue shares.

• Authors retain copyright in works they upload to PubWiki. They grant PubWiki a non-exclusive license to let users create story branches based on those works within the platform, and to store, display and recommend the works and branches, as well as use them to promote the platform. We will obtain the author’s consent before quoting their work in promotional material.
• By publishing a story branch under an author’s novel, a reader assigns copyright in that branch to the original author, including adaptation rights and rights to exploit derivative works, and agrees not to exercise moral rights. This assignment is to the original author even for nested branches. A private branch is subject to the same assignment when it is made public.
• Readers retain copyright in their private branches, but may not use them outside the platform or assert rights over the author’s subsequent work.
• Readers can continue reading their own branches on the platform even after the rights have been assigned to the author.

• Novel authors can remove any public branch under their work. They can also block users to prevent them from posting comments or creating story branches under their works.
• All branches must follow the platform’s content rules. The platform is responsible for moderation; authors are not responsible for content written by readers.
• When an author deletes a work, links into its branches are removed from that work, but public branches remain accessible through direct links. Authors may ask the platform to delete those branches.

This is not a problem. Readers cannot assert any rights over the author’s future work, and authors have no obligation to read reader-created branches.

Yes. PubWiki does not require exclusivity.