Privacy and Data Handling

Text submitted for editing is processed in memory for the active request and returned to your browser. The platform does not store the original passage or the edited output in its database, does not write either to application logs, and does not build a copy, archive, index or training set from them. Closing or refreshing the page discards the result.

Only the minimum required to operate an account:

• Account identity handled by the authentication system (email address and password hash).
• Plan, subscription status, billing-cycle dates and entitlement status.
• Numeric usage counters: the number of processed words, never the words themselves.
• Short-lived, non-reversible request fingerprints used for rate limiting and duplicate-submission protection.
• Support messages you choose to send through the platform.

Editing is carried out by a securely configured server-side process. Model credentials are held on the server and are never exposed to the browser. Passages are transmitted for the single request and are not retained by the platform afterwards.

Account records, usage counters and support conversations are protected by row-level access rules so that a signed-in person can reach only their own records. Administrators can access support conversations solely to answer them.

AI-detection scores are probabilistic and vary by detector, version, language and passage length. Lev-Al Prose improves naturalness and preserves authorship; it cannot guarantee a particular score or replace an institution's academic-integrity requirements.

You can request deletion of your account and its stored records through the in-platform support system. Because submitted passages are never stored, there is no text archive to delete.