Managing Your Listing Sample Clauses

Open Split View

Download

Share

Cite

Managing Your Listing. Cancellations, Travel Issues, and Booking Modifications.

Sample 1

Save

Copy

Managing Your Listing 

Sample 1Sample 2Sample 3See All (7)

Save

Copy

Related to Managing Your Listing

• Information About You and Your Visits to the Website All information we collect on this Website is subject to our Privacy Policy. By using the Website, you consent to all actions taken by us with respect to your information in compliance with the Privacy Policy.

• Using Your Card You understand that the use of your credit card or credit card account will constitute acknowledgement of receipt and agreement to the terms of the Credit Card Agreement and Credit Card Account Opening Disclosure (Disclosure). You may use your card to make purchases from merchants and others who accept your card. The credit union is not responsible for the refusal of any merchant or financial institution to honor your card. If you wish to pay for goods or services over the Internet, you may be required to provide card number security information before you will be permitted to complete the transaction. In addition, you may obtain cash advances from the Credit Union, from other financial institutions that accept your card, and from some automated teller machines (ATMs). (Not all ATMs accept your card.) If the credit union authorizes ATM transactions with your card, it will issue you a personal identification number (PIN). To obtain cash advances from an ATM, you must use the PIN issued to you for use with your card. You agree that you will not use your card for any transaction that is illegal under applicable federal, state, or local law. Even if you use your card for an illegal transaction, you will be responsible for all amounts and charges incurred in connection with the transaction. If you are permitted to obtain cash advances on your account, you may also use your card to purchase instruments and engage in transactions that we consider the equivalent of cash. Such transactions will be posted to your account as cash advances and include, but are not limited to, wire transfers, money orders, bets, lottery tickets, and casino gaming chips, as applicable. This paragraph shall not be interpreted as permitting or authorizing any transaction that is illegal.

• Quarterly Reporting If reporting is on a quarterly basis, the AGENCY shall submit to the Orange County Citizens’ Commission for Children a complete, accurate, and programmatic Quarterly Report, in a format as provided by the COUNTY, on or before the 10th of the month following the close of the quarter, as well as supporting documentation. The Quarterly Reports shall, if applicable to the Scope of Work in Attachment “A”, list “Units of Service” provided (i.e.: hourly, per session, etc.) and/or any other pertinent outcome measurements outlined in Attachment “A”.

• PAYING YOUR BILL 10.1 What you have to pay

• Know Your Customer Information The Administrative Agent shall have received at least three Business Days prior to the Closing Date all documentation and other information about the Borrower as has been reasonably requested by the Administrative Agent at least 10 Business Days prior to the Closing Date that is required by regulatory authorities under applicable “know your customer” and anti-money laundering rules and regulations, including without limitation the USA PATRIOT Act.

• Quarterly Reporting Timeframes Quarterly reporting timeframes coincide with the State Fiscal Year as follows: Quarter 1 - (July-September) – Due by October 10 Quarter 2 - (October-December) – Due by January 10 Quarter 3 - (January-March) – Due by April 10 Quarter 4 - (April-June) – Due by July 10

• Management; Community Policies Owner may retain employees and management agents from time to time to manage the Property, and Owner’s agent may retain other employees or contractors. Resident, on behalf of himself or herself and his or her Guests, agrees to comply fully with all directions from Owner and its employees and agents, and the rules and regulations (including all amendments and additions thereto, except those that substantially modify the Resident’s bargain and to which Resident timely objects) as contained in this Agreement and the Community Policies of the Property. The Community Policies are available at xxxxx://xxxxxxxxxxxxxx.xxx/policies.pdf or on request from the management office and are considered part of this Agreement.

• Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

• 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: 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

• Anti-Money Laundering and Red Flag Identity Theft Prevention Programs The Trust acknowledges that it has had an opportunity to review, consider and comment upon the written procedures provided by USBFS describing various tools used by USBFS which are designed to promote the detection and reporting of potential money laundering activity and identity theft by monitoring certain aspects of shareholder activity as well as written procedures for verifying a customer’s identity (collectively, the “Procedures”). Further, the Trust and USBFS have each determined that the Procedures, as part of the Trust’s overall Anti-Money Laundering Program and Red Flag Identity Theft Prevention Program, are reasonably designed to: (i) prevent each Fund from being used for money laundering or the financing of terrorist activities; (ii) prevent identity theft; and (iii) achieve compliance with the applicable provisions of the Bank Secrecy Act, Fair and Accurate Credit Transactions Act of 2003 and the USA Patriot Act of 2001 and the implementing regulations thereunder. Based on this determination, the Trust hereby instructs and directs USBFS to implement the Procedures on the Trust’s behalf, as such may be amended or revised from time to time. It is contemplated that these Procedures will be amended from time to time by the parties as additional regulations are adopted and/or regulatory guidance is provided relating to the Trust’s anti-money laundering and identity theft responsibilities. USBFS agrees to provide to the Trust: (a) Prompt written notification of any transaction or combination of transactions that USBFS believes, based on the Procedures, evidence money laundering or identity theft activities in connection with the Trust or any Fund shareholder; (b) Prompt written notification of any customer(s) that USBFS reasonably believes, based upon the Procedures, to be engaged in money laundering or identity theft activities, provided that the Trust agrees not to communicate this information to the customer; (c) Any reports received by USBFS from any government agency or applicable industry self-regulatory organization pertaining to USBFS’ Anti-Money Laundering Program or the Red Flag Identity Theft Prevention Program on behalf of the Trust; (d) Prompt written notification of any action taken in response to anti-money laundering violations or identity theft activity as described in (a), (b) or (c) immediately above; and (e) Certified annual and quarterly reports of its monitoring and customer identification activities pursuant to the Procedures on behalf of the Trust. The Trust hereby directs, and USBFS acknowledges, that USBFS shall (i) permit federal regulators access to such information and records maintained by USBFS and relating to USBFS’ implementation of the Procedures, on behalf of the Trust, as they may request, and (ii) permit such federal regulators to inspect USBFS’ implementation of the Procedures on behalf of the Trust.