1. Scope
This policy applies to buildebook.com, its author workspace, and the BuildEbook beta. It does not cover a publishing marketplace or third-party site you choose to use after exporting a book.
2. Data we collect
Account data
We collect the name, email address, password hash, account status, credit balance, and basic account timestamps needed to create and protect an account. We do not store the password itself.
Project data
We store book briefs, titles, outlines, chapter text, cover choices, author names, and export-related settings so the workspace can save and produce the project.
Technical and safety data
We process limited request information such as cryptographically transformed IP and user-agent data, rate-limit counters, session records, generation status, and error identifiers. Administrator actions are recorded in an audit log.
3. How we use data
We use data to operate accounts, save projects, generate requested drafts, prepare exports, enforce credits and rate limits, prevent abuse, diagnose failures, support users, and maintain service security. We do not sell personal information or use private manuscripts for advertising.
4. AI processing
When paid AI generation is enabled and you request an outline or chapter, the relevant brief, book context, outline, and chapter instructions are sent to the configured AI provider to fulfill that request. Demo-mode drafts are generated locally and are not sent to that provider.
BuildEbook requests that API responses are not stored where the provider supports that setting. Provider handling is also governed by its applicable business/API terms. AI generation may produce errors or unexpected material; review every draft before using or publishing it.
6. Retention
Account and project data is retained while the account is active and for a reasonable operational period afterward. Security logs, audit records, generation events, and backups may be retained longer where needed for safety, integrity, dispute handling, or legal obligations. Beta retention periods may evolve as deletion tooling is completed.
7. Security
BuildEbook uses hashed passwords and session tokens, HTTPS, isolated database credentials, access controls, request limits, and audited administrator mutations. No internet service can guarantee absolute security, so authors should avoid placing unnecessary secrets, regulated personal data, or confidential third-party material in prompts or manuscripts.
8. Your choices
You can edit or remove manuscript text from an active project and sign out to revoke the current browser session. To request access, correction, export, or deletion of account data, email privacy@buildebook.com. Identity verification may be required before a request is completed.
9. Children
BuildEbook is not directed to children under 13, and we do not knowingly collect their personal information. A parent or guardian who believes a child submitted data should contact us.
10. Changes
We may update this policy as the beta and its providers change. Material changes will be reflected by a new effective date and, where appropriate, an in-product notice.
11. Contact
Questions about this policy or privacy requests can be sent to privacy@buildebook.com.