Data Usage Policy for Graylog Cloud Sample Clauses

The Data Usage Policy for Graylog Cloud defines how user data is collected, stored, and processed within the Graylog Cloud service. It typically outlines the types of data that may be gathered, such as log files, user activity, or system metadata, and specifies the purposes for which this data can be used, like service improvement or security monitoring. By clearly establishing the rules and limitations around data handling, this clause ensures transparency for users and helps maintain compliance with privacy regulations, thereby building trust and reducing the risk of data misuse.
Data Usage Policy for Graylog Cloud. For Subscriptions based on Daily Volume Limit, Customer can exceed the purchased daily index volume a maximum of five times in a calendar month, up to a maximum of two times the volume of their contracted Daily Volume Limit in aggregate over the calendar month. Without limiting Graylog’s foregoing rights, with respect to Hosted Services, Graylog may work with Customer to reduce usage so that it conforms to the applicable usage limit, and Graylog will in good faith discuss options to right size Customer’s subscription as appropriate. For the avoidance of doubt, notwithstanding anything to the contrary herein, Graylog will have the right to directly invoice Customer for overages, regardless of whether Customer purchased the Hosted Service from an authorized reseller.
View SourceView Similar (5)
Data Usage Policy for Graylog Cloud. For Subscriptions based on Daily Index Volume Limit, Customer should not exceed the purchased Daily Index Volume Limit more than a maximum of five times in a rolling 30 day period, up to no more than a maximum of two times the volume of their contracted Daily Index Volume Limit in aggregate over such period. If the Customer exceeds the Daily Index Volume Limit five times or more in any such period, or if Customer exceeds any other License Metric Limitation not based on daily index volume, Customer, at Graylog’s request, shall negotiate in good faith with Graylog on appropriate amendments to the pricing and other relevant terms of these Hosted Service Terms that are consistent with Customer’s actual Subscription use of the Software. Notwithstanding the foregoing sentence, Customer acknowledges and agrees that exceeding the License Metric Limits (including the daily index volume limits) constitutes a material breach of these General Terms.
View Source

Related to Data Usage Policy for Graylog Cloud

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Two-­‐character labels All two-­‐character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Such labels may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator, provided that such two-­‐character label strings may be released to the extent that Registry Operator reaches agreement with the related government and country-­‐code manager of the string as specified in the ISO 3166-­‐1 alpha-­‐2 standard. The Registry Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such labels that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Reverse ADSL Loops If a CLEC’s ADSL Transmission Unit (including those integrated into DSLAMs) is attached to Sprint’s Network and if an ADSL Copper Loop should start at an outside location, and is looped through a host or remote, and then to the subscriber, the copper plant from the outside location to the Sprint host or remote central office must be a facility dedicated to ADSL transmission only and not part of Sprint’s regular feeder or distribution plant.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.