Blueprint
Control Center
Website information
How Blueprint handles authentication, server configuration data, and basic website usage data.
Blueprint stores the service data needed to operate the website and Discord bot: an authenticated website session, the linked Discord account identifier provided by Continental ID, and per-server configuration saved through the dashboard.
Server settings can include channel and role IDs, module toggles, message templates, runtime state such as leveling and ticket records, suggestion numbering, starboard references, and modmail routing mappings.
Blueprint reads the Discord metadata and message events required by the modules you enable. Ticket transcripts are sent to the Discord channel you configure, and modmail forwards member messages to the configured staff inbox; those message contents remain Discord data rather than being copied into Blueprint's settings database.
This data is used to sign you in, determine which Discord servers you are allowed to manage, and apply the settings you save for each server.
Blueprint does not need broad personal-profile data to perform its core workflow. It uses only the fields required to match authenticated users to Discord access and persist server configuration.
Blueprint uses a session cookie so the dashboard can keep you signed in between requests. The cookie is used for authentication and basic session integrity, not for advertising.
Blueprint configuration data is used to operate the service and is not intended for resale or advertising. Web sessions expire after seven days. Guild settings and module runtime records remain until the server is removed or the operator performs the documented deletion workflow; logs and encrypted backups follow the deployment's retention policy.
When a server explicitly enables AI tools, the configured AI service and Continental ID access service receive the request data needed to answer the request and verify access. Blueprint does not store AI prompts or responses in its local SQLite databases. Provider retention, training use, and regional processing depend on the deployment's provider agreements and must be confirmed before public launch.
Only save data to Blueprint that is appropriate for your server configuration workflows. Avoid placing sensitive secrets or private personal information into free-text settings unless the feature explicitly requires it and your organization approves that usage.