Verified but private: how identity works on AroundMe

You want two things from any service that puts you in a room with strangers, and at first they look like opposites. You want to know these are real, verified people: not bots, not burner accounts, not someone who can misbehave and then vanish. And you want the opposite of a data grab: not your face in a feed, not your life packaged into a profile, not your details handed to whoever's buying.

Those pull against each other only if verification and exposure are the same lever, if the price of proving everyone's real is putting everyone on display. AroundMe is built on the claim that they're not the same lever at all. Being verified and being visible are two different things, and you can have the first without the second. This post is how we split them: verify enough to establish trust, and expose as little as possible to everyone else.

How does AroundMe verify members?

Everyone is verified before they can be matched into a group. It's a one-time check, at onboarding, that ties your account to a real, reachable person instead of an anonymous burner. The method fits the community we're opening: a confirmed school email at our first campus, a work email or professional profile as we add new groups. AroundMe is for adults, 18 and over. That's the entire job we ask of verification, and the reason is accountability. Anonymity is what makes bad behavior cheap; someone whose account can be identified and permanently removed acts differently from a burner account. We'll say exactly what the check is rather than dress it up. Claiming ID checks or verification badges we don't run would be its own kind of dishonesty. What matters is the model: verification buys trust, and then it stops. Passing it doesn't publish a thing about you: it never becomes a profile others can browse, or a dossier assembled to be displayed or sold.

What verification confirms, and where it stops

• Confirms a real, single person: not a bot, not a burner account
• For adults only: 18 and over
• Confirms someone accountable: reachable, and removable if they act badly
• Stops there: passing verification publishes nothing about you
• Never becomes a browsable, searchable, or swipeable profile
• Never becomes a marketing dossier assembled to display or sell

Verified for trust, not for browsing

Most apps in this category make one move we refuse: they turn verification into a profile. You prove you're real, and the reward is being listed: searchable, filterable, swipeable, a face in someone's feed. AroundMe does the first and not the second. Verification gives the platform accountability; it does not hand other members a catalog entry with your name on it. That's why there's no feed, no search, and no way to look anyone up. We removed browsing from the product entirely, and the full reasoning for having no profiles at all is its own piece. For identity, the takeaway is narrower and sharper: being verified and being visible got pulled apart on purpose, so the accountability you're owed never turns into exposure you didn't ask for.

Why you tell us what you like, not who you are

Dating and ad-driven social apps run on a dossier: the more you fill in (photos, bio, preferences, history), the better the profile they can display to others or sell to advertisers. Your profile is the thing the whole product is built around. AroundMe asks for something narrower and far more useful: your intent. What you like doing, and when you're free. Not a marketing profile; a statement of what you want to do. Matching uses that to compose a good group of 4-6 around a shared activity at a nearby meeting spot. It isn't assembling a page for you to show off or a segment to monetize. You're telling us what you want to do, not publishing who you are for anyone to evaluate.

What does your group actually see about you?

Only what you need to show up and meet safely, and deliberately not one field more. Minimum-necessary is the rule inside a matched group: at the invite, your groupmates see your first name and a short note on why the group fits, which is enough to recognize your group at the meeting spot and no more. Your surname, your photo, and your contact details aren't shown to the group at all; they stay held privately unless you and someone you've actually met both opt in later. The information you hand a stranger is the minimum that lets a real meetup happen, never a file they could keep, search, or use to find you afterward.

From verified to matched: where your information goes

1. 1
   You verify onceA one-time check at onboarding: a real, reachable person, not an anonymous burner. Done to establish trust, not to build a page.
2. 2
   It's held, not publishedVerification proves you to the platform. Nothing about you goes on display; there's no profile for anyone to find.
3. 3
   You state your intentWhat you like doing and when you're free. The narrow thing matching actually needs, not a dossier about you.
4. 4
   Matching composes a groupYour intent builds a group of 4-6 around a shared activity, not a segment to sell or a profile to rank.
5. 5
   Your group sees the minimumA first name and why the group fits. Enough to meet you safely at the meeting spot; nothing to look you up with.

Privacy is the default, not a setting you have to find

On most apps, privacy is a scavenger hunt: a dozen toggles buried in a menu, defaulted to "share," and it's on you to find and flip every one before you're covered. We inverted that. For the things that matter, private isn't a setting at all; it's the only starting state. There's no "make my profile public" switch to forget, because there's no public profile to switch on. You don't opt out of a feed. You were never in one. The principle underneath is that same minimum-necessary rule: collect what trust and matching genuinely require, expose as little as possible, and never build the sellable profile other apps depend on. Privacy you have to discover and defend isn't really privacy; it's a maze with your data as the prize. Making it the default is the whole point. It's a business-model choice too, and we'd rather be plain than over-promise: the model isn't built to turn you into an asset to be browsed or sold, so there's simply less about you to expose in the first place.

Private by default, in practice

• No public profile exists, so there is no make-it-public switch to forget
• No feed to opt out of: you were never in one
• Collects only what trust and matching genuinely require
• Exposes as little as possible to everyone else
• Not built to turn you into an asset to be browsed or sold

Where verified-but-private pays off

All of this stays abstract until you're standing at a meeting spot with a group of people you haven't met, and that's exactly where the split earns its keep. Because you're a first name and nothing else to anyone you haven't chosen, a stranger who gives you a bad feeling walks away with your first name and nothing to search, save, or text. Verification means everyone in the group is a real, accountable person; privacy means none of them left with a file on you. The two halves do different jobs, and they meet in person (how this identity layer sits inside the whole in-person safety design, from public meeting spots to groups never smaller than four, is its own post).

The balance, in one line

Verify enough to trust each other; expose as little as possible to everyone else. Being verified and being visible are two different things, and AroundMe keeps the first while refusing the second. You state what you like doing, not who you are for a feed. Your group learns the minimum it needs to meet you safely, and not a field more. Privacy is where you start, not a setting you hunt for. And it all cashes out at the meeting spot, where everyone is real and no one walks away holding more of you than a first name.