What is stored, and for how long
| What | Where | Kept |
|---|---|---|
| Cached figures | DynamoDB | 4 hours, then read again from AWS |
| Cost Attribution trend | DynamoDB | One point a day, the last 90 days |
| Uptime checks | DynamoDB | Each check for 4 days; the daily summary for 90 days |
| Settings, including the tags you declare | DynamoDB | Until you change them |
| Sign-in accounts: email address and password | Amazon Cognito | Until an administrator removes the account |
| Anthropic keys, if you add them | Secrets Manager, under a KMS key | Until you remove them in Settings |
| Function logs | CloudWatch Logs | 1 month |
| API access logs: time, path, status and the caller's IP address | CloudWatch Logs | 1 month |
All of it is in your workload account, in the Region you deploy to, and encrypted at rest by the AWS service that holds it. The Anthropic keys are the one item under a KMS key of its own, which only the dashboard's API may use.
Amounts are stored in US dollars, the currency AWS bills in. Converting them to your currency happens in the browser and is never stored.
What is not stored
- No copy of your bill, your inventory or your findings is kept anywhere but the cache above.
- The API tells every browser and proxy not to keep its answers.
- The site itself is served through CloudFront's edge locations, which cache the pages and their images. The figures are never cached at the edge.
Where AWS answers from
Some AWS services the dashboard reads are global. Cost Explorer and the billing services answer from AWS's own US East (N. Virginia) endpoint, whichever Region you are in. The read passes through AWS's endpoint, and the answer is stored in your Region.
Security Hub and GuardDuty are regional, and the dashboard reads one Region: the one it is deployed to. Findings from your other Regions reach it only if you aggregate them there, and the Security page says which Regions its answer covered, so a narrow read is visible rather than silent.
What leaves the account
Only what you send us: a message typed into the Support page, with the sender's email address. The full list of what crosses the boundary, in both directions, is on Architecture.