Privacy and Cookies
Nexus Docs is self-hosted. The organization running the instance controls its database, search index, email provider, analytics configuration, and deployment environment.
Required cookies
Required cookies keep the application working. They can include session, authentication, CSRF, and consent-preference values.
These cookies are needed for:
- Signing in
- Keeping a session active
- Protecting forms and account actions
- Remembering cookie preferences
- Showing gated documentation according to the signed-in user's access level
Optional analytics
Analytics is optional and controlled by environment configuration. The root layout initializes consent defaults before tag manager scripts run, so analytics storage starts denied until a visitor grants consent.
If no tag manager ID is configured, analytics scripts are not loaded.
Self-hosted data
Documentation content is stored in the repository. Runtime data such as users, permissions, invitations, feedback, access requests, and audit records is stored in the configured database.
Search records are stored in MeiliSearch and filtered according to the same access rules used by page rendering.
Operator responsibility
When you deploy Nexus Docs, you are responsible for the legal policy shown to your users, your data-retention rules, your email provider configuration, and any analytics or tracking tools you enable.