Skip to main content
DRAFT FOR ATTORNEY REVIEW. This page has not been reviewed by a lawyer yet.

Acceptable Use

Who EdgeLinklies to

These rules apply to everyone who uses EdgeLink: people who visit the site or sign in, and people who run a device, gateway or bridge that sends readings to it.

What is not allowed

  • Send readings only from a device registered in EdgeLink, with that device's own credential. A reading's source must match its device.
  • Send readings only. Do not send commands, settings or firmware: EdgeLink refuses readings typed as commands and never sends anything back to a device.
  • Do not try to set a reading's world (live or demo), class or trust level. These come from the device registry, and readings with unknown attributes are refused.
  • Stay within the limits: 64 KB per request, 50 readings per request, 4 KB of data per reading, and the device's per-minute rate limit (120 by default, 600 at most). Requests over a limit are refused.
  • New devices start pending and untrusted, and their readings are held until an administrator approves the device. Do not try to get around this.
  • Keep a device credential private. Never put it in code you publish. If it leaks, ask an administrator to revoke it and issue a new one.
  • Do not try to reach records, accounts or features you are not allowed to use, or to get around access controls.
  • Do not pretend to be a device or a person you are not, or give false information.
  • Do not test the security of the app without written permission.
  • Do not use the app for anything unlawful.

What the app does about it

  • Devices, credentials, readings, held readings and referrals can be read only by administrators. They are changed only by administrators or by the app's own functions.
  • A device credential's secret is stored only as a one-way hash, and is shown once.
  • A new device starts pending and untrusted. Readings from a device that is not yet approved are held for an administrator.
  • EdgeLink only receives readings. It never sends a command, setting or firmware file to a device.
  • Requests are limited in size and number, and each device has a per-minute rate limit.
  • Actions are written to an audit log that is sealed once a day.
  • Live and demo records are kept apart.