Tiered data billing explained

about/pricing-and-account-management.md

@@ -109,7 +109,9 @@ bandwidth of your service to meet those needs.
 We make it easy for you to store unlimited amounts of data using Tiered Storage; a high-performance
 storage tier and a low-cost bottomless storage tier. You can keep up to 16 TB compressed
 (typically 80-100 TBs uncompressed) in the high-performance storage tier, and configure less-frequently
-accessed data to be moved to our low-cost storage tier built on S3.
+accessed data to be moved to our low-cost storage tier built on S3. 
+
+Because of the proprietary format used to store data in Amazon S3, $COMPANY charges for tiered data based on its uncompressed size, even if you compress it first.
 
 Timescale Cloud is very efficient and generally needs less compute than other databases to deliver
 the same performance. The best way to size your needs is to signup for a free trial and to test

use-timescale/data-tiering/about-data-tiering.md

@@ -13,7 +13,9 @@ cloud_ui:
 
 Timescale's tiered storage architecture includes a standard high-performance storage tier and a low-cost object storage tier built on Amazon S3. You can use the standard tier for data that requires quick access, and the object tier for rarely used historical data. Chunks from a single hypertable, including compressed chunks, can stretch across these two storage tiers. A compressed chunk uses a different storage representation after tiering.
 
-In the high-performance storage, chunks are stored in the block format. In the object storage, they are stored in a compressed, columnar format. For better interoperability across various platforms, this format is different from that of the internals of the database. It allows for more efficient columnar scans across longer time periods, and Timescale Cloud uses other metadata and query optimizations to reduce the amount of data that needs to be fetched from the object storage tier to satisfy a query.
+In the high-performance storage, chunks are stored in the block format. In the object storage, they are stored in a compressed, columnar S3 format. For better interoperability across various platforms, this format is different from that of the internals of the database. It allows for more efficient columnar scans across longer time periods, and $CLOUD uses other metadata and query optimizations to reduce the amount of data that needs to be fetched from the object storage tier to satisfy a query.
+
+Because of the proprietary format used to store data in Amazon S3, $COMPANY charges for tiered data based on its uncompressed size, even if you compress it first.
 
 Regardless of where your data is stored, you can still query it with standard SQL. A single SQL query transparently pulls data from the appropriate chunks using the chunk exclusion algorithms. You can `JOIN` against tiered data, build views, and even define continuous aggregates on it. In fact, because the implementation of continuous aggregates also uses hypertables, they can be tiered to low-cost storage as well. 
 

use-timescale/data-tiering/enabling-data-tiering.md

@@ -18,6 +18,8 @@ or [manually tier and untier data][manual-tier].
 
 You can query the data on the object storage tier, but you cannot modify it. Make sure that you are not tiering data that needs to be **actively modified**.
 
+Because of the proprietary format used to store data in Amazon S3, $COMPANY charges for tiered data based on its uncompressed size, even if you compress it first.
+
 ## Enable tiered storage
 
 You enable tiered storage from the `Overview` tab in Console.