FAIR USE POLICY

This Fair Use Policy ("Policy") outlines acceptable use of Tez ERP ("Product"). This Policy is in addition to the Tez ERP Terms and Conditions and any applicable order, invoice, commercial proposal or written service arrangement under which Innovative ERP Solutions Limited ("IESL") provides access to the Product or related services.

IESL may make reasonable modifications to this Policy from time to time by posting a revised version on the product website. Revisions may take effect upon posting or on a later stated effective date. Material changes affecting existing commercial rights will be handled in accordance with the Tez ERP Terms and Conditions.

Questions about this Policy, including whether contemplated use is permitted, and reports of violations should be directed to the support contact published by IESL. The examples below are not exhaustive.

Acceptable Use and Prohibited Activities

1. Violating any applicable law or engaging in unlawful conduct in any jurisdiction relevant to the use of the Product.
2. Displaying, performing, sending, receiving, uploading, processing or storing content that violates applicable law or third-party rights.
3. Deleting, altering or violating copyright, proprietary or trademark notices unless expressly permitted by the rights holder.
4. Obtaining or attempting to obtain unauthorised access to any system, network, service, account, database or data.
5. Accessing data belonging to any user, site, account, system or network that the user is not authorised to access.
6. Introducing or activating viruses, worms, malware, harmful code, Trojan horses, SQL injection attacks or other malicious or disruptive mechanisms.
7. Sending unsolicited, unlawful or non-consensual messages through SMS, email, WhatsApp or any other communication medium.
8. Reselling, sub-licensing or commercially redistributing services, in whole or in part, without IESL's prior written consent, or misrepresenting a relationship with IESL.
9. Using automation, APIs, scripts, bots, bulk jobs or reporting processes in a manner that degrades service availability, affects other customers, creates abnormal infrastructure load or circumvents purchased limits.
10. Using the Product to facilitate fraud, security abuse, credential theft, data scraping, unauthorised surveillance or other harmful activity.

Deployment and Usage Limits

Tez ERP supports flexible deployment, which may include hosting on IESL-managed infrastructure, third-party cloud infrastructure, customer-controlled cloud infrastructure or on-premise servers. For IESL-hosted or IESL-managed services, usage limits are governed primarily by the Customer's purchased package, order, invoice and technical environment.

1. Users: Licence entitlement is governed by the number and type of users included in the purchased package. The Product may restrict creation or access beyond the permitted entitlement.
2. Entities / Companies: The Product can support multiple entities or companies where the architecture and common masters/settings permit. The number available to a Customer is governed by the purchased package. Large numbers of entities may require additional infrastructure or configuration and may affect performance.
3. Branches: The Product can support multiple branches. The number available is governed by the purchased package, and very high branch counts may require additional capacity or technical review.
4. Departments: The Product can support multiple departments. Entitlement and performance are subject to the purchased package, technical configuration and reasonable usage.
5. Account Heads: The Product supports extensive account-master creation. Very large volumes may affect search, reporting or transaction performance and may require technical review or additional resources.
6. Inventory Items: The Product supports large inventory masters and has historically been used/tested with high item volumes. Very large master volumes may affect performance and may require technical review, indexing, archival or additional infrastructure.
7. Transactions: Transaction creation and storage are subject to package-specific database and resource entitlements. Older or legacy packages may have been marketed with specific transaction-storage thresholds. Such historical thresholds do not create a universal entitlement for current plans; the Customer's applicable order/package controls.
8. Document Storage: Attachments and document storage are subject to the storage included in the purchased package. Legacy packages may have referenced specific storage allowances such as 2 GB; current entitlement is package-specific and additional storage may be chargeable.
9. API Calls: API usage is subject to purchased API entitlement, rate limits, third-party limits, security controls and system capacity. Legacy packages may have referenced a benchmark such as 500 API calls per day; current limits are package-specific and higher volumes may require a separate API pack or infrastructure arrangement.
10. GSP / Statutory Calls: GSTN, e-invoice, e-way bill, public search, return-related and similar calls may rely on third-party/GSP services. Limits depend on the package, number of users, third-party rate limits and prevailing commercial terms. Very high usage may be restricted or charged separately.
11. Email: Customers may be permitted to configure their own email account or use an approved email service, subject to provider policies, credentials, sending limits and the purchased plan.
12. WhatsApp: WhatsApp messaging requires an applicable WhatsApp/Meta-approved messaging arrangement, message credits or third-party service and is subject to provider pricing, template approval, policy and consent requirements.
13. SMS: SMS usage is subject to the Customer's purchased or promotional message entitlement and applicable provider/TRAI rules. Certain legacy plans historically included monthly complimentary messages; such legacy benefits apply only where expressly included in the Customer's current commercial arrangement.
14. Automation, bulk imports, report generation, backups and server resources: Unusually high or automated consumption may be throttled, scheduled, restricted or made subject to additional charges where required to protect service stability and fair access for other customers.

Reasonable Use and Additional Capacity

Usage limits are based on product architecture, infrastructure capacity, third-party restrictions, security considerations, fair access for other customers and the commercial package purchased. If a customer has higher requirements, IESL may offer additional users, storage, API capacity, transaction capacity, messaging, server resources, dedicated infrastructure or a tailor-made package on a chargeable basis.

Enforcement

Excessive, abusive, automated, abnormal, unlawful or unusually high usage may be investigated and, where reasonably necessary, restricted, throttled, suspended or made subject to additional charges. IESL may take immediate protective action where required to safeguard security, system stability, legal compliance, third-party services or other customers.

Relationship with Applicable Terms

This Policy forms part of and should be read together with the Tez ERP Terms and Conditions and the Customer's applicable order confirmation, invoice, proposal, SRS, Statement of Work or other mutually approved written commercial document. In the event of an inconsistency relating to product scope, licence entitlement, commercial entitlement, support, service level, hosting, usage, data retention, liability, refund, termination or other contractual rights and obligations, the Tez ERP Terms and Conditions and mutually agreed written commercial documents shall prevail to the extent permitted by applicable law.