Data
What TurboFinOps processes, where it is stored, how it is protected and how long it is retained.
Account data
Email, name, organization and role context.
Cloud metadata
Resource IDs, names, regions, sizes, costs and tags.
Savings and findings
Rule signals, severity, status, estimated impact, receipt checkpoints and verification notes.
Action history
Requests, approvals, executions, outcomes and correlation IDs.
Audit logs
Immutable state-changing events used for receipt and evidence review.
Billing data
Stripe customer ID, plan and usage counters.
TurboFinOps is a metadata platform, not a workload data platform.
Storage bucket contents
Database contents
Application logs
Network packet data
Source code
End-user workload data
Tenant isolation
Every database query is scoped to organizationId and membership is validated server-side.
Credential safety
Cloud and AI secrets are encrypted at rest, never logged and never returned in API responses.
Transport
All browser, API and provider communication uses TLS where supported by the integration path.
Retention controls how long operational metadata, savings signals, receipt evidence and audit history remain available after collection. Enterprise customers can negotiate custom periods for regulatory or procurement requirements.
| Plan | Resources & findings | Audit logs | Post-cancellation handling |
|---|---|---|---|
| Free | 30 days | 30 days | 30 days after account deletion request |
| Professional | 6 months | 6 months | 30 days after account deletion request |
| Enterprise | Custom contract term | Custom contract term | Defined in order form / DPA |
Billing records may be retained longer when required for tax, accounting or legal compliance. Data deletion requests can be sent to privacy@TurboFinOps.com.
Connect one AWS, Azure or GCP scope, approve the safest savings actions, and give finance a receipt when the savings verify.
