Nock privacy policy

Publisher: Nock / nock.tools. Updated 2026-09-01.

Who we are

Publisher: Nock, operating nock.tools and www.nock.tools. Nock is a marketplace of pay-per-call MCP tools for AI agents. Contact: hello@nock.tools or support@nock.tools. Origin owner: frog42 (repository frog42/nock). We do not sell personal data.

Prepaid credits and Stripe

Paid tools deduct prepaid Nock credits. Credits are purchased through Stripe Checkout. Nock currently runs Stripe in TEST mode (sk_test keys, test cards). If live mode is enabled later, live Stripe charges would apply to live cards. Stripe receives wallet metadata we attach to Checkout (wallet id) plus whatever Stripe collects to process payment. Nock does not store full card numbers.

Wallet id

A wallet id is an agent-chosen string (tool argument `wallet` or header X-Nock-Wallet). If omitted, Nock may derive a fallback such as ip:<client-ip> so credits and rate limits can be scoped. Treat wallet ids as identifiers, not secrets.

Tool inputs and outputs

When you call a tool we process the arguments you send (domains, URLs, VAT numbers, names, repo ids, email addresses, PDF URLs, and similar). Successful calls return strict JSON facts. Failed paid calls that throw invalid_input are not charged. Results may be cached about 24 hours so repeat calls are not billed again.

Third-party public data

Paid tools fetch third-party public data on your behalf. Depending on the tool, that includes: RDAP (rdap.org) for live WHOIS/IP cards; OpenStreetMap Nominatim for geocoding; GitHub REST API for public repository cards; EU VIES for VAT checks; OpenSanctions and OFAC SDN public lists for sanctions screening; YouTube official timedtext/caption tracks; crt.sh certificate transparency logs; URLhaus (abuse.ch) for URL risk flags; ipwho.is for IP geolocation; customer-requested public HTTP/DNS/TLS endpoints when you call a fetch or inspect tool; Stripe for prepaid credit Checkout and webhooks. Those operators see the request Nock makes (for example the hostname or VAT number you asked about) under their own policies. Nock does not scrape behind logins or scan private/localhost networks.

Logs and retention

The prepaid credit ledger is in-process memory on the Node host (not a customer CRM). Catalog demand from request_tool is stored as private Vercel Blob JSON. Hosting logs (Vercel) retain request metadata such as path, status, and IP for a limited period under Vercel’s policies. Stripe retains payment records under Stripe’s policies. We do not keep a separate marketing database of tool payloads. Cached tool results expire after about 24 hours.

No sale of PII

Nock does not sell personal information, does not run ads, and does not rent wallet ids or tool arguments to data brokers. request_tool strips or refuses obvious secrets; do not send passwords, API keys, or private credentials.

Contact

Privacy questions: hello@nock.tools or support@nock.tools. If those mailboxes are not live yet, use the Origin owner on frog42/nock.

Contact

hello@nock.tools · support@nock.tools. Mailboxes may not be staffed yet. You can also reach the Origin owner via the frog42/nock repository. Origin: frog42/nock.