Deleting customers, apps and your account

You can delete a customer, an app or your whole account in the console. Each one takes effect at once and finishes in the background: UsageRail waits for subscriptions to end and for their final usage reporting to finish before it deletes anything.

Before you delete

Download what you want to keep from the app's Usage page: hourly usage, billing period totals, the usage sent to Stripe, and the Stripe mapping, which lists the Stripe customer and subscription of each customer. Deleted data can't be brought back.

Deleting a customer

On the customer's page, choose Delete customer and type their email address or customer ID. Then:

1. Cut off. Their API keys are revoked and they're signed out of the portal. Your servers start refusing their requests within about 20 seconds.
2. Cancellation scheduled. Within a minute, any checkout page they left open is closed and their subscription is set to end with the current period, the same as cancelling it in the console. That period's fee and usage are billed as usual. A subscription that was never paid is cancelled straight away.
3. Settled. The subscription has ended, reporting the last period's usage has finished, and any credit pack payment that was still clearing has cleared or failed. Reporting usually finishes within 3 days of the period end, and takes longer if a report failed or the invoice is still a draft. Deletion goes ahead even when a period ends up not billed or not matching Stripe; those periods stay listed on the app's Stripe page.
4. Data deleted. Their keys, usage, credits and portal sign-ins are deleted.

A customer on an existing Stripe subscription keeps that subscription, since it's yours in Stripe. Their deletion waits in step 3 until the usage of their last period has been sent with the rest of their Stripe customer's.

If they still have credits, or owe credits, when they settle, the deletion stops before the last step and their page shows the amounts. Refunds are up to you, in Stripe. When you've dealt with it, choose Confirm and delete.

The customer's page shows which step they're on and what it's waiting for.

Deleting an app

In the app's Settings, choose Delete app and type the app's name. From then on, calls from your servers to UsageRail and to the server API get a 410, every API key is revoked, nobody can sign in to its portal, and its custom domain is removed. Each customer then goes through steps 2 and 3 above.

When they've all settled, the app's overview lists any customers who still have credits or owe credits, and you confirm once for all of them. UsageRail then cleans up what it set up in your Stripe account: it deletes its webhook endpoint and archives the products, prices, meter and customer portal settings it created. Archived products and prices stay on the invoices that use them. Your existing subscriptions, prices and meter aren't touched; UsageRail only stops reporting their usage, and the period under way when you delete the app isn't sent. Last, the app's data is deleted.

Deleting your account

In Account, choose Delete account and type the email you sign in with. Every app is deleted as above, your UsageRail plan ends with the period you've paid for, and you're signed out everywhere. You can still sign in to follow the progress. When every app is gone and your plan has ended, your email address is removed and you can sign up with it again.

What's kept

• Usage sent to Stripe: 13 months after each billing period, in case an invoice is disputed. It keeps the totals and the Stripe customer and subscription IDs, without the customer's email address.
• The log of changes in your account: 13 months.
• A deleted customer's external ID: 30 days, so usage that reaches UsageRail late from your servers is dropped instead of creating a new customer.
• Database backups: copies there are removed as those backups expire.