Privacy Policy

We collect account information such as name, email address, authentication details, and basic profile metadata needed to operate the workspace.

We store the content you upload or submit, including files, URLs, extracted text, generated wiki content, chat threads, and source citations tied to your atlas.

For public atlas pages, we also store public chat activity. Anonymous visitors are tracked with a browser-level anonymous identifier, and signed-in non-owners may have their name and email stored with the questions they ask.

We use your information to authenticate users, process uploaded materials, generate wiki pages, answer chat questions, show citations, and maintain atlas history.

We also use operational logs and product telemetry to debug failures, improve reliability, prevent abuse, and understand how the product is being used.

If an atlas owner marks an atlas as public, visitors may be able to browse the atlas landing page, source files, wiki, and other public surfaces without signing in.

Public chats are visible to the service operators and may later be visible to the relevant atlas owner inside the product. Owners should only publish atlases they are comfortable exposing in read-only form.

We may use infrastructure, hosting, storage, authentication, analytics, and model providers to operate Living Wiki. Those providers may process data strictly to deliver the service on our behalf.

We do not sell personal information. We may disclose information when required by law, to enforce our terms, or to protect the product, users, or the public.

We retain information for as long as it is needed to provide the service, maintain workspace history, comply with legal obligations, and resolve disputes.

We use reasonable administrative, technical, and organizational safeguards, but no online system can guarantee absolute security.

Atlas owners can remove documents and chats from their workspace where product controls allow it. Public visitors can stop using the service at any time.

We may revise this policy as the product evolves. When we do, we will update the text on this page and change the effective date above.