lossless rewrite.

Privacy

Lossless Rewrite helps you keep selected wording and ideas when rewriting with an AI chat. It is maintained by Francesco Dettori. Contact hello@llmderby.com with “Lossless Rewrite” in the subject for privacy or data-removal requests.

What stays on your device

• Selected passages, source labels, PDF page numbers, drafts, replies and check results are held in extension session storage. Chat selections are scoped to a tab and conversation. Closing a chat tab clears its selection records; Clear selections removes them immediately.
• The full editor’s optional Save locally action stores a document in local extension storage. This copy is not encrypted. Clear document removes it.
• PDFs you open are processed locally with bundled PDF.js. The complete PDF is not uploaded by Lossless. Selected passages, filenames and page numbers can be included in a prompt you send.
• Saved reference projects, currently available to private test accounts, store PDFs and selections encrypted in your browser profile. The key also lives there, so this does not protect against someone using your unlocked browser.
• Google sign-in stores a session token in extension storage, restricted to trusted extension contexts. There is no browser sync. Uninstalling removes the extension’s local data.

Writing rules are kept in local extension storage. Automatic capture recognizes supported style requests at the start of messages you send, entirely on your device. It does not scan past conversations or AI replies, and does not call an extra model. You can undo a captured rule or turn capture off in My writing rules. You can edit, disable or remove them in Writing rules. They apply across Lossless chats on that device.

When text leaves your device

Using the Lossless send shortcut or sending a /lossless request adds your selected passages and enabled writing rules to the current chat draft and sends it to that chat provider. Ordinary messages are unchanged. Lossless does not read the system clipboard in the background.

When you run a hosted meaning check, Lossless sends the selected passages, enabled writing rules and completed reply through our Supabase backend to Jev (TypeSafe). On Free you choose Check finished reply; private test accounts can run automatic checks after an explicit Lossless send. We do not store document text in our application database or deliberately log it. Network infrastructure and providers may process operational metadata under their own policies. Checks can be wrong.

If you choose the optional local companion instead, it sends the necessary text to your configured decision provider. API keys stay in that companion. Writing and repair prompts use your existing chat account.

Accounts and email updates

Google sign-in is handled by Supabase. We use your verified email and account identifier for access, usage limits and any plan interest you register. We store usage credits, request identifiers and completion status to enforce limits and avoid duplicate charges. Paid checkout is disabled.

If you preregister for Plus or Pro, we store your verified email, chosen plan and consent record in Supabase. Brevo sends a confirmation and will be used for updates about that plan. Brevo processes delivery and link events. Every new confirmation includes an unsubscribe link requiring no sign-in. Removing your interest stops that plan’s updates. We retain minimal delivery status to prevent duplicate confirmations and a hashed unsubscribe token.

Our Supabase authentication project is shared with other applications operated by the maintainer; Lossless application records are separate. A Lossless deletion request will not delete your accounts in those other applications.

Your choices and retention

You can remove site access in Chrome, sign out, clear selections and saved documents, delete saved reference projects, or uninstall the extension. Remove plan interest through Compare plans or the email footer. Account, usage and minimal email delivery records remain until you request their deletion or they are no longer needed for operation or security. Contact us to request access, correction or deletion of Lossless data. Please do not send manuscript text, credentials or other sensitive material with your request.

Limited use

Lossless Rewrite’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not sell personal data, use it for advertising, or transfer it for unrelated purposes. The extension contains no advertising or analytics SDK. Service providers process data only as needed for the described features. We do not use your document text to train models; your chosen AI providers’ separate terms and settings still apply.

Permissions

Site access is limited to the listed AI chat sites and the Supabase backend. Scripting inserts the selection and rewrite controls; activeTab identifies the current chat; sidePanel displays the editor; storage retains your choices and session. Optional identity permission enables Google sign-in. Optional nativeMessaging connects your locally installed companion. Lossless does not request access to all websites or browsing history.

Source code and support · Home