Data handling & retention

This page describes what Nodaryx does and does not store when you call the API or use the Playground. It reflects how the platform actually behaves.

What we do NOT store

Nodaryx does not persist the content of your requests. The following are never written to our database or application logs:

• Prompt / message content you send to a model
• Model response text returned to you
• Uploaded file contents (see Files)
• Web-search query text issued on your behalf

Application logs record status and metadata only — never the body of a request or response.

What we DO store

To meter usage, bill accurately, and support troubleshooting, we record metadata only for each request:

• Timestamp, model, and request status (success / failure / timeout)
• Token counts (input / output / total)
• Cost and platform charge
• Latency and error code (when a call fails)
• The API key, organization, subscription, and product the call belongs to

This is the data behind your Usage page and your invoices. It contains no prompt or response text.

Uploaded files are ephemeral

Files you upload in the Playground are parsed for text in memory to build the request. The extracted text and the original file are not persisted — once the request is served, they are gone. Nothing about a file's contents is written to storage or logs.

Wallet, orders, and audit

• Wallet transactions and recharge orders are retained as financial records.
• Admin actions on an account (tier / status / plan / credit changes) are written to an audit log — the action, actor, reason, and a redacted before/after value, never request content.
• Full API keys and provider keys are never exposed after creation; only a key prefix is shown.

Retention & deletion

Usage metadata, billing records, and audit logs are retained to provide your usage history, invoices, and account security. Because we never store prompt or response content, that content has nothing to delete.

For account data export or deletion requests, contact support.