Terms of service

These terms are between Cudatus, which operates the Relay API and this website, and the organisation that holds a Relay API key.

Relay is sold to organisations, not to individuals. There is no consumer account and no personal subscription.

Relay accepts road event reports from authorised organisations, normalises them, and makes them available to other authorised organisations by area query and by real-time stream. It also ingests public road data feeds published by public authorities.

Relay is not a navigation service, an emergency service, or a safety-critical system, and it must not be used as the sole basis for a safety decision. Events are reports from third parties; we do not verify them independently.

• A key identifies one organisation. All activity under a key is attributed to that organisation, and reputation on the network is carried by the organisation rather than by any individual event.
• You are responsible for keeping your key secret and for everything done with it. Tell us immediately if it is exposed and we will revoke it.
• Stream tickets are short-lived, read-only credentials derived from your key. They may be handed to a browser; your key may not.
• We may suspend a key that is publishing false events, that is abusing the invalidation mechanism, or that is placing the service at risk.

• Point events about road conditions, and only about road conditions.
• Never a vehicle trajectory, a vehicle identifier, a driver identifier, or anything from which one could be reconstructed. The contract does not carry these fields and you must not smuggle them into free-text fields.
• Nothing you do not have the right to publish, and nothing deliberately false. Publishing false road hazards on a network used by other road users is the most serious misuse of this service.

You keep ownership of what you publish. You grant Cudatus a non-exclusive, worldwide, royalty-free licence to store, process and redistribute it through the Relay network, including to other participants, for as long as the event is live and in the analytical record afterwards.

Use it in your product. Do not resell the raw feed as a competing event feed, and do not attempt to re-identify the organisations that publish events on the network — nothing on the wire names a publisher, and working to reverse that, whether by correlating publication patterns or by any other means, is not a permitted use.

Events carry a time to live. Continuing to display an event after it has expired is a misuse of the data and, for a wrong-way vehicle alert, a dangerous one.

Cudatus publishes a latency target of a 95th-percentile round trip under one second between publication and reception. That is a commitment we measure and publish, not a contractual service level, and no service credit attaches to it unless a separate written agreement says so.

The service is provided as is. We do not warrant that it will be uninterrupted, that any particular event will be delivered, or that any event is accurate.

We commit to backward compatibility on the versioned event envelope: fields are added, never removed or repurposed. Your client must ignore fields and values it does not recognise. A change to the meaning of an existing field will be served at a new URL version alongside the old one for as long as the old one has a consumer.

Cudatus is not liable for indirect or consequential loss. Liability is capped at the fees paid in the preceding twelve months. Nothing here excludes liability which cannot be excluded by law.

We may change these terms; material changes will be notified to the contact address on the account before they take effect. Either party may terminate at any time. On termination your key stops working; events you already published stay on the network until they expire.

French law, and the courts of the company’s registered seat.

Questions about these terms: contact@cudatus.com.