Privacy Policy
jp-entity-evidence · 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: request logging (Cloudflare Workers Logs) is turned off for this service, so the names, places or other inputs you send are not kept in a request log.
- MCP responses: this service does not write MCP responses to storage; each response is sent directly over the connection.
- 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.
- Names passed to our gBizINFO relay: a company name you enter may be passed to our own gBizINFO relay (jp-gbizinfo) to find its corporate number. That relay records the name only as an unkeyed SHA-256 hash; short or easily guessed names can be recovered from such a hash, so treat it as the name itself. Batch checks (entity_evidence_batch, paid): the companies you send (names, corporate numbers, registration numbers, address hints, domains) are part of the paid result. We store that result, including those inputs and the evidence returned for each company, for 30 days after settlement so that you can fetch it again with get_receipt, then delete it; with it we keep only a keyed one-way value of the arguments to recognise a retry with the same payment. Each company is checked through our own relays in the same way as the free check (names may be passed to our gBizINFO relay as described above). If no company could be checked, nothing is charged and no result is stored for retrieval. The payment record (wallet address, transaction hash, amount, tool, time) is kept for 7 years for accounting and does not contain the companies you sent. Corporate numbers passed to our National Tax Agency relay: the corporate number used for a lookup (the one you entered, or the one found by name) is passed to our own relay of the National Tax Agency Corporate Number System Web-API (jp-corporate-number). That relay records the corporate number as sent, with the time and the result status, for 366 days to show that it makes no bursts of access to the National Tax Agency, and caches the agency's answer for up to 1 day. When you enter a company name without a corporate number (and the name does not look like a person's name), that name is also passed to the same relay to search the agency's records for its corporate number; the relay records the name only as an unkeyed SHA-256 hash (short or easily guessed names can be recovered from such a hash, so treat it as the name itself), with the time and the result status, for 366 days, and caches the answer for up to 1 day. A corporate number identifies a corporation or other organization, not a person.
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: turned off for this service. 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 what official Japanese public records state, through relays of the same operator, for reference. It is not an official service of any Japanese authority, not legal, compliance, tax or investment advice and not an assessment of any organization or person. A sanctions screening without a match is not a statement that a transaction is permitted. Confirm on the official sources. Names that look like a person's name are screened only against the MOF asset-freeze list; this service does not profile individuals. 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 の Workers Logs）を止めており、送られた名前・場所などの入力は呼び出しの記録に残りません。MCP の応答は保存に書かず、そのまま接続で返します。IP アドレスは当方のデータベースには保存しません（Cloudflare のログの範囲で Cloudflare が扱います）。無料の呼び出しの上限を数えるため、IP アドレスと User-Agent の先頭 64 文字をまとめた一方向のハッシュを Cloudflare の回数の計数（1分程度）に渡しますが、どちらも保存はしません。
- Gビズインフォの中継へ渡す名前：入力された会社名は、法人番号を探すために、当方の Gビズインフォの中継（jp-gbizinfo）へ渡すことがあります。中継の側では名前を鍵なしの SHA-256 のハッシュで記録します。短い名前や推測しやすい名前はこのハッシュから元に戻せるため、名前そのものとして扱ってください。まとめての確認（entity_evidence_batch・有料）：送られた会社（名前・法人番号・登録番号・住所の一部・ドメイン）は有料の結果に含まれます。get_receipt で取り直せるよう、入力と各社の確認結果を含む結果を精算から30日保存し、その後に消します。あわせて残すのは、同じ支払いでの再試行を見分けるための、入力から秘密の鍵で作った一方向の値だけです。各社は無料の確認と同じく当方の中継を通じて確かめます（名前を Gビズインフォの中継へ渡すことは上記のとおりです）。1社も確かめられなかったときは課金せず、取り直し用の結果も保存しません。支払いの記録（アドレス・取引ハッシュ・金額・道具・時刻）は会計のため7年保存し、送られた会社の情報は含みません。国税庁の中継へ渡す法人番号：照会に使う法人番号（入力されたもの、または名前から見つけたもの）は、当方の国税庁 法人番号システム Web-API の中継（jp-corporate-number）へ渡します。中継の側では、国税庁へ短時間に大量のアクセスをしていないことを示すため、法人番号を送ったとおりに時刻・結果の状態とともに366日記録し、国税庁の応答を最長1日キャッシュします。法人番号を入れずに会社名だけを入力したとき（人の名前らしくない場合）は、国税庁の記録から法人番号を探すため、その名前も同じ中継へ渡します。中継の側では名前を鍵なしの SHA-256 のハッシュで、時刻・結果の状態とともに366日記録し、応答を最長1日キャッシュします。短い名前や推測しやすい名前はこのハッシュから元に戻せるため、名前そのものとして扱ってください。法人番号は法人などの団体を示す番号で、個人を示すものではありません。
- 目的：決済・二重課金の防止・結果の再取得・会計記録・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 または取引ハッシュを添えてください）。
- 免責：公的な記録に書かれていることを、同じ運営者の中継を通じて参考のためにまとめたものであり、日本の行政機関の公式のサービスではありません。法務・コンプライアンス・税務・投資の助言ではなく、組織や人を評価するものでもありません。制裁の照合で該当が無いことは、取引が許されることを示しません。公式の情報源で確かめてください。人の名前とみられる入力は財務省の一覧の照合だけに使い、個人の調べ上げはしません。利用規約もご覧ください。