Fair Use Policy Restructuring (#1100)

* Restructured fair use policy to account for sync time and zero usage in 30 days

* formatting

---------

Co-authored-by: Idalith Bustos <idalith.bustos@gmail.com>

Author: kchandrasekera

website/src/pages/en/subgraphs/fair-use-policy.mdx

@@ -6,21 +6,23 @@ title: Fair Use Policy
 
 ## Overview
 
-This outlines storage limits for Subgraphs that rely solely on [Edge & Node's Upgrade Indexer](/subgraphs/upgrade-indexer/). This policy is designed to ensure fair and optimized use of queries across the community.
+This page outlines the fair usage of [Edge & Node's Upgrade Indexer](/subgraphs/upgrade-indexer/). This policy is designed to ensure the efficient use of queries and storage across the free-tier community.
 
-To maintain performance and reliability across its infrastructure, Edge & Node is updating its Upgrade Indexer Subgraph fair use policy. Free usage tiers remain available, but users who exceed specified limits will need to upgrade to a paid plan. Storage allocations, sync thresholds, and usage limits vary by feature.
+Storage limits, sync thresholds, and usage requirements are explained below. Users who exceed specified limits will need to advance to a paid plan.
+
+We thank users for doing their part to maintain performance and reliability across Edge & Node's infrastructure.
 
 ### 1. Scope
 
-This policy applies to all individual users, teams, chains, and dapps using Edge & Node's Upgrade Indexer in Subgraph Studio for storage, usage, and queries.
+This policy applies to all individual users, teams, chains, and dapps using Edge & Node's Upgrade Indexer in Subgraph Studio.
 
 ### 2. Fair Use Limits
 
 #### **Storage Limits**
 
 Free Storage: **Up to 10 GB**
 
-Beyond that, pricing is variable and adjusts based on usage patterns, network conditions, infrastructure requirements, and specific use cases. Reach out to InfraDAO [indexing@infradao.com] or @jmulq on Telegram to discuss options that meet your technical needs.
+Beyond that, pricing is variable and adjusts based on usage patterns, network conditions, infrastructure requirements, and specific use cases. Note that Subgraphs of any size will be deleted after 30 days of dormancy (no usage) in order to make space for active Subgraphs.
 
 #### **Syncing Limits**
 
@@ -32,19 +34,17 @@ Subgraphs must sync within **14 days** of deployment.
 
 To preserve the stability of Edge & Node's Subgraph Studio and the reliability of The Graph Network, the Edge & Node Support Team will monitor storage usage and sync times across Subgraphs. Subgraphs that violate limits will be subject to corresponding action, including the deletion of that Subgraph for any of the following reasons:
 
-- Abnormally high or sustained bandwidth or storage usage beyond posted limits
-- Circumvention of storage thresholds (e.g., use of multiple free-tier accounts)
-- Failure to fully sync within 14 days of deployment and remaining inactive
+- **Storage** usage beyond posted limits. This includes circumvention of storage thresholds (e.g., use of multiple free-tier accounts).
+- **Utilization** that is abnormally high, or zero utilization, or sustained bandwidth.
+- **Sync** time greater than 14 days after deployment.
 
 The Edge & Node Support Team reserves the right to revise fair limits or impose temporary constraints for operational integrity.
 
-If you exceed your fair use limits:
+If you exceed your fair use limits, you will receive an email alert giving you a grace period of **7 days** to take action. Here are some options:
 
-- Try [pruning Subgraph data](/subgraphs/best-practices/pruning/) to remove unused entities and help stay within storage limits
-- [Publish your Subgraph to the Network](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) and [add signal](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) to encourage other Indexers on the network to serve it
-- Sync your Subgraph after deployment
-- You will receive an email alert
-- A grace period of **7 days** will be provided to upgrade or reduce storage
+- Try [pruning Subgraph data](/subgraphs/best-practices/pruning/) to remove unused entities and help stay within storage limits.
+- If your subgraph references chains that receive indexing rewards, [indicated by double check marks in the Subgraphs column here](/subgraphs/best-practices/pruning/)), then [publish your Subgraph to the Network](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) and [add signal](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) to encourage other Indexers on the network to serve it.
+- If your Subgraph references a chain that **does not** receive indexing rewards, reach out to InfraDAO [indexing@infradao.com⁠] or @jmulq on Telegram to discuss options that meet your technical needs.
 
 Edge & Node's team is committed to helping users avoid unnecessary interruptions and will continue to support all builders.