Skip to content

LightDocs · Legal

Privacy policy

Draft updated October 28, 2026

A clear view of the information involved in running LightDocs, the choices available to you, and the service details that still need confirmation.

1. Scope and responsibility

This draft describes the proposed privacy practices for the LightDocs website and knowledge base service. The final notice must identify the legal entity responsible for personal information and provide a working privacy contact before taking effect.

When a customer publishes personal information in a knowledge base, that customer is responsible for deciding what to publish and for providing appropriate notices to their readers. Any processing of customer data on their behalf must be covered by the applicable service agreement.

2. Information involved

The marketing website includes Vercel Web Analytics to understand page visits and website usage. Visiting a website also involves technical request information processed by hosting and delivery infrastructure.

The LightDocs service supports Google and GitHub sign-in and stores documentation created by users. The final service notice must specify which profile fields, account identifiers, authentication information, logs, and content are actually collected. This marketing-site repository does not establish those details.

Information you choose to send when asking for support may include your name, contact details, and the contents of your message. Do not send passwords, access tokens, or sensitive personal information through public social channels.

3. Purposes and legal grounds

The proposed purposes are operating the service, authenticating accounts, hosting documentation, responding to requests, preventing abuse, and understanding website usage. Information should not be repurposed for unrelated uses without the required notice and lawful basis.

Where applicable law requires a legal basis, the final notice must map each activity to the appropriate basis, such as performing a contract, meeting a legal obligation, a properly assessed legitimate interest, or consent. Consent must be withdrawable where it is used.

4. Public documentation

The current public beta is designed for public help centers. Published articles may be accessible without an account and may be indexed, copied, or cached by search engines and other visitors. Only publish material you are authorized to make public.

Private sites and user management are planned for the Startup package and are not part of the current public-beta offering. Do not use a public help center for confidential information.

5. Providers, sharing, and transfers

The website uses Vercel Web Analytics and links to external services, including the LightDocs app, Google, GitHub, and social networks. Those services have their own privacy notices. The app’s hosting, storage, authentication providers, and other recipients must be verified and disclosed in the final service notice.

Any international processing locations and applicable transfer safeguards must be confirmed before the final notice is published. This draft does not claim that all data stays in a particular country or region.

6. Cookies and browser choices

The marketing-site source includes Vercel Web Analytics and does not implement a waitlist or email collection form. The final cookie disclosure must reflect the deployed website and app, including any authentication storage or third-party scripts added later.

You can manage cookies and site storage through your browser. Blocking storage used by the application may affect sign-in. Where non-essential technologies require consent, they should be enabled only after that consent is obtained.

7. Retention and security

The intended retention approach is to keep information only for the purpose for which it was collected, including necessary account administration, security, and legal requirements. Specific schedules for accounts, content, logs, analytics, backups, and deletion requests must be confirmed in the final notice.

Security controls and deletion timelines must reflect actual service operations. No online service can guarantee absolute security; this draft makes no unverified claims about encryption, certifications, data residency, or backup erasure.

8. Your choices and rights

Depending on applicable law, you may have rights to request access, correction, deletion, restriction, portability, or to object to processing. You may also have the right to withdraw consent and raise a complaint with your local data protection authority.

A dedicated privacy-request channel, identity-verification procedure, and applicable response deadlines must be confirmed before this policy becomes final. The Contact page currently links to the public channels already listed by LightDocs; do not post personal information there.

9. Updates and contact

A final policy should show its effective date and explain how material changes will be communicated. Changes to processing must not be presented as retroactive consent.

For current public contact channels, visit the Contact page. The legal operator and a direct privacy contact remain required before this draft can become the service’s final privacy notice.