Privacy notice

How data is handled by the current Chatsax application. Effective September 7, 2026.

Data you submit

API inputs, URLs, documents, images, and request options are processed by Chatsax and forwarded to the selected upstream provider to deliver the requested service. Do not submit information you are not authorized to share.

Operational records

The gateway records key identifiers, routes, model names, response status, latency, and available token usage. Application usage records do not intentionally store prompt or document bodies. The dashboard currently queries a 30-day reporting window; this is not an automatic deletion promise.

Local device storage

Language and theme preferences are saved locally. Account sessions use an HttpOnly cookie. Manually connected API keys are kept in session storage, or local storage when Remember is selected. Log out or disconnect to remove local access. No advertising or analytics cookies are installed.

Anonymous API access uses an essential cookie and a random device identifier to restore your key. Hashed network identifiers limit trial issuance.

Service providers

Cloudflare hosts the application, accounts and billing ledger. Jina processes API inputs. Resend delivers verification and reset emails. Stripe processes card payments and stores saved card details; Chatsax receives payment identifiers and limited card metadata, not full card numbers. Alipay and WeChat payments use the configured payment gateway. Google or GitHub supply verified identity details if selected. Each provider applies its own data policies.

Questions and requests

Use the contact form for account, billing and data-handling requests. Include the relevant order or request identifier and never include passwords or API keys.

These statements describe Chatsax, not the policies of Jina or Cloudflare. Jina · Cloudflare