Back to meetadev

Last updated 26 October 2026

Privacy policy

meetadev helps people at developer events find who to meet. This page says what we collect, why, who can see it, how long we keep it, and how you can delete it. meetadev is run by Hazardsecurity in Nigeria, which is responsible for your data (the “data controller”). Questions or requests: hello@meetadev.xyz.

The short version

  • You sign in with Google. We get your name, email address, profile photo and Google account ID. Never your password.
  • Your phone number, WhatsApp and contact email are shown only to people you're connected with, which happens when you both chose to meet.
  • Choosing “Meet” on someone is private. They only find out if they chose to meet you too.
  • We don't sell your data or show ads. We use PostHog to see how people use meetadev so we can improve it, and you can turn that off on My badge.
  • You can delete your account yourself, any time, from My badge.

What we collect

Your name, email address, profile photo and Google account ID. We use them to create your account and sign you in.

Your display name, headline and intro, role, level, what you're here for (for example mentoring or hiring), the tech you use, the cities you follow, and optionally your LinkedIn, GitHub, X and website. Contact details you add: phone, WhatsApp and a contact email.

The events you join, who you chose to meet or passed on, your connections, “We met” confirmations, your chat messages and whether they were delivered and read, people you blocked, reports you made, and, if you organise, your events and organiser application.

Your IP address, used to limit sign-ups and other actions so the service can't be abused. If you turn on notifications, your browser's push address for this device. Our hosting provider keeps standard server logs.

We use PostHog to understand how meetadev is used: pages you open, buttons you tap, your device and browser type, rough location from your IP address, and steps such as signing up, joining an event, choosing Meet or Pass, matching, sending a message (not what it says) and confirming you met. These are linked to your account ID, not your name or email. We also record some sessions as screen replays to find what's confusing. Everything you type is hidden in them, and chats, contact details and admin pages are left out completely. If your browser sends Do Not Track, none of this is collected.

You can turn analytics off any time on My badge → Help improve meetadev. It stays off on that browser.

Who can see what

  • Anyone: event and community pages, and the badge of anyone who is listed in the directory (name, photo, headline, intro, role, interests and public links).
  • People at the same event: your badge in their deck and the people list, unless you hid yourself from the directory. Your place on the event's leaderboard, which counts the people you met.
  • Your connections only: your phone, WhatsApp and contact email, and your chats with them.
  • Event organisers: who joined their event, a count of how many people swiped, matched and met, and reports about people at their event. Not your private contact details or messages.
  • Nobody: who you passed on, and who you chose to meet unless it became mutual.

Why we use it (lawful basis)

  • To provide the service you signed up for: your account, badge, deck, matches, connections, chat and leaderboard.
  • Your consent: the optional details you add, and notifications, which you can turn off at any time.
  • Our legitimate interests: keeping people safe and stopping abuse, through rate limits, reports, blocks and event bans; and understanding how the app is used so we can improve it, which you can switch off.
  • Legal obligations: where the law requires us to keep or share information.

Cookies and storage

We use what the site needs to work, plus analytics storage you can turn off. There are no advertising cookies.

  • dfi_session: keeps you signed in, for up to 30 days.
  • Sign-in check: a short-lived cookie that protects the Google sign-in step, for about 10 minutes.
  • dfi_event: remembers the last event you opened, for 90 days.
  • mad_start: remembers that you saw the welcome screen, for a year.
  • Theme: your light or dark choice, saved in your browser only.
  • Analytics (PostHog): a random ID and visit details saved in your browser's local storage, until you clear it or turn analytics off.
  • mad_no_analytics: remembers that you turned analytics off, for a year.

Services we use

We share data with these providers only so meetadev can run. They process it on our behalf.

  • Google: sign-in.
  • Vercel: hosting the website.
  • Neon: our database.
  • PostHog: product analytics and screen replays, as described above.
  • Your browser's push service (for example Google, Apple or Mozilla): delivering notifications you turned on, which can include a short preview of a message.

Some of these providers store or process data outside Nigeria, including in the United States. Where that happens we rely on their contractual and security commitments to protect it as the law requires.

How long we keep it

  • Your account, badge, connections and chats: until you delete your account.
  • Sign-in sessions: up to 30 days, or until you log out.
  • Rate-limit records: a counter tied to your IP address or account, replaced as soon as its time window ends.
  • Events you created stay up for the people who joined them, unless an organiser deletes the event.
  • Analytics: usage events for up to 12 months and screen replays for up to 30 days. After you delete your account they are tied only to an ID that no longer points to anyone.

Deleting your account

Go to My badge and choose “Delete my account”. This removes your badge, contact details, connections, the people you chose to meet or passed on, your chats (including the other person's copy of those conversations), your notification subscriptions and your sessions. It can't be undone.

To keep the service fair and safe, a few things stay, without your name or any way to contact you:

  • Meetings you confirmed still count for the people you met.
  • Reports you made, because they are about someone else.
  • Bans, blocks and reports involving you are kept against a one-way code made from your Google account ID, so they apply again if the same Google account signs up later. The code doesn't contain your ID, name or email, and we only use it to recognise a returning account.

If you can't sign in any more, email us from the address on your account and we'll delete it for you.

Your rights

Under Nigeria's Data Protection Act 2023 (and similar laws where you live) you can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or move it to another service, and you can withdraw consent at any time. You can edit most of your data yourself on your badge. For anything else, email hello@meetadev.xyz; we reply within 30 days.

If you're not happy with our answer, you can complain to the Nigeria Data Protection Commission (NDPC).

Age

You must be at least 13 to use meetadev. If you're under 18, you need permission from a parent or guardian. If you believe a child is using meetadev without it, tell us and we'll remove the account.

Security

Connections to meetadev are encrypted. We store only a scrambled form of each sign-in session, never a password, and contact details are only sent to people you're connected with. No system is perfectly secure: if we learn of a breach that affects you, we'll tell you and the regulator as the law requires.

Changes

We'll update this page when what we collect or how we use it changes, and change the date at the top. Big changes will also be announced in the app.

See also the terms of use and the community guidelines.