Privacy
- Service operator
- AgentRanking
- Jurisdiction
- local-vm
- Contact
- [email protected]
This policy describes the data the AgentRanking control plane processes to operate the inference marketplace, billing and provider payouts. It distinguishes synchronous prompts from asynchronous artifacts because their retention differs.
Account and workspace data
The service stores user identity, workspace membership, roles, API-key metadata and session metadata. Session cookies are secure, HttpOnly and host-only. Full API-key secrets are shown once; only a hash is stored. Wallet addresses are stored with their chain namespace and are displayed according to the chain's canonical formatting.
Prompts and generated output
Synchronous prompts remain in process memory and are not logged. Asynchronous inputs and generated outputs are stored as bounded encrypted local files with workspace ownership, random paths, integrity digests and a default 24-hour expiry. PostgreSQL stores metadata and references, not prompt bodies. A repeated idempotent non-streaming request is rejected as a replay; the result body is not cached for redelivery.
Streaming output is delivered incrementally. The server records usage and billing metadata rather than treating every token as a durable message log.
Operational telemetry
The control plane records request IDs, status codes, latency, resource ownership and security-relevant audit events. Authentication secrets, signatures, full wallet challenges and request payloads are redacted from logs. Support staff do not receive authentication secrets, wallet signatures or raw payment-request payloads; access to financial evidence is separately role-gated and audited.
Chain data
Deposits and payouts inherently publish wallet addresses, transaction hashes or signatures, amounts and network metadata on public blockchains. The platform additionally stores deposit invoices, scanner observations, reconciliation evidence and treasury configuration. Transaction hints supplied by a client are untrusted until verified by the scanner.
Cookies and local storage
A host-only session cookie maintains authentication and a CSRF cookie protects state-changing requests. Browser contribution additionally keeps a local install key in this browser's storage. There is no third-party advertising script and no remote font fetch in the application shell.
Provider device data
Provider enrollment binds a device identity public key. Private keys remain on the provider device. The control plane records device inventory, generation, heartbeat and control-session metadata needed to route work and detect stale capacity. Workspace prompts and artifacts are not exposed to other providers or workspaces.
Retention and access
Retention varies by record: usage lines and financial journal entries are durable, exports are short-lived, async artifacts default to 24 hours, and operational logs follow the operator's documented retention. Support access is scoped and audited. Workspace deletion is handled by the operator on request; data is removed or de-identified according to financial-record and legal retention obligations.
Requests
Privacy and data requests are handled through the support channel shown in the authenticated console. Identity and workspace ownership are verified before data is disclosed or changed; a wallet connection alone is not a step-up.
This page is operator-owned content. The operator may update it when data handling or legal requirements change.
