Information We Collect
- Account information such as email address, workspace name, and login method.
- API key metadata such as key prefix, status, creation time, and last-used time.
- Usage metadata such as requested model, routed model, provider, token counts, cost, latency, and status.
- Recharge and billing metadata such as amount, order status, payment reference, and timestamps.
- Support messages you send to us.
API Content
API requests and responses are processed to provide routing, billing, abuse prevention, debugging, and reliability. We may retain limited logs or diagnostic previews when needed for operations, security, or billing review.
Payments
Payment details are processed by our payment provider. inCat stores payment status, order identifiers, and billing records needed to credit your prepaid balance and resolve support requests. We do not store full card numbers.
How We Use Information
- to create and secure accounts;
- to route API requests and calculate usage charges;
- to manage prepaid credits, invoices, refunds, and support;
- to detect abuse, fraud, service misuse, and security issues;
- to improve reliability, routing quality, and cost controls.
Sharing
We share information with infrastructure, payment, authentication, analytics, and model provider services only as needed to operate inCat. API content may be sent to the model provider selected by the routing layer.
Contact
To request support or ask about privacy, contact [email protected].