Privacy
What CloudFix collects, what it doesn't, and how we handle it.
CloudFix works from infrastructure metadata and cost data. It never holds your AWS credentials, never reads your workload data, and never sells data to anyone.
Data we collect
Three kinds of data, all of it needed to run the service.
Account information
- Name and email address
- Company name
- Billing information (processed through AWS Marketplace)
AWS account metadata
- AWS account ID
- Service configuration data (read-only)
- Resource metadata: instance types, configurations, tags
- Cost and Usage Report data
Usage data
- Feature usage in the CloudFix dashboard
- Fix history and approval records
- Savings reports generated
Data we don't collect
CloudFix never has your AWS credentials.
It uses IAM role assumption (STS AssumeRole), not stored credentials. The discovery role is read-oriented: its writes are limited to resource tagging, query execution and a few finder-specific actions, all listed on the security page.
No AWS credentials
No secret keys, access keys or passwords are ever stored or sent to CloudFix. Access is by IAM role assumption only.
No bulk data access
CloudFix cannot read your secrets, Parameter Store values, log events, database items, queue messages or snapshot contents. Analysis is based on resource metadata and cost data; a few finders need narrow, purpose-specific reads, granted only when that finder is enabled.
No personal data from AWS
No personally identifiable information is collected from your AWS accounts. CloudFix reads infrastructure configuration, not user data.
Retention
How long we keep it.
| Data | Retention period |
|---|---|
| Active account data | Duration of subscription |
| AWS Cost and Usage Report data | Analyzed in memory, not stored long-term |
| Deleted account data | Purged within 30 days |
| Audit logs | Retained for 1 year, or until 30 days after contract termination, whichever comes first |
| Fix execution history | Duration of subscription + 30 days |
Sub-processors
A minimal set, and we do not sell data.
We notify customers at least 30 days before adding any new sub-processor. Purposes, data and certifications for each are on the data processing page.
| Provider | Purpose | Data location |
|---|---|---|
| Amazon Web Services (AWS) | Infrastructure provider, AWS Marketplace billing, IAM role assumption | US East (us-east-1) |
| Amazon CloudFront | CDN and TLS termination for the CloudFix dashboard. Part of AWS infrastructure, not a separate third party. | AWS global edge network (origin: us-east-1) |
| Amazon Route 53 | DNS for the CloudFix dashboard. Part of AWS infrastructure, not a separate third party. | AWS global anycast network |
| AWS Shield | DDoS protection. Part of AWS infrastructure, not a separate third party. | AWS global edge network |
| PostHog | Product analytics | US |
| Kayako | Customer support platform | US |
Questions about our privacy practices?
Read the full privacy policy, or ask us directly.