Online Activity Reports Sample Clauses

Online Activity Reports. While Party Time Mixes earnestly strives to ensure all information provided to you by the company in online reports is accurate and reliable, due to variables and factors beyond Party Time Mixes’ control, Party Time Mixes or anyone creating or transmitting the information, does NOT guarantee the information to be wholly accurate. All sales volume information is provided as is without warranties, express or implied, or representations of any kind whatsoever. In particular, but without limitation, there shall be no warranties of merchantability, fitness for a particular use, or non-infringement. To the fullest extent permissible under applicable law, Party Time Mixes and/or other persons creating or transmitting the information will in no event be liable to any Party Time Mixes Independent Consultant or anyone else for any direct, indirect, consequential, incidental, special or punitive damages that arise out of the use of or access to sales volume information (including, but not limited to, lost profits, bonuses, or commissions, loss of opportunity, and damages that may result from inaccuracy, incompleteness, inconvenience, delay, or loss of the use of the information), even if Party Time Mixes or other persons creating or transmitting the information shall have been advised of the possibility of such damages. To the fullest extent permitted by law, Party Time Mixes or other persons creating or transmitting the information shall have no responsibility or liability to you or anyone else under any tort, contract, negligence, strict liability, products liability or other theory with respect to any subject matter of this agreement or terms and conditions related thereto.
AutoNDA by SimpleDocs
Online Activity Reports. While Scentsy Family earnestly strives to ensure all information provided to you by the Company in online reports is accurate and reliable, due to variables and factors beyond Scentsy Family‘s control, Scentsy Family, or anyone creating or transmitting the information, does NOT guarantee the information to be wholly accurate. All sales volume information is provided as is without warranties, express or implied, or representations of any kind whatsoever. In particular, but without limitation, there shall be no warranties of merchantability, fitness for a particular use, or non-infringement. To the fullest extent permissible under applicable law, Scentsy Family and/or other persons creating or transmitting the information will in no event be liable to any Consultant or anyone else for any direct, indirect, consequential, incidental, special, or punitive damages that arise out of the use of or access to sales volume information (including but not limited to lost profits, bonuses, or commissions, loss of opportunity, and damages that may result from inaccuracy, incompleteness, inconvenience, delay, or loss of the use of the information), even if Scentsy Family or other persons creating or transmitting the information shall have been advised of the possibility of such damages. To the fullest extent permitted by law, Scentsy Family or other persons creating or transmitting the information shall have no responsibility or liability to you or anyone else under any tort, contract, negligence, strict liability, products liability, or other theory with respect to any subject matter of this agreement or terms and conditions related thereto.

Related to Online Activity Reports

  • CONTRACT SALES ACTIVITY REPORT Each calendar quarter, Vendor must provide a contract sales activity report (Report) to the Sourcewell Contract Administrator assigned to this Contract. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Vendor must submit a report indicating no sales were made). The Report must contain the following fields: • Customer Name (e.g., City of Staples Highway Department); • Customer Physical Street Address; • Customer City; • Customer State/Province; • Customer Zip Code; • Customer Contact Name; • Customer Contact Email Address; • Customer Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Vendor.

  • Diversity Report The Contractor shall report to each Customer, spend with certified and other minority business enterprises. These reports shall include the period covered, the name, minority code and Federal Employer Identification Number of each minority business utilized during the period, Commodities provided by the minority business enterprise, and the amount paid to each minority business on behalf of each purchasing agency ordering under the terms of this Contract.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Daily Job Reports 6.7.2.1 Developer shall maintain, at a minimum, at least one (1) set of Daily Job Reports on the Project. These must be prepared by Xxxxxxxxx's employee(s) who are present on Site, and must include, at a minimum, the following information:

  • Privacy Statement 6.1. The Parties agree to keep all information related to the signing and fulfillment of this Agreement confidential, and not to disclose it to any third parties, except for subcontractors involved in this agreement, unless prior written consent is obtained from the other Party. Should subcontractors be engaged under this agreement, they are required to adhere to its terms and conditions.

  • Diversity Reporting Upon request, the Contractor will report to the Department its spend with business enterprises certified by the OSD. These reports must include the time period covered, the name and Federal Employer Identification Number of each business enterprise utilized during the period, commodities and contractual services provided by the business enterprise, and the amount paid to the business enterprise on behalf of each agency purchasing under the Contract.

  • Billing Information 6.1 NLT and the RL shall provide each other with information within their possession that is necessary to allow them to provide accurate and timely billing to each other and to any other relevant third parties.

  • INCIDENT REPORTS Any serious occurrence involving a beneficiary, outside the normal routine of the OTP (see TRICARE Operations Manual (XXX), Chapter 7, Section 4), shall be reported to the referring military providers and/or Military Treatment Facility (MTF)/Enhanced Multi-Service Market (eMSM) referral management office (on behalf of the military provider), and DHA, and/or a designee, as follows: (a) An incident of a life-threatening accident, patient death, patient disappearance, suicide attempt, incident of cruel or abusive treatment, or any equally dangerous situation involving a beneficiary, shall be reported by telephone on the next business day with a full written report within seven days. (b) The incident and the following report shall be documented in the patient’s clinical record. (c) Notification shall be provided, if appropriate, to the parents, legal guardian, or legal authorities.

  • Project Reports 1. The Borrower shall monitor and evaluate the progress of the Project and prepare Project Reports in accordance with the provisions of Section 5.08 of the General Conditions and on the basis of the indicators agreed with the Bank. Each Project Report shall cover the period of one calendar semester, and shall be furnished to the Bank not later than one month after the end of the period covered by such report.

  • Monthly Reports On or before the 15th day after the end of each month during the term of this Management Agreement, Manager shall prepare and submit to Owner the following reports and statements:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!