LEGAL

Privacy Policy

Version
2.0
Effective
September 3, 2026
Last reviewed
September 3, 2026
In short
  • We collect what the engagement needs and nothing we do not use.
  • We do not train models on your manuscript, and we do not sell data.
  • Some rights are handled by a person rather than a button, and this page says which.

The summary is a reading aid. The numbered terms below are the operative wording.

1. Overview

BookKraft Studio ("we", "us") runs a governed book-production service. This policy describes what we collect, why, who processes it, and how to exercise your rights. Privacy questions go to privacy@bookkraft.app.

2. Inquiry and discovery data

When you use the discovery form or write to us, your message reaches us as email — the form composes a message in your own mail client and sends nothing to a server on its own. We keep that correspondence to answer you and to scope an engagement.

In plain languageThe discovery form is not a database submission. It opens your email app, so you can see exactly what is sent.

3. Account data

Studio accounts hold a name, an email address, the invitation and role that grant access, and the authentication records needed to keep you signed in. Access is invite-only and scoped by role and project assignment.

4. Manuscripts and creative assets

The manuscripts, characters, canon records, artwork and production files created in an engagement are stored so the service can work, and are visible only to the people whose role and project assignment allow it. We do not train AI models on your work, and we do not make it public unless you generate a share link or approve publication.

In plain languageYour book is not training data and it is not a marketing asset.

5. Model-provider processing

Generation and analysis run through third-party model providers. Only the text and context needed for the specific request is sent, and only when a request is made. Each provider processes it under its own published terms and its own retention behaviour, which we do not control. We do not hold a negotiated no-retention or no-training agreement covering every provider, and we will not claim one we do not hold. The providers currently reachable are named in your engagement documentation on request.

In plain languageWe send the minimum, per request. We are not going to promise you a provider contract we have not signed.

6. Analytics

We do not run third-party analytics, advertising or cross-site tracking on the public site or in the Studio today. Standard server request logs exist for security and reliability. If we introduce optional analytics, this page and the Cookie Policy will say so and a preference control will exist before anything optional is set.

In plain languageThere is no analytics tag on this site right now.

7. Billing

There is no checkout, card entry or stored payment method on this site. Engagements are invoiced directly, and payment details are handled by the financial institutions involved, not by the platform.

8. Retention

Correspondence, account records and engagement work are retained while the engagement is active and afterwards for as long as we need them to meet legal, accounting and canon-continuity obligations. There is no automated deletion timer today, so we do not state a fixed window we cannot enforce; deletion happens on request as described below.

In plain languageWe would rather tell you deletion is a human process than quote you a window that no job actually runs.

9. Access, correction, export and deletion

You can ask for access to your data, correction of it, an export of it, or its deletion, by writing to privacy@bookkraft.app. These are handled by a person: there is no self-service privacy settings page, and export tooling inside the Studio is available to signed-in Studio users only. We acknowledge a request within two working days and tell you what we can act on and what we must retain.

In plain languageEmail us and a human does it. We are not going to point you at a settings screen that does not exist.

10. Children

The Studio is invite-only and offered to adults. We do not knowingly collect personal data from children, and we make no claim to certification or compliance under any specific children's privacy regime for this service. If you believe a child's data has reached us, write to us and we will remove it.

In plain languageNot a children's product, and not claiming a children's-privacy certification.

11. Security

Access is authenticated, authorization is enforced in the database per tenant, role and project assignment, and sensitive columns are withheld from client queries. We hold no third-party security certification and do not claim one.

12. Contact and changes

Privacy requests and questions go to privacy@bookkraft.app; other legal questions go to legal@bookkraft.app. The version, effective date and last-reviewed date of this policy appear at the top of the page and every change is recorded at the foot of it.

Questions about your data? Write to privacy@bookkraft.app.
Operator & contact

This service is operated by BookKraft Studio. Legal enquiries: legal@bookkraft.app. Privacy enquiries: privacy@bookkraft.app.

Change history
  1. v2.0 · September 3, 2026

    Removed four claims the implementation does not support: a provider retention and training prohibition, a named children's-privacy compliance regime, a fixed deletion window, and self-service data-rights controls. Each was replaced with what is actually implemented. Removed the payment-provider reference. Added inquiry data, model-provider processing, analytics, billing, retention and security sections, plus version, effective date, last-reviewed date, change history and separate legal and privacy contacts.

  2. v1.0 · July 1, 2026

    First published Privacy Policy.