Your data

Applicant privacy notice

Last updated 14 November 2026.

This notice adds to the main Re:Build privacy policy, which covers who we are, your rights, international transfers and the services Re:Build uses for tickets and mailing lists. All of that applies here too. This page covers what's particular to applying to be a participant: what we collect, who sees it, why, and how long we keep it. KimmiCon Limited is the data controller.

What we collect

  • On the first screen: your name, your email, and whether you'd like us to keep you up to date on all things Re:Build, with when you answered.
  • In the survey and your profile: your answers about who you are and how you like to take part, the links you give us, what you would bring and like to see, and the names and contacts of anyone you suggest we invite or who'd co-host a session with you.
  • If you leave part-way: when, the screen you left from, and the reason and note you give, if you give them.
  • If you choose to: whether you're part of an under-represented group, in your own words; any accommodations we can make for you; and documents you upload, such as a CV or a deck. All optional.
  • Signing in: when you last signed in, and the session that keeps you signed in.
  • If you book a call, or ask us to find you a time: your name and email, whether you'd like us to keep you up to date, when the call is, who it's with, your time zone, whether it was cancelled, and anything you tell us about when suits you. Booking starts an application in your name, which goes no further unless you carry on.
  • If you nominate someone: your name and email, their name, their email or a profile link, and why you suggested them. If someone nominated you, that's what we hold about you.
  • What the team writes: reviewers' verdicts, reasons and comments on your application, and the decisions we make.
  • What happens: a record of when you started, came back, left, or answered an offer (with any note you add), of documents added or removed, and of calls booked or cancelled; which version of the form you used; when you said "I understand" to the note at the top of your profile; and, if you accept a place, which version of this notice was current.
  • Your visits: when you work on your application, roughly for how long, which screens you were on and which parts you changed (never what you wrote), and whether you were on a phone, a tablet or a computer. You can stop this, and delete what we have, at the foot of your profile.
  • If you say yes to analytics cookies (we don't use any yet; see Cookies and analytics): which of our pages you visit and how you move through them. Never what you wrote.

What we read about you

To understand who you are without asking you for too much, we read what is public at the links you give us (a profile, a blog, a podcast, recordings of your talks) and anything you share with us directly, such as slides or documents you upload. We only go looking where you have pointed us, or at material that is publicly about your professional work. We may use software, including AI tools running on systems we control, to summarise it for the Re:Build team. Nothing about you is decided automatically: people choose.

Why, on what basis, and for how long

These add to the table in the main policy. The conference is on 5 and 6 May 2027, so six months after it is November 2027, and nine months after is February 2028.

PurposeLawful basisKept for
Considering your application, choosing participants, and shaping what you do at Re:Build: which sessions, with whom, for which audienceSteps you ask us to take before buying a participant ticket, and our legitimate interest in choosing a balanced roomIf you're not selected, you decline, or you leave part-way: six months after the conference. If you take part: nine months after the conference (more below)
Signing you in, and emails about your application and, if you take part, the conferenceAs aboveAs above
Reading public material at the links you give usLegitimate interests; you can objectAs your application
Whether you're part of an under-represented group, and any accommodationsYour explicit consent, given by answering. The people choosing participants see the first only if you also tick the boxAs your application. Anything kept for reporting is reduced to counts with no names attached
Keeping you up to date on all things Re:BuildConsent: the tickUntil you untick it or opt out
Checking back once, if you leave part-way, in case something got in the way, technical or otherwiseLegitimate interests: you'd started applying; you can tell us not toAs why people leave
Learning what isn't working, from why people leaveLegitimate interestsSix months after the conference
Making the form easier, from how long people spend on it and where they get stuck (your visits)Legitimate interests: improving how people apply; you can stop it from your profileSix months after the conference, or until you stop it
Seeing which pages people read and how they move through them (Google Analytics). Only if we add it, and only if you say yesConsent: the cookie bannerUp to 14 months, or until you change your mind
Nominations, and people you suggest we inviteLegitimate interests: finding people for the roomSix months after the conference, unless they apply
Calls: arranging them, and knowing who we've spoken toSteps you ask us to takeSix months after the conference, or with your application if you apply
Keeping your profile for a future Re:Build, if you took partLegitimate interests: making it easy to take part again; you can object at any timeUntil you ask us to delete it, or there's to be no future Re:Build. We remind you every six months that we hold it
Records of the emails we send: your address, the subject, and whether each arrived, bounced or was marked as spamLegitimate interests: knowing mail gets throughA month
Stopping abuse: counting requests by IP address, email address or account, and logging refused or failed requests, which can include your email addressLegitimate interestsA day for the counts, a month for the logs

After the conference. If you take part, we keep your profile for nine months after the conference. If you decline a place, or once the event is over, you can ask us to delete it at any time and we will. If there's to be another Re:Build, we'd like to keep participants' profiles so you can put yourself forward again without starting over. If we do, we'll tell you before the nine months are up, and from then on we'll remind you every six months that we hold yours, with an easy way to have it deleted.

If mail to your address bounces for good, or you mark ours as spam, Amazon keeps the address on a do-not-send list and we stop writing to it, until you ask us to take it off. Deleted data leaves our backups within 35 days.

Being named

We expect to promote the people taking part and what they bring, such as on our website, on social media and in the programme. We haven't settled exactly what that looks like yet. We'll decide before we send any offers and update this notice if we need to, and when you accept a place we'll ask you to confirm you've read the latest version. Nothing from your application is published before you've accepted.

Who sees what

  • The Re:Build team, who choose participants, see your profile, and can open any documents you upload, from the moment you finish the survey.
  • What you tell us about being part of an under-represented group helps us balance the room. The people choosing participants see it only if you tick the box that says they may. Accommodations are never shown to them.
  • The organisers see everything, so they can run the event, handle bursaries and look after you on the day.
  • Your visits are seen only by the organisers, to make the form easier. They play no part in choosing participants.
  • If you book a call, the person you'll talk to sees your name and email, even before you've finished the survey.
  • The services that host it for us: Amazon Web Services in Ireland stores it and sends our emails. Replies to our emails and requests for a call reach the organisers through Google Workspace. If you book a call, the invite also sits in the calendar of the person you'll talk to, which may be kept by Google, Microsoft or Apple, and the call itself runs on their video service, such as Google Meet, Zoom or Microsoft Teams. If you say yes to analytics cookies, Google sees what they record (see Cookies and analytics). Nobody else sees any of it.

Emails

About your application. We use your email to sign you in, to write to you about your application and, if you take part, about the conference: what you need to know, and when. That comes with applying, so there is no box to tick. To stop them, step away from your application or ask us to delete it. Stepping away doesn't hide what you've written from the team; deleting does.

Keeping you up to date on all things Re:Build, such as future events or other ways to get involved like sponsoring, only if you tick the box that says we may. It starts unticked and it's optional. We record when you answered and which wording you saw. You can change your answer on your profile at any time, and every one of those emails lets you opt out, which we honour.

If you leave part-way, we may check back with you once, to make sure there's no difficulty we should know about, technical or otherwise. If you don't reply, we won't write again, and if you'd rather we didn't write at all, say so when you leave or email us.

If you nominate someone and ask us to send the message, or ask us to reach out to someone you'd invite or co-host with, we get in touch with them once and say who suggested them. Please only suggest people you think would be glad to hear from us.

Emails from this site have no images and track nothing: we don't know whether you opened one or clicked a link. The main policy covers the mailing list.

Cookies and analytics

Signing in sets one cookie, which keeps you signed in for up to 30 days. The "Talk to us" button remembers, in your browser, that you've closed its note. Recording your visits needs nothing more: it uses the cookie that keeps you signed in, and what it records stays with us. The pages load their fonts from Google Fonts, which sees your IP address.

Analytics. We don't use any here yet. We may add Google Analytics, as rebuildcon.uk has, to see which pages people read and how they move through them. If we do, it will only run if you say yes to a cookie banner, you can change your mind at any time from a "Cookie settings" link, and we'll never pass it your name, your email or anything you've written. The main policy says what Google Analytics collects and how long it's kept.

Your rights

You have all the rights set out in the main policy: to a copy of what we hold, to correct it, to delete it, to object, to restrict how we use it, and to withdraw consent at any time. Unticking a box takes effect straight away. Clearing an answer removes it from your profile straight away, though a reviewer who read it before may see what changed until they next look. For anything else, email kim@rebuildcon.uk, including if someone nominated you and you'd rather we didn't hold your details. You can also complain to the Information Commissioner's Office at ico.org.uk.

Changes to this notice

We date each version and list what changed here, so you can see what's different since you last read it. If a change matters to you, we'll tell you, and when you accept a place we'll ask you to confirm you've read the latest version.

  • 14 November 2026: we now record your visits to your application, and you can stop it from your profile. And we say how Google Analytics would work here if we add it; we don't use it yet.
  • 9 November 2026: first version.