SellSensorDataToAI
  • 6 of 11IoT and telematics platforms whose terms say the readings belong to the businesssource
  • 5 of 11platforms that reserve a pooled, aggregated or anonymised use of device datasource
  • 2 of 11platforms whose terms promise no export of the data when the contract endssource
  • 2026-10-28newest read of the IoT platform terms on this boardsource

Fleet operators, plant owners and IoT product firms

Sell sensor data to AI? Read your IoT platforms' terms first

Years of machine readings often sit in somebody else's cloud: a telematics service, an industrial data platform, a device cloud. We read 22 documents from 11 of those platforms, newest on 2026-10-28: 6 say the data belongs to the business, and 5 keep a right to an aggregated or anonymised copy.

Source: Iot software data terms: every row, with its source

IoT platform terms on your readings, platform by platform

11 vendors, read 2026-10-28

  1. Arduino

    Whose data the readings are:
    not stated
    Platform keeps a pooled copy:
    not stated
    Getting the readings out at exit:
    not stated

  2. AWS

    Whose data the readings are:
    the business
    Platform keeps a pooled copy:
    excluded
    Getting the readings out at exit:
    30 days

  3. Blynk

    Whose data the readings are:
    the business
    Platform keeps a pooled copy:
    reserved
    Getting the readings out at exit:
    not stated

  4. Cognite

    Whose data the readings are:
    the business
    Platform keeps a pooled copy:
    reserved
    Getting the readings out at exit:
    on request

  5. Geotab

    Whose data the readings are:
    not stated
    Platform keeps a pooled copy:
    reserved
    Getting the readings out at exit:
    not stated

  6. Inductive Automation

    Whose data the readings are:
    not stated
    Platform keeps a pooled copy:
    not stated
    Getting the readings out at exit:
    not stated
Every vendor, every answer (5 more)

Card 1 of 2

Describe the sensor and machine data you hold

  1. The sensor data 2 questions, 2 required
  2. The business behind the devices 9 questions, 8 required
  3. Timing and who is writing 6 questions, 5 required

Card 2 of 2

The sensor data

What do most of the readings come from?

Where are the readings stored today?

  • Every sensor data enquiry is read by a person
  • No IoT platform on the board hears about your enquiry
  • The form never asks for raw logs, device IDs or customer names

Three steps

  1. Tell us what the devices measure, how long they have logged and which clouds or historians hold the readings.

  2. We check those platforms' clauses on the board and the rules on connected product data, database rights and personal data that decide what can be licensed.

  3. We reply with the route that fits: a licence while the business keeps running, a sale of the readings by its directors when a solvent business closes or by the administrator, liquidator or trustee of one that cannot pay its debts, or a route agreed with the adviser who sent you.

No IoT platform, telematics service or data buyer pays to appear here, and nothing on the site is an affiliate link. Each answer is our reading of a platform's published terms or of a statute, not advice on your own contracts. Our fee: when a business licenses or sells its sensor data to a buyer we introduced, it pays us 12.5% of the deal, with a minimum charge, if we act as its exclusive agent, or 10%, with a minimum charge, if its data goes into a bundle or the pool, agreed in writing beforehand; anything a buyer pays us is credited back to the business.

IoT platform terms on your readings, platform by platform

Last updated

One row per telematics service, IoT cloud or industrial data platform, each answer resting on a sentence of the document named beside it. Not stated means the documents we read, end to end, never answer the question.

Each vendor's own published terms were read through estate-fetch and stored whole (sha256 on every row). For every document, four questions were answered from the vendor's own words: who owns the business's data, vendor keeps aggregated or anonymised use, training AI on the business's data, export at exit. Every stated answer carries the sentence it rests on, checked against the stored text; 'not stated' means the document read does not address the question. A vendor with several documents reads 'varies' where they disagree. 11 vendors, 22 documents.

IoT or telematics platformWhose data the readings arePlatform keeps a pooled copyGetting the readings out at exitSource
Arduinonot statednot statednot stated Arduino Terms and Conditions
AWSthe businessexcluded30 days AWS Service Terms (AWS IoT Services, section 39)
Blynkthe businessreservednot stated Blynk Platform Terms of Service
Cognitethe businessreservedon request Cognite End User License Agreement
Geotabnot statedreservednot stated Geotab Main Services Agreement, Canada and US (2026-07-23)
Inductive Automationnot statednot statednot stated Inductive Automation Master Software License Agreement (Ignition)
Losantthe businessreservednot stated Losant Terms of Service
Microsoftnot statednot statednot stated Microsoft Product Terms, privacy and security terms
Particlethe businessnot statednot stated Particle Terms of Use
Samsarathe businessreservedno export promised Samsara Master Terms of Service
ThingsBoardnot statednot statedno export promised ThingsBoard Cloud Terms of Use

Cite this page

“IoT platform terms on your readings, platform by platform”, Sell Sensor Data to AI, https://sellsensordatatoai.com/ (updated 2026-10-28). Each vendor's own published terms were read through estate-fetch and stored whole (sha256 on every row). For every document, four questions were answered from the vendor's own words: who owns the business's data, vendor keeps aggregated or anonymised use, training AI on the business's data, export at exit. Every stated answer carries the sentence it rests on, checked against the stored text; 'not stated' means the document read does not address the question. A vendor with several documents reads 'varies' where they disagree. 11 vendors, 22 documents.

Guides

The longer answers, with sources.

  1. Telematics data ownership: what Samsara and Geotab keep
  2. The EU Data Act on connected products: who gets the data
  3. Who owns sensor data? Machine-generated data in EU, UK and US law
  4. Who buys sensor data, telemetry and vehicle logs

Straight answers

Can a business sell the data its sensors collect to an AI company?

Usually, where the business owns the readings and they hold no personal data it has not cleared. On this board 6 of 11 platforms say the data is the customer's; the others' documents do not say. What a platform kept for itself, and whether drivers or tenants can be identified, decide the rest.(Iot software data terms: every row, with its source)

Does Samsara or Geotab own my fleet's telematics data?

Samsara's master terms say the customer owns all Customer Data, while reserving data that is anonymised, de-identified or aggregated. Geotab's main services agreement says Geotab and its licensors own Aggregated Data. Neither document we read claims the raw readings for the platform.(Iot software data terms: every row, with its source)

Do IoT platforms train AI on my device data?

Only ThingsBoard says either way: its cloud terms say it does not use customer data to train or improve its own AI models. The documents we read from the other 10 platforms are silent on training.(Iot software data terms: every row, with its source)

Does the European Data Act change who can sell machine data?

It gives the user of a connected product, the business that owns, rents or leases it, a right to the data the product generates, and it says a manufacturer holding non-personal product data may use it only on the basis of a contract with that user. It has applied since 12 September 2025.(Iot software data terms: every row, with its source)

Is a log of sensor readings protected as a database?

In the EU, not by the database right where the data comes from a connected product: Article 43 of the Data Act switches that right off. In the UK a database right runs 15 years from the end of the year the database was completed. In the US, copyright never covers the underlying facts.(Iot software data terms: every row, with its source)

Who buys sensor, telemetry and vehicle data?

Some of the organisations on our buyer board name it on their own pages: Deepen's Refinery marketplace takes sensor and vehicle data for physical AI, Datarade lists IoT data providers, and Scale AI names data from operating businesses and robots. Most of the rest name other kinds of data.(Iot software data terms: every row, with its source)

Sources

This site's own datasets, every figure quoted from its source and dated:

  1. AWS Service Terms (AWS IoT)
  2. AWS Customer Agreement
  3. Microsoft Product Terms: privacy and security terms (Azure IoT)
  4. Samsara Master Terms of Service
  5. Samsara Terms of Service (UK)
  6. Samsara Enterprise Trial Agreement
  7. Samsara commitment to privacy
  8. Geotab Main Services Agreement, Canada and US (2026-07-23)

The question this page is here to answer

Can a business export and license the sensor readings and machine time series held in its IoT platform, industrial historian or telematics cloud, and what does each platform's own terms say about who owns them, aggregated use, AI training and export at exit?

6 of the 11 IoT platforms we read say the readings belong to the business. Tell us what your devices log and where it is stored, and we will reply by email.

Answered by Sell Sensor Data to AI, which reads every enquiry this page takes.

Ask about my sensor data

Ask about my sensor data