Privacy Policy

Who we are

DevConnect runs in-person events in London for people building on Roblox. This policy explains how we handle personal data through www.devconnect.events and the tools behind it.

The data controller is DevConnect Ltd (company number 16998850), 53 High Street, Billericay, CM12 9AX, England. You can reach us about anything in this policy at lucien@devconnect.events.

What we collect

Your account

Sign-in is handled by Clerk, our authentication provider. You can sign in with email, Discord or Roblox. Clerk holds your account, including your email address if you give one and the details shared by the service you sign in with. We never see your Discord or Roblox password.

You don't need an account to browse the site or buy a ticket. You only need one to connect Roblox or to see your tickets in one place.

Signing in with Roblox

Roblox asks for your permission before sharing anything with us. If you agree, Roblox shares:

• your Roblox user ID
• your username and display name
• your profile picture

Roblox's profile information also includes your account creation date and a link to your Roblox profile. We don't use those two details.

We use this information to identify your account, to show your profile picture while you are signed in, to show your Roblox account on the ticket form, and to show your avatar on your ticket and badge. This permission only tells us who you are: it does not let us read or change anything in your Roblox account. Roblox doesn't share your email address with us, so if your DevConnect account doesn't have one, you enter one on Stripe's checkout page when you buy a ticket.

Tickets

When you buy a ticket, you give us your name, role, and game or studio, tell us whether we can photograph you, and confirm that you are 18 or over. If your account is linked to Roblox, we also store your Roblox user ID and username, and whether Roblox shows a verified badge on your account. If it does, the name on your ticket is your Roblox name. We store these details with your account ID if you are signed in, the event, ticket type, price, payment status, relevant dates and a random ticket code.

You can also tell us about any allergies or dietary needs. This can reveal information about your health or beliefs, so it is optional. We use it only to cater for you at the event, it is visible only to our team, and we may pass it to the venue or caterer for that purpose.

You can add a bio, a Discord username and an email address to your trading card. These are printed on the card, and other guests keep the cards they are given, so only add what you are happy to share. The email on your card can be different from the one you pay with.

We start a record as soon as you go to checkout, so you can come back and pay later, and it stays on file if you don't finish paying. It doesn't hold your place, so the event can sell out before you pay.

To check your Roblox profile and show your avatar on the ticket form and your badge, our server sends your Roblox user ID to Roblox's public services and fetches the avatar image. Our server may keep that image in memory for up to an hour. We don't save it to our database.

Our guest lists are curated, so we may review what you tell us, along with public information about your work, when deciding who attends.

Payments

Payments are taken on a checkout page hosted by Stripe. We give Stripe your ticket code, a link to your badge page, the event name and the price, plus your email address if you are signed in. On that page, Stripe asks for your full name, email address, billing address and card details. Your card details go directly to Stripe, and we never see or store them. Stripe sends us your name, email address and billing address, and we store them with your ticket, along with Stripe's payment references, the amount paid and whether the ticket is paid or refunded.

Your public badge page

Each paid ticket gets a badge page at a link containing a random code. Anyone with the link can see it, without signing in. It shows your name, role, game or studio and ticket code, along with the event name and date, plus your avatar and any Roblox verified badge if your account is linked to Roblox.

Your Roblox username is not printed on the badge, but your Roblox user ID is part of the avatar image's web address, so someone could find your Roblox account from the page. Sharing the link can also show a preview card with your name, avatar and event. Your email address is not shown.

We ask search engines not to index badge pages, but we can't control where a link goes once it is shared. A badge page stops working if its ticket is refunded. To have one taken down sooner, contact us.

Technical data

Our hosting provider, Vercel, processes the requests your browser makes, which include your IP address and browser details. Clerk may record similar details to keep your account and session secure.

When you open an event page, our server counts the visit. We record the event, the day, the website or tagged link that sent you, and your approximate city and country, which Vercel works out from your IP address. To count each visitor once a day we store a keyed hash of your IP address and browser details that changes every day, so we can't follow you from one day to the next. We don't store the IP address itself, and these records aren't shared with anyone else.

When you start a checkout, we store a keyed hash of your IP address, so one connection can't start too many unpaid checkouts. We clear it when you pay, or at the next checkout for that event once 35 minutes have passed.

Photos and video at events

We take photos and video at our events and use them on our website and social channels. When you buy a ticket, we ask whether we can photograph you. If you say no, we won't knowingly feature you, though you could still appear in the background of a wide shot. To change your answer, or to have a photo of you removed, tell us at the event or contact us afterwards.

Our Discord server

If you join the DevConnect Discord server, we can see your Discord user ID, username and avatar. We keep your ID and username, your event message preference and a record of the event messages we send you by direct message. Each message has an unsubscribe link.

People we invite through LinkedIn

You may not have given us your details directly. To find people to invite to our events, we use tools that search for publicly available professional profiles on LinkedIn. We may collect your name, headline, company, location, profile link, profile photo, and connection and follower counts.

We use AI to score how relevant you are to our events and to draft a short invitation. We may then send you a connection request and a message on LinkedIn. To object or have your record removed, contact us.

Why we use it, and our legal basis

• Providing your account and ticket, and running the event you booked: performing our contract with you.
• Curating guest lists, keeping the site secure, counting event page visits, event photography, Discord event messages and LinkedIn invitations: our legitimate interests in running relevant, safe events and telling people about them. You can object at any time.
• Allergies and dietary needs: your explicit consent, which you give by entering them. You can withdraw it at any time by contacting us.
• Keeping payment and accounting records: complying with our legal obligations.
• Showing your badge page: performing our contract with you, as the badge is part of your ticket.

Who we share it with

We do not sell your personal data. We share it only with the providers that help us run DevConnect:

• Clerk: sign-in and accounts
• Stripe: payments
• Resend: ticket confirmation emails and event emails
• Vercel: website hosting
• Neon: our database
• Roblox: Roblox sign-in and avatar lookups
• Discord: Discord sign-in, our server, direct messages and telling our organisers about ticket sales
• Railway: hosting for our Discord and outreach tools and their records
• Serper and IPRoyal: web search and network routing for LinkedIn outreach
• Anthropic: AI scoring and invitation drafts for LinkedIn outreach
• LinkedIn: where outreach messages are sent

We may also share data where the law requires it. Some events are run with partners and sell tickets on another platform such as Luma. The event page links to it, and that platform's own privacy policy applies to anything you enter there.

International transfers

Some of these providers are based outside the UK, including in the United States, so your data may be processed there. Where that happens, we rely on protections recognised under UK data protection law, such as adequacy regulations or the standard contractual clauses our providers offer.

Cookies and analytics

We don't use analytics or advertising cookies, and we don't run outside tracking tools on this site. Event page visits are counted on our own server without cookies, as described under Technical data.

Clerk uses cookies and similar browser storage to keep you signed in, and they are needed for sign-in to work. The site also stores one small value in your browser for the current tab so that the opening animation only plays once. Stripe's checkout page is run by Stripe, and its own cookie policy applies there.

How long we keep it

We keep ticket and payment records, including unfinished checkouts, for six years after the end of the financial year they relate to. You can ask us to remove your allergy or dietary details at any time. Your account stays with Clerk until you ask us to delete it. Discord and outreach records stay until you opt out or ask us to remove them, or until we no longer need them. Event page visit records stay until we no longer need them.

We may keep some data for longer where the law requires it, for example accounting records.

Your rights

Under UK data protection law, you have the right to:

• ask for a copy of your personal data
• have inaccurate data corrected
• have your data deleted in some circumstances
• restrict or object to how we use it
• receive data you gave us in a portable format, where this applies
• withdraw consent at any time, where we rely on it

To use any of these rights, email lucien@devconnect.events. You can remove our access to your Roblox account from your Roblox settings at any time.

If you are unhappy with how we have handled your data, please contact us first. You can also complain to the UK Information Commissioner's Office at ico.org.uk.

Age

Our events and tickets are for people aged 18 or over. Roblox only lets accounts for people aged 13 or over authorise apps like ours.

Changes to this policy

If we change this policy, we will update it here and change the date at the top.