Partner Personnel & Flow-Down Terms

In this document, "partner organisation" means a Lynr Network member admitted as an organisation. "Personnel" means any individual the partner organisation names in an application or profile, puts forward for an opportunity, or deploys on a Lynr client workstream, whether that person is an employee, worker, director, contractor, subcontractor, associate or agent of the partner organisation.

These terms apply to the partner organisation. They also describe the obligations a named individual is expected to be under, and an individual may be asked to acknowledge them directly.

The partner organisation must ensure that, before any personnel access Lynr Network information, client information or a client workstream, that person is bound by written obligations at least as protective as the ones in this document and in the Project Participation Terms.

• The binding must be in place before access, not after an incident.
• It must survive the end of that person's relationship with the partner organisation for as long as the underlying obligation lasts.
• The partner organisation remains fully responsible to LYNR for the acts and omissions of its personnel as if they were its own.
• LYNR may ask the partner organisation to confirm in writing that a named individual is bound, and to identify the mechanism used.

Where LYNR asks the partner organisation to record named personnel — for example a named accountable lead, a delivery team or a person put forward for a specific opportunity — the partner organisation must keep those records accurate and must tell LYNR promptly when a named person is added, replaced or removed.

Substituting personnel on a live client workstream requires LYNR's agreement. LYNR may decline a substitution where the replacement does not meet the standard the workstream was scoped on.

• Confidentiality: client identity, briefs, data, evidence, commercial terms and other non-public Network or client information must not be disclosed or used outside the agreed purpose.
• Data protection: personal data accessed through Lynr or a client must be handled only on documented instructions and only for the agreed purpose, with appropriate security.
• Security: agreed access controls, device standards, credential handling and system boundaries must be followed; access must not be shared.
• Intellectual property: deliverables and work product produced for a client must be capable of transfer or licence to that client on the terms agreed for the engagement, free of undisclosed third-party or open-source encumbrances.
• Non-circumvention: an individual introduced through Lynr must not use that introduction to contract directly with the client outside the agreed route while the relevant restriction applies.
• Accuracy: credentials, references, certifications and case evidence attributed to that individual must be true and permitted to be shared.
• Conduct: professional, lawful and non-discriminatory behaviour with clients, other members and LYNR personnel.

Where a partner organisation gives LYNR personal data about its personnel — names, roles, biographies, credentials, references or contact details — the partner organisation confirms it is entitled to provide that information and that it has told those individuals how it will be used.

LYNR processes that information as an independent controller for the purposes described in the Network Privacy Notice. A named individual may contact privacy@getlynr.com to exercise their data rights directly, whether or not they hold a Lynr Network account.

The partner organisation must maintain the insurance cover it has declared to LYNR, or the cover reasonably required for the work, and must ensure its personnel are covered for the work they perform. Insurance declarations made during application must be kept current, and a material lapse must be reported to LYNR without undue delay.

• The partner organisation must notify LYNR without undue delay of any confidentiality, security or personal-data incident affecting Lynr Network or client information.
• LYNR may require that a named individual is removed from a Lynr client workstream where there is a reasonable concern about conduct, confidentiality, security, conflict of interest or delivery standard.
• Removal of an individual does not by itself end the partner organisation's membership, and ending membership does not end obligations that are expressed to survive.

These terms sit alongside the Network Member Terms and the Project Participation Terms. Where a signed engagement agreement covers the same subject for a specific client assignment, that signed agreement prevails for that assignment. Nothing here creates employment, agency, partnership or exclusivity between LYNR and any individual.