Cogzia Fair Use Policy

Version: 1.1 Effective Date: December 10, 2025 Last Updated: December 10, 2025

1. Purpose

This Fair Use Policy ("Policy") governs your usage of the Cogzia platform and is incorporated into our Terms of Service. It ensures equitable access to our resources for all users while allowing us to maintain a sustainable service.

We're a growing company. Our pricing is based on assumptions about typical usage patterns. This Policy exists because we cannot predict every usage scenario, and some patterns may be economically unsustainable at current price points. We're committed to working with you to find solutions that work for both of us.

2. Our Commitment

We commit to:

• Transparency: Clearly communicating usage expectations and any concerns about your usage.
• Good Faith: Working with you to find appropriate solutions before taking restrictive action.
• Reasonable Notice: Providing advance notice of changes except in cases of abuse or emergency.
• Fairness: Applying this Policy consistently across similar use cases.

3. Usage Categories

3.1. Included Usage

Each Subscription tier includes certain usage allocations. These are designed to accommodate typical use cases for that tier and will be described in more detail on our pricing page.

The specific numeric limits (the [X] values above) are not contractual by themselves. The current, binding limits for each tier are those published on our pricing page and in your order form, which may be updated from time to time in accordance with our Terms of Service.

3.2. Soft Limits vs. Hard Limits

Soft Limits: Most usage limits are "soft limits." If you occasionally exceed them, we won't immediately cut off access. Instead, we'll:

1. Monitor the pattern
2. Reach out if usage is consistently elevated
3. Work with you to find an appropriate tier or custom arrangement

Hard Limits: Some limits are strictly enforced for system stability:

• Maximum request rate (requests per second)
• Maximum payload size
• Maximum concurrent connections

These are documented in our API documentation.

4. What Constitutes Excessive or Abusive Usage

4.1. Excessive Usage (Economic)

Usage may be considered excessive if it:

• Consistently exceeds 2x your tier's included allocations over two or more consecutive billing cycles;
• Consumes disproportionate compute, storage, or network resources relative to your tier;
• Creates costs to Cogzia that materially exceed the revenue from your Subscription; or
• Follows patterns that suggest your usage would be more appropriately covered by a higher tier or a custom enterprise plan.

Our response: We'll contact you to discuss upgrading, optimizing your usage, or arranging custom pricing that reflects your needs, as further described in Section 5 and in our Terms of Service.

4.2. Abusive Usage (Policy Violation)

Usage is considered abusive if it:

• Violates our Terms of Service or Acceptable Use Policy
• Attempts to circumvent rate limits or usage tracking
• Uses automated tools to artificially inflate usage or game the system
• Negatively impacts service availability or performance for other users
• Involves security probing, vulnerability scanning, or unauthorized access attempts
• Resells or redistributes Service access without authorization

Our response: We may suspend or terminate access immediately, without refund.

4.3. Unintentional Resource Exhaustion

Sometimes legitimate use cases inadvertently consume excessive resources (e.g., a bug in your code, an unexpected traffic spike, or a misconfigured integration).

Our response: We'll notify you promptly and work with you to resolve the issue. We won't penalize good-faith users for honest mistakes, but we may temporarily throttle access to protect the Service.

5. Monitoring and Enforcement

5.1. Usage Monitoring

We monitor aggregate usage metrics to:

• Ensure service quality and availability
• Detect and prevent abuse
• Identify users who may benefit from different plans
• Plan capacity and infrastructure

We do not monitor the content of your data except as necessary to provide the Service or as required by law.

5.2. Enforcement Actions

Depending on the severity and nature of the issue, we may take one or more of the following actions:

These examples are illustrative, not exhaustive; our actual response will depend on the specific facts and applicable law. Any suspension or termination of your Subscription will be carried out in accordance with our Terms of Service (see Section 5.3 and Section 12 of the Terms).

5.3. Notice Requirements

• Notification/Warning: Sent via email; no immediate action required from you
• Throttling: May be applied immediately for system protection; notification within 24 hours
• Feature Restriction: 7 days' notice except in emergencies
• Mandatory Upgrade: 14 days' notice to select a new plan
• Suspension: Immediate for abuse; 7 days' notice for economic reasons
• Termination: Per Terms of Service

6. Custom and Enterprise Arrangements

If your usage needs exceed our standard tiers, we offer:

6.1. Custom Pricing

Negotiated pricing that reflects your specific usage patterns and volume. Contact sales@cogzia.com.

6.2. Enterprise Agreements

For organizations with significant usage, we offer enterprise agreements with:

• Committed usage volumes at discounted rates
• Dedicated support
• Custom SLAs
• Flexible billing arrangements

6.3. Early Adopter Considerations

If you're an early adopter on promotional pricing and your usage grows significantly, we'll work with you to transition to appropriate pricing in a way that recognizes your early support.

7. Changes to This Policy

7.1. Policy Updates

We may update this Policy to reflect:

• Changes in our infrastructure costs
• New features or usage categories
• Learnings from actual usage patterns
• Industry standards and best practices

7.2. Notice of Changes

We will provide at least 30 days' notice of material changes to this Policy via email and/or notification in the Service. Changes will not retroactively affect usage that occurred before the effective date.

7.3. Your Options

If you disagree with Policy changes, you may:

• Contact us to discuss your specific situation
• Downgrade or cancel your Subscription before changes take effect
• Request a custom arrangement

8. Our Promise

We're building Cogzia to be a long-term, sustainable business. This Policy exists not to restrict you, but to ensure we can continue serving all our users fairly.

If you ever have questions about your usage or this Policy, please reach out. We'd rather have a conversation than enforce restrictions.

Contact: support@cogzia.com

9. Examples

The following examples are provided for illustration only. They are not promises of a particular outcome in any specific situation, and our actual response may differ based on the details of your usage, your Subscription, and applicable law.

Example A: Growing Startup

Situation: A Pro user's MCP executions grow from 5,000/month to 50,000/month as their product scales.

Our response: We reach out to congratulate them on their growth and discuss Team or custom pricing that fits their trajectory. No penalty, just a conversation.

Example B: Inefficient Integration

Situation: A user's API calls spike 10x due to a polling loop that should use webhooks.

Our response: We notify them of the spike, explain the issue, and offer guidance on optimization. If they fix it promptly, no further action.

Example C: Clear Abuse

Situation: A Free user creates multiple accounts to circumvent limits and resells access.

Our response: Immediate termination of all accounts. No refunds. Possible legal action.

Example D: Cost Surprise

Situation: A user's legitimate use case turns out to be far more expensive to serve than we anticipated at their price point.

Our response: Honest conversation. We explain the economics, explore optimization options, and work toward pricing that's sustainable for both parties. We honor existing terms through the current billing cycle.

This Fair Use Policy is part of your agreement with Cogzia. Please read it in conjunction with our Terms of Service and Acceptable Use Policy.