Privacy Policy
This policy explains the limited operational data collected to run the API, issue pilot keys, prevent abuse, and understand dataset demand.
Information We Collect
We may collect email addresses submitted for API keys or pilot access, role, region, company name if provided, use case, budget intent, requested datasets, hashed API key records, account and credit ledger records, endpoint paths, request parameters excluding API keys, status codes, latency, cache status, user-agent labels, and referrer hostnames.
Information We Do Not Intentionally Store
We do not intentionally store plaintext API keys, payment card numbers, browser cookies, passwords, or full private conversation transcripts. Request parameters named api_key are excluded from analytics records.
How We Use Information
We use operational data to issue keys, enforce rate limits and credits, debug failures, measure demand by dataset and agent type, qualify pilot buyers, improve documentation, and prepare future billing review.
Processors And Storage
During the pilot, operational records may be stored locally for development and mirrored to Supabase when configured. Future payment processing is planned through Paddle, which will process payment data under its own terms when checkout is enabled.
Contact
For access, deletion, or privacy questions, use the contact page. Do not send secrets or API keys in plain text messages.