Trust & data practices
What Veezee stores, how it's protected, and how to leave.
What we store
We keep request and response bodies to support idempotent replay: if you retry a call with the same Idempotency-Key, you get back the exact stored result instead of a second charge. Bodies are kept for up to 30 days and are size-capped. Ledger events (the record of what was charged and when) are kept indefinitely, since they're your billing record.
Telemetry
Operational telemetry uses opaque, hashed identifiers, never raw account or request data. We don't put personal information in telemetry.
Keys
API keys are shown to you exactly once, at creation. We store only a hash of the key, not the key itself.
Authentication
Veezee uses API keys only. There is no OAuth flow.
Billing and cancellation
Paid plans are self-serve through Stripe. Cancel or change your plan any time from the Stripe billing portal linked to your account.