Privacy proof: what stays on your device

Browser tools

Word counting, converters, developer utilities, fancy text, the game-name checker, bio composer, notepad and handwriting rendering run in browser JavaScript. Closing the page clears ordinary workspace state; the notepad intentionally stores drafts locally on the current device.

Handwriting

Source text and rendered pages remain in the browser. Starting a premium checkout sends order metadata such as page count and price, not the handwriting text. Operator-installed handwriting font files are served as static WOFF2 assets only after their licence metadata and hashes are recorded.

Assisted writing and optional AI

Assisted tools send the submitted text to TXTNimble to produce the result. Usage events retain only metadata such as input/output lengths. If an operator enables the optional private AI endpoint and the visitor selects AI enhancement, the text is forwarded through that configured boundary for the requested enhancement.

How to verify

Open browser developer tools and use the Network panel while running a client tool. The client tool itself should make no processing request to TXTNimble. Payment checkout, optional analytics/ads, and future cloud pickers are separate explicit integrations and must not be confused with the processing path.