Participation Terms
Version in force: 11 November 2026
These Participation Terms apply to each UniVCC research and data-collection activity listed in the Activity Schedule set forth below, such as a questionnaire, a form or a survey. These terms have two parts, four annexes and the Activity Schedule. Part A is the click-through text, accepted at the consent screen and again by the Approver. Part B turns the same clauses into a signable agreement; only the cover page, Schedule 1 and the signatures are added. Annex 1 holds the undertakings that laws outside the EU expect from a recipient, and applies to every Respondent. Annexes 2 to 4 list the publication levels, the security measures and the service providers. The Research Partner Addendum, published on its own page, lists the Research Partners (clause 5.4) and forms part of these terms.
Part A: Participation Terms
1. Who we are and what these terms are
1.1 These terms are between UniPrisma Kft., trading as the University Venture Capital Coalition (“UniVCC”, “we”), Révay köz 4, 1065 Budapest, Hungary, company registration number 01-09-448571, and the organisation that submits a response to a UniVCC research or data-collection activity listed in the Activity Schedule (an “Activity”; the “Respondent”, “you”).
1.2 A person with authority to bind the Respondent accepts these terms at the start of the Activity. The Approver confirms them again at approval. By accepting, that person confirms they have this authority.
1.3 UniVCC and the Respondent are each an independent controller of the personal data they process. UniVCC decides the purposes and means of the research. The Respondent decides what it shares. These terms are not a joint-controller arrangement (GDPR Art. 26) and not a data processing agreement (GDPR Art. 28). Neither party processes personal data on the other’s behalf. A Research Partner with access to a Response under clause 5.4 is a separate, independent controller of the personal data its named researchers access. It is not a processor or a joint controller of UniVCC or of the Respondent.
1.4 These terms apply together with UniVCC’s privacy policy. If they conflict, these terms prevail for the Activity. Annex 1 applies to every Respondent.
2. Definitions
- Respondent: the organisation that submits a Response (clause 1.1).
- Approver: the person named in a Response who approves it for the Respondent or, if none is named, the lead respondent (the person who leads the Response for the Respondent), who confirms their authority and approves it.
- Response: everything the Respondent enters or uploads in an Activity, including drafts.
- Fund Data: information in a Response about a fund, its manager or its investors that is not Personal Data.
- Personal Data: information in a Response about an identified or identifiable natural person.
- Publication Level: the level each field carries under Annex 2: P (public), R (restricted) or X (confidential).
- Aggregate: a figure that combines data from several Responses and passes the rules in clause 7.
- Validated: reviewed by UniVCC against the Respondent’s confirmation or a public source before publication.
- Research Partner: a regional organisation listed in the Research Partner Addendum, which works with UniVCC on research on its own region and has the access to that region’s Responses set out in clause 5.4.
- Research Partner Addendum: the list of Research Partners published at univccoalition.org/research-partner-addendum. It forms part of these terms.
3. Taking part is voluntary
3.1 Taking part is by invitation and voluntary. It is not a condition of membership of the coalition, and it does not affect any membership decision.
3.2 You may leave any question unanswered, or answer “Not available”, “Prefer not to disclose” or “Confidential”.
3.3 You may stop at any time. We delete an unfinished Response 30 days after it was last saved.
4. What we use a Response for
4.1 We use Responses only for structured market research on university- and RTO-affiliated venture funds:
- benchmarks;
- an ecosystem map;
- research publications;
- analysis for coalition members;
- private peer-benchmark reports for Respondents;
- research on a region with each Research Partner for that region (clause 5.4).
4.2 We do not:
- sell Responses;
- use them for marketing;
- use them to assess you for membership;
- add them to our contact or sales records. The one exception: the Approver named in a Response gets a contact record with their contact details, role and organisation only, never any answers;
- use them to train or fine-tune any AI model.
4.3 Any new use needs the approval of both UniVCC founders and an updated data-protection impact assessment. A new use applies to your existing Response only if you agree.
5. Who sees your raw Response
5.1 Apart from the named researchers of a Research Partner under clause 5.4, only the UniVCC founders and accounts a founder has granted, each under a confidentiality undertaking, see a Response in identifiable form.
5.2 Except as clause 5.4 allows, no partner, funder, member or other third party receives a Response, or any part of it, in identifiable form.
5.3 The service providers in Annex 4 host or process data for us under written contracts (GDPR Art. 28). They may not use it for their own purposes.
5.4 Research Partners. Where the Research Partner Addendum lists a Research Partner for your region, its named researchers may work with your Response on UniVCC’s platform once it is approved and once clauses 5.5 and 5.6 are met. Your Response stays on our platform, and the Research Partner receives no routine copy of it. Your stricter choices always apply. Access depends on the level of each field:
- Public fields, and fields you approved for attribution: named researchers may access and validate them.
- Restricted fields, and questions with no publication level: named researchers may access them on the platform where needed for validation and agreed analysis.
- Confidential fields, such as fees, carry, returns and investor commitments: anonymised Aggregates by default. A named researcher sees them in identifiable form only for a genuine research need recorded by UniVCC, and only if that person takes no part in the Research Partner’s fundraising, investment selection or commercial negotiations. If no such researcher is available, these fields stay with UniVCC.
- Anyone who takes part in that fundraising, investment selection or those negotiations: public or approved attributable data and anonymised Aggregates only.
Named researchers may see the work contact details (name, role, organisation, work e-mail) of the person who completed your Response, of colleagues who completed sections and of the Approver only where needed to clarify or validate an answer. This access is part of these terms; there is no separate opt-in. If your fund documents, limited partnership agreements or side letters do not allow it, do not submit a Response, or write to privacy@univccoalition.org first.
5.5 Before any of its researchers has access to a Response, each Research Partner signs a written agreement with UniVCC. Under it, the Research Partner:
- works with Responses on UniVCC’s platform, through individual accounts with two-factor authentication. It has no routine download. An extract is made only where a written workplan provides for it, limited to the fields and the period stated there;
- is an independent controller of the personal data its named researchers access. It acquires no right in the dataset or the taxonomy, which remain UniVCC’s. You keep your rights in your own data;
- keeps the Response confidential to at least the standard of clause 11, with access limited to named researchers, each under a written undertaking;
- uses it only for validating Responses, agreed research on its region, benchmarking and approved publications, and never for marketing, fundraising, deal sourcing, investment decisions or competitive positioning;
- follows the same Publication Levels, your stricter choices and the Aggregate rules as UniVCC (clauses 6 and 7), publishes nothing that identifies you without your approval, and publishes from restricted data only in a report or workplan agreed with UniVCC;
- contacts you, or a person named in your Response, about that Response only to clarify or validate your answers, never for marketing, fundraising or investment;
- does not pass the Response on to anyone else;
- tells UniVCC promptly of any security incident that affects it (clause 14.1);
- deletes any extract, and any notes that identify you or a person, within 30 days of UniVCC’s notice (clause 13). UniVCC gives that notice within 5 working days of deleting or anonymising the Response, or of your deletion request or withdrawal;
- has this access under the EU Standard Contractual Clauses, Module 1 (controller to controller). Responses are not delivered by e-mail.
5.6 A Response belongs to a region only when every vehicle in it is domiciled in that region. The domicile of the vehicles decides, not that of the manager: a Response from a manager based in the European Union whose vehicles are all domiciled in another region belongs to that other region. Your region is the region to which your Response belongs. A Response with vehicles in more than one region, or with a domicile we do not know, stays with UniVCC only. A Response with any vehicle domiciled in the European Union is never available to a Research Partner, and a Research Partner never has access to a Response that belongs to another region. No access is given before the signed agreement is in place. If you submitted your Response before a Research Partner was listed for your region, we tell you at least 30 days before that Research Partner has access to it. If you accept these terms while a Research Partner is listed for your region, you are told so at acceptance. A Response submitted under an earlier version of these terms is available to a Research Partner only if the Respondent agrees afresh (clauses 4.3 and 16.2).
6. Publication
6.1 Nothing from your Response is published before an authorised person on your side approves it.
6.2 Each field carries a Publication Level (Annex 2):
- P: may be published with your name, once Validated.
- R: used in our analysis. Members receive it only as Aggregates; a fund that contributed a Response receives its own benchmark report (clause 8).
- X: never published in a form that identifies you or anyone else. Used only in Aggregates.
6.3 At approval you may set any field to a stricter level than Annex 2 gives it. You may not set a field to a less strict level, and nothing that has not been Validated is published.
6.4 We never publish Personal Data about a person without that person’s own separate opt-in, in a box that is not ticked in advance. Your approval covers your organisation’s Fund Data. It does not cover other people’s Personal Data.
6.5 Before we first publish a P field with your name, we show you the text. You may correct any factual errors.
6.6 You may withdraw a publication choice at any time. Withdrawal applies to future publications. Material already published stays as it is, but we remove your name from online material we control where we reasonably can.
6.7 We do not publish rankings of funds.
7. Aggregates
7.1 We publish or share an Aggregate only if it meets all of these:
- it combines at least 3 funds (published counts of funds per country or region are the one exception);
- no single fund contributes more than 50% of the total for a sum or average;
- it does not show a minimum, a maximum or the value of the top fund;
- it cannot be worked out by comparing it with other figures we publish;
- a second UniVCC person has validated it against these rules.
7.2 We publish a description of these rules. We may apply stricter rules, and we may pool countries or years to protect small groups.
7.3 An Aggregate that meets clause 7.1 contains no information that identifies you or any person. We may keep and use it after your Response is deleted.
8. Benchmark reports to you
8.1 We may give you a private benchmark report comparing your fund with Aggregates of its peers.
8.2 The report is confidential to you. You may share it within your organisation, with your governing bodies and with your professional advisers. You may not publish it without our written consent.
8.3 If you are a public body and receive a request under freedom-of-information law for a report or for our correspondence, you will tell us before releasing it where your law allows, so we can explain why parts are confidential.
8.4 Reports and Aggregates are research. They are not investment advice and are provided as they are.
9. What you confirm
You confirm that:
- 9.1 you may share what you enter, including under your fund documents, limited partnership agreements, side letters and any other confidentiality obligation, and that each Research Partner for your region may have access to it under clause 5.4;
- 9.2 where a field asks about investors, you give the names of institutional investors only as the version of the questionnaire for your fund’s country asks for them. For investors who are private individuals you never give a name; you give only the number of such investors and a commitment band;
- 9.3 you name colleagues only by role contact (name, title, work email), and you have told them that UniVCC will contact them and that the named researchers of each Research Partner for your region may see their work contact details under clause 5.4, or you allow us to tell them directly;
- 9.4 the Response is accurate to the best of your knowledge when approved;
- 9.5 you do not include special-category personal data (such as health, ethnic origin or political views), data about children, or data about criminal matters;
- 9.6 you will tick “Fundraising” in the vehicle’s current activities if the fund is raising capital, so that we hold back attributable performance figures until you tell us fundraising has closed.
10. Personal data
10.1 Each party is responsible for its own processing of Personal Data and for its own lawful basis. UniVCC relies on its legitimate interest in running the research, and in giving each Research Partner for the Respondent’s region access under clause 5.4, as documented in its assessment. It relies on a person’s consent only to publish that person’s Personal Data.
10.2 About people other than the person filling in the form, we collect only role contacts; we never collect the names of investors who are private individuals (clause 9.2). We give every person named in a Response our own notice within one month, before any publication and before any access by a Research Partner. The notice says who we are, what we hold, why, who can access it (including each Research Partner for the region, where clause 5.4 applies), where it is processed, how long we keep it and how to exercise their rights.
10.3 People can exercise their rights by writing to privacy@univccoalition.org. If one of us receives a request that concerns the other’s processing, it passes the request on promptly.
10.4 Annex 1 sets out further undertakings that apply to all Personal Data we receive, whatever its country of origin.
11. Confidentiality
11.1 We treat every part of a Response that is not published under clause 6 as confidential business information, supplied to us in confidence. Where it qualifies, we protect it as a trade secret under Hungarian Act LIV of 2018.
11.2 You may mark any field “trade secret” and give a reason. We record the marking and keep it with the data.
11.3 We disclose confidential information only:
- as clause 6 allows;
- to each Research Partner for your region, as clause 5.4 allows, under a written duty of confidentiality at least equal to this clause;
- to our professional advisers under a duty of professional secrecy;
- where the law or a court or authority requires it. We then disclose no more than required and tell you first, where the law allows.
11.4 These obligations last as long as the information remains confidential, and at least five years after your Response is deleted.
12. Storage, security and AI
12.1 We store Responses in the European Union and analyse them there (clause 12.3). The one transfer outside the EU that these terms provide for is access by the named researchers of each Research Partner for your region (clause 5.4), under the EU Standard Contractual Clauses, Module 1. We tell you before any other transfer outside the EU. E-mails we send about a Response (invitations, receipts) go through Google Workspace, provided by Google Ireland Limited in its EU data region, with sub-processors as listed by Google; they contain contact details and the organisation and fund names, never the answers in the Response.
12.2 We apply the security measures in Annex 3.
12.3 We may use AI to help analyse Responses: coding free-text answers, summarising and drafting. We analyse them with AI providers that process them in the EU and do not store their content, currently Berget AI AB in Stockholm, Sweden, with Scaleway SAS in Paris as fallback (Annex 4). We may replace them or add other EU providers under the same safeguards; Annex 4 always names the providers in use, and we tell you before a change. When we use AI:
- each provider processes the data only for us and may not use it for training;
- we remove names and contact details before a Response reaches the model, wherever the task allows;
- a person reviews every AI output before it is published or shared;
- no decision about a person or a fund is made by AI.
13. How long we keep a Response
13.1 We delete an unfinished Response 30 days after it was last saved.
13.2 We keep a completed Response for up to five (5) years from our last contact with you about it. Then we anonymise it: the fund facts you approved for publication are kept and the people are removed, so that no person can be identified. Our last contact is the latest of your submission, our review, a change of stage and the last e-mail we sent you other than a reminder; an open follow-up holds it. A reminder does not extend retention. Aggregates and published reports are kept. A Research Partner keeps no extract or note that identifies you or a person longer than we keep the Response. We notify it within 5 working days after we delete or anonymise the Response, and it deletes them within 30 days of that notice. A Response recorded as outside the scope of the research on its eligibility answers is kept on the same terms, as a record of that outcome. It is not published, is not available to a Research Partner and is not used in Aggregates.
13.3 You may ask us to delete your Response at any time. We attempt to delete it within 30 days; backup copies expire within 90 days. Where the request concerns Personal Data, rights under GDPR Articles 12 and 17 are unaffected and we answer within one month. If a Research Partner had access to it under clause 5.4, we remove that access, notify it within 5 working days of your request, and it deletes any extract or note that identifies you or a person within 30 days of that notice. Material already published stays as clause 6.6 describes, and Aggregates stay as clause 7.3 describes.
13.4 Deleted data leaves our backups within 90 days. On request we confirm the deletion in writing.
14. Incidents
14.1 If a security incident affects your Response, including an incident at a Research Partner that had access to it, we tell you without undue delay, and where possible within 72 hours of becoming aware of it. We say what happened, what data is affected and what we are doing.
14.2 This is in addition to our duties to the Hungarian supervisory authority (NAIH) and to the people affected. Each party cooperates with the other as far as reasonably needed for the other’s own legal duties.
15. Liability
15.1 Each party is responsible for its own processing of Personal Data towards the people concerned and the authorities (GDPR Art. 82 and 83). A Research Partner is responsible in the same way for its own processing of the data it accesses.
15.2 Benchmark reports and published figures are research, provided as they are. UniVCC is not liable for decisions anyone takes on the basis of them.
15.3 Taking part in an Activity is voluntary and free of charge. To the fullest extent Hungarian law allows, neither party is liable to the other, in contract or otherwise, for anything arising from participation in an Activity or from its results. This clause does not exclude or limit:
- liability for intentional wrongdoing (Hungarian Civil Code, sections 6:152 and 6:526);
- liability for harm to life, bodily integrity or health (Hungarian Civil Code, sections 6:152 and 6:526);
- any liability that mandatory law, including data-protection law, does not allow to be excluded.
Each exclusion and each exception in this clause is separate and severable. If any part of it cannot be relied on, the rest continues to apply. Nothing in these terms limits the rights of a person whose Personal Data is processed.
16. Changes and ending
16.1 You may end your participation at any time by writing to privacy@univccoalition.org. Clauses 13.3 and 13.4 then apply. Clauses 8.2, 11, 13 and 15 continue to apply.
16.2 We may change these terms. We tell you at least 30 days before a change takes effect. A change that widens how we use or publish a Response applies to your Response only if you agree.
17. Law and disputes
17.1 Hungarian law governs these terms. The courts of Budapest have jurisdiction. A signed agreement under Part B may choose differently in Schedule 1.
17.2 Before going to court, the parties try to settle a dispute by discussion for at least 30 days.
17.3 Nothing in this clause limits the right of a person to complain to a supervisory authority, or to bring a claim in the courts where they reside (GDPR Art. 77 and 79).
18. Contact
Privacy and these terms: privacy@univccoalition.org. UniPrisma Kft., Révay köz 4, 1065 Budapest, Hungary.
Part B: Research Data Contribution and Confidentiality Agreement
The executable version, offered on request to institutions whose legal department seeks an executed written agreement. This agreement is generated from the same source as Part A, so the clauses are word for word the same. Only the cover page, Schedule 1 and the signatures are added.
Cover page
Research Data Contribution and Confidentiality Agreement between:
- UniPrisma Kft., trading as the University Venture Capital Coalition (UniVCC), Révay köz 4, 1065 Budapest, Hungary, company registration number 01-09-448571, tax number 26606572-2-42; and
- [Respondent’s full legal name], [legal form], [registered address], [registration number] (the “Respondent”).
The parties agree that:
- (a) clauses 1 to 18 of the UniVCC Participation Terms for the Activity named in Schedule 1, version [version] of [date], their Annexes 1 to 4 and the Research Partner Addendum, attached, form part of this agreement;
- (b) this agreement is mutual: clause 11 (confidentiality) also binds the Respondent for any confidential UniVCC material it receives, including benchmark reports and results shared before publication;
- (c) Schedule 1 prevails over the clauses where they differ;
- (d) this agreement replaces any click-through acceptance by the Respondent for the same fund.
Schedule 1: options chosen for this agreement
| Item | Default | Chosen for this agreement |
|---|---|---|
| Governing law (clause 17.1) | Hungarian law | ☐ Hungarian law · ☐ Respondent’s law: [state] · ☐ no choice of law |
| Forum (clause 17.1) | Courts of Budapest | ☐ Courts of Budapest · ☐ Respondent’s courts · ☐ arbitration: ☐ Permanent Arbitration Court attached to the Hungarian Chamber of Commerce and Industry · ☐ Vienna International Arbitral Centre |
| Liability (clause 15.3) | No cap: liability excluded as far as the law allows | No cap: liability excluded as far as the law allows |
| Activity (Activity Schedule) | None | [name of the Activity] |
| Funds covered | One fund | [fund names] |
| Fields set stricter than Annex 2 | None | [list, or “as set at approval”] |
| Security evidence (Annex 3) | Annex 3 as published | ☐ Annex 3 · ☐ DPIA summary · ☐ answers to the Respondent’s security questions |
| Respondent’s contact for notices | Approver | [name, role, email] |
| Respondent’s data-protection contact | None | [name or function, email] |
| UniVCC contact | privacy@univccoalition.org | privacy@univccoalition.org |
Signatures
| For UniPrisma Kft. | For the Respondent |
|---|---|
| Name: | Name: |
| Title: | Title: |
| Date: | Date: |
| Signature: | Signature: |
Signed electronically or in two counterparts. Each party keeps a PDF.
Annex 1: Undertakings for all personal data we receive
This annex applies to every Respondent, in every country. Many laws outside the EU let an organisation send personal data abroad only if the recipient is bound to protect it. These undertakings give every Respondent that commitment in one text.
A1. Protection at GDPR level, whatever the origin. UniVCC protects all Personal Data it receives under these terms at least to the standard of the GDPR, whatever country it comes from. These undertakings are legally binding on UniVCC. They are given to the Respondent and, where the Respondent’s law requires it, also to the people the data is about.
A2. Data about organisations gets the same care. UniVCC applies the same security, confidentiality and deletion rules to information about organisations as to Personal Data. (Some laws, such as South Africa’s POPIA, treat organisations as data subjects.) For data from a South African fund, UniVCC protects it to a standard equivalent to POPIA, including data about legal persons.
A3. Purpose and onward transfer. UniVCC uses the data only for the purposes in clause 4. It does not pass identifiable data to anyone except the service providers in Annex 4 and, to the extent clause 5.4 allows, the named researchers of each Research Partner for the Respondent’s region listed in the Research Partner Addendum, each bound to the same protections. Access by a Research Partner outside the EU uses the EU Standard Contractual Clauses, Module 1. Any other transfer outside the EU would need a lawful transfer mechanism under GDPR Chapter V, an update of Annex 4, and notice to the Respondent first.
A4. Rights of the people concerned. Any person whose data UniVCC holds may ask for access, correction, deletion or restriction, or object, by writing to privacy@univccoalition.org. UniVCC answers within one month. A person may complain to the Hungarian supervisory authority (NAIH), or to the authority in their own country where their law gives them that right.
A5. Consent where a law requires it. Where a Respondent’s law lets it share a person’s data only with that person’s consent, UniVCC collects that consent itself, directly from the person in its own invitation flow, before using their data beyond contacting them.
A6. Official forms on request. Where a Respondent’s law requires a specific official instrument before it may send personal data abroad, UniVCC signs it on request, without changes. Examples: Türkiye’s standard contract, the EU Standard Contractual Clauses (Module 1), any model clauses Chile’s authority adopts. If such an instrument and these terms differ, the instrument prevails for that Respondent’s Personal Data, as far as its law requires. The Respondent makes any filing its own law requires.
A7. Information for the Respondent’s own assessment. On request UniVCC supplies what a Respondent needs for its own transfer or impact assessment: these terms, Annexes 3 and 4, the Research Partner Addendum, the DPIA summary, and answers to reasonable written questions. (This covers, for example, Quebec’s assessment before data leaves the province.)
A8. Government requests. If any authority asks UniVCC for a Respondent’s data, UniVCC tells the Respondent first where the law allows. It discloses no more than the law requires.
A9. Breaches of this annex. If UniVCC can no longer meet these undertakings, it tells the Respondent promptly. The Respondent may then end its participation and have its data deleted under clause 13.3.
Annex 2: Publication levels
Every field carries one level. The field-by-field list for each Activity is attached to this annex.
| Level | What it means | Typical fields |
|---|---|---|
| P Public | May be published with the fund’s name once Validated | Fund name, manager, affiliated university or RTO, legal form, domicile, vintage or first close, size or size band, stage and sector focus, public deals and exits |
| R Restricted | Used in analysis; members receive Aggregates, a contributing fund its own benchmark report; qualitative items published only on per-item opt-in | Governance and investment-committee model, the university’s role, evergreen or closed-end structure, co-investors (the funds or managers a vehicle has co-invested with) |
| X Confidential | Never published in identifiable form; Aggregates only | Fees and carry, IRR, TVPI, DPI, MOIC, LP categories and commitments, deployment pace, realisations |
| Personal Data | Any field | Never published without the person’s own opt-in (clause 6.4); contact details never published |
Annex 3: Security measures
- Location: Responses are stored and analysed in the EU. Hosting, database and backups at Clever Cloud in Paris. AI analysis as set out under AI below. E-mail through Google Workspace (Google Ireland, EU data region, with sub-processors as listed by Google); e-mails carry contact details and the organisation and fund names, never the answers. The one transfer of Responses outside the EU is to each Research Partner for the Respondent’s region (clause 5.4, Research Partner Addendum). You are told before any other transfer outside the EU.
- Access: the founders, and accounts a founder has granted, each under a confidentiality undertaking. For its own region’s Responses only, the named researchers of each Research Partner to the extent clause 5.4 allows, each under a written undertaking, through individual accounts on UniVCC’s platform and not by e-mail. Anyone who takes part in that Research Partner’s fundraising, investment selection or commercial negotiations sees only public or approved attributable data and anonymised Aggregates. No funder or member receives Responses or LP data in that capacity; a Research Partner that is also a member has access only under clause 5.4.
- Separation: LP data stored apart from performance data in working files.
- Encryption: in transit (TLS) and at rest.
- Backups: the hosting provider’s daily database backups, plus a weekly copy of all tables in Clever Cloud storage, kept for 90 days.
- Not allowed: Responses outside UniPrisma Kft.’s own accounts and tools, except an extract made for a Research Partner under a written workplan (clause 5.5).
- AI: We analyse Responses with AI providers that process them in the EU and do not store their content, currently Berget AI AB in Stockholm, Sweden, with Scaleway SAS in Paris as fallback (Annex 4). We may replace them or add other EU providers under the same safeguards; Annex 4 always names the providers in use, and we tell you before a change. No training on Response content; names removed before prompts where the task allows; human review of every output.
- Releases: every published Aggregate is validated by a second person against clause 7.
- Deletion: automated: 30 days after the last save (unfinished) and up to 5 years from the last contact (completed questionnaire responses anonymised, other form submissions deleted).
- Incidents: a written incident response plan.
- People: confidentiality obligations in every contract; documented AI-literacy training for staff who use AI tools.
Annex 4: Service providers that process Responses for us
| Provider | What it does | Where | Contract |
|---|---|---|---|
| Clever Cloud SAS | Hosting, database, backups, file storage | France (EU), Paris | Data processing agreement (GDPR Art. 28) |
| Berget AI AB, Stockholm (Sweden) | AI-assisted analysis of Responses | Sweden (EU) | Data processing agreement (GDPR Art. 28); no training on Response content; zero data retention: prompts and outputs are not stored |
| Scaleway SAS, Paris (France) | AI-assisted analysis of Responses when Berget AI is unavailable | France (EU), Paris | Data processing agreement (GDPR Art. 28); no training on Response content; zero data retention |
| Google Ireland Limited (Google Workspace, Gmail) | Sends invitations, notices and receipts | Ireland (EU), EU data region, with sub-processors as listed by Google | Data processing agreement (GDPR Art. 28) |
We may replace an AI provider or add other EU providers under the same safeguards. This annex always names the providers in use, and we tell you before a change.
Activity Schedule
Each Activity has its own entry. The clauses above apply to every Activity except where its entry says otherwise, and an entry prevails over the clauses for that Activity: for example, a membership application is not published at all (Activity B). The entry sets what differs: who takes part, what is collected, what it is used for, who sees it, whether and how it is published, how long it is kept, and which clauses do not apply. A new Activity is added here, and to the Research and Data list on the Legal page, before it opens. Clauses 6 to 8 and Annex 2 apply as stated to an Activity whose entry says so.
Activity A: UVC/RTO Fund Questionnaire
| Item | Entry |
|---|---|
| Who takes part | An organisation that is a university- or RTO-affiliated fund, or an organisation acting for one |
| What is collected | The questionnaire’s fields, each with a Publication Level (Annex 2) |
| What it is used for | Research: benchmarks, an ecosystem map, research publications, analysis for coalition members, a private benchmark report for each fund that took part, and research on its own region with a Research Partner |
| Who sees it | As each field’s level sets (Annex 2). Only the UniVCC founders and accounts a founder has granted, each under a confidentiality undertaking, and, to the extent clause 5.4 allows, the named researchers of each Research Partner for the Respondent’s region (clauses 5.4 to 5.6, Research Partner Addendum) see individual Responses |
| Publication | Clauses 6 to 8 apply. Nothing is published before the Approver or, if none is named, the lead respondent agrees |
| Kept | Completed Responses for up to 5 years from the last contact, then anonymised. Unfinished drafts are deleted 30 days after the last save |
| Clause 9.2 | Applies |
Activity B: Membership Application
| Item | Entry |
|---|---|
| Who takes part | An organisation applying to join the coalition |
| What is collected | The application form’s fields |
| What it is used for | The decision on membership, and UniVCC’s own analysis and benchmarks, in aggregate |
| Who sees it | Only named members of the UniVCC team, bound by confidentiality |
| Publication | None in identifiable form. Aggregates combine at least three organisations. UniVCC does not share an application with external or commercial parties without the applicant’s written consent |
| Kept | As the Privacy Policy states for applications and members |
| Terms accepted | The applicant accepts these terms, as far as this entry says, with the tick “I have read and agree with the legal information” on the application form, which covers everything on the Legal page. The Privacy Policy governs the application itself. The sharing rule in the Publication row binds UniVCC |
| Clauses that do not apply | 1.2 (second sentence), 3.1 (second sentence), 4.1, 4.2 (third bullet), 5.4 to 5.6, 6, 8, 9.2, 9.6 and 13.1 to 13.2 |