Enduring Net Local Contact Tracing Data Policy

Privacy Notice

All information necessary to enable Local Contact Tracing (LCT) is stored on local devices under the control of the device owners and data generators, who are also data controllers. Information necessary to enable local contact tracing includes:

  • Publicly recognizable names of places (Public Places or Rooms) where people gather
  • Nickname, avatar, or even real ID of visitors to those public places
  • Each Visitor records the Public Places and dates visited
  • Each Public Place records the Nickname of each Visitor along with date visited

Data used by LCT is less than 14 days old. All other past data is ignored by LCT and may be deleted by the Public Place or Visitor.

About Us

Local Contact Tracing has been designed to complement existing COVID regime. LCT is designed to be deployed with minimal time and financial resources.

LCT is a grassroots initiative adopted and used inside narrow local confines (from small town communities to large organizations). Visitors log visits to Rooms (Public Places). Visitors warn Rooms when Visitor goes into quarantine. Rooms alert other contemporaneous Visitors of their exposure to the virus and trigger further covid tests. Those Visitors, if positive, can warn other Rooms of exposure. The process continues instantaneously across the locale minimizing the time to intervene and maximizing the time unexposed people can go about their lives and livelihoods. LCT is designed to justify timely COVID testing. Test results can be stored and shared as verifiable credentials.

The LCT strategy reverses the order of importance in the weapons to defeat the virus:

Trace -> Test -> Treat

Data Collection

Visitors and Rooms use the LCT web application to record visits to Rooms. The LCT app stores these visits using IndexedDB provided by all modern web browsers. When a Visitor visits a Room, the Visitor’s app sends a message to a cloud-based server that brokers messages between Visitors and Rooms. The server forwards the visit data to the appropriate Room without keeping a copy. The Room stores detail of the visit locally using the same web storage mechanism.

If a Visitor goes into quarantine, the Visitor’s app identifies all Rooms visited in the last 14 days and sends messages to each one that contain the dates visited. The Rooms identify all Visitors to that Room in the last 14 days. The Room sends a message to the server with this list of visitors and dates. The Server sends exposure alerts to each Visitor.

Exposed Visitors repeat the same process until the entire network is aware of the increased risk of spread.

Data Categories

The three LCT data structures are simple. The first two structures identify Visitors and Rooms. These data reside on the local storage of the Visitor and Room. The LCT server uses a third data structure to send and receive messages to and from Visitors and Rooms.

(i) Visitor Data

Visitor data has this structure:

{ 
visitor: 'Nurse X, 
id: 'kWjzGUKmvWhgeRlmAAAA', 
nsp: 'enduringNet' 
},

The Visitor chooses their Nickname. The id field is a string generated by an algorithm that is unguessable and likely unique. The nsp field identifies the local jurisdiction hosting the LCT network. Its value is given by LCT administrators and assigned to Visitors in that locale automatically.

(ii) Room Data

Room data has this structure:

{
room: 'Manchester Pub',
id: 'kSrcg7LYgbtyBio5AAAB',
nsp: 'enduringNet',
},

The only difference in Room data is the name of the public place. By definition, a public place as a unique name (otherwise confusion would ensue).

(iii) Message Data

Messages consist in the identity object of Visitors and Rooms, and they include a short message (usually indicating Room entry and departure) plus a timestamp of the visit.

{
visitor: {
visitor: 'Nurse X',
id: 'kWjzGUKmvWhgeRlmAAAA',
nsp: 'enduringNet',
},
room: {
room: 'Manchester Pub',
id: 'kSrcg7LYgbtyBio5AAAB',
nsp: 'enduringNet',
},
message: 'Entered',
sentTime: '2020-09-20T20:33:04.248Z',
},

Rooms and Visitors store these messages in the same local storage as their respective identity objects. Visit data expires 14 days after sentTime.

The LCT Server usually passes messages directly to recipients. But when a Room or a Visitor is not online (or when the Room is online but not ‘open’), the server will cache the message until the recipient can receive it. The message data is not stored outside memory, and it is available only to the intended recipient.

Legal Basis for Processing Data

Since no PII is processed, and there is no presumption of privacy when entering a public place.

Data Sharing

Since the server can only receive data from a known identity and specific personal device (like a mobile phone, tablet, laptop or desktop) and it transmits (but not store) that data only with an identity/device specified in the message, there is little to no risk of involuntary data sharing.

Data Security and Retention

LCT is designed to eliminate barriers to participation. LCT processes information just sufficient to give all parties maximum situation awareness regarding the prevalence of COVID in their community.

Since covid exposure data has a limited lifetime, LCT ignores any data older than 14 days. That is, messages cannot contain visits older than 14 days. Visitors and Rooms can delete data on their local device whenever they want. The only caveat is that absent data, they may not see some exposure alerts.

Complaints

Since LCT is based on messages, LCT can use the same technology to provide support to users and a venue to complain about the network visible only to parties in the network. For further queries and feedback please contact enduringnet@gmail.com.

Credits

The LCT application is developed by Michael Corning, who is the Cryptocosm Architect at Secours.io

 

Go back to QR-Codes, Room or Visitor. If you have any feedback, please email enduringnet@gmail.com.