Iterable Fair Use Policy

This Fair Use Policy (โ€œPolicyโ€) outlines reasonable usage limits for certain data storage within the Iterable platform to ensure optimal performance and equitable resource allocation for all users. By utilizing Iterableโ€™s services, Customer agrees to adhere to the terms of this Policy.

Custom Event Storage Limit

The Custom Event storage limit is set at a baseline of fifty (50) times Customerโ€™s User Profiles, capped at a maximum of one and a half (1.5) billion Custom Events. โ€œCustom Eventsโ€ are any user-defined actions which can include but are not limited to Customerโ€™s business-related activities in the Iterable Platform. โ€œUser Profilesโ€ are unique pages stored on Iterableโ€™s platform that contain data on user attributes and behaviors.

Calculation Examples: a. For an account with one million (1,000,000) User Profiles, Custom Event storage is limited to fifty million (50,000,000) b. For an account with forty million (40,000,000) User Profiles, Custom Event storage is limited to one and half billion (1,500,000,000) Custom Events.

User Profile Update Frequency

Total Iterable User Profile updates per day (defined as a 24-hour period) for a Customer shall not exceed the total contracted number of User Profiles. This limit applies to all changes made to a User Profileโ€™s attributes.

SMS Outbound Alphanumeric โ€“ Europeย 

If SMS usage to any individual country under Iterable SMS Outbound Alphanumeric โ€“ Europe is more than 70% of the total SMS usage (as provided on the Customerโ€™s Enterprise Order) during the term of the Agreement, Iterable reserves the right to renegotiate the pricing structure with Customer for future usage. Iterable also reserves the right to limit Customerโ€™s usage of the SMS Outbound Alphanumeric โ€“ Europe until negotiations are complete and a new Enterprise Order is executed between the Customer and Iterable.

Compliance During Contract Termย 

This Policy applies continuously throughout the entire term of Customerโ€™s Agreement with Iterable. The term length is defined in Customerโ€™s applicable Order Form. If, at any time during the term of the Agreement, Customerโ€™s Custom Event storage exceeds the specified limit, the account shall be deemed non-compliant and in breach of this Policy.

Resolution for Non-Complianceย 

In the event Customerโ€™s account breaches the limits defined within this Policy, Customer agrees to promptly work with Iterable to reduce their Custom Event storage to within the permitted limits defined in this Policy. Within fifteen (15) calendar days of receiving written notice from Iterable, Customer shall remedy any breach of the limits set forth in this Policy and bring its account within the permitted thresholds.

Remedial Actionย 

Iterable reserves the right to implement measures, including but not limited to blocking the storage of additional Custom Events in Customerโ€™s account, until such time that Customerโ€™s account fully adheres to this Policy.

Policy Modifications

Iterable reserves the right to modify or update these limits and the terms of this Policy at its sole discretion. Any such changes will be communicated to Customer with advanced written notice.

General

This Policy is an material part of the Master Services Agreement and Enterprise Order Form (โ€œOrder Formโ€) between Iterable and Customer (collectively, the โ€œAgreementโ€). Any capitalized term used in this Policy but not expressly defined shall have the meaning given to such term in the Agreement between Iterable and Customer. Failure to comply with this Policy may result in the termination of Customerโ€™s services, as outlined in Customerโ€™s Agreement.