Privacy Policy

Last updated: September 29, 2026

Who is responsible for your data

The controller of the personal data described here — the business that decides why and how it is processed — is KIZUNA Creation, a sole proprietorship established in Japan, which operates vet402. Contact the controller at support@vet402.com. In Japan, KIZUNA Creation is the business handling personal information under the Act on the Protection of Personal Information (APPI).

vet402 is operated by KIZUNA Creation. See our Legal Notice for how operator disclosure works. Privacy questions or deletion requests: support@vet402.com.

Data we collect

Account email address
API usage logs (agent IDs, wallet addresses queried, scores returned)
Customer whitelist/blacklist entries you configure
Billing metadata via Stripe (we do not store card numbers)
Request metadata for security and rate-limiting — including the IP address a request is made from — kept only as long as needed to run those controls
The public blockchain addresses and ERC-8004 agent identifiers we score, together with the on-chain activity we read about them and the scores we derive (see people we score who are not our customers below)
If you ask us to correct a score, whatever you send us to make that case — which may include an email address and a wallet signature you provide voluntarily
Record notifications you asked for (record_subscriptions): the email address you entered, which endpoint record it follows, what kind of notification it is, the free-text reason you gave if you gave one, the last verdict we notified you about, and a one-way hash of the IP address the request came from (used to rate-limit sign-ups, never stored in the clear)
Notification consent (record_subscriptions): a one-way hash of the link we emailed you to confirm or stop record notifications, and when you confirmed or unsubscribed. Nothing but the confirmation email is sent until you confirm, and every notification carries a one-click unsubscribe link
Waitlist entries (waitlist_entries): the email address you entered, which offering you registered interest in, and the free-text note you added if you added one
Pre-publication notices to sellers: the business contact email address we wrote to, the seller's name and endpoints, the measurement facts in the message, and any reply. See emails we send to sellers before we publish below
Disputes (disputes): the endpoint the dispute is about, the subject and reason you wrote, and the wallet address plus the signed message and signature that prove control of it. This table holds no email address; if you write to support instead, that correspondence lives in the support inbox

Wallet addresses

Wallet addresses are public blockchain identifiers. We treat them as pseudonymous data and do not intentionally collect direct personal identifiers beyond your email.

Legal basis (GDPR / UK GDPR)

Where the EU or UK GDPR applies, we rely on the following lawful bases. If you are in a jurisdiction with a different framework (for example Japan's APPI or a US state law), equivalent bases apply under that law.

Performance of a contract (Art. 6(1)(b)) — creating and running your account, authenticating API keys, metering usage, and answering support.
Legitimate interests (Art. 6(1)(f)) — scoring public blockchain addresses and agent identifiers so that operators can assess payment risk, together with securing the service and preventing abuse. The interest is providing an independent fraud-risk signal for on-chain payments; the data is already public on-chain; and anyone scored has a free route to object and to have factual errors corrected (see below). The same basis covers the pre-publication notices we email to sellers, whose interest is to hear about a result before it is published. You can ask us for our balancing assessment.
Legal obligation (Art. 6(1)(c)) — keeping billing and tax records for the period the law requires.
Consent (Art. 6(1)(a)) — we do not currently rely on consent for any processing (our analytics is cookieless and needs none). If that ever changes we will ask for it separately and you will be able to withdraw it.

Emails we send to sellers before we publish

Before we publish results that name a seller, we may email that seller to tell them what we measured — for example that paid calls to their endpoint were not delivered — and when we plan to publish, so they can correct us or fix the problem first. These notices come from records@vet402.com and replies go to support@vet402.com. They report measurement facts; they are not advertising and we do not use them to sell anything.

Where the address comes from. We write to a business contact the seller has published: the contact in its public listing in an x402 discovery catalog, or the support or contact address published on the seller's own website or domain. We do not buy address lists and do not guess personal addresses.

How to stop them. Reply to a notice, or write to support@vet402.com, and say you do not want these notices; one person reads that inbox and we will not send further pre-publication notices to that address. Stopping notices does not stop the measurement or its publication, which follow our published methodology either way. We keep the message and any reply in the support inbox and in Resend's sending log; we do not add these addresses to any mailing list.

Retention

Query logs are retained per your plan (90 days Free, 1 year Pro+). You may request deletion of your account by contacting support.

Record notifications, waitlist entries and disputes are kept until you ask us to remove them, because each of them exists to be acted on later: a notification has to outlive the change it is watching for, and a dispute is part of the record of a correction. None of the three expires automatically — no scheduler deletes them — so the route is a person. Mail support@vet402.com and say which one you mean; we remove it by hand within 7 days and confirm to the same address. Replying to a notification email reaches the same inbox and counts as the same request. Where a dispute has already produced a published correction, we remove your contact details and keep the fact that a correction was issued, which is the entry other people rely on — the grounds for that are in people we score who are not our customers below.

Subprocessors and third parties

We use the providers below to run the service. Each processes only the data its function needs, under its own data-processing terms. We do not sell personal data, and we do not share it with anyone for their own marketing.

Vercel (United States) — application hosting and edge delivery; sees request metadata including IP addresses.
Neon (United States) — the PostgreSQL database that stores accounts, API key hashes, usage logs, and scores.
Stripe (US) — billing and payment processing for paid plans; holds card data directly, which we never see or store.
Alchemy (US) — Base blockchain RPC and indexing; receives the public wallet addresses we read on-chain data for.
Blockscout — block-explorer API used to read public on-chain data; receives the public wallet addresses we query.
Solana Labs public mainnet RPC (api.mainnet-beta.solana.com) — used to re-read Solana settlements on-chain; receives transaction signatures and wallet addresses, all of which are already public on that chain.
Resend (United States) — email delivery for the record-change notifications you asked for, for replies about a dispute, and for the pre-publication notices we send to sellers (see above); receives the recipient email address and the body of that message. We do not use it for marketing email and we send no newsletter.
Plausible Analytics (European Union) — aggregate traffic statistics. Plausible is cookieless and sets no persistent identifier; what your browser sends it is described under information your browser sends to a third party below.
GitHub (United States) — hosts vet402's public source code and issue tracker. If you open an issue or pull request there, it is published under your GitHub account and GitHub's own terms apply.

This list can change as the service evolves; the current list lives on this page, and we will update it here before a new subprocessor starts handling personal data. If you need it confirmed in writing for a procurement review, ask us by email.

Cookies

We use one cookie, and only after you log in to the dashboard: a strictly-necessary session cookie that keeps you signed in. It is set httpOnly, secure, and sameSite=strict, and it is used for nothing but authentication. Because it is strictly necessary, it needs no consent. We set no advertising or cross-site tracking cookies, and our analytics (Plausible) is cookieless, so there is no consent banner to click through.

Where your data is stored

The operator administers the service from Japan. The data itself is stored and processed by the providers above, in these countries:

United States — the database (Neon, on AWS in the US East (Ohio) region), the application servers (Vercel, Washington, D.C. region; pages are also cached on Vercel's worldwide edge network), email delivery (Resend), billing (Stripe), and source code hosting (GitHub).
European Union (Germany) — traffic statistics (Plausible).
Japan — the support inbox is read, and the service is operated, from Japan.

Personal data originating in the EEA or UK is therefore transferred to and processed in third countries, including the United States and Japan. We rely on our providers' standard data-processing terms, including standard contractual clauses where they apply, for those transfers. Each of these countries has its own data-protection law, and the protection there may differ from the protection where you live.

How we protect your data

Responsibility. KIZUNA Creation is responsible for handling personal data in vet402, and access to the production database and hosting accounts is limited to the operator's accounts.
In transit. The site and API are served over HTTPS.
Stored secrets. API keys are stored as keyed hashes, not in the clear; the IP address behind a notification sign-up is stored only as a one-way hash; and secrets are redacted from server logs.
Retention. Query logs are deleted on the schedule in Retention by a scheduled job.
Facilities. We run no servers of our own; the data sits with the providers named above, in the countries named above.

Information your browser sends to a third party

When you open a page on vet402.com, your browser loads a script from plausible.io and sends Plausible Analytics (Plausible Insights OÜ) the address of the page you are on (including any campaign parameters in it), the referring page, your screen width, and the names of a few events we define, such as a button click, with non-identifying details about them. Plausible also receives your IP address and browser user-agent with the request. According to Plausible's published data policy, it uses them only to count unique visitors with a daily-changing hash and to derive the country, browser and device type, and does not store the IP address. We use the result for aggregate traffic statistics only. Plausible sets no cookie. This is the only third party our pages send information to from your browser; Stripe receives your details only on its own checkout and portal pages.

People we score who are not our customers

vet402 scores blockchain addresses and agent identifiers that belong to third parties — people and businesses who never opened an account with us. If one of those addresses can be traced to you, the data-protection law where you live may treat our score as personal data about you, and you have rights over it even though you are not our customer.

The data involved is the public on-chain address, the public transaction activity we read about it, and the score we derive from that activity. We do not attach names, contact details, or off-chain identity to an address unless the person behind it gives them to us — for example by using the correction route.

How we handle erasure and objection, concretely. You can ask us to correct a score built on a factual error, and you can object to our scoring your address. The free route for both — no account, no fee — is section 8 of the Terms, and every factual correction we make is published on our corrections log. You also have the rights to erasure (Art. 17) and to restriction of processing (Art. 18), and we weigh every verified request individually — we do not refuse by policy, and "we never delete anything" is not an answer we give. Where a legal ground we may rely on — freedom of expression and information (Art. 85), the establishment, exercise, or defense of legal claims, or fraud prevention — outweighs your request in your specific situation, we respond with restriction rather than nothing: we stop publishing or stop scoring the entry concerned, annotate it, and correct anything inaccurate, instead of leaving it up unchanged. Where no such ground prevails, we delete or anonymize the data. What we will not do is silently rewrite our own record to hide a mistake we made — accountability for our errors and your rights over your data are not in conflict, and we intend to honor both. Either way we tell you our decision and our reasons, and if you disagree you can complain to your data-protection authority.

A score is an opinion, not an accusation of fact. A low score or a BLOCK is our read of a public record on a given day, not a statement that any person is a criminal or a fraudster; the distinction, and why we draw it, is set out in sections 6 and 7 of the Terms.

Your rights over your data

Depending on where you are, you may have the right to access the personal data we hold about you (GDPR Art. 15), to have it corrected if it is wrong (Art. 16), to have it deleted (Art. 17), to ask us to restrict a particular use of it (Art. 18), to object to processing based on our legitimate interests (Art. 21), to receive it in a portable format (Art. 20), and to withdraw consent where we relied on consent. We weigh each request on its own facts — none of these is answered with a blanket policy — and we do not make automated decisions with legal or similarly significant effects about you as a user of this site.

To exercise any of these, email support@vet402.com from the address on the account, or tell us which address it was. One person reads that inbox; we aim to acknowledge within 5 business days (Japan time) and to complete the request within 30 days. There is no charge. We will say no only where the law lets us — for example where we must keep billing records for tax purposes — and we will say which exception we are relying on rather than just declining. If you are unhappy with how we handled it, you can complain to your local data-protection authority.

Two things we cannot do, and would rather say plainly than leave you to discover. First, we cannot erase the blockchain: wallet addresses and their transaction history are public records on Base that we read, not records we created or control, so deleting your vet402 account does not remove anything from the chain. Second, if you believe a trust score about an address is wrong — which is a different problem from a privacy request — the route for that is in section 8 of the Terms: it is free, needs no account, and works whether or not you are a customer.