ARTICLE 1: APPLICATIONS OF CONDITIONS

1.1 TrillionThings.io is a trading name for the DataPlane Ltd (the "Supplier"). The Supplier shall provide the Data Orchestration Cloud Service ("Services") or ("service") to The Customer and The Customer shall consume the Services in accordance with these Conditions which shall govern the contract between the parties to the exclusion of any other terms or conditions whether proposed by The Customer, implied by law, trade custom, practice or course of dealing or otherwise (the "Contract").

ARTICLE 2: MEANS

2.1 In the context of the Services, The Supplier shall provide The Customer with centralized, regionalized and or local instances of: protocol socket also referred to as Service Access Point or ("SAP") fixed geolocated SAP IP address in compliance with the physical location, message storage, message queuing services, for customer to use with their IoT assets. IoT assets refers to The Customer physical IoT device(s) and or head-end (upstream) application server in the cloud or on customer premises.

2.2 Resources allocated to The Customer such as SAP and message storage are either DEDICATED/Private to The Customer or SHARED by The Customer with other Customers. Where The Customer opts to use shared SAP, the performance cannot be guaranteed. 2.3 Depending on the selected type of Services (private SAP, message storage, message queueing, protocol transformation, etc.) different features and/or options may be available. E.g. when using private SAP additional IoT application framework types are supported than when using the shared SAP services. Message storage service is a multi-tenant, geo-redundant service that is encrypted at rest on the storage and in transaction.

2.4 Before choosing and using primary subscription or any addon services, The Customer undertakes to carefully examine that the addon(s) it has subscribed to are not already provided on the primary subscription package to avoid charges for services already available on its primary subscription package.

The Customer undertakes to ensure the combination of features that constitutes a primary subscription package are suitable for their IoT assets. The Customer shall ensure that the primary subscription package and or any additional addon service it has subscribed to are configured correctly in the appropriate service objects (" Device Object(s)", "Service Template(s)" and "Customer Endpoint Profile(s)"). The customer shall also ensure the subscribed and or configured services can be used as a suitable combination for their fleet of IoT assets. The different service types, configurations and characteristics are described and available online in the documentation section of The Supplier website.

From time to time new configuration option, new service versions and configurations may be added to improve security, performance and support new features and services. It is up to The Customer to pay attention to these developments.

2.5 Resources (Private SAP, Shared SAP, storage, queue and service objects) available to The Customer remain the exclusive property of The Supplier.
2.6 The Infrastructure capabilities used in connection with the Service may be limited.
2.7 Due to the highly-technical nature of the Service, The Supplier is only subject to an obligation of means.
2.8 For the entire duration of the subscription, The Supplier provides The Customer with a Management Interface that enables them to manage the Services, configure their devices and service objects and retrieve their stored and or queued messages.
2.9 The Customer may access the IoT messaging service via the internet where The Customer is using the cloud based IoT messaging service.
Customers with on-prem deployment of the Services will have full control over the access to the service from within or from outside of their organisation. This document focuses on The Customers using the cloud based service.
The Customer must have an internet connection in order to log in to the Management Interface and access the Service, and is solely responsible for the aforementioned internet connection, in particular its availability, reliability and security.

ARTICLE 3: TECHNICAL SUPPORT

3.1 Where The Supplier is responsible for any disruption to the Service, The Customer has the right to contact the support service via the Management Interface, or by using the contact details available on The Supplier website. Each request or incident report received results in the creation of a ticket ("incident ticket"). The customer is notified by email of the creation of the ticket and the corresponding number.
3.2 When an incident has been submitted, The Customer provides The Supplier with as much information about the problem, to enable the successful completion of diagnosis.

ARTICLE 4: CONDITIONS OF USE OF SERVICES

4.1 The Customer subscribes to the Services on The Supplier website. The subscription requires the registration of a payment method from which payments shall be executed for the primary subscription packages and or any addon subscription The Customer has subscribed to.
4.2 From the time of confirming account registration (activation) of the Services, The Customer has the ability to create service objects and subscribe and or switch between primary subscription packages as well as subscribe to one or more addons in the Management Interface to manage and use the Services.
4.3 The Customer shall be the sole administrator of their account. The Supplier shall under no circumstances be involved in the administration of The Customer's account. Similarly, The Customer bears sole responsibility for their usage of the services such as message storage, message queues and staying within the subscribed limits for storage size, iot device bundles, per message (payload) size limit provided to them.
4.4 The Supplier is responsible for the administration of the cloud Infrastructure on which the services of The Customer are configured.
4.5 The Customer confirms they have all the necessary technical knowledge to ensure the correct administration of the Services and underlying service objects on their account. The Customer confirms to back up their device objects, messages in the message storage and message queue resources. The Customer also undertakes to acquaint themselves with the documentation related to the Services, provided by The Supplier.
4.6 The Customer bears sole responsibility for the application framework, protocol, configuration and data running on and or sent or received from their IoT assets where applicable. The Supplier shall not be liable for any failure of the proper operation of the aforementioned objects and entities.
4.7 The Customer undertakes to comply with the licence conditions and conditions of the operating system and or the licence conditions and conditions of use of the applications used on their IoT assets.

The Supplier reserves the right to modify the Services in particular by way of any updates and/or version upgrades that it deems necessary in their sole discretion. The Customer assumes full responsibility for maintaining their IoT assets and ensuring all necessary security maintenance operations are carried out in a timely fashion. The Supplier shall not under any circumstances be held responsible, including without limitation where said operations (maintenance, updates, etc.) are performed in violation of the applicable conditions of use/licence conditions, or where The Customer IoT assets fails to perform and/or operate correctly following maintenance operations and/or updates performed by The Customer.

4.8 The Supplier reserves the right to restrict access to certain IP addresses, ports and protocols which are deemed to be sensitive in order to protect the Infrastructure. Similarly, The Customer acknowledges that the TCP/IP and UDP/IP underlying transport protocol flows are limited.

4.9 The Customer has the option, via the Management Interface, to increase and decrease the number of IoT assets for example device bundle, upstream head-end application (messaging endpoint profiles) and storage capabilities and volume in their account.
The customer has the option to request for private dedicated SAP for any of the supported protocols and application framework. The Customer must first subscribe to the private SAP (addon) service and then raise a ticket via the management interface to provide details (protocol type, application framework, preferred region etc) for each of the private SAP setup required by The Customer. The request is handled asynchronously. Upon receipt of the request The Supplier will endeavour to issue the requested number of private SAP with the setup requested where possible. The Supplier reserves the right to reject any request that is deemed as contravening our terms of use or risks compromising security of The Supplier services and features or Customer assets. The Supplier shall fully refund The Customer where a private SAP request cannot be fulfilled. The Customer shall be liable for paying for private SAP when issued by The Supplier.

The Customer is solely responsible for operations (such as retrieving stored messages for backups, Snapshot, etc.) they deem necessary before deleting any of their IoT asset, stored and or queued messages. Before The Customer unsubscribes from a paid subscription package, down grades its subscription package or cancels one or more addons, The Customer shall ensure that the service object configuration, message storage usage, outstanding messages in the queue, etc that will exceed its down graded subscription limit are adjusted and or deleted in-line with the new subscription limit. This is especially important if the switching of subscription package or cancellation of addons will result in amongst others: reduced resource allowances, lower IoT device bundle size, reduced service object limits, reduced features, reduced message storage capacity, lower priority messaging, lower max payload per message, etc.

4.10 The Supplier reserves the right to limit or restrict certain functionality of the Services to guarantee the security of the Infrastructure.
4.11 The Customer undertakes to use the Service with good mutual understanding.

ARTICLE 5: OBLIGATIONS AND RESPONSIBILITY OF THE SUPPLIER

5.1 The Supplier shall provide the Services with reasonable care and skill and in accordance with good industry practice.
5.2 The Supplier undertakes to: a) Ensure the administration of The Supplier cloud infrastructure. The Supplier shall use reasonable endeavours to replace any defective part of the cloud infrastructure as soon as reasonably possible except where The Supplier is not directly responsible for the failure or in situations where the repair or replacement procedure requires an interruption of Service which exceeds the usual replacement time. In the latter case, The Supplier will notify The Customer as soon as reasonably practicable. c) Upon notification by The Customer of an incident, intervene as soon as possible, provided the incident is not caused by The Customer's misuse of the Instance.

Any data replication mechanisms implemented by The Supplier are under no circumstances a guarantee to The Customer against the loss of their contents and data.

ARTICLE 6: OBLIGATIONS AND RESPONSIBILITY OF THE CUSTOMER

6.1 The Customer acts as an independent entity and shall solely bear all risk associated with its activity when using the Services. The Customer is solely responsible for the IoT assets, content of transmitted, broadcast or collected data, the processing and updating of data, and message records sent to and or received from their IoT assets.

6.2 The Customer shall comply at all times with the Privacy and Electronic Communications (EC Directive) Regulations 2003 (the “PEC Regulations”).
6.3 The Supplier only ensures access to the Services to enable The Customer to store their data and where applicable their customer's data.
6.4 The Customer shall take all technical steps available to ensure that it holds and retains connection logs or any data which can allow anyone to identify any person who contributes to the creation of content for the services for which The Customer is the provider, according to the legislation in force and, shall at all times comply with the PEC Regulations.
6.5 The Customer undertakes to respect the rights of third parties, rights of the individual, intellectual property rights such as copyrights, patent rights or trademark rights, database rights and any other intellectual property. The Supplier shall not be held liable for the content of any transmitted, disseminated or collected data, data processing or updating, or any files, namely address files of any kind.
6.6 The Customer is prohibited from making any files or links that breach third party intellectual property rights, deploying services which are intended to cause security breaches, using proven spamming techniques on the internet, any intrusive activity or any intrusion attempt (including, but not limited to: port scans, sniffing, spoofing), and any activity or contentious behaviour such as traffic exchanging (Jingling, Hitleap, etc), crypto-currency mining, video game bots, etc. The customer agrees to fulfil any license that is required if they use a third-party software when using the Service.
6.7 In such events, The Supplier reserves the right to suspend the Service without notice and immediately terminate the subscriptions, without prejudice to the right to all damages that The Supplier may claim.
6.8 The Supplier shall therefore not be liable, in any way whatsoever, even jointly, for the information, messages, payload, files (especially address files), data and any other of The Customer's content, and the way in which it is used under the Service, including its transmission, broadcasting to internet users, collection, updating etc.
6.9 The Customer is solely liable for the consequences of any malfunction of their IoT assets as a result of any usage, by their staff or any person to which The Customer may have provided their password(s) and any other means of access (such as API access keys, Tokens, etc…).
Similarly, The Customer is solely liable for the consequences of the loss of passwords and any other means of access.
6.10 In order to maintain the security level of The Customer's account, The Supplier reserves the right to request that The Customer update their account details and any service objects created by The Customer where security vulnerability is identified. If The Customer does not act upon such requests, The Supplier reserves the right to disable the account, subscriptions and all access to the account. Similarly, in the event that The Supplier finds that The Customer account and or configured service objects represents a security risk, The Supplier may send an email to The Customer to inform the latter with a reconfiguration or deletion procedure to maintain the integrity of the Service and the Infrastructure. The Supplier reserves the right to disable the services on the account pending The Customer's reconfiguration of their service objects.
6.11 The Customer acknowledges that, for security reasons, some features and protocols are likely to be restricted under the Services. Anonymisation services (Proxy) and cardsharing (CCCam or equivalent) are prohibited under the Services.
6.12 The Services, especially the Cloud Computing technologies that The Supplier uses for providing the required services do not guarantee Service continuity or the protection or retention of Customer data.
6.13 It is The Customer's responsibility to pay for any subscriptions, addons, licenses or usage rights contracted with The Supplier. Should The Customer fail to do so, The Supplier reserves the right to suspend the Services without prior notification.
6.14 The Supplier reserves the right to carry out checks to ensure that The Customer's use of the Service complies with these conditions. The Supplier reserves the right to suspend the Service without notice, in the event of a breach by The Customer of The Supplier's Special Conditions, in general, of any applicable statutory and regulatory provisions, or of any third-party rights.

ARTICLE 7: Message Payload Ownership

7.1 The Customer retain ownership of the payload of IoT messages sent to and received from their IoT assets. No Customer payload data is shared with any third-party.

ARTICLE 8: MITIGATION (protection against DOS and DDoS attacks)

8.1 The Supplier shall implement protection against DOS and DDoS-type (Distributed Denial of Service) hacking attempts provided that these attacks are conducted in a manner reasonably considered to be serious enough by The Supplier to warrant such protection. In implementing such protection, The Supplier shall use reasonable endeavours to ensure that the operation of The Customer's Services is maintained throughout the duration of a DOS or DDoS attack.
8.2 The function in Article 8.1 involves monitoring the traffic sent to The Customer's Services from outside The Supplier's network. The traffic identified as illegitimate shall then be rejected by The Supplier prior to reaching The Customer's IoT assets, thus allowing legitimate use of the Services in spite of an attack.
8.3 As a result of the high technicality of the Service, certain attacks may not be detected by the protection measures implemented by The Supplier. The protection measures outlined in Articles 8.1 and 8.2 shall not apply in the case of attacks such as SQL injection, brute-force, abuse of security vulnerabilities, or attacks of a similar nature to the latter. In such cases, the Infrastructure and the Service may be temporarily suspended and unavailable.
8.4 Given the nature of a potential DOS or DDoS attack and their complexity, The Supplier shall implement different levels of traffic protection in order to preserve their Infrastructure and the Services.
8.5 The mitigation of a DOS or DDoS attack is activated only at the time of the detection of the attack by The Supplier and or The Suppliers cloud Infrastructure provider's tools and for a non-fixed period, and deactivated only once the attack and illegitimate traffic are no longer present. Thus until the mitigation is activated, the Service shall handle the attack directly, which may lead to the temporary unavailability of the Service.
8.6 While mitigation is activated, The Supplier shall not guarantee the accessibility of the Services but it shall endeavour to limit the impact of a DOS or DDOS attack on the services and on The Supplier's cloud Infrastructure.
8.7 If, in spite of the activation of mitigation, a DOS or DDOS attack is of such a nature as to adversely affect the integrity of The Supplier's Infrastructure or the infrastructure of the other customers of The Supplier, The Supplier shall strengthen its protection measures which may lead to the deterioration of The Customer's Services or impact its availability for which The Supplier shall not be liable.
8.8 Where part of the traffic generated by a DOS or DDOS attack is not detected by The Supplier's equipment and reaches The Customer's Services, the effectiveness of the mitigation shall also depend on the appropriate configuration of The Customer's Services. In this regard, The Customer must ensure that it has the adequate resources to administer the configuration of The Customer's Services properly.
8.9 The Customer shall be solely responsible for ensuring it secures its IoT assets and Services, implementing security tools (firewall, etc.), periodically updating their system, backing up their data and for ensuring the security of their software (scripts, codes etc.).

ARTICLE 9: GEOLOCATION

9.1 The Customer chooses their primary region during account creation or during account details update. The selected primary region is used to aid the selection and prioritization of regional gateways for upstream traffic routing towards customer application.
9.2 The Customer acknowledges and accepts that they are also subject to the legislation applicable on the territory where the cloud infrastructure is located. The Customer acknowledges and accepts that when the message storage service is used, the messages from The Customer IoT assets may be stored on encrypted block storages that may be hosted in a region other than their preferred primary region.
9.3 The Customer therefore acknowledges the ability of The Supplier to suspend the Service should it be used for a prohibited activity in the location of the cloud infrastructure used by The Supplier to provide the services.
9.4 Similarly, regarding geolocated IP addresses, The Customer undertakes to ensure that they do not use the Service to breach legislation applicable in the country for which the IP address is declared. If The Customer uses the Service in this way, The Supplier may be forced to suspend The Customers access to every one of their subscribed Private SAP or to all shared SAP.

ARTICLE 10: BACKUPS

The Customer is solely responsible for all measures to ensure the backup of data, especially when the data is sensitive and / or necessary for business continuity. The Customer is responsible for establishing and managing a business continuity plan and / or disaster recovery plan, and more generally all technical and organisational measures likely to enable The Customer to continue operating in the event of a major Services malfunction which may impact business continuity and the availability and integrity of their IoT asssets, content and data

ARTICLE 11: SERVICE LEVEL AGREEMENT (SLA)

11.1 The Supplier shall use its reasonable endeavours to meet the following Service level targets: (a) Shared SAP: Monthly availability rate: 99.9% (b) Private SAP: Monthly available rate: 99.99% (c) Management Interface: Monthly available rate: 99.95% (d) Message Storage Service: Monthly availability rate: 99.99% Monthly resilience rate of data: 100%. “Monthly availability rate” means the total number of minutes in the month minus the number of minutes of Unavailability in the month in question, divided by the total number of minutes in the month in question. “Unavailability” means the loss of access to The Customer's private or shared SAP, or the loss of connectivity to all the regional RESTful API gateway, for more than three (3) consecutive minutes.

The Supplier calculates the downtime from the moment an incident ticket has been opened by The Customer. If due to some configurations made by The Customer, The Supplier is not able to realise the above monitoring techniques to check the availability of Services, the commitment of availability set out above shall not apply. “Resilience” means the capacity of The Supplier to again provide The Customer with access to the private SAP, shared SAP and or messaging API interface prior to an incident of unavailability that has been duly notified (see the following conditions). The resilience commitment only applies to the management interface, messaging APIs and regional SAP services. The Supplier's resilience commitment is under no circumstances a guarantee to The Customer against the loss of their contents and data. The Customer remains responsible for their data backup and business continuity as stated in article 10. The Service level targets described above are in place; subject to the exclusions listed below and provided that The Customer works with The Supplier, in the event of unavailability, to restore the Service as described as follows. In the event of unavailability, The Customer shall declare the incident and shall provide The Supplier with all relevant information useful for the diagnosis and intervention by The Supplier. The Customer undertakes to remain constantly available in order to collaborate with The Supplier including by providing further information and carrying out all the necessary tests and checks. If necessary, The Customer agrees to give access to its Management Interface. If The Customer is not available or does not cooperate with The Supplier, it cannot benefit from the Service level targets defined. The above commitment does not under any circumstances apply to the availability of components that are under the responsibility of The Customer, in particular the software or applications installed and used by The Customer on their IoT assets.

11.2 If The Supplier ascertains that the Services is available and fully operational, The Supplier shall be absolved of this SLA. However, under these circumstances, The Supplier, at the request of The Customer, undertakes to assist The Customer in identifying the source of any difficulties found by The Customer. If The Supplier ascertains an Unavailability, it will complete the diagnostic and work in collaboration with The Customer to re-establish availability.
11.3 If the Service level targets defined above in Article 11.1 are not achieved, The Customer may, apart from the cases of exclusion numbered below, request the following Service credits: · Non-compliance with availability rate: Credit equal to 0.5% of the monthly fee paid for the month concerned by The Customer for the unavailable components per consecutive sequences of one (1) minute (beyond the first three (3) consecutive minutes of lost access or connectivity), up to a maximum of 25% of the monthly amount of the subscription and or addon in question.

The funds are credited directly to The Supplier account belonging to The Customer, on The Customer's request. The Customer must make their request in their Management Interface, in the month following the month in which The Supplier recorded the downtime. Otherwise, The Customer is no longer able to obtain such compensation. The credit must be used by The Customer under the Public Cloud Service in the calendar month following the month when they were credited to The Supplier account belonging to The Customer. Otherwise, the credit is lost and cannot be used. Credit can under no circumstances be refunded to The Customer in cash. It is expressly agreed that the aforementioned Service credits are The Customer's sole remedy for all damages, losses, liabilities, costs and expenses resulting from The Supplier's failure to comply with its obligations. As such, The Customer will renounce any further requests, claims and/or action. If an event leads to the failure of several Service level agreements, the credits cannot be combined. The Customer will receive the most favourable credit amount.

11.4 The Customer may not claim for aforementioned Service credits where the unavailability or Resilience breach results, in whole or in part from (i) events or factors beyond control of The Supplier, including but not limited to events of force majeure, actions of a third-party, internet connection issues, the malfunction of the internet, the malfunction or misuse of hardware or software under the control of The Customer (in particular applications running on their IoT assets), (ii) a breach of the obligations of The Customer pursuant to this Contract (in particular failure to collaborate with The Supplier to resolve the incident), (iii) the misuse or inappropriate use of the Service by The Customer (in particular the misuse of the Instance or The Supplier Management Interface), (iv) scheduled maintenance, (v) an interruption caused by The Supplier's intervention under the Conditions set out in Article 6 of this document, or (vi) computer hacking or piracy. In such cases, excluding point (iv), The Supplier reserves the right to invoice The Customer for the cost of the work done to re-establish the availability of the Services. The Supplier shall provide a quotation for such work, which shall be sent to The Customer for approval. The Supplier shall use all reasonable endeavours to establish the cause of the unavailability, and confirm which exclusion set out above applies. The Supplier shall be permitted to use components in its information system (such as connection data) for this purpose.

ARTICLE 12: DURATION OF CONTRACT AND SERVICE

12.1 The Customer is not bound to any contract at account activation (first successful login) time. At any time after account activation The Customer may subscribe to a paid primary subscription package. The subscription packages are based on monthly rolling contract further referred to as "Contract" or "contract". The contract shall commence from the date The Customer subscribes to its first paid subscription package. The contract shall remain in force for an indefinite period. It may be terminated in accordance with The Supplier's terms and conditions.
12.2 The Customer may choose, based on their requirements, to add supplemental services referred to as "Addons" or "addon" such as private SAP, extended message storage capacity, etc. via the Management Interface.
12.3 There is no minimum duration of use. However, any month started shall be invoiced by The Supplier and paid in full by The Customer, in accordance with the conditions set out in Article 13.

ARTICLE 13: PRICES, PAYMENT METHODS AND BILLING

The prices subscription packages and Addons are available at https://trillionthings.io. These prices are quoted in US dollars or pounds sterling and exclusive of VAT.
The Supplier shall bill The Customer monthly Services fee at the end of their billing cycle. The Customer's billing cycle begins at the commencement of the contract and automatically renews one month after. For example, if The Customer decides to subscribe to a paid subscription package on the March 8, the first billing cycle ends April 7, and the second billing cycle begins on April 8. If the commencement date is the 29th, 30th or 31st, the beginning of the second and future billing cycles will be on the 1st, 2nd, and 3rd, respectively.

13.1 The prices of each subscription package and addon is based on A fixed-rate monthly billing cycle payment plan. The fixed-rate payment plan allows The Customer to use the subscription package services during the full billing month. With regards to addons, the fixed-rate payment plan allows The Customer to use the addon services as long as it is subscribed to. As soon The Customer unsubscribes from an addon (addon cancellation), the services and features provided by the addon will with immediate effect no longer be available to The Customer. The addon usage for that billing cycle is pro-rated to ensure The Customer is charged only for the period within the billing cycle when the addon was active.
If The Customer switches to another primary subscription package during the month, the monthly payment plan shall be invoiced on a pro-rata basis for the remainder of the billing cycle. The fixed-rate monthly payment plan (in full or on a pro-rata basis under the conditions detailed above) shall be paid in full by The Customer. This also applies where the subscription is cancelled before the end of The Customer billing cycle.
Any subscription that is active shall continue to be invoiced at every billing cycle (monthly) by The Supplier to The Customer even if the Services is not used.
With regards to the message storage services, the storage service shall be charged per gigabyte once The Customer exceeds its free storage service allowance (if applicable). The gigabyte of message storage is always charged as a whole, even if it is not fully used (rounded to the superior gigabyte).

13.2 The Supplier reserves the right to invoice the cost of these Services to The Customer before the end of the billing cycle of use in the event that the Services used by The Customer reach a significant total amount during the billing cycle month. The contract commencement time is evaluated by The Supplier based on the data available on its systems. The data is considered binding and fully enforceable on The Customer. The Customer shall be billed at the end of every billing cycle (invoice creation date), by automatically billing The Customer's default credit/debit card on file or Customer's Supplier Account. The Customer undertakes to always retain a sufficient amount, in the default credit/debit card to pay for their invoices within the agreed deadlines. If The Supplier is unable to take payment from the payment method, an email shall be sent to The Customer requesting settlement of the outstanding amount as soon as possible. In the absence of prompt payment, the Service will be suspended by The Supplier for non-payment.

ARTICLE 14: TERMINATION, LIMITATION AND SUSPENSION OF SERVICE

14.1 Each party may terminate the Contract without liability to the other party in an event of force majeure as stated in The Supplier General Terms and Conditions.
14.2 In other cases, The Customer is free to terminate the Contract upon 30 days' notice by submitting a termination request via the Management Interface or by using the contact details available on The Supplier website.
14.3 In all cases where The Customer breaches the provisions of Article 6 in these special terms and conditions, particularly by carrying out any expressly prohibited activity using The Supplier's servers and/or publishing expressly prohibited content on The Supplier's servers and/or any activity that could potentially give rise to civil and/or criminal liability and/or affect the rights of third parties, The Supplier has the right to disconnect and/or interrupt The Customer's services immediately and without prior notification and to terminate the Contract with immediate effect and without notice to The Customer, without prejudice to the right to damages that The Supplier may claim.
14.4 Under the terms of this Contract, in the event of termination regardless of the reason for termination, The Customer's messages (both meta-data and payload), device objects and all configuration shall be deleted.
14.5 In the event of any Customer breach and where The Supplier elects not to terminate for breach, Services will be either restricted, limited or suspended depending on the gravity and the frequency of the breach. The measures will be determined based on the nature of the breach(es) established.
14.6 The Customer accepts in advance that The Supplier shall implement restriction, limitation or suspension measures of the Service where The Supplier receives a notification accordingly from a competent administrative, arbitration or judicial authority, pursuant to the appropriate applicable laws.

BY PLACING AN ORDER ONLINE, THE CUSTOMER SIGNIFIES THEIR UNCONDITIONAL ACCEPTANCE OF THIS CONTRACT. If The Customer has any questions after reading this contract, they should contact The Supplier using the contact form on The Supplier website or post address provided on The Supplier's website at trillionthings.io.