Billing correction
GPT-6 Astra passed
- Tokens
- 64,258
- Cost
- $0.57
Write the reminder that Lumenrack sends to the billing owner of a Lumenrack Vault account before a correction to how backup storage is billed takes effect. Cover the facts below.
Lumenrack Vault is the Lumenrack managed analytics database. Every Vault service with backups enabled keeps a full base copy of its data plus incremental changes for the retention period. This message is a reminder; a first notice about the same correction went out on August 1, 2026.
What happened: an error in the billing logic has been undercharging for backup storage. Invoices reflected only the incremental changes, not the full base copy that Vault stores. Backup docs: https://lumenrack-email.s3.amazonaws.com/docs/vault-backups
What is changing: the correction takes effect on October 1, 2026. Past undercharges are not billed; the correction applies only to backup storage from that date forward. The rate does not change: backup storage stays at $0.023 per GB-month, and the line appears on the invoice under the SKU VAULT-BKP-GB-MO. The effective date leads the email as its own labelled callout, above the what-happened explanation; the before-and-after example is laid out as two matching labelled cells with the monthly amounts emphasised.
Before and after, for a service holding 400 GB of data with 7-day retention, where the incremental changes over those 7 days come to 80 GB:
- Before the correction: billed on 80 GB of incremental changes, which is $1.84 per month.
- After the correction: billed on the full backup footprint of 480 GB (the 400 GB base copy plus 80 GB of incrementals), which is $11.04 per month.
Who is affected: every Vault service with backups enabled, on every tier. Services with backups turned off are not affected.
What to expect, in this order:
- A 60-day grace period before any billing change. It began with the first notice on August 1, 2026, and the correction applies from October 1, 2026.
- Backup visibility in the console: the full and incremental sizes stored for each service. https://lumenrack-email.s3.amazonaws.com/console/backups
- An updated pricing calculator that estimates backup costs from actual stored data. https://lumenrack-email.s3.amazonaws.com/pricing/calculator
Separately, and unrelated to the billing correction: exporting backups to the customer's own bucket is now available on every service tier. Docs: https://lumenrack-email.s3.amazonaws.com/docs/vault-backup-export
The FAQ about the correction is the one call to action. https://lumenrack-email.s3.amazonaws.com/docs/vault-backup-billing-faq
Questions or account-specific situations go to Lumenrack support. https://lumenrack-email.s3.amazonaws.com/support
The email apologizes for the inconvenience and signs off from the Lumenrack Vault team.
The footer says the message is about the recipient's account, gives the postal address, and links to the console https://lumenrack-email.s3.amazonaws.com/console support https://lumenrack-email.s3.amazonaws.com/support and privacy https://lumenrack-email.s3.amazonaws.com/privacy
Dark mode should be supported.
Use /world/lumenrack-email for brand chrome and CSS; the transactional family fits. Use the absolute HTTPS URLs from tokens.json; do not use /world/ paths as image src.
Leave the HTML in output/email.html, a plain-text version in output/email.txt, and the subject in output/meta.json as {"subject": "..."}. Don't include From, To, or Date headers.