Privacy Policy
Absolute Privacy Principle
Based on the core philosophy of a "Self-hosted AI Assistant", the OpenMake platform stores your chat history, prompts, project data, skills, agent metadata, usage records, and credentials in your local environment or proprietary server.
1Zero Data Extraction
The OpenMake development team and third-party services do not collect or harvest any chat logs or file contents generated within your infrastructure. The default local model path does not transmit prompts to external AI services.
2Optional External Service Notice
The default setup uses the local LLM gateway configured by LLM_BASE_URL and LLM_DEFAULT_MODEL. External transmission is limited to optional integrations you enable yourself: external providers (OpenRouter, NVIDIA NIM, or Ollama cloud) receive prompts only when a user selects an external model with their own key; Web Search sends queries to Google Custom Search when GOOGLE_API_KEY and GOOGLE_CSE_ID are configured; the web scraping tools fetch the pages you ask about; NotebookLM grounding contacts Google with your own session cookie only for conversations where you pin a notebook; and Google, GitHub, or Kakao OAuth communicate with those providers during sign-in when their credentials are configured. External provider keys and the NotebookLM cookie are AES-256-GCM encrypted at rest.
3Role-Based Access Control (RBAC)
Administrators can strictly govern and control team member permissions through the internal system dashboard. All authentication processes are managed securely on-premise through the integrated database or OAuth2 (Google, GitHub, or Kakao, if configured). JWTs are issued in HttpOnly cookies, and every privileged action is written to the audit log.
Your AI. Your Server. Your Rules.
We return complete control of your data back to you.