Trust

Cancelling and removing CostPulse

Last updated October 17, 2026

Overview

Leaving takes up to three independent steps. Cancel the subscription so billing stops. Delete the CloudFormation stack so CostPulse has no access to your AWS account. Ask us to delete your data if you want it gone; nothing is deleted on a timer. Each step is below, with what happens to your data and when.

Deleting the stack does not cancel a subscription, and cancelling does not remove anything from your AWS account. Do both.

1. Cancel your subscription

Paid with a card (Stripe). Sign in, open Your account, and choose Manage billing. That opens Stripe's billing portal, where you can cancel, switch between Starter and Team, update your card, and download invoices. No email or call is needed.

A cancellation takes effect at the end of the billing period you have paid for, as our Terms describe. Your plan and alerts keep working until then, and your account page shows the end date. You can undo the cancellation in the same portal before that date. Mid-period cancellations are not refunded pro rata, except where the law requires it.

Bought through AWS Marketplace. AWS bills you, so you cancel with AWS: in the AWS console open AWS Marketplace, Manage subscriptions, choose CostPulse, then cancel the subscription. You need to be signed in to the AWS account that subscribed, with permission to manage Marketplace subscriptions. When AWS reports the subscription as ended, your CostPulse plan changes to cancelled on its own.

If anything gets in the way, email [email protected] and we will cancel it for you.

2. What happens after you cancel

When your plan ends:

  • Anomaly detection, alert delivery to Slack, Teams and email, and the weekly digest stop.
  • You can no longer connect additional AWS accounts.
  • Your dashboard stays readable, and nothing is deleted. If you subscribe again, monitoring resumes with your history and settings intact.
  • We stop reading your AWS billing data. The IAM role still exists in your account until you delete it (step 3), which removes CostPulse's access entirely.

Alert history is deleted automatically 90 days after each alert is created, whether or not you cancel. Cancelling does not delete your daily spend data, your account or your configuration, and nothing is deleted on a timer, so if you come back your history is still there. They are kept until you ask us to delete them (step 4).

3. Remove CostPulse from your AWS account

The Connect AWS button and the AWS Marketplace Quick Launch both deploy a CloudFormation stack named CostPulse (unless you renamed it) in us-east-1, in your management (payer) account. Delete it in the same account and region:

  • Console: CloudFormation, region US East (N. Virginia), Stacks, select the stack, Delete.
  • Or with the AWS CLI:
aws cloudformation delete-stack --stack-name CostPulse --region us-east-1

Deleting the stack removes:

  • The IAM role costpulse-readonly-<your account ID>. This ends CostPulse's access; there is no other path into your account.
  • The CUR 2.0 data export costpulse-cur-<your account ID>, so AWS stops writing new billing files.
  • The bucket policy that let AWS billing services write into the bucket.

The S3 bucket is kept on purpose. The bucket costpulse-cur-<your account ID> has DeletionPolicy: Retain in the template, because the billing files in it are yours. CloudFormation leaves it, and its files, in place. Its lifecycle rule stays too, so the files it holds expire 120 days after they were written. To remove it now, empty it and then delete it, either in the S3 console (Empty, then Delete) or with:

aws s3 rm s3://costpulse-cur-<ACCOUNT_ID> --recursive
aws s3 rb s3://costpulse-cur-<ACCOUNT_ID>

The template does not turn on versioning, so emptying the bucket this way removes everything in it.

If you reused an existing export (CurSetupMode = UseExisting), the stack created only the IAM role. Deleting the stack removes the role and leaves your own export and bucket exactly as they were.

If you created the role by hand rather than with the stack, delete that role in IAM. That is all CostPulse had.

For the full list of what the role can read, see IAM permissions.

4. Delete your CostPulse data

Once your plan has ended, choose Delete my data on Your account, or email [email protected]. We confirm the request with you and then delete your daily spend data, connected-account records, alert channels, settings and sign-in within 30 days, as our Privacy policy says. Database backups that may still hold it expire within 35 days. If you answered the optional question we ask after a cancellation, that answer is deleted with the rest.

We keep a record that the deletion happened, with dates and row counts but none of your data, and payment records as required for bookkeeping. If another CostPulse account also connects the same AWS account, the spend data that account relies on is kept for it.

To remove the CostPulse app from Slack or Microsoft Teams, uninstall it from your workspace's app management. Alerts stop when your plan ends either way.