Privacy Policy
japan-agent-api · Operator: MK Career Planning · Last updated: 2026-10-12
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).
- Argument hash: the payment record also keeps an unkeyed SHA-256 hash of the arguments, used to recognise a retried payment. Short or easily guessed inputs can be recovered from such a hash, so treat it as the inputs themselves.
- 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: to investigate faults, Cloudflare Workers Logs for this service are kept for up to 7 days. Query strings (the part of the URL after
?, where GET inputs go) are removed from the logged URLs; values inside the URL path itself (for example a receipt_id) can still appear in these logs.
- 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.
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: 90 days after settlement, then deleted (
get_receipt then returns RECEIPT_NOT_FOUND).
- Payment records (wallet address, transaction hash, amount, argument hash): 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 information published by public bodies (the Japan Meteorological Agency, e-Stat, J-LIS). It is not a forecast, does not issue warnings of its own, gives no legal advice and does not guarantee safety. "No match in checked sources" or "not listed" does not mean there is no impact or that something is unavailable. Always confirm with the official source. 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 で再取得するため。送られた入力を含みます。例：旅程の日付と場所）、支払いの記録に引数の SHA-256（鍵なし。再試行の見分けに使う。短い・推測しやすい入力はハッシュから戻せるので、入力そのものとして扱います）、無料ツールは道具・経路ごとの1日の回数と、IP アドレスの上位3つの区切りを日替わりの鍵でハッシュした1日の利用者数の推定（無料ツールの入力は当方のデータベースに保存しません）。障害の調査のため、このサービスの呼び出しの記録（Cloudflare の Workers Logs）を最長7日残します。記録の URL からクエリ（URL の ? より後ろ＝GET で送られた入力）は除いていますが、URL のパスに入る値（receipt_id など）は記録に残ることがあります。MCP の口では、接続が切れても続きを受け取れるよう、応答（送られた入力を含むことがあります）を届けるまでのあいだ Cloudflare の Durable Object の保存領域に一時的に置き、届けたら通常すぐに消します。IP アドレスは当方のデータベースには保存しません（Cloudflare のログの範囲で Cloudflare が扱います）。無料の呼び出しの上限を数えるため、IP アドレスと User-Agent の先頭 64 文字をまとめた一方向のハッシュを Cloudflare の回数の計数（1分程度）に渡しますが、どちらも保存はしません。
- 目的：決済・二重課金の防止・結果の再取得・会計記録・1日の上限・利用の集計。
- 第三者：Cloudflare（配信・保存）、集金係（Coinbase Developer Platform、予備に PayAI・Dexter。Coinbase で精算した有料の HTTP の口は、Coinbase の公開の一覧に載ることがあります。載るのは口であって、利用者ではありません）、ブロックチェーン（Base 上の取引は公開され、消せません）。
- 保存期間：有料の結果は精算から90日、支払いの記録は7年。消したデータ（保存期間の終わり・削除の依頼）も、データベースの時点復元（Cloudflare D1 の Time Travel）で最長30日は戻せる状態で残り、その後はなくなります。
- 削除依頼・問い合わせ：mk.career.planning@gmail.com（ウォレットアドレスと receipt_id または取引ハッシュを添えてください）。
- 免責：気象庁・e-Stat・J-LIS の公表情報の中継・整形であり、予報ではありません。法的な助言でもありません。安全を保証しません。利用規約もご覧ください。