Skip to content
Emberwire OTA firmware delivery

Legal

Legal and policies

Summaries, in plain language, of the documents that govern the service. Where a summary and the signed agreement disagree, the agreement wins — but we try hard to make that a theoretical concern rather than a practical one.

Who operates the service

Service name
Emberwire
Registered office
{{CITY}}, {{COUNTRY}}
Operating jurisdiction
{{COUNTRY}}
General enquiries
support@{{DOMAIN}}
Security reports
security@{{DOMAIN}}
Abuse reports
abuse@{{DOMAIN}}
Legal and contracts
legal@{{DOMAIN}}
Data protection
privacy@{{DOMAIN}}

Company registration details and tax identifiers appear on every invoice and in the signed agreement. Delivery nodes are operated in the cities listed on the delivery network page through colocation and transit arrangements.

Terms of service — the parts that matter

What we undertake

To store the images you upload, deliver them unaltered to devices that present a valid manifest, and operate the control plane to the commitments on the pricing page. We do not modify your images; the digest a device verifies is the digest of the bytes you uploaded.

What you undertake

That you have the right to distribute the firmware you upload, that you will not use the service to deliver software to devices whose owners have not agreed to receive it, and that you keep your signing keys and tokens under your control.

Liability

Capped at the fees paid in the preceding twelve months, with the usual carve-outs for wilful misconduct and for breaches of confidentiality. We are not liable for the consequences of firmware you authored — the platform limits blast radius, it does not review your code.

Term and exit

Monthly, no minimum commitment, no notice period. On termination you keep read and export access for 90 days. Images, manifests, signatures and the full device history are exportable throughout.

Changes

Material changes to the terms are announced 30 days ahead by email and on Status. If you do not accept them, you may terminate before they take effect and export everything.

Suspension

We may suspend delivery for non-payment after two written notices, or immediately where delivery would be unlawful or where an account is actively distributing malicious firmware. Suspension stops new waves; it does not roll devices back.

Acceptable use

Short, because it has to be enforceable.

Not permitted

  • Delivering firmware to devices whose operator has not agreed to receive updates from you.
  • Delivering software designed to damage a device, exfiltrate data from its user, or disable functionality a purchaser paid for, without clear disclosure.
  • Using the delivery network as general-purpose file hosting. It serves firmware images referenced by signed manifests, and nothing else — the protocol does not offer another shape.
  • Attempting to reach another customer's namespace, images or device records.
  • Load testing against production nodes without arranging it first. The simulator exists; use it.

Reports to abuse@{{DOMAIN}} are acknowledged within one business day. Where a report concerns firmware content rather than the platform, we will put you in contact with the vendor and, if the claim is substantiated and serious, suspend delivery.

Data processing

What Emberwire processes, and in which role
Data Role Why Retention
Firmware images and manifests Processor Storage, delta generation and delivery. 24 months, or your setting
Device identifier, product line, build state Processor Deciding what a device should be running and recording what it ran. 24 months
Transfer metadata — node, bytes, timing, error codes Processor Delivery, billing and incident diagnosis. 13 months
Coarse region of a device Processor Choosing candidate nodes. Region, not location. 13 months
Your team's account data Controller Authentication, audit of operator actions, billing. 7 years where tax law requires
Support correspondence Controller Answering you, and remembering what we answered. 36 months

What we never receive

Application payloads, sensor readings, user accounts on your devices, precise location, or anything your firmware handles at runtime. The agent reports update state and nothing else, and there is no mechanism to make it report more.

End users of your devices

Where a device identifier can be tied to an individual in your own systems, you are the controller and we are your processor. The data processing addendum covers this; it is signed as part of the main agreement and needs no separate negotiation.

Residency and pinning

A product line can be pinned so that images replicate only to nodes in an agreed set of countries. Control-plane records live in the region you select at onboarding and do not move.

Deletion

Deleting a product line removes its images, manifests and delta bases within 30 days, including from node caches. Device history can be deleted independently, subject to any retention you are yourself obliged to keep.

Subprocessors

By category. The current named list, with entity names and countries, is in the customer portal and changes are notified 30 days ahead.

Purpose Category Regions Data reached
Delivery node capacity Colocation and transit providers The 12 countries listed on Delivery network Image blocks in transit and in cache; transfer metadata
Origin storage Object storage provider Europe and North America Image blocks, manifests
Transactional email Email delivery provider Europe Contact address and message content
Invoicing and payment Payment processor Europe Billing contact, invoice line items
Error and performance monitoring Self-hosted, no third party Europe Stack traces and platform metrics; no customer images

Signing keys are not in this table because subprocessors never hold them. In the default configuration neither do we — see Security.

Disclosure and government requests

What we do with a request

We require valid legal process in {{COUNTRY}}, we check it against the scope it claims, and we narrow it where it is broader than the law allows. We notify the affected customer before responding unless we are legally prohibited from doing so, and then as soon as the prohibition lapses.

What we could hand over

Account data, invoices, and update history for a named fleet. We cannot hand over a signing key we do not hold, and we cannot produce firmware a device would accept. That is an architectural property, not a policy we could be asked to change.

Export control

Firmware images may be subject to export control in your jurisdiction and in ours. You warrant that what you upload may lawfully be distributed to the regions you target; region pinning exists partly so that this is enforceable rather than aspirational.

Transparency

We publish a count of legal requests received and complied with once a year. To date the count has been zero, which we will state for as long as it remains true.

This website

No cookies, no third parties, no analytics

These pages set no cookies, load nothing from anyone else, and contain no tracking of any kind. The forms on the pricing and status pages are handled entirely in your browser and submit nowhere. The customer dashboard, which is a separate application, sets one session cookie that is strictly necessary for authentication.