This page explains the categories of information the platform may process to provide accounts, API access, security, usage visibility, and support.
The service may process account information you provide, authentication and security records, API-key metadata, API request and usage records, subscription and payment activity, support interactions, and technical information needed to operate and secure the platform.
Information is used to provide and secure accounts, authenticate API requests, enforce plans and limits, diagnose failures, prevent abuse, maintain audit history, deliver requested notifications, and improve service operations.
The dashboard uses session mechanisms required for sign-in and authenticated access. Operational cookies should be treated as necessary service functionality rather than advertising cookies.
Operational data may be retained as needed for account administration, security, auditing, dispute handling, and legal obligations. Reasonable technical and organizational safeguards should be maintained around credentials and stored service data.
Do not place passwords, live API keys, admin tokens, or other secrets into public support messages. Keep your credentials secure and rotate them if you believe they have been exposed.
This policy may be updated as the service, infrastructure, or legal requirements change. The effective date above should be updated when material revisions are published.
Support, debugging, and billing conversations never require credentials. Use request IDs, endpoint paths, and redacted responses instead.
Privacy questions use authenticated support.Account-specific privacy questions are handled through authenticated support, so your workspace context stays attached and secrets stay out of public channels.
