QueryMind Connect Privacy Policy

Effective November 8, 2026

1. Operator and scope

QueryMind Connect (the "Service") is operated by Blueurban. The representative and privacy officer is Jaehoon Lee. Business registration number: 105-29-33544. Mail-order business registration: 2026-Hwaseongdongtan-2624. Address: S Building, 8F, Unit 11, 14 Dongtancheomdansaneop 1-ro, Dongtan-gu, Hwaseong-si, Gyeonggi-do, Republic of Korea. Privacy inquiries and support requests: support@jupgo.co.kr.

This policy applies to QueryMind Connect, the hosted service that connects to AI services such as ChatGPT and Claude through MCP (Model Context Protocol). QueryMind products installed on a customer's own premises are governed by their separate contracts and policies.

This policy takes effect on November 8, 2026.

2. Personal data we process and why

Account and organization management: signup email, organization name, account credentials (passwords are stored only as hashes), roles and invitations within the organization, and OAuth client, authorization and token records, used to create accounts, sign in, check permissions and keep connections working.

Database connection: the database address, type, access account and password entered by the organization, schema metadata (table and column names and structure) and business definitions, used to connect and prepare queries. Database passwords are accepted only through a separate secure form, never in chat.

Query processing: questions, clarification replies, parameters, business definitions, generated and executed SQL, results and evidence passed through the tools, used to handle the request and follow-up questions. Connected business data and question text may contain personal data; its scope is determined by the organization's access rules.

Operations and security: query jobs, audit records (question, SQL, actor, time, row count), usage records and access logs including IP addresses, used for authorization, quota management, operation, troubleshooting and security incident response.

Support: the content and contact details of inquiries sent to support@jupgo.co.kr, used to handle that inquiry.

The Service processes only what is needed for signup, connection and queries, and does not use this data for marketing or profiling.

3. Recipients, processors and AI services

Connected AI services: the Service sends MCP responses, meaning the answer, applied conditions, query evidence and a limited portion of the result (at most 100 rows per result, after the organization's access rules and privacy masking are applied), to the AI service the user chose to connect, such as OpenAI for ChatGPT or Anthropic for Claude. Further processing by that AI service is governed by its own terms, privacy policy and the organization's settings.

External language-model processing: the general question tools (ask and clarify) use the API of OpenAI, L.L.C. (United States) to generate SQL and compose answers. The data sent consists of the question text, schema structure information (table and column names and statistics), and the first 100 rows of a completed result after personal data such as national ID numbers, phone numbers and email addresses has been masked. Under OpenAI's API data policy, data sent to the API is not used to train models and may be retained for up to 30 days for abuse monitoring (OpenAI public policy as of November 8, 2026). Approved query tools (tools whose names start with q_) run deterministically without this language-model call.

Hosting: the Service runs on servers operated directly by Blueurban in the Republic of Korea. We do not otherwise provide or sell personal data to third parties; we disclose it to authorities only when required by law.

Organization customers may request a separate data processing agreement.

4. Retention and deletion

Account and organization data (email, organization name, roles, invitations): deleted when the organization is terminated or a deletion request is processed. Deletion requests are processed within 30 days of receipt.

Database credentials: deleted when the organization removes the connection or when the organization is terminated. Organization termination includes removal of that organization's execution environment and metadata store.

Query result data: result data kept on the server is cleared one hour after the query completes (display grace period). Conversation context (threads kept for follow-up questions) is deleted by the cleanup job once 90 days have passed since the last update.

Audit records (question, SQL, actor, time, row count) and access logs: retained for security and dispute handling while the Service is in use, and deleted one year after the organization is terminated, unless applicable law requires longer retention.

Usage records: retained for one year after organization termination as the basis for quotas and billing, then deleted. OAuth authorization and token records: unusable immediately upon expiry or revocation; stored records are removed by periodic cleanup. Support inquiries: kept for one year after the inquiry is resolved, then deleted.

Recovery backups: backups made before deployments or changes are kept on access-controlled storage, used only for recovery, and destroyed within one year of creation.

Disconnecting QueryMind in an AI service or revoking its OAuth authorization ends the connection with that AI service; it does not by itself delete the account, organization or audit records stored in QueryMind. To request deletion, follow the procedure in Section 5.

5. Your rights and how to exercise them

Users and organizations may request access to, correction of, deletion of, or suspension of processing of personal data by writing to support@jupgo.co.kr. After confirming the requester's identity or organizational authority, we respond with the outcome or a handling plan within 10 days of receipt, and deletion is completed within 30 days of receipt.

Organization administrators manage connected databases, permitted query definitions, member roles and row-level access rules through the Service's management tools. Disconnecting from an AI service and revoking OAuth authorization are done in that AI service's connection settings; revocation of tokens on the QueryMind side can be requested by email.

In the Republic of Korea, complaints about personal data infringement may also be directed to the Personal Information Dispute Mediation Committee (1833-6972, www.kopico.go.kr), the Personal Information Infringement Report Center (118, privacy.kisa.or.kr), the Supreme Prosecutors' Office (1301) or the National Police Agency (182).

6. Security measures

Data in transit is encrypted with TLS, and authentication with AI services uses OAuth 2.1 with PKCE. Each organization has its own execution environment and metadata store; every request is checked for organization, scope and role, and the organization's row-level access rules are applied to queries automatically.

Business databases are accessed read-only, and SQL that would modify data is blocked at generation and execution. Responses are size-limited and personal identifier patterns such as national ID numbers, foreign registration numbers, passport numbers, phone numbers, bank account numbers, card numbers and email addresses are masked before delivery. Database credentials are stored separately per organization with controlled operator access and access logging.

Even with these measures, responses may contain personal data depending on the data the organization connects. Organization administrators should grant the connected database account and the permitted query scope the minimum necessary access.

7. Processing locations and international transfers

The Service's servers and the personal data they store are located in the Republic of Korea. Regardless of any region selection shown at signup, all data is currently stored in the Republic of Korea.

International transfer: when the general question tools are used, the question text, schema structure information and the masked first 100 rows of a result are sent by API call to OpenAI, L.L.C. (United States, privacy contact privacy@openai.com) to generate SQL and compose the answer. The transfer takes place when the question is processed, and retention follows OpenAI's API data policy (no model training, abuse monitoring for up to 30 days). Organizations that do not want external language-model processing may use only the approved query tools (q_) or the on-premises configuration offered under a separate contract.

Responses delivered to the AI service the user connected (OpenAI, Anthropic and others) are processed where that provider's service and the user organization's agreement with it determine.

8. Effective date, changes and contact

This policy takes effect on November 8, 2026. When it changes, we post the changes and their effective date on this page (https://querymind.co.kr/oauth/privacy) at least 7 days in advance, or 30 days in advance for changes that materially affect your rights.

This policy is provided in Korean and English; if the two versions differ, the Korean version prevails. Contact: Blueurban, support@jupgo.co.kr.