Security

Last updated: August 21, 2026

The first question technical buyers ask is the right one: what exactly do you see? Here's the honest answer.

What we store#

Usage metadata only: model and provider names, token counts, computed costs, timestamps, and the custom fields you attach to events — each capped at 256 characters. That's the entire event shape; see the event documentation.

What we never see#

Prompts and completions. The ingestion API has no field for them — there is nothing to opt out of, because the content of your AI conversations structurally cannot reach us. Your API traffic goes directly to your AI provider; Marginal only receives the metadata your application chooses to send afterwards.

Infrastructure#

• Data lives in a managed PostgreSQL database (Supabase) on Amazon Web Services infrastructure in the Mumbai region (ap-south-1).
• All traffic is encrypted in transit with TLS.
• Access control is enforced at the application layer: every query is scoped to your company and its projects.
• Payments are handled by Paddle as Merchant of Record — card details never touch our servers.

API keys#

Ingestion API keys are scoped to a single project and only authorize sending events — a leaked key cannot read your data or touch your account. Keys can be rotated from the dashboard at any time.

Retention#

Usage events are retained while your account is active. The ingestion request log (raw request debugging) is automatically purged after 7 days. Full deletion of your data is available on request — see our Privacy Policy.

Reporting a vulnerability#

Found something? Email jithin@marginalhq.com — reports are read by the person who wrote the code, and we'll respond quickly.