Lucid Ventures LLC / Privacy
Privacy notice
Updated September 18, 2026 · Draft, under legal review.
Account and contact information
We use your email address to sign you in and respond to requests. Required httpOnly session cookies support authentication. Operational request logs support service reliability. Contact-form submissions may be retained as lead records and sent as a notification to the Lucid team. Do not include customer datasets or credentials in the contact form.
The public preview
The interactive workspace preview uses synthetic customer records in browser memory. It does not upload its workflow state, call a model with that state, or retain it in localStorage. Refreshing or leaving the page clears the example. Ordinary website request logs and any existing account session remain separate from that example.
Private Business Mind pilots
An explicitly provisioned private workspace stores the supported customer summary you provide, approved business definitions and descriptions, generated template drafts, decisions, manually recorded outcomes, and versioned evidence artifacts. Provide only records you are authorized to process. Use opaque customer identifiers and omit names, email addresses, phone numbers, credentials and sensitive documents. Opaque identifiers can still relate to individuals and are treated as private workspace data.
Purpose and separation
Private pilot records are used to deliver the agreed workflow and maintain its evidence history. They are not pooled into other customer workspaces or used by this pilot to train an AI model. The reactivation recipe uses rules and templates, not model calls. Public and appropriately licensed external data is maintained separately from private customer records.
Service infrastructure
The application is hosted on Vercel and its database uses Neon. Account or contact emails may use Resend. Existing payments are handled by Stripe. The pilot does not send customer follow-up drafts, initiate charges, or write to your source systems. Any additional processor, connector or model use must be addressed before that capability is enabled for private data.
Access, export and deletion
Private workspace content is restricted by authenticated membership and role. Owners can export the workspace archive and delete active workspace records, artifacts and receipts. Deleted data may remain in infrastructure backups until those backups expire under provider retention. Immediate erasure from every backup is not promised. Account closure and other privacy requests can be directed to hello@lucidagent.ai.
Retention and agreements
Source and decision versions are retained in the active private workspace so the work remains inspectable. The pilot has explicit capacity limits; those limits are not a substitute for an agreed retention period. Private-data onboarding requires a scope and retention review before activation. This notice remains a draft and is not a claim of a completed compliance certification.
Questions about your information: hello@lucidagent.ai.