Search Results

3T is a leader in network solutions and logistics / transportation software, 3T's Event software redefines how you optimise the position of your business on a global scale in todays digital world. Event. Start building your next integration with Event Connect Register interest View documentation Technology that improves your business Our Event Connect API solutions are designed to be innovative and easy-to-use, allowing you to build new experiences with our TMS. Speed up your development with our specialised integrations: EVENT Order – order message solutions EVENT G0 – delivered receipt solutions View documentation Order Message solutions EVENT Order is our point-of-order integration pushing incoming orders directly into the planning and optimised plan information back Learn more Order Tracking solutions EVENT Go are a suite of API's that directly connect you to your logistics network through Event. It provides visibility, delivery and invoice detail so you can stay in control of keeping your customers happy. Learn more POD / Invoice solutions EVENT Go includes tracking, proof-of-delivery, additional cost requests and invoice detail from your chosen logistics providers Learn more

Home / Product Line Our connect API landing page is below, here you can download the swagger, see example json requests and code examples. https://event3tdev.developer.azure-api.net/ Once you are ready to get started please send an email over to servicedesk@3t-europe.com . We will send you back an API key that you can use for testing purposes. Carrier Connect API An API for Carriers to plug into Event This API allows carriers to pull data from Event, update Event with tracking, shipping labels and much more. Retrieve a route from Event In Event each of your routes will have a unique id number, this id can be found in connect. This unique identifier can be used to communicate with Event through our API and pull back route data for a specific route id. Example below. https://event3tdev.azure-api.net/carrierconnect/route/1e11Em49 This will return all the route detail for this route and all the detail for each of the stops on the route. Get all routes by collection date You can also pull all your routes for a given collection date. https://event3tdev.azure-api.net/carrierconnect/routes/2022-09-07 This will return a collection of routes, it will still included all the stop level detail. Get all customers you are connected to in Event If at any time you want to see all of the customers you are connected to in Event, you can call the operation below. https://event3tdev.azure-api.net/carrierconnect/accounts/ No parameter needs to be passed, we will identify who you are by the key you have passed in the request. Update routes and stops in Event The connect API also gives you the ability to send us information and update your routes/stops in Event. For example the below operation can be used to send us back shipping labels, documents and costs. https://event3tdev.azure-api.net/carrierconnect/stops/ Send us tracking updates You can send us back tracking information using the operation below, there is also the option to send us back GPS information so we can track the shipment on route. https://event3tdev.azure-api.net/carrierconnect/trackingevents/ Need us to push updates to you? If you need us to push information to you we have got you covered, using the operation below you can register a url for us to send webhook notifications to. https://event3tdev.azure-api.net/carrierconnect/trackingevents/ Currently, our recommended best practice for securing Webhooks involves using basic authentication and HTTPS on your endpoint. This will help prevent any altering of any information communicated to you by 3T, prevent any third parties from seeing your webhooks in transit, and will prevent any third parties from masquerading as 3T and sending fraudulent data. 3T performs certificate validation and requires any TLS-enabled (HTTPS) webhook recipients to have a certificate signed by a public trusted certification authority. We do not support sending webhooks to over SSLv2, SSLv3, or any connection using so-called export-grade ciphers. The example response shows the webhooks event you will receive to your endpoint once it is enabled.

Home - Documentation - Validation and certification (Event Go) Validation and certification Event Go Documention Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Event Go API (POD) Overview Our test scenarios are meticulously crafted to ensure partners have accurately configured their systems to seamlessly interact with our Delivery as a Service APIs. Prior to going live, partners must successfully pass certification tests to validate integration against our specified requirements, ensuring a reliable interaction with our delivery services. Key verification points include: Estimate Payload Verification: Validate parameters such as weight, preparation duration, alcohol availability, target delivery time, and address accuracy. Delivery Payload Verification: Assess parameters including target collection time, vendor order ID, and special instructions. Request Identifier Mapping: Ensure proper mapping of requestId as a unique identifier for each SaaS delivery. Delivery Creation Verification: Confirm partners create the NEW, UPDATE, CANCEL, COMPLETE delivery API call to verify creation. De How does it work? Onboarding Getting started Delivery simulation Validation and Certification

Home - Documentation - Getting started (Event Go) Event Order API (POS) About our Partnership How does it work? Integration flow Getting started Environment-Specific Endpoint: In this section, you’ll find a comprehensive list of endpoint URLs tailored to different environments. Whether you’re testing on staging, developing locally, or production, ensures seamless integration by selecting the appropriate URL corresponding to your environment. Here is the Environment Specific Endpoints: UAT - POST https://event3tuat.azure-api.net /Oasis/omf PROD - POST https://event3t.azure-api.net /Oasis/omf General API Management Gateway - https://event3tuat.azure-api.net Event Go Documention Additional information Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification next... Delivery simulation

Event Connect About Event Connect Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Event Go API (POD) Overview How does it work? Onboarding About Event Connect Event Connect is an API logistics integration, aimed a providing a platform that fits the majority of Point-of-sale systems while at the same time giving the Event TMS with all the data it needs to provide the perfect Transport Management result for the customer. What is this partnership? Getting started Delivery simulation Validation and Certification

Home - Documentation - Delivery simulation (Event Go) Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Delivery simulation The Delivery Simulation Endpoint facilitates external partners in emulating the complete delivery process for testing objectives. Engineered to replicate real-world delivery workflows, it initiates from assigning the delivery to a courier and advances through sequential stages until the delivery fulfillment. At each juncture, a webhook is activated, enabling external partners to validate the integration with their system. It's crucial to note that this endpoint is exclusively accessible within staging environments. Following the creation of an /estimate and /delivery, you gain access to utilize the generated requestId for accessing the simulate endpoint. This endpoint enables you to simulate the entire delivery process, providing a realistic emulation of the workflow from start to finish, thereby allowing comprehensive testing and validation of your integration This funtion is tbc Event Go Documention Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification next... Validation and certification

Self-serve rate card import Uploading rate cards for carriers you connect with To use a non parcel carrier, you will need to upload a rate card A rate card simply shows where a carrier will deliver to and how much that delivery will cost... If you are using ROUTE in Event you will need to connect to carriers. To allocate routes to your connected carrier you need a rate card. Carriers in Event have a standard universal rate card or you can arrange and negotiate your own rates. This guide assumes you have created an account with a carrier, connected to them through Event and now need to upload your negotiated rate card so you can start allocating routes. Connect and allocate Decide on a carrier and create an account [contract] with the carrier (outside of Event) Connect to your chosen carrier through Event* Receive a 'carrier now connected' notification Create a rate card, upload. Start allocating routes to your carrier * A carrier will add themselves to EVENT through being invited. They only need to be invited once and in doing so will create access, login details and a 'connected' presence in the Event ecosystem overall for all current and future Accounts to connect to. You just need to upload a rate card.. * There is not set requirement for naming a rate card upload file. We will add a date time stamp to make sure it is unique Do not change the format of these rate cards! Download, change the date but not the headers or the tab names Which rate card do i use? The rate card templates are simply based on the a tariff in WEIGHT or PALLET based. Are you adding a groupage pallet tariff or one based on weight? hint: FTL is always added as weight. See the examples below to help you quickly create a rate card. If creating an FTL tariff, use the Template 1. This includes EXW. If creating an Groupage PALLET based tariff, use the Template 1 If creating an Groupage WEIGHT based tariff, use the Template 2 Standard plt / weight tariff click to download Template 1 FTL all postcode Rate card template PLT - Day / night / weekend / holiday 19-04-2023 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc This tariff includes where a carrier provides different costs based on the time of day or day of week It is only for the FTL sheet, not for Groupage Column J cannot be used if any of columns O-T are being used. Leave J as = blank Column U can be used with either column J or columns O-T. It can also be used on its own. The daytime setting can be configured in AccountVITALS / Setup Basics / Rate Card Bank holidays can be configured in AccountVITALS / Setup Basics / Holidays The headers for columns O-U will be used to show as the servie in Change Carrier Template 2 Groupage all UK postcode rate card template PLT. Upto 10 plts 12-02-2019 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc Template 3 Rate card template weight - Groupage 12-02-2019 - AP Hint: Its important to define if the Groupage tariff is per weight band or pallet. The excel spreed sheet tab defines this Template 4 Rate card template weight bands- Groupage 17-09-2021 - AP This function includes 2 new columns. 'PER' column and 'ROUNDING' column. PER = rate per kg. This can be 1 as std or 100kg ROUNDING = set to round by, e.g. 10 (to mearest 10) The PER calculation example is: 99-250kg line in tariff rate = 39.98 Set PER rate as 100kg Shipped 145kg Set rounding to 10kg (nearest 10kg) so 150kg calculated rate = 39.98 x 1.5 Template 4a Rate card template weight bands with minimum charge 14-09-2022 - AP Template 5 Rate card template pallet per lifts - Groupage 17-09-2021 - AP This function is the standard Groupage rate card by pallet. The difference is a configuration to set between per plt or per lift. This Lift configuration will use the stackability from the Stop. If 7 plts and stackable, lifts = 3 lifts The default is per pallet. Groupage rate card by m3 Template 6 GRP rate card by m3 08-05-2021 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc Use column F & G for calculating Stop volume (10-15 m3 band = 4.50 x total m3) Use column H & I for calculating Stop volume as a fixed total cost (10-15 m3 band = 180.00 fixed rate) To set the calcuation at PLANNED or DESPATCHED status, use the configuration in Carrier VITALS To speed up creating multi equipment type FTL rate cards... Template 7 FTL x3 equipment types UK postcodes template 12-02-2019 - AP Template 8 FTL x2 equipment types UK postcodes template 12-02-2019 - AP Distance tariff by metric Template 9 Distance tariff from a source point 12-02-2019 - AP This distance tariff allows for a cost to be calculated from a source postcode and by a metric, i.e. per tonne Distance tariff from point A-B Template 10 Distance tariff from a source point 12-02-2019 - AP This distance tariff allows for a cost to be calculated based on the actual distance banding from any location to any location. It is not dependant on any metric, simply a cost per distance by an equipment type Parcel tariff by service Template 12 Parcel tariff by weight and service 11-10-2021 - AP Tariff for calculating parcel wieght and service through SLM rules What if i want to use a carrier but i have no rate card? You do not need to add a rate card for a carrier to be able to use the carrier in Event. Using Event's 'Spot Rate' function lets you allocate to any carrier at any time Rate Card Validation So once you have uploaded a rate card, AMI will validate the contents and notify you of the result. The validation will include format and contents, providing information, where a failure occurs on what the failure is. Initial validation that must be passed to proceed; 1. Correct column headers Validation will fail if the headers are named differently to the template. Validation error message ' Column headers are not named correctly' 2. Correct order of the columns Validation will fail if the columns are not in the correct position. Validation error message ' Columns are not in the required positions' 3. Carrier ID Validation will pass if the carrier ID exists on the Account being uploaded to and will fail if the carrier does not exist in Account receiving upload. Validation error message for notification and storing ' Carrier ID must match the carrier's code in Carrier VITALS' Specific validation 1. Origin country Is required. Format is ISO code. Validation error message ' Add a valid ISO 2 digit country code, i.e. US, GB ' 2. Origin code Is required. Format can be numbers or letters. CV, 01, 850. Validation error message 'Valid post or area code required in the format of at least the 1st 2 digits of the code, i.e. CV, 11, 98' 3. Destination country Is required. Format ISO code. Validation error message ' Add a valid ISO 2 digit country code, i.e. US, GB ' 4. Destination code Is required. Format c an be numbers or letters . CV 22 6HL , CV 22, CV , 01, 01000, 10000. Validation error message 'Valid post or area code required in the format of at least the 1st 2 digits of the code, i.e. CV22, 11, 98' 5. FromBand Is required. A number of at least 0. Can be format 1.000000001. Validation error message 'Must add a number in the format 1 ' Example: for FTL this would be 1 6. ToBand Is required. A number of at least 0. Can be format 1.000000001 if Groupage. Validation error message 'Must add a number in the format 2.000000001 ' Example: for FTL this would be 99999 7. Stop rate Is required if Delivery type = FTL. Format must be 0.00. Validation error message ''Rate must be included for FTL and cannot be left empty. It can be 0.00' 8. Equipment Is required. Validate the equipment type against the Account Equipment database and if a match can be found allow, if no match fail validation. Validation error message '[failed equipment name] is not a valid equipment type for this Account. Please use a valid type or update your equipment' 9. SLM rule Not required. Default is blank. This is a specialist rule for RULE ASSIST only. Max characters = 10 Validation error message where not matching rule is found in SLM 'No matching rule found in Route Assist rules' To use this rule, ROUTE ASSIST rules for the carrier must match those in the rate card. To use this function, add the SLM rules to the ROUTE ASSIST column called 'Groupage type' *this rule will lookup ROUTE ASSIST rule, take the associated Groupage Type and when looking up the rate card, will look to match a SLM rule to the Groupage type added. 10. Mode Is required. Must be LAND, AIR or SEA. AMI will default to LAND if not added. If added but not one of the 3... Validation error message 'Mode must equal LAND, SEA or AIR in this format ' 11. Service Is required. Default is Economy. AMI will default to Economy if not added. If added but not Economy, check for match in Account's Service and update. No validation message. 12. Delivery type Is required. Must be '2' for FTL or '4' for Groupage. Validation error message 'Delivery type must be '4' for GROUPAGE or '2' for FTL' 13. Cost Is required. validation just a number. Must be a number in format 0.00, 200.00. Can be 0.00 if no rate is known. Validation error message 'A rate must be included and cannot be left empty. Format is 0.00. It can even be 0.00 '

Home - Documentation - Additional information (Event Order) Event Order API (POS) Additional information For more information on how to integrate your POS with Aptean Event, please visit our API Developer Portal . Event Go Documention About our Partnership How does it work? Integration flow Additional information next... Event Go - Overview Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification

Home - Documentation - How does it work? (Event Go) Event Order API (POS) About our Partnership How does it work? Integration flow Additional information How does it work? Here is an example of how we will take care of the last-mile logistics on your behalf: Customer creates an ORDERS and triggers through Event Order API Event TMS plans and optimises the order, allocating it to the best carrier and rate Event Go API will trigger the planned ROUTES back to the customer The preferred Logistics Provider will start the deliver and Event Go can trigger TRACKING UPDATES When the delivery is confirmed, Event Go can trigger DELIVERY CONFIRMATION with PROOF OF DELIVERY (POD) Any additional and approved COST ADDITIONS can be triggered by Event GO Finally, Event Go can trigger the logistics Providers Invoice breakdown to complete the delivery exacution of the order. Event Go Documention Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification next... Onboarding

Home - Documentation - Overview (Event Go) Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Overview Welcome! Event Go is our last-mile delivery product that directly connects you to your logistics network. Through our external APIs, you can seamlessly request updates on the status of your orders delivering or delivered to your customer’s. This section provides documentation and resources to assist you in setting up your POS integration to receive delivery status updates using our suite of API's to your logistics network. Event Go Documention next... How does it work? Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification

Home - Documentation - Integration flow (Event Order) Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification Integration flow Our Point-Of-Order (Event Connect) integrations put your customers and order management processes front and centre, pushing incoming orders directly from your Point-Of-Sales system to Event TMS. This means for our integration an order flow of: A NEW, an order that has stock allocated is preferred An UPDATE, to the order if it needs to be amended A CANCEL, if the order is cancelled A COMPLETE, once despatched Event is trying to deliver all your orders the more efficient, cost effective say possible, so some rules help acheive this: Event is at Orderline level Imagine a shopping basket, all different products but going to the same destination. Each product is a line number. An order can have multiple products shipping, each one would be a line. For example. 1.001, 1.002, 1.003 An order number must be unique Once cancelled an order number cannot be reused. Date change if any uncertainity on the orders status. You need to tell us where, when and what to deliver The better the address, the more chance it will be delivered correctly. We validate on Google addresses The delivery date is required, we can calculate a collection date. The quantity, weight and dimensions or we dont know what to pack on a truck Event Go Documention Event Order sync flow Basic NEW order A customer can place an order at anytime. The 1st point to clarify is 'when' to tigger the NEW order through the Event Order API? This is usually when it has a stock allocation and the order is a confirmed. This can be 3, 4 or more days before due collection date. It can be 1 or 2 days. The planning cycle would expect to generally receive the orders the day before collection is due for optimisation, carrier allocation and notification. A basic order flow would be an order, with multiple orderlines, triggered to Event through Event Order. Event will validate the order, plan the order and trigger back a route informing you how and when the order will be collected. Event. NEW order Order accepted Plan result TMS Planning optimisation Event Connect Updating an order An order can be updated many times before it is despatched. To trigger these updates through Event Order, you can use the UPDATE prefix. Event uses this prefix to simply update the existing order rather than create a duplicate order. An UPDATE can be for many reasons BUT should always only be for actual changes to the order that affect its delivery. For example these are primary Update types: Quantity, weights Delivery Date Order instructions Product components We don't expect to receive updates that are triggered through your POS because the order is viewed and no primary update is made. Unneccessary messaging generates unlooked for cost. Are UPDATEs the same for parcels and pallets? An UPDATE can also be considered to be a 'pack confirmation'. So for a parcel, packing the orders and generating the actual weight and dimensions of the package. The enables Event TMS to calculate the correct mode and carrier to make the delivery, in the same way for palletised goods, the last UPDATE is always the last instruction for delivery at that moment in time. Event. TMS Event. TMS Plan result NEW order Order accepted UPDATE order UPDATE order Order accepted Order accepted Event Connect An order short? Short despatch, partial despatch, out of stock. All situations at the point of a truck leaving a depot to deliver that require attention. The prefered and most straightforward process is to cancel of the short and to input a new order for it, a new unique order or a new orderline. Original order 1.001, cancel off. Input order 1.002 as this would be a unique order. next... Additional information

Top of Page Privacy Policy Security Policy The Event policies Privacy Policy Our Privacy Principles If you read nothing else, please read this: The most fundamental privacy principle 3T Logistics Ltd (“we”, “3T”, “us” and “our”) follow is that by default, anything you add to 3T’s EVENT control Platform is private to your Company. That is, files shared, orders added within a specific EVENT control application requires authentication as a member of that team. 3T is the custodian of data on behalf of the companies that use the EVENT control Platform. We don’t own EVENT user data. EVENT users own their data. They like it that way and so do we. At 3T we believe that more transparency is better than less. We try to make our product easy to use, with settings and options that are easy to find and understand. This is good for privacy, good for the product, and good for 3T customers and users. Privacy goes hand in glove with security and confidentiality. We see these things being the three legs that keep the stool balanced and upright. Each is as important as the other and if one is missing the stool won’t stand. They are all very important to us and we take them very seriously. For the purposes of the applicable data protection laws, legislation and regulations, the data controller is 3T Logistics Ltd. We are registered in England and Wales under company number 03973355 and have our registered office at 5 Smith Way, Grove Park, Enderby, Leicester, LE19 1SX. 2. Information we collect and receive We collect different kinds of information. Some of it is personally identifiable and some is non-identifying or aggregated. Here are the types of information we collect or receive: Information you give us This is information about you that you give us by filling in forms on our site or by corresponding with us by phone, e-mail or otherwise, it includes information you provide when you register to use our site, subscribe to our service and when you report a problem with our site. The information you give us may include your name, address, e-mail address and phone number and financial and credit card information. Any information you add to your profile is visible to other people on your team depending on their level of permission. Log data. When you use EVENT control, our server’s automatically record information, including information that your browser sends whenever you visit a website or your mobile app sends when you’re using it. This log data may include your Internet Protocol address, your browser type and settings, the date and time of your request, information about your browser configuration and plug-ins, language preferences, and cookie data. Log data does not contain message content and is not routinely deleted. Device information. In addition to log data, we may also collect information about the device you’re using EVENT application on, including what type of device it is, what operating system you’re using, device settings, unique device identifiers, and crash data. Whether we collect some or all of this information often depends on what type of device you’re using and its settings. Geo-location information. Precise GPS from mobile devices is collected only with your permission. WiFi and IP addresses received from your browser or device may be used to determine approximate location. 3. Cookies About Cookies When you use or access the EVENT control Platform, we may use small text files containing a string of alphanumeric characters called cookies to improve the overall experience, among other things. A cookie is a piece of data stored on the user's hard drive or browser containing information about the user. Information from cookies alone generally do not provide us with information to personally identify you. 3T may use both session cookies and persistent cookies. A session cookie generally disappears after you close your browser. A persistent cookie remains after you close your browser and may be used by your browser on subsequent visits to the EVENT control Platform or other web sites. Persistent cookies can generally be removed by you. Please review your web browser "Help" file to learn the proper way to modify your cookie settings and to remove cookies. Cookies that we use We use cookies for the following purposes: (a) Authentication – we use cookies to identify you when you visit our website and as you navigate our website. (b) Status – we use cookies to help us to determine if you are logged into our website. (c) Personalisation – we use cookies to store information about your preferences and to personalise the website for you. (d) Security – we use cookies as an element of the security measures used to protect user accounts, including preventing fraudulent use of login credentials, and to protect our website and services generally . Cookies used by our service providers (a) Our service providers use cookies and those cookies may be stored on your computer when you visit our website. (b) We use Google Analytics to analyse the use of our website. Google Analytics gathers information about website use by means of cookies. The information gathered relating to our website is used to create reports about the use of our website. Google’s privacy policy is available at: https:/www.google.com/policies/privacy/. Managing Cookies Most browsers allow you to refuse to accept cookies and to delete cookies.The methods for doing so vary from browser to browser, and from version to version. You can however obtain up to date information about blocking and deleting cookies via these links: (a) https://support.google.com/chrome/answer/95647?hl+en(Chrome) ; (b) https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences (Firefox) ; (c) http://www.opera.com/help/tutorials/security/cookies/(Opera); (d) https://support.microsoft.com/en-gb/help/17442/windows -internet-explorer-delete- manage-cookies (internet Explorer); (e) https://support.apple.com/kb/PH21411 (Safari); and (f) https://privacy.microsoft.com/en-us /windows-10-microsoft-edge-and-privacy (Edge). Blocking all cookies will have a negative impact upon the usability of many websites. If you block cookies, you will not be able to use all the features on our website. 4. How we use your information We use your information for the following Providing the EVENT service. We use information you provide to carry out our obligations arising from any contracts entered into between you and us and to provide you with the information, products and services that you request from us. To authenticate you. Understanding and improving our products. To make the product better we have to understand how users are using it, we call this solo.COMMUNITY. We have a fair bit of data about usage and we intend to use it many different ways to improve our products, including research. This policy is not intended to place any limits on what we do with usage data that is aggregated or de-identified so it is no longer tied to an EVENT user. Investigating and preventing bad stuff from happening. We work hard to keep EVENT secure and to prevent abuse and fraud. Communicating with you Solving your problems and responding to your requests. If you contact us with a problem or question, we will use your information to respond to that request and address your problems or concerns. Email messages. We may send you service and administrative emails. We may also contact you to inform you about changes in our services, or our service offerings. These messages are considered part of the service and you may not opt-out of them. In addition, we sometimes send emails to EVENT users about new product features or other news about EVENT or 3T. You can opt-out of these at any time by contacting us at service.desk@3t-europe.com . Personal data that we process for any purpose or purposes shall not be kept for longer than is necessary for that purpose or those purposes. 5. Disclosure of your Information You agree that we have the right to share your personal information with: Any member of our group, which means our subsidiaries, our ultimate holding company and its subsidiaries, as defined in section 1159 of the UK Companies Act 2006. [HS1] Our payment service providers. We will share transaction data with our payment services providers only to the extent necessary for the purposes of processing your payments, refunding such payments and dealing with complaints and queries relating to such payments and refunds. You can find information about the payment services providers’ privacy policies and practices at [URLs]. 6. Security 3T takes reasonable steps to protect information you provide to us as part of your use of the 3T service from loss, misuse, and unauthorized access or disclosure. When you enter sensitive information (such as sign-in credentials) we encrypt the transmission of that information using secure socket layer technology (SSL). We follow generally accepted standards to protect the personal data submitted to us, both during transmission and once we receive it. However, no electronic or email transmission or digital storage mechanism is ever fully secure or error free. To learn more about current practices and policies regarding security and confidentiality, please see our Security Practices; we keep that document updated as these practices evolve over time. 7. Your Rights If the data you provide to us is personal data you have principal rights under data protection law which include: - the right to access; - the right to reflection; - the right to erasure; - the right to restrict processing; - the right to object to processing; - the right to data portability; - the right to complain to a supervisory authority; and - the right to withdraw consent. You have the right to confirmation as to whether or not we process your personal data and, where we do, access to the personal data, together with certain additional information. That additional information includes details of the purposes of the processing, the categories of personal data concerned and the recipients of the personal data. Providing the rights and freedoms of others are not affected, we will supply to you a copy of your personal data. The first copy will be provided free of charge, but additional copies may be subject to a reasonable fee. You have the right to have any inaccurate personal data about you rectified and, taking into account the purposes of the processing, to have any incomplete personal data about you completed. In some circumstances you have the right to the erasure of your personal data without undue delay. Those circumstances include: the personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed; you withdraw consent to consent-based processing; the processing is for direct marketing purposes; and the personal data have been unlawfully processed. However, there are certain general exclusions of the right to erasure. Those general exclusions include where processing is necessary: for exercising the right of freedom of expression and information; for compliance with a legal obligation; or for the establishment, exercise or defence of legal claims. In some circumstances you have the right to restrict the processing of your personal data. Those circumstances are: you contest the accuracy of the personal data; processing is unlawful but you oppose erasure; we no longer need the personal data for the purposes of our processing, but you require personal data for the establishment, exercise or defence of legal claims; and you have objected to processing, pending the verification of that objection. Where processing has been restricted on this basis, we may continue to store your personal data. However, we will only otherwise process it: with your consent; for the establishment, exercise or defence of legal claims; for the protection of the rights of another natural or legal person; or for reasons of important public interest. If you consider that our processing of your personal information infringes data protection laws, you have a legal right to lodge a complaint with a supervisory authority responsible for data protection. You may do so in the EU member state of your habitual residence, your place of work or the place of the alleged infringement. To the extent that the legal basis for our processing of your personal information is consent, you have the right to withdraw that consent at any time. Withdrawal will not affect the lawfulness of processing before the withdrawal. You may exercise any of your rights in relation to your personal data by written notice to us. 8. Changes to this Privacy Policy We may change this policy from time to time, and if we do we’ll post any changes on this page. If you continue to use EVENT after those changes are in effect, you agree to the revised policy. If the changes are material, we may provide more prominent notice or seek your consent to the new policy. 9. Contacting us You can contact us: (a) by post, using the postal address 3T Logisitcs Ltd Grove Park, 5 Smith Way, Enderby, Leicester LE19 1SX (b) using our website contact form (c) by telephone: +44 (0) 116 240 5940 (d) by email, using service.desk@3t-europe.com Privacy Policy Security Policy Each Owner and each User (as defined in our Terms of Service) using EVENT control applications expect their data to be secure, confidential, and private. We understand how important this is to our customers and work to the best of our abilities to ensure all three expectations are met. Please review the information below regarding our current policies and practices, along with our Privacy Policy and Terms of Service. This is a living document and we will update it as our service evolves and industry practices change. 1. Security As a company, we use the service for nearly all of our communication. Ensuring that the Event service remains secure is vital to protecting our own data. The security of your information is required for our success as a business. Below are some details on our security practices. 2. Encrypted Traffic by Default, in Both Directions Event uses 256-bit AES, supports TLS 1.2 for all of your messages, and uses the ECDHE_RSA Key Exchange Algorithm. We monitor the security community's output closely and work promptly to upgrade the service to respond to new vulnerabilities as they are discovered. 3. External Security Audits We contract with respected, external security firms who perform regular audits of Event to verify that our security practices are sound and to monitor the service in light of new vulnerabilities discovered by the security research community. 4. Secure Physical Location Our servers are located in Microsoft Azures data centers. They've devoted an entire portion of their site to explaining their security measures, which you can find here: https://www.microsoft.com/en-us/trustcenter/compliance/default.aspx 5. Experienced Team Even before EVENT control, we (as 3T) have been providing services on the internet for a long time. We're good at it. Our engineering, quality assurance and technical operations team members are experienced and keep their skills up to date as industry best practices evolve. We’ve coded, tested and administered services running on thousands of physical servers in data centers around the world and we bring the collective wisdom that comes with many decades of secure practice to the operation of the 3T service. 6. Security Features for Team Members & Administrators The highest security risk to any system is usually the behaviour of its users. We want to provide you with the tools you need to protect your own data. For example, we log every time your account is signed in to, noting the device used and location of the connection, and make these access logs available to you. Account administrators can review consolidated access logs for the whole team. We also make it easy for each user to remotely close all Event connections and sign out all devices authenticated with their Event credentials at any time (so if you or one of your teammates lose your phone or laptop, you don't have as much to worry about). We will continue to roll out additional features which afford you more control over the security of your own Event environment. We will also be adding more options for Account administrators to set internal security policies, such as establishing password strength requirements or requiring use of PIN-lock functionality for Event’s mobile apps. 7. Availability We understand that you rely on EVENT control to work. We're committed to making EVENT control a highly-available, ultra-reliable service that you can always count on. We build systems that tolerate the failure of individual computers or whole data centers, keep many copies of your data online for redundancy, practice disaster-recovery measures often, and always have staff on-call to quickly resolve unexpected incidents. 8. Confidentiality We regard the information you share within your EVENT control users as private and confidential. We place strict controls over our employees’ access to internal data and are committed to ensuring that your data is never seen by anyone who should not see it. While the operation of the EVENT control service would not be possible unless there were some technical employees with sufficient system permissions to enable them to access and control software that stores and indexes the content you add to your EVENT control application, this team is kept purposefully small and are prohibited from using these permissions to view customer data unless it is necessary to do so. All of our employees and contractors are bound to our policies regarding customer data and we treat these issues as matters of the highest importance within our company. If, in order to diagnose a problem you are having with the service, we would need to do something that would expose your personal company data to one of our employees in a readable form, we will ask for your consent prior to taking action. Our platform will automatically generate an audit entry of any such access. There are limited circumstances when we ever share customer content without first obtaining permission. These are outlined in our Privacy Policy. Security Policy