This policy describes how the TextToEbook.com application handles information in its current browser-based ebook workflow. It distinguishes the manuscript you edit on your device from information sent when you load the website or choose to contact us. It is intended to help you make informed choices about using the editor and keeping your own copies of your work.
The ebook maker does not require an account. Its manuscript editing, cover-image processing, draft persistence, and PDF generation are designed to happen in your browser. Questions about this policy can be sent to contact@texttoebook.com.
Manuscripts and book settings
The book data you enter includes the title, subtitle, author name, publisher, description, chapter text, optional sections, typography, colors, and page settings. These values form the editable draft. The application uses them to display the editor and create the document you request.
The ebook workflow does not send that manuscript to an application PDF server. PDF generation uses local browser code and font assets served with the site. Selecting a template or changing a color changes local book state; it is not a request to publish the manuscript on a public page.
This local design does not protect against every risk on your device. Other people with access to the same browser profile, installed software with relevant permissions, or a compromised operating environment may be able to access information stored there. Use a device and browser profile appropriate to the sensitivity of your writing.
Automatic draft storage
The application saves the current draft in IndexedDB, a browser storage facility associated with the site. This allows the draft to be restored when you return using the same browser profile and site origin. Storage is local to that environment and is not an account-based cloud synchronization service.
Browser storage may be cleared through browser settings, removed by privacy tools, restricted in private browsing, or affected by storage limits. The saved-state indicator reports whether the app’s local save operation succeeded. It cannot guarantee that the browser will retain the data indefinitely.
Save draft downloads an editable JSON file. Keep that backup somewhere you control. Importing a saved draft brings its information back into the editor, and the application downloads a backup of the current book before replacing it. You are responsible for protecting downloaded files and any copies you create elsewhere.
Cover images and generated files
An image selected for the cover is read locally by the browser and included in the book draft. The current editor accepts supported PNG and JPEG files within its stated size limit. The image is not uploaded to a separate image-hosting account by the ebook workflow.
A cover image stored in the draft is also present in a downloaded draft backup. The generated PDF contains the image and the book content needed to display the finished document. Treat both files as copies of your manuscript when deciding where to store or share them.
When you download a PDF, your browser and operating system determine its destination and may keep a download history. If you later email, upload, or publish that file, the destination’s own handling applies. TextToEbook does not control the privacy settings of services you use after export.
Requests made when you visit the site
Loading the application requires network requests for pages, scripts, styles, and locally hosted font files. The hosting infrastructure receives ordinary connection information needed to deliver those resources, such as the requested path and network-level request details. That traffic is separate from the manuscript stored in the editor.
The application does not intentionally include manuscript text in page URLs, analytics events, or server error messages. Avoid manually placing private text in a URL or sending it through a contact message if you do not want that information to leave your device.
The current source does not add advertising pixels or third-party behavioral analytics. Hosting services and browsers may maintain operational records under their own practices. This policy does not claim that infrastructure logs never exist or promise a retention period that the application itself does not control.
Contact messages
The Contact page asks for a name, email address, subject, and message. If email delivery is configured, submitting the form sends those fields to the application’s contact endpoint and the configured mail provider so the message can be delivered and answered.
If no mail provider is configured, the form reports that delivery is unavailable. It does not claim that the message was sent. You can instead choose to email contact@texttoebook.com using your own email application. That action involves the email services used by you and the recipient.
Do not include passwords, payment information, identification documents, or a full confidential manuscript in a support request. A concise description and a small non-sensitive example are usually more useful for investigating an editor problem. Contact correspondence may be retained in the recipient’s mailbox for responding to and understanding the request.
Cookies and browser storage
The ebook application uses browser storage for its local draft rather than an account login cookie. A hosting platform may separately use access or security mechanisms to deliver a private preview or protect the site. Those mechanisms are distinct from the manuscript persistence implemented by the editor.
Browser settings allow you to inspect or remove site data. Removing that data can erase the local draft. Download a backup before clearing it if you want to continue editing later. Closing a tab alone does not necessarily remove the draft because persistence is intended to support returning to the project.
When you use a shared computer, do not assume that closing the editor makes its local information inaccessible to the next person using the same browser profile. Export the files you need, then remove the relevant site data through the browser’s controls if that is appropriate for your situation.
Control over your copies
You can edit the book information, remove chapters, replace cover images, or start a new book through the editor. Destructive chapter and new-book actions include a confirmation step. The app’s backup behavior is intended to reduce accidental loss, but you should still keep an independent copy of important work.
To remove the locally saved draft completely, use the editor’s clear-local-draft action or your browser’s site-data controls. Downloaded PDFs and JSON backups are separate files and are not removed when browser storage is cleared. Delete or manage those files through your device’s normal file controls.
We cannot retrieve a browser-only manuscript from a central manuscript database because this version does not maintain such a database. A support request for a lost local draft may therefore depend on a backup you already saved or the capabilities of your own device and browser.
Changes and questions
This policy should be updated if the application later adds account synchronization, remote document processing, analytics, or other data-handling features. Such changes would alter the current local workflow and should be described in the product as well as in this policy.
The date shown on this page identifies the policy edition presented here. Review it again when using a materially changed version of the service. If a particular privacy requirement is essential to your project, contact us before entering sensitive material rather than assuming that an unmentioned capability or guarantee exists.
For questions about application behavior or a contact message you sent, email contact@texttoebook.com. Describe the relevant interaction and approximate date without adding unnecessary private content. We will use the information you provide to understand the request, while recognizing that local drafts remain under your browser’s control.