Wever Labs public policy
Privacy Policy
How the Wever Labs website, free MCP connector, and paid x402 rails process request data, payment authorizations, receipts, and public Base mainnet settlement records.
Last updated September 30, 2026
Scope and operator
This policy applies to weverlabs.com, the free MCP connector at weverlabs.com/mcp-free, and the paid x402 rails at weverlabs.com/mcp. Wever Labs is the publisher and operator for these services.
Paid settlement is live in native USDC on Base mainnet. Mainnet USDC has real monetary value.
Website data
The website and its host may process ordinary request information needed to deliver and secure the site, such as IP address, request time, requested URL, user agent, referrer, TLS and network information, and error or abuse signals.
If you email Wever Labs, we process your address, message, attachments, and related correspondence to respond and maintain a support record.
Free MCP connector data
The free MCP connector provides six anonymous, read-only tools. It requires no account, authentication, wallet, or payment. Requests may include ordinary metadata such as IP address, user agent, requested tool, request identifiers, and timing, as well as inputs supplied for the free computations and their results.
Anonymous access does not mean that no request data is processed. The connector and its infrastructure process requests to provide results and maintain availability and security.
Paid x402 rail data
The paid MCP rails process public wallet addresses, payment authorization payloads, and onchain settlement records for native USDC on Base mainnet. Signed-wallet requests also use wallet verification and usage records to apply the shared allowance of 10 free calls per rolling 30 days, followed by per-tool pricing.
Depending on the tool, requests may also include authentication information, signed mandates, agent and provider identifiers, network and asset identifiers, service inputs and results, fulfillment evidence, receipt records, ledger entries, replay-protection identifiers, recovery records, and verification outcomes.
Compatibility reports store the named client, connection stage, success state, optional bounded notes, and a one-way digest of any reporter value. External activity remains unclassified unless independent evidence supports another classification. Synthetic activity is never counted as organic use.
Public blockchain data
Base mainnet settlement data is public and immutable. Transaction hashes, public addresses, token transfers, block numbers, timestamps, network identifiers, and contract events may be visible to anyone and copied by blockchain nodes, explorers, and other services.
Public blockchain data is not controlled by Wever Labs and cannot be changed or deleted by Wever Labs. Native USDC on Base mainnet has real monetary value.
How data is used
- Provide the free connector, discovery, connection, mandate, settlement, fulfillment, verification, receipt, and recovery functions.
- Authenticate protected requests and enforce owner-defined authority.
- Prevent replay, duplicate economic effects, fraud, abuse, and unauthorized access.
- Reconcile ledger, settlement, fulfillment, evidence, and receipt records.
- Maintain availability, measure compatibility, investigate failures, and improve protocol support.
- Respond to support, security, legal, and operational requests.
Retention
Wever Labs does not currently apply one fixed deletion period to every service record. Durable transaction, ledger, mandate, fulfillment, evidence, receipt, reconciliation, and replay-protection records, including records associated with mainnet settlement, are retained for the operating life of the service and longer when needed to preserve audit integrity, resolve disputes, investigate security events, or meet legal obligations.
Operational telemetry and compatibility records are retained while useful for service operation, reliability, security, and protocol support. Hosting and infrastructure logs follow the applicable provider configuration. Support correspondence is retained as needed to resolve the request and maintain appropriate business records.
Public blockchain data may remain available indefinitely, regardless of Wever Labs retention choices.
Service providers and public systems
Wever Labs uses Netlify for website hosting and Cloudflare for service infrastructure. Base mainnet processes public blockchain transactions. MCP Registry provides public MCP discovery listings. Email and security providers may process support correspondence and protective signals.
Following an external link, including an explorer or registry listing, subjects your request to that service's own practices.
Security practices
Wever Labs separates the anonymous, read-only connector from paid economic tools. Paid rails validate payment authorizations and apply replay controls. Tools requiring signed authority validate that authority for the requested action. Signing material and infrastructure secrets are kept out of public website responses.
No internet system is perfectly secure. Report a suspected vulnerability to hello@weverlabs.com. Do not include private keys, seed phrases, or live credentials in email.
Requests and choices
You may ask about access, correction, or deletion of information associated with you by contacting hello@weverlabs.com. We may need to verify the request and may retain records where integrity, security, legal obligations, or public blockchain limits prevent deletion.
Do not include private keys, seed phrases, or unrelated credentials in tool inputs or support correspondence. Avoid submitting sensitive personal information that is not needed for your request.
Changes and contact
We may update this policy as the website, services, processors, or legal requirements change. The updated date identifies the current version.
Privacy, general questions, and security reports: hello@weverlabs.com
Support: weverlabs.com/support