Privacy notice

There are eight forms on this site and they are eight different things. A requirement is you asking us to find something. A partnership enquiry is you asking about a founding corporate place. An answer to an open requirement is you telling us you might be the counterparty another organisation is looking for. A research route is a university, institute or research group either looking for a partner or offering a capability to be matched against work already in our register. A pilot enquiry is a public body proposing a problem to be tested, which becomes a programme rather than a single question. An association enquiry is a chamber, association or NGO bringing one need from an organisation it serves, which is not the same thing as that organisation asking us itself. A capability registration is a specialist telling us what it does, which is recorded as something the organisation says about itself until a person has checked it. A funding thesis is an investor or funder telling us what it would look at, which is not the same thing as asking us to find something.

Each one collects your name, organisation, role, email, an optional telephone number and the text you write. The requirement form also asks the type, the constraint and the deadline. The partnership enquiry also asks which direction you are working in and what your first requirement would be. The answer form carries the identifier of the requirement you are answering, taken from the page you came from rather than typed by you. The research form asks which of those two directions you are in, the research area, the maturity of the work and any timing. The pilot form asks what kind of public body you are, how the work would be paid for if it went ahead, the policy area and any timing. The association form asks what kind of organisation you are, which organisation you are bringing and whether it is ready to be introduced. It deliberately asks for no person at that organisation: no name, no email, no telephone. The introduction is made by the association. The capability form asks what you do, the sectors and jurisdictions you can act in, your working languages, what shows you have done this before, any conflicts we should know about, how you would expect to be engaged and your availability. The engagement basis is recorded so that nobody has to ask the question twice. It is not a price list and it is not published. The investor form asks what kind of investor or funder you are, whether you are interested in organisations in the corridor or in funding a KyoLink programme, what you invest in, the sectors, the stages, a band rather than a figure, where you can deploy, any structural constraint, what you will not look at, and how a decision is made. There is deliberately no field for a score, a valuation or an amount invested: we filter against what you stated, and a record that could hold a view of ours is where that stops being true.

When you attend an event we hold the registration data provided by the platform used for that event.

We use this only to answer you, to prepare an introduction you have consented to, and to report on the outcome. We do not sell it and we do not use it for unrelated marketing.

We never hold a single yes. Each permission is recorded separately, with its date, and you can withdraw any of them by replying to the acknowledgement email.

The requirement form, the research route, The capability registration and The funding thesis each ask for three: that we may contact you about what you sent; that we may describe, in writing, what you are looking for or what you offer, without naming your organisation; and that we may name your organisation to the one organisation we propose it to, whichever side of the introduction it is on.

The third permission is the written permission itself. It covers one thing at a time: that requirement, that research route, that task, that match, and nothing else; a second approach needs a second permission.

The partnership enquiry, the answer to an open requirement and The association enquiry each ask for one: that we may contact you about what you sent.

Neither of them asks for anything else, because neither of them involves naming you to anybody. The second and third permissions above exist only where we are going to approach somebody on your behalf.

The pilot enquiry asks for two: that we may contact you about what you sent; and that we may describe, in writing, what you are looking for or what you offer, without naming your organisation.

The third permission, naming you to the organisation we approach, is not asked for here. A public body is named in public by its own communications people, at the moment it decides to be, and not through a checkbox on a form.

Passing on your contact details is a separate permission. We ask for it only when an introduction is actually proposed, never in advance.

Two further permissions exist and are never collected by a form. Public requirement allows us to publish an anonymised description of what you are looking for on the open requirements page. Public naming allows us to name your organisation publicly, in an outcome record or in programme materials. Both are asked for by a person, in writing, at the moment they are needed, and either can be withdrawn. Being a member, a partner or a counterparty is not permission to publish anything.

Photography at events is handled at the event: we say that photography takes place, you can opt out on arrival, and publishing an identifiable image is a separate permission we ask for by name.

We keep a submission for twenty-four months from the day it is received, which is the same clock the operating register uses, unless the law requires us to keep it longer. Write to contact@kyolink.org to see, correct or delete what we hold, and we will act within thirty days.

The site is hosted on Cloudflare Pages. Form submissions are stored in a Cloudflare D1 database in the European Union and notified by email through Resend. Event registration is handled by the platform named on each event page. Fonts are served from this domain, so the pages make no third-party request and set no cookies. Visitor statistics, if enabled, come from Cloudflare Web Analytics, which uses no cookies and no cross-site identifiers.