Menu
Lucy
Privacy header art

Privacy

Your working room is not an ad profile.

Twelve sections, plain words. Last updated 20 September 2026.

1. The principle.

Lucy does not sell your data, does not train third-party models on your work, and does not build an advertising profile from it. If that ever changes, it will be stated here first, not discovered later.

2. What stays in your browser.

The active entitlement reference, browser binding, conversation state, attachments, generated-image and video references, and code artifacts live in browser storage so you can leave and return. Clearing site data, switching profiles, or storage failure can remove them. Export work you need to retain.

3. What the access service keeps.

Email, payment identifiers returned by the processor, which access you hold and whether it is active, access codes and use state, access windows, renewal state, and the bound browser. Kept to sell access, prevent fraud, and keep the lights on — the minimum the product needs.

4. What leaves the browser when you ask Lucy to work.

Prompts and attachments are processed on private inference hardware operated for Lucy — inference services configured for Lucy, not third-party model APIs. Stripe processes payments. Hosting, storage, and access infrastructure see the ordinary request metadata needed to serve the product.

5. Cookies and storage.

Lucy sets no advertising cookies and runs no ad trackers. Browser storage holds your session; Stripe's checkout sets its own cookies on its own pages under its own policy.

6. Retention.

Session data lives in your browser until you clear it. Billing and entitlement records are kept as long as needed for the sale, fraud prevention, tax records, and legal obligations, then removed or de-identified.

7. Your rights.

Ask for a copy, correction, or deletion of your personal information at privacy@lucy.app. Requests are verified against the checkout email before anything moves. Deleting everything deactivates access tied to it.

8. Children.

Lucy is not for under-16s. Accounts found to belong to children are removed on notice to privacy@lucy.app.

9. Security.

Reasonable technical and organizational measures protect the service — encryption in transit, isolated secrets, device-bound access. No system is immune; breach notifications go to the checkout email on file.

10. Sensitive material.

Use judgment with confidential, regulated, privileged, export-controlled, or otherwise highly sensitive material. A request is transmitted to inference infrastructure as part of producing the answer, image, code, or media you request.

11. Changes.

Material changes are posted here with a new date. Continued use after posting is acceptance.

12. Contact.

Privacy questions and rights requests: privacy@lucy.app. General support: support@lucy.app.

Product posture · 20 September 2026