Security
How Cupelio handles access, usage data and financial records.
Write-only ingest keys
Cupelio ingest keys authorize submission of usage events. They cannot read reports or access your provider account. Usage ingestion does not require your provider credentials.
Encrypted in transit and at rest
Every connection to Cupelio runs over TLS. Your data is encrypted at rest on our infrastructure provider.
Tenant isolation, enforced by the database
Organization data is scoped with Postgres row-level security. Automated tests check cross-organization reads and writes. Public model prices are shared reference data.
Only accounting fields are retained from usage payloads
New usage submissions retain only normalized accounting fields: provider, model, timestamp, token counts and customer, feature and workflow identifiers. Unknown fields, including prompt and response content, are discarded before persistence.
Append-only financial records
Application write paths append financial corrections instead of editing recorded cost and revenue events. Database rules restrict changes by application roles. These controls do not remove administrative access to the database.
Certifications and availability
Cupelio has no SOC 2 or ISO 27001 certification and offers no uptime guarantee.
Questions about any of this: security@cupelio.com.