Privacy.
Plain English. The binding data terms for beta partners live in the signed beta agreement; this page explains how we handle information across the site and the private beta. Last updated 2026-06-13.
Who we are
lakecode is operated by Lakeside Analytics (“we”, “us”) [TODO: confirm formal legal entity & registered address]. Questions: hello@lakecode.ai.
What we collect
- What you send us — when you email a beta or contact address (or any future request form), we receive your email address, name, and whatever you choose to tell us about your team and systems.
- Basic server logs — our static-site host records standard request logs (IP, user agent, timestamps) for security and reliability.
- No advertising trackers. The site currently sets no analytics or advertising cookies. If we add privacy-respecting analytics, we'll update this page first.
Your code & documents (beta)
During the private beta, ingestion turns your code and docs into structured claims in your org's substrate — a database dedicated to your org, physically separate from other tenants. The substrate is your data: it is exportable at any time and deleted on exit. These terms are written into the signed beta agreement, which controls.
How we use information
To respond to you, operate and improve the beta, and keep the service secure. We do not sell your information.
Who we share it with
Only the service providers needed to run lakecode: our static-site host, our LLM provider (Anthropic), and — for the Databricks edition — your own Databricks environment. Each processes data only to provide the service. [TODO: confirm and list subprocessors before launch.]
Retention & your rights
We keep contact information for as long as needed to support the beta relationship. You can ask us to access or delete your information at any time: hello@lakecode.ai. Beta substrate data follows the deletion terms in the agreement.
Security
We use reasonable measures to protect data, including per-org isolation in the beta. No method of transmission or storage is perfectly secure, and we don't claim certifications we don't hold.
Changes
We'll post any changes here and update the date above. Material changes that affect beta partners will also be communicated directly.