Effective date: October 15, 2026 · Last updated: November 2, 2026
This Privacy Policy explains how MioDio LLC, a Florida limited liability company ("MioDio," "we," "us"), collects, uses and shares information when you or your software agents use the Meridian API at meridian.miodiollc.com (workers.miodiollc.com remains a permanent alias), its documentation and the Meridian MCP package (the "Service"). Meridian has no accounts, no signup, and no tracking cookies, and we do not sell personal information.
a. Request data you send. Blockchain addresses (wallets, vaults, tokens), amounts, and other parameters in your requests. The parameter-drift and transaction-simulation routes also receive the full unsigned transaction you are about to sign (from, to, value, data, and optional gas). Drift may also receive an EIP-712 typed-data payload. Both routes may receive an intent object (action, recipient/spender, token, amount, slippage, expected contract). Intent fields may include free text if you put it there. Public blockchain addresses are pseudonymous. They can become personal data if linked to an identifiable person, so we treat them with care.
b. Payment data. For paid calls: the paying wallet address, the signed x402 payment authorization, amount, asset, network, transaction hash, and settlement status. This is recorded permanently on the public Base blockchain by design, and we cannot alter or delete it. After settle, we store for 30 days the paying wallet address, the settlement transaction hash, and a nonce fingerprint (a hash of the authorization nonce, not the nonce itself), together with a signed receipt (receipt id, route template, request and response hashes, a short verdict summary, the settled or advertised route amount/asset/payTo/scheme, timestamp, key id, and signature) and a settlement index linking the transaction or payer+nonce fingerprint to that receipt. The receipt id is a bearer secret; we do not return it from the free payment-status route.
c. Technical data. When any request reaches our infrastructure, our host (Cloudflare) processes your IP address, approximate location derived from it, user-agent, request path and query, timestamps, and response status for delivery, security and abuse prevention. The Meridian application does not write request IP addresses or query parameters to its own database. Addresses you send to GET /v1/payment/status are looked up only in our settle index (no RPC). Addresses you send to POST /v1/payment-check are queried against public chain data and are logged only as usual request logs. Anyone can query any address; that data is already public on-chain.
d. Communications. If you email corp@miodiollc.com, we keep your email address and message.
e. Optional referral tokens. If you add a ref query parameter on the homepage, /docs, or a free /v1/demo/* URL, we may write a sanitized copy of that token (letters, numbers, ., _, and - only, truncated) plus the request path to Cloudflare Workers Logs so we can count referrals. We do not write the token to KV, and we do not store an IP address or other personal data with it. Unusable or empty tokens are discarded and never logged raw.
We do not intentionally collect names, government IDs, financial account numbers, or sensitive personal information, and ask that you not send them.
Legal bases (EEA/UK users). Performance of a contract (providing paid calls), legitimate interests (security, fraud prevention, service improvement, record-keeping), and legal obligation (tax and accounting records). We do not rely on consent for core processing, and we do not do automated decision-making that produces legal effects about you. Our risk and screening outputs describe addresses, not people.
We do not sell or "share" (for cross-context behavioral advertising) personal information. We disclose it only to: - Service providers acting for us: Cloudflare (hosting, CDN, logs, KV storage), blockchain RPC providers (which receive the addresses we query and, for transaction simulation, the full unsigned transaction so they can dry-run it), x402 payment facilitators (which receive the payment authorization), and GitHub (code hosting and scheduled data refresh jobs, which do not receive request data); - Public blockchains: settlement data is public by nature; - Legal and safety: when required by law, subpoena or court order, or to protect our rights, users or the public; - Business transfers: to a successor in a merger, acquisition or asset sale, subject to this Policy.
expirationTtl). After that they expire. They are a record of what was returned, not a payment credential. Past the Workers Free KV write cap, a receipt lookup may 404 and payment status may say not_found even after a successful paid call.We use industry-standard measures, including TLS encryption in transit, a managed edge host, least-privilege access to secrets, and no storage of private keys from users. No system is perfectly secure. If a breach of personal information occurs, we will notify affected persons and regulators as required by law, including Fla. Stat. § 501.171.
Depending on where you live, you may have rights to access, correct, delete, port, or object to or restrict processing of your personal information, and to withdraw consent where we rely on it. These include rights under the EU/UK GDPR and U.S. state privacy laws where they apply. To exercise them, email corp@miodiollc.com. Because we have no accounts, we may ask you to prove control of a wallet (for example, by signing a message) or to provide the transaction hash and approximate time of the request. We will not discriminate against you for exercising your rights. EEA/UK residents may also complain to their local data protection authority. We respond within the time required by law (generally 30–45 days).
Note: we cannot delete data recorded on a public blockchain, and we may keep data we must retain by law.
California residents. We do not sell or share personal information, and we do not use or disclose sensitive personal information. Categories we collect (last 12 months): identifiers (IP address, blockchain address), commercial information (paid-call records), internet activity (request logs), and geolocation approximated from IP. We collect them for the purposes in Section 2 and disclose them only as in Section 3.
We are based in the United States, and our providers may process data in the U.S. and other countries. Where GDPR applies, transfers rely on our providers' Standard Contractual Clauses or the EU-U.S. Data Privacy Framework, as applicable.
The Service is for businesses and developers and is not directed to children under 18. We do not knowingly collect children's personal information.
The API sets no tracking or advertising cookies. Our host may set strictly necessary security cookies on HTML pages, for example for bot protection.
We may update this Policy by posting a new version with a new "Last updated" date. If changes are material, we will note them on the Service.
MioDio LLC, Attn: Privacy · 755 Monroe Rd, Unit 470067, Sanford, FL 32747, USA · corp@miodiollc.com