MantisMeshLast updated: October 31, 2026.
What the service processes
MantisMesh processes public wallet addresses, signed authentication challenges, short-lived sessions, request metadata, encrypted checkpoint and handoff payloads, and payment/usage records. Task identifiers, wallet relationships, retention, callback URLs and other operational metadata are not encrypted as payloads. Recovery registrations refer to encrypted checkpoints; they do not accept a separate recovery payload.
Why we process it
We use this information to authenticate wallet ownership, enforce authorization and quotas, store and retrieve state, coordinate tasks, deliver reviewed callbacks, settle payments and operate the service.
Infrastructure and payment providers
Cloudflare provides hosting, secure connections and storage. PayAI facilitates x402 payments, and Solana transactions are public. These providers may process connection and transaction metadata under their own policies. MantisMesh does not add third-party advertising, visitor analytics or tracking cookies to this website.
Retention and deletion
Objects require explicit expiry of at most 30 days. Expired objects become inaccessible immediately; scheduled physical cleanup can lag. Delete-after-read consumes a payload, with an encrypted same-key retry result retained for up to five minutes, capped by original expiry. Operational and payment records are retained for at most 30 days in the application. Backups and provider logs may have separate retention; blockchain transactions cannot be erased by MantisMesh.
Encryption and access
Payload encryption uses operator-managed application keys. This is not end-to-end or zero-knowledge encryption. The service can decrypt an authorized read. We do not log plaintext payloads or bearer credentials. Never submit private keys, seed phrases or data you cannot lawfully process.