Service access is not data ownership.

Your organisation’s source data does not become DAIOTA’s property because it is used to provide our services. The applicable agreement defines access, permitted use and the rights of your organisation and its authorised data providers.

Contractual rights over data and the privacy rights of individuals are separate. Where information relates to an identifiable person, the responsibilities of each party depend on its actual role, the processing activity and applicable law.

Data starts with your sources.

Depending on the engagement, DAIOTA receives inputs directly from a fleet operator or insurer, or through an authorised third-party provider. The source and the scope of access are defined for the integration.

Relevant inputs may include vehicle telemetry, activity records and the operational or programme context needed for the service. The actual categories depend on your integration; a general description is not permission to collect additional data.

Analysis does not rewrite the source.

DAIOTA processes authorised inputs to produce the agreed analytical outputs. Processing can include quality checks, standardisation, validation and the creation of derived metrics or estimates.

These operations are different from editing a source record in your organisation’s or provider’s system. Access and any ability to write back to a source system must be explicitly defined in the integration and agreement.

Permitted uses are defined by the engagement. Any separate purpose—such as unrelated advertising, onward sale or model training—requires its own valid authorisation and applicable terms; access for one service is not blanket permission for another use.

Insights return through your API integration.

DAIOTA delivers analytical results through the agreed API integration so your organisation can use them in its own workflows. The integration defines which outputs are available and who is authorised to receive them.

If your engagement also includes Web or private Slack delivery, those channels and their authorised recipients are defined separately. API delivery does not, by itself, mean that no data is accessed, processed or retained.

Outputs support review and human decisions. They should not be represented as an automatic insurance decision, an accident probability or a causal finding.

Clarity throughout the data lifecycle.

Your service terms and data-processing arrangements should explain the practical boundaries of data handling:

• Access: the people and service providers permitted to handle data, and for what purpose.
• Storage and retention: what is retained, where processing takes place, and the retention period or criteria—including logs, caches and backups where applicable.
• Return and deletion: the arrangements at the end of the engagement, including backup timelines and any applicable legal retention requirements.
• Transfers and service providers: relevant hosting locations, subprocessors and cross-border processing where applicable.
• Protection and incident handling: the applicable safeguards, points of contact and arrangements for responding to a data incident.

Ask for the details relevant to your deployment. A delivery method alone does not answer these questions, and a privacy overview is not a substitute for the agreed data-processing terms.

Business enquiries are a separate data flow.

When you contact DAIOTA or request a demo, the details you choose to provide—such as your name, business email, company and message—are used to handle your enquiry and discuss the relevant service.

Please do not include driver-level records, customer policy files, credentials or other sensitive service data in a general enquiry. Use the agreed integration or an appropriate transfer channel arranged with your organisation.

Website cookies, analytics, technical logs and third-party website services need their own disclosures, reflecting what is actually active. These details, the applicable retention arrangements and the legal entity responsible must be confirmed in the final website policy.

For personal-data requests relating to a fleet or insurance programme, contact the responsible organisation. DAIOTA can help identify the appropriate route within the relevant engagement.