Fair Use Policy

Last updated: 2026-05-28

1. Why This Policy Exists

Public cloud providers meter resources — CPU, storage, and especially outbound data transfer (egress). A small number of customers consuming disproportionate resources affects our costs and, ultimately, the pricing for everyone. This Policy ensures that all customers enjoy predictable, good-faith use of the Service without subsidizing outlier usage.

2. General Principles

You agree to use the Service in a manner consistent with typical team collaboration and workplace productivity. The tools we host (file sharing, code hosting, password management, chat, etc.) are designed for human-scale use by your team. Activities that fall outside this scope, whether they consume excessive bandwidth, compute, storage, or support, are not considered fair use.

When assessing fair use, we apply the Dutch principle of reasonableness and fairness (redelijkheid en billijkheid). If you are unsure whether your intended use is reasonable, please ask us.

3. Fair Use Guidelines

3.1 Egress (Outbound Data Transfer)

Each subscription plan includes a storage allocation. Your monthly egress allowance is 2x the storage limit of your plan, as stated in your order or pricing page.

Example: If your plan includes 100 GB of storage, your monthly egress allowance is 200 GB.

What counts toward egress:

• All outbound data transfer from the hosted applications to end users (web traffic, API responses, file downloads, normal email delivery, remote sync, etc.). Only consistently excessive email volumes — beyond what is typical for your team's size — may trigger an overage review. Legitimate day-to-day communication is not penalised.
• Data transfer between different cloud regions or availability zones (if applicable).

What does not count toward egress:

• Inbound traffic (uploads from your team).
• Traffic between applications within your private network (e.g., app-to-app calls inside the same deployment).
• Backend administrative traffic (ImagIT's monitoring, updates, and maintenance).

3.2 Storage

Allocate storage for your actual team needs. Examples of atypical storage use include storing large media archives, VM images, database dumps, or backup archives unrelated to the hosted applications. If your stored data significantly exceeds typical usage for your plan tier, we may contact you to discuss a plan upgrade or adjusted pricing.

3.3 Compute (CPU / Memory)

The hosted applications are sized for typical team collaboration workloads. Activities that strain compute resources beyond that scope are not fair use, including but not limited to:

• Running custom scripts, cron jobs, or background workers that consume sustained high CPU or memory.
• Operating data processing pipelines, media transcoding, or render jobs.
• Cryptocurrency mining, password cracking, or any form of proof-of-work computation.
• Running containers, VMs, or additional server software not provisioned by ImagIT.

CI/CD pipelines. If your plan includes code hosting with built-in CI/CD runners (e.g., GitLab CI, Gitea Actions), standard pipeline execution within the platform's native runner framework is permitted and does not violate this section. However, running CI/CD jobs that consume disproportionate resources (e.g., mining, benchmarking, or work-unrelated computation) remains prohibited.

3.4 API and Application Usage

API requests to the hosted applications are subject to rate limits, which are set per application and documented in the respective administrator guides. Excessive API usage that degrades performance for other customers may result in temporary or permanent rate limiting.

Examples of disproportionate use include:

• Automated scraping or bulk-exporting of data beyond what a normal team workflow produces.
• Using the Service as a content delivery network, public distribution platform, or primary backup target for external infrastructure.
• Running integration or sync scripts that poll at very high frequency.

3.5 Support

We provide support for setup, troubleshooting, and operational questions. Fair use of support means:

• Submitting one support request per issue and awaiting a response before follow-ups.
• Not using support as a substitute for reading available documentation.
• Not engaging support staff for internal training, custom development, or extended consulting without a separate services agreement.

Repeated abuse of the support channel may result in reduced priority or a requirement to purchase a support package that matches your volume.

3.6 Account Sharing and Access

Accounts are per-seat and intended for individual named users. You may not share login credentials across multiple people. If you need to provision access for additional team members, you must add them to your subscription. Automated system accounts for integration purposes are permitted but must be disclosed to us.

4. Monitoring and Notification

We monitor aggregate usage per customer account. When your egress or storage usage reaches 80% of your allowance, we will send a notification to the account email address. When you reach 100%, you will receive a second notification.

These notifications are sent at most once per day. You are responsible for monitoring your own usage if real-time tracking is important to you.

5. Exceeding Your Allowance

If you exceed your plan's usage allowances, one of the following will apply, depending on the plan and circumstances:

(a) Overage charges. You may continue to use the Service normally, and we will invoice you for the excess at the rates stated in your order. If your order does not specify overage rates, the default rates published on our pricing page apply. Overage is billed monthly.

(b) Throttling. For plans that do not support overage billing, or where excessive usage is sustained, we may throttle outbound throughput or reduce compute priority to protect the overall infrastructure.

(c) Plan upgrade. If your usage consistently exceeds your allowance for three consecutive months, we may require you to move to a higher-tier plan that better fits your usage profile.

(d) Support restrictions. Repeated abuse of support may result in a mandatory move to a paid support tier.

6. Enforcement

We prefer to resolve fair use issues cooperatively. If your usage exceeds these guidelines, we will:

1. Send a notice explaining the issue and requesting corrective action within 7 days.
2. If the issue persists, schedule a call to discuss a plan upgrade or adjusted pricing.
3. As a last resort, we may suspend or terminate access under the terms of the Terms of Service.

We reserve the right to take immediate action if your usage poses a risk to the infrastructure or other customers (e.g., a compromised account generating massive outbound traffic or a security incident).

7. Changes to This Policy

We may revise this Policy from time to time. Changes will be communicated in accordance with the Terms of Service. Continued use of the Service after changes take effect constitutes acceptance of the revised Policy.

8. Questions

If you are unsure whether your intended use is covered by this Policy, or if you have specific requirements that may require higher limits, please contact us:

• Email: [email protected]
• Website: https://imagit.eu