Privacy Policy
jp-caa-labeling-orders · Operator: MK Career Planning · Last updated: 2026-11-01
1. What we handle
- Payer wallet address and transaction hash of each paid call (x402, USDC), with the tool name, price, network and time.
- Results of paid calls (the response body), so that you can fetch them again with
get_receipt if the response was lost after payment. The stored result includes the inputs you sent (for example the dates and places of an itinerary).
- Retry check value: while a paid result is kept, we also keep a keyed one-way value of the tool name and the arguments (HMAC-SHA256 with a secret key), used only to recognise a retry with the same payment. It cannot be turned back into the inputs without the key, and it is deleted together with the result. Calls that are not settled (paused, refused or failed) keep no such value. Records made before 2026-11-01 may hold an unkeyed SHA-256 hash of the arguments instead, which is deleted on the same schedule.
- Free tool usage: daily counts per tool and channel, and a daily estimate of distinct callers computed from a one-way hash of the first three parts of the IP address with a key that changes every day. We do not store free tool inputs in our database.
- Request logs: we do not keep Cloudflare's automatic request logs, so caller IP addresses, locations derived from them, and User-Agents are not logged by us. For fault investigation we keep only the log lines our own code writes (errors and summaries of background jobs), which are written not to include IP addresses, request headers, query strings or request bodies; Cloudflare may attach basic details of the call to them, such as the request method and the path without the query string (values inside the path, for example a receipt_id, can appear). Cloudflare Workers Logs keeps these lines for up to 7 days. Cloudflare may still process connection data to deliver the service under its own policy.
- MCP responses: when you use the MCP endpoint, a response (which can include your inputs) may be held briefly in Cloudflare Durable Object storage until it has been delivered, so that a dropped connection can resume. It is normally removed as soon as it has been delivered.
- IP addresses: we do not store IP addresses in our own database. Cloudflare, which hosts this service, processes IP addresses and request metadata to deliver the service and may keep them in its logs, under Cloudflare's own policy. To enforce per-client rate limits on free calls, we pass a one-way hash of your IP address and the first 64 characters of your User-Agent to Cloudflare's rate-limiting counters, which only count requests over about a minute; we do not store either.
- CAA labeling act orders: this service stores only what it needs to relay national orders under the Act against Unjustifiable Premiums and Misleading Representations published by the Consumer Affairs Agency (CAA): for each release, the names, corporate numbers and addresses of the companies named as respondents as published, the order type and date, the cited clauses and, when stated, the surcharge amount, with the release page and PDF URLs, the SHA-256 of the release page and the time it was read. The names of individuals in those releases (such as company representatives) are removed before storage and are never stored or returned, and the text of the release PDFs is not stored. Releases whose respondents are only individuals or sole proprietors are not recorded at all (not even counted), and list titles are not stored. Corporate numbers, company names and locations you send in a lookup are not stored.
We do not ask for names, email addresses or accounts to use the API.
2. Why
- To process payments, prevent double charges (idempotency) and let you re-fetch a paid result.
- To keep accounting records and to enforce daily limits.
- To measure aggregate usage. Our own monitoring payments are excluded from customer figures.
3. Third parties
- Cloudflare (hosting, storage, logs).
- Payment facilitator that verifies and settles x402 payments: Coinbase Developer Platform (api.cdp.coinbase.com), or PayAI (facilitator.payai.network) or Dexter (x402.dexter.cash) as a fallback. When a paid HTTP endpoint is settled through Coinbase, Coinbase may list that endpoint (not you) in its public x402 Bazaar catalog. The facilitator receives the signed payment, which includes your wallet address.
- Public blockchain: payments settle on Base. Wallet addresses, amounts and transaction hashes on a public blockchain are public and permanent; neither we nor anyone else can delete them.
We do not sell personal data and do not use it for advertising.
4. Retention
- Results of paid calls and their retry check values: 30 days after settlement, then deleted together (
get_receipt then returns RECEIPT_NOT_FOUND).
- Payment records (wallet address, transaction hash, amount, tool, time): 7 years for accounting, then deleted.
- Free tool daily counts: kept as aggregate statistics.
- Deleted data: after we delete data (at the end of a retention period or on request), it can remain recoverable through our database provider's point-in-time recovery (Cloudflare D1 Time Travel) for up to 30 days, after which it is gone.
- Request logs: up to 7 days (Cloudflare Workers Logs). Other Cloudflare logs: according to Cloudflare's retention settings.
5. Requests and contact
To ask about or request deletion of data linked to your wallet address, contact: mk.career.planning@gmail.com
Please send the wallet address and, if possible, the receipt_id or transaction hash. We can delete stored results; payment records required for accounting are kept for the period above, and data on the blockchain cannot be deleted.
6. Disclaimer
This service relays and restructures orders published by the Consumer Affairs Agency of Japan (CAA). It is not an official list or service of the CAA or the Government of Japan, it does not rate any company, and it gives no legal or compliance advice. Always check the official release. See the Terms of Service.
7. Changes
We will update this page and its date when this policy changes. See also Support and the Terms of Service.
日本語の要旨
- 運営者：MK Career Planning
- 扱う情報：有料の呼び出しの支払い元ウォレットアドレス・取引ハッシュ・金額・時刻、有料の結果（receipt で再取得するため。送られた入力を含みます。例：旅程の日付と場所）、有料の結果を残すあいだは、同じ支払いでの再試行を見分けるためだけに、道具の名前と入力から秘密の鍵で作った一方向の値（HMAC-SHA256。鍵がなければ入力に戻せません）も残し、結果と一緒に消します（精算しなかった呼び出しには残しません。2026-11-01より前の記録には鍵なしの SHA-256 が入っていることがあり、同じ期間で消します）、無料ツールは道具・経路ごとの1日の回数と、IP アドレスの上位3つの区切りを日替わりの鍵でハッシュした1日の利用者数の推定（無料ツールの入力は当方のデータベースに保存しません）。Cloudflare が自動でとる呼び出しの記録は残していないため、呼び出し元の IP アドレス、そこから推定される地域、User-Agent は当方の記録に残りません。障害の調査のために残すのは、当方のプログラムが書く記録（エラーと裏の処理の要約）だけで、IP アドレス・リクエストのヘッダー・クエリ（URL の ? より後ろ）・本文は書かないようにしています。これらの記録には、Cloudflare がメソッド（GET・POST など）やクエリを除いたパスなど呼び出しの基本的な情報を添えることがあります（パスに入る値、たとえば receipt_id は残ることがあります）。記録は Cloudflare の Workers Logs に最長7日残ります。なお、サービスを届けるために Cloudflare が自社の方針のもとで接続の情報を扱うことはあります。MCP の口では、接続が切れても続きを受け取れるよう、応答（送られた入力を含むことがあります）を届けるまでのあいだ Cloudflare の Durable Object の保存領域に一時的に置き、届けたら通常すぐに消します。IP アドレスは当方のデータベースには保存しません（Cloudflare のログの範囲で Cloudflare が扱います）。無料の呼び出しの上限を数えるため、IP アドレスと User-Agent の先頭 64 文字をまとめた一方向のハッシュを Cloudflare の回数の計数（1分程度）に渡しますが、どちらも保存はしません。
- 消費者庁の景品表示法の命令：このサービスは、消費者庁が公表した景品表示法に基づく命令（国の分）の中継に要るものだけ（公表ごとの相手の会社の名称・法人番号・所在地（公表どおり）、命令の種類・日付・条項、書いてあれば課徴金の額、公表のページと PDF の URL、公表のページの SHA-256、読んだ時刻）を保存します。公表資料にある個人の名前（会社の代表者など）は、保存の前に取り除き、保存も出力もしません。PDF の本文も保存しません。相手が個人・個人事業者だけの公表は記録しません（件数も残しません）。一覧の題も保存しません。照会で送られた法人番号・会社名・所在地は保存しません。
- 目的：決済・二重課金の防止・結果の再取得・会計記録・1日の上限・利用の集計。
- 第三者：Cloudflare（配信・保存）、集金係（Coinbase Developer Platform、予備に PayAI・Dexter。Coinbase で精算した有料の HTTP の口は、Coinbase の公開の一覧に載ることがあります。載るのは口であって、利用者ではありません）、ブロックチェーン（Base 上の取引は公開され、消せません）。
- 保存期間：有料の結果と再試行の照合用の値は精算から30日で一緒に消し、支払いの記録（アドレス・取引ハッシュ・金額・道具・時刻）は7年。消したデータ（保存期間の終わり・削除の依頼）も、データベースの時点復元（Cloudflare D1 の Time Travel）で最長30日は戻せる状態で残り、その後はなくなります。
- 削除依頼・問い合わせ：mk.career.planning@gmail.com（ウォレットアドレスと receipt_id または取引ハッシュを添えてください）。
- 免責：消費者庁が公表した命令の中継・整形であり、消費者庁・日本国政府の公式の一覧・サービスではありません。会社を評価せず、法律・コンプライアンスの助言はしません。必ず公式の公表資料で確かめてください。利用規約もご覧ください。