Your writing deserves clear boundaries.
A draft explanation of how this version handles text, accounts, and service requests. Final operator and provider details must be added before public launch.
Local text tools
Text cleanup, word counting, readability calculations, comparison, and local writing signals are performed in your browser. Using these local operations does not require submitting the text to an AI service.
If you explicitly use a local save or history feature, the saved text may remain in your browser storage on that device until you clear it. Other people using the same browser profile may be able to access it. Browser settings can remove or block that storage.
AI rewriting and external detection
When you request an AI rewrite or a model-based detection assessment, the text and relevant editing options are sent to the application server and the configured service provider. A provider is required for these operations. Only submit material you are authorized to share with that provider.
Before public launch, this section must name each active provider, link its privacy terms, and explain its retention and model-training practices. No blanket claim about third-party training or retention is made in this draft.
Accounts, billing, and operational data
When account services are enabled, the application may process account identifiers, email addresses, session data, usage records, and billing references needed to operate the service. Payments are not enabled in this pre-launch version.
Hosting and service infrastructure may process request metadata such as IP addresses, timestamps, error information, and browser details. Production log content, access controls, retention schedules, and any analytics choices must be documented before launch. API credentials belong on the server and must not be placed in browser storage.
Cookies and browser storage
Account sign-in, when enabled, requires session functionality. The application may also store interface preferences or an explicitly saved local draft in your browser. Clearing browser storage may sign you out and remove those local drafts.
Any future optional analytics or marketing cookies need a separate implementation and an appropriate disclosure or consent flow where applicable. This draft does not authorize adding those services silently.
Your requests and the final policy
Before launch, the operator must provide a working contact for access, correction, deletion, portability, complaints, and any other rights that apply in its service locations. The final policy must state how account deletion interacts with payment records, backups, legal obligations, and locally saved drafts.
Do not submit sensitive material during this preview. A complete production privacy policy and verified service configuration are launch requirements.