Privacy Policy
OneQAZ Trading Intelligence — MCP Server, API & Website
OneQAZ ("we") provides a research-information service that exposes live market intelligence (crypto,
Korean stocks, US stocks) to AI clients over the Model Context Protocol (MCP) and an HTTP API. This policy explains how
we process personal information when you (or an AI client acting on your behalf) use api.oneqaz.com, and
when you visit oneqaz.com. It is written to meet Korea's Personal Information Protection Act (PIPA) and to
inform users elsewhere, including in the EU/EEA and the UK. Our own servers are located in the Republic of Korea.
01Purposes and legal basis
- Operate and secure the service (rate limiting, abuse prevention, debugging).
- Diagnose client and protocol compatibility problems.
- Measure aggregate usage (which tools are called, by which client type) to improve the product.
- Enforce access tiers, attribute usage to API keys, and issue and manage the API keys you request.
- If you choose to connect an AI app to a OneQAZ account (OAuth): create a free account when you choose Connect free, authenticate the account, issue, refresh and revoke the app's access tokens, and apply limits per account.
Anonymous use needs no account or consent screen. Request logs are processed on the basis of our legitimate interest in operating and securing the service, limited to what is reasonably necessary (PIPA Art. 15(1)(6); GDPR Art. 6(1)(f)). The contact email of an API-key holder is processed to issue and manage the key you asked for, and account-connection data is processed to provide the connection you asked for (PIPA Art. 15(1)(4); GDPR Art. 6(1)(b)). Connecting an account is optional; anonymous use continues to work without it.
We do not sell your data, build advertising profiles, use request logs to train AI models, or make automated decisions about you based on them.
02Personal information we process
Anonymous use does not require an account, and we do not collect names or payment details. The
following is generated automatically for each request to api.oneqaz.com:
- IP address
- Rate limiting, abuse prevention, and regional routing. For requests routed through Cloudflare this is the client address Cloudflare reports.
- User-agent
- To identify the client type (Claude, ChatGPT, Gemini, etc.).
- Tool / resource name
- The requested tool or resource and the request type
(e.g.
get_daily_brief). - Outcome metadata
- Success/failure, HTTP status, JSON-RPC error code, a short error description (at most 200 characters; input values echoed back by validation errors are redacted), latency (ms), and the shape of the result (rows returned, total available, whether it was truncated or empty).
- Derived session key
- A hash of IP + user-agent + a 30-minute time bucket. No cookie or other persistent identifier is set on your client.
- API key (if provided)
- Used to determine your rate-limit tier and access level. With each request we record the resolved tier and a one-way fingerprint of the key (the first 16 hex characters of its SHA-256 hash). The key itself is never written to request logs.
- Whitelisted request parameters
- A limited summary of tool arguments (e.g.
symbol,market,interval,category, date ranges, result limits, identifiers) and, for thesearchtool, the search keyword truncated to 60 characters. Calls made without arguments are recorded as such. Argument content outside this whitelist is not stored. - MCP client & protocol metadata
- The client name/version sent at
initialize(clientInfo), the MCP protocol version, theAcceptheader (first 200 characters), the protocol session id header if your client sends one, the call order within a session, and request/response payload sizes, and — if the connection URL you used carries one — a referral label (ref) from a fixed list (for examplequickstart); any other value is recorded only asother. - Traffic classification
- A derived label (crawler / operator-self-test / external) used to keep aggregate usage statistics honest.
- Contact email (API-key holders only)
- Provided by you when you ask for an API key.
If you connect an AI app to a OneQAZ account (optional), we also process:
- Account identifier
- A random identifier we generate (not derived from your email or key). If you sign in with an API key, it is linked to that key; if you choose Connect free, it is not linked to any key, email or other information about you. Requests made through the connected app record this identifier.
- Connected app identifier
- The address of the metadata document the AI app publishes (for
example a
claude.aiorchatgpt.comaddress) or a random identifier issued when the app registered, and the name the app declares. Requests made through the app record this identifier. - Connection record
- Which app you connected, the access you granted, when, and when the connection was withdrawn.
- Access and refresh tokens
- Stored only as one-way hashes; we keep no copy of the tokens themselves.
- Sign-in screen records
- When a sign-in attempt fails, the IP address and time are written to our server log. The API key you type on the sign-in screen is only checked against our key list — it is never stored or logged.
Of these, the IP address, the derived session key, the API-key fingerprint, the contact email and the account
identifier are personal information or can identify you in combination; the other fields describe the request, not you. We do not store the
contents of responses we send you. Visiting oneqaz.com does not send us any personal information (see
sections 06 and 08).
03Retention period
- IP address and derived session key — up to 12 months from the request.
- Other request fields — kept as usage history. Once the IP-derived fields are replaced they no longer identify you, except that requests made with an API key or a connected account remain attributable to that key or account while its contact email or the account exists.
- Contact email of an API-key holder — until the key is revoked or you ask us to delete it.
- Account connection (if you connect an AI app) — sign-in codes: deleted within 1 day after use or expiry; token hashes: within 7 days after they expire or are revoked; connection records: 30 days after you withdraw the connection, or 12 months after the connection was last used; app registrations that were never connected: after 30 days; an account created with Connect free: deleted automatically the day after its last connection record is deleted; an account linked to an API key: until you ask us to delete it.
- Database backups — rotated and deleted within about four weeks.
If another law requires us to keep data for longer, we keep only the items it requires, for the period it requires, separately from other data.
04Destruction procedure and method
- Procedure — when the retention period ends, IP addresses and session keys are irreversibly replaced by a processing job using a one-way transformation whose random key is discarded after each run, so the records can no longer be linked to an IP address. Contact emails are deleted without delay when the key is revoked or on your request. Account-connection records, and accounts created with Connect free that no longer have a connection, are deleted by a daily job when their retention period ends. When you ask us to delete an account, we revoke all of its connections and tokens immediately and delete the account without delay; the account identifier left in usage history then no longer identifies anyone.
- Method — electronic records are deleted or overwritten so that they cannot be restored or reproduced. We keep no paper records.
05Provision to third parties
We do not provide personal information to third parties. The only exception is where the law requires it — for example, a lawful request from an investigative authority with a warrant (PIPA Arts. 17–18).
06Outsourcing and overseas transfer
We entrust the following providers with processing that is necessary to deliver the service over the internet, which involves transfer outside Korea. We disclose the details here under PIPA Art. 28-8(1)(3).
- Cloudflare, Inc.
- Task CDN, DDoS protection and secure tunnel (TLS
termination) for
api.oneqaz.com· Country United States, and the countries of Cloudflare's global data-center network · Items IP address, request headers (incl. user-agent) and request contents in transit (including what you enter on the account sign-in screen) · When & how over the network, each time you call the API · Retention per Cloudflare's processing terms · Contact privacyquestions@cloudflare.com, 101 Townsend St., San Francisco, CA 94107, USA - GitHub, Inc.
- Task hosting the
oneqaz.comwebsite (GitHub Pages) · Country United States · Items IP address and browser information of website visitors · When & how over the network, each time you visit the website · Retention per GitHub's policies · Contact privacy@github.com, 88 Colin P. Kelly Jr. St., San Francisco, CA 94107, USA - BunnyWay d.o.o. (Bunny Fonts)
- Task delivering the web fonts used on our pages · Country Slovenia (EU), and the countries of its CDN · Items IP address and browser information · When & how over the network, when your browser loads the fonts · Retention per Bunny's policies · Contact support@bunny.net, Dunajska cesta 165, 1000 Ljubljana, Slovenia
How to refuse. These transfers are needed to deliver the API and the website over the internet, so to refuse them you need to stop using the API or visiting the website; neither can be provided without them. If your browser blocks web fonts, the pages still work with system fonts.
When you reach OneQAZ through an AI client, the AI platform you chose handles your request under its own policy; that is not a transfer made by OneQAZ.
07Security measures
- Administrative — access to personal information is limited to the operator.
- Technical — encrypted transport (HTTPS/TLS); the database is not exposed to the internet and is reachable only from our internal network; separate database roles per service; API keys are never written to request logs (one-way fingerprint only); only a whitelisted summary of arguments is stored; IP addresses are irreversibly replaced after 12 months. For account connections: tokens stored only as hashes, short-lived (1-hour) access tokens, refresh tokens rotated on every use with reuse detection, PKCE, and a sign-in screen that shows where you will be returned and cannot be embedded in other sites.
- Physical — servers and storage are kept at a location managed directly by the operator.
09Your rights and how to exercise them
- You may request access to, correction or deletion of, or suspension of processing of your personal information (PIPA Arts. 35–37). Where the GDPR applies, you may also object to processing and request restriction or portability.
- Send requests to contact@oneqaz.com. A legal representative or an authorised agent may act for you with a power of attorney.
- Requests made without a connected account are not tied to an account, so please include the IP address and approximate time of your requests, or the API key concerned (you may send its SHA-256 fingerprint instead of the key itself), so that we can find the records.
- If you connected an AI app, you can disconnect it in that app, or ask us to withdraw the connection or delete the
account. Withdrawal makes the app's tokens stop working immediately. For a request about a connected account, include
its account identifier — your AI app can show it by calling the
get_account_statustool. - We respond within 10 days. Where the law allows us to limit a request (for example, where another law requires retention or it would harm someone else's rights), we will tell you the reason.
- If you are in the EU/EEA or the UK, you may also lodge a complaint with your local data-protection authority.
10Privacy officer
- Department
- OneQAZ Privacy Office — responsible for personal information protection, access requests and complaints
- Contact
- contact@oneqaz.com
11Remedies for infringement
You can seek dispute mediation or advice from the following Korean bodies, which are independent of OneQAZ:
- Personal Information Dispute Mediation Committee — 1833-6972 · www.kopico.go.kr
- Personal Information Infringement Report Center (KISA) — 118 · privacy.kisa.or.kr
- Supreme Prosecutors' Office — 1301 · www.spo.go.kr
- Korean National Police Agency — 182 · ecrm.police.go.kr
12AI client disclosure
When an AI client (such as Claude, ChatGPT, or Gemini) calls OneQAZ on your behalf, your request reaches us through
that client's platform. Every response carries disclaimer, is_investment_advice=false, and
data_classification=research_information_only.
If you connect an AI app to your OneQAZ account, we issue access tokens to that app at your direction. The AI platform stores and uses those tokens under its own policy. You can disconnect at any time (see section 09).
13Not applicable
- We do not process sensitive information or unique identifiers such as resident registration numbers.
- The service is not directed at children under 14, and we do not knowingly collect their information.
- We do not process pseudonymised information under PIPA's special provisions, and we make no automated decisions that affect your rights.
14Changes
This policy takes effect on 2026-10-16. Change on 2026-10-16: added the connection-URL referral label
(ref, fixed list) to MCP client & protocol metadata — section 02. Change on 2026-10-14: an AI app can be connected on the free plan without an
API key (Connect free); such accounts are linked to no key or personal details and are deleted automatically once no
connection remains — sections 01–04 and 09. Change on 2026-10-08: added optional account connection for AI apps (OAuth)
— sections 01–04, 06–09 and 12. We announce changes by updating the date above; previous versions are
available in the public
change history.
This policy is published identically at oneqaz.com/privacy and api.oneqaz.com/privacy.